K
kwilder
Like many other developers I've written a VB.Net app to automate Word
2000. The app does work on my machine, but when I create an
Installation package and install it on other users machines, it may
work, but most of the time it doesn't. I followed the instructions on
how to install the Office XP PIA's, but I don't think it installed
correctly.
Here's why:
-- When I set a reference, the associated DLL's are in my applications
/bin folder, not the GAC
-- When I use the Imports statement such as "Import Word" that's all I
can do. I can't do this:
Imports Word = Microsoft.Office.Interop.Word
There is no Microsoft.Office namespace.
Does anyone have any ideas why this isn't working?
Here's my system configuration:
OS: Windows Server 2003 (used as a development machine, not to be used
as an Office server!)
Office Version: 2000
Visual Studio 2003
So all of this means that if I try to run the example listed here,
http://support.microsoft.com/default.aspx?scid=kb;en-us;316383, is
doesn't work. If fails on the CreateObject("Word.Application") line.
Any help would be appreicated.
Thanks,
King Wilder
2000. The app does work on my machine, but when I create an
Installation package and install it on other users machines, it may
work, but most of the time it doesn't. I followed the instructions on
how to install the Office XP PIA's, but I don't think it installed
correctly.
Here's why:
-- When I set a reference, the associated DLL's are in my applications
/bin folder, not the GAC
-- When I use the Imports statement such as "Import Word" that's all I
can do. I can't do this:
Imports Word = Microsoft.Office.Interop.Word
There is no Microsoft.Office namespace.
Does anyone have any ideas why this isn't working?
Here's my system configuration:
OS: Windows Server 2003 (used as a development machine, not to be used
as an Office server!)
Office Version: 2000
Visual Studio 2003
So all of this means that if I try to run the example listed here,
http://support.microsoft.com/default.aspx?scid=kb;en-us;316383, is
doesn't work. If fails on the CreateObject("Word.Application") line.
Any help would be appreicated.
Thanks,
King Wilder