Type Mismatch
What did you do?
Did you use the first declaration and have a reference to Word 11?
Or did you use the late binding and discard any reference?
==========
In the first case, I'd try reregistering xl2003.
Close Excel and
Windows Start Button|Run
excel /unregserver
then
Windows Start Button|Run
excel /regserver
The /unregserver & /regserver stuff resets some of the windows registry to
excel's factory defaults.
Orion Cochrane wrote:
I did use what you said. It worked for a year on my home computer. It worked
on my laptop here too. The only unusual thing I did between a couple of days
ago and yesterday was uninstall Office 2007. It still works on the home
computer. Do I have to reinstall Office 2003 to get it to work? My other
reports work, as they are based in Excel.
--
I am running on Office 2003, unless otherwise stated.
"Dave Peterson" wrote:
How did you declare appWD?
Did you use:
dim appWd as Word.application
or if you unchecked that reference (you may have to modify other portions of
your code):
dim appWD as Object
Orion Cochrane wrote:
I had a 60-day Office Home & Student 2007 installed on my laptop, and I
installed Office Standard 2003. Running 2 versions of Office gave me problems
when I clicked on an Office 2007 program (any file I opened started in 07,
not 03). So I uninstalled the Trial version, and am now running on 03. I have
an application that generates a report in Word, and now it gives me as Type
Mismatch error on the following line:
Set appWD = CreateObject ("Word.Application")
It worked prior to uninstalling Office 2007. I have a reference to the Word
11.0 Object Model, so what's the problem?
--
I am running on Office 2003, unless otherwise stated.
--
Dave Peterson
--
Dave Peterson
|