Word 2002 Automation / Windows 2000 SP4

  • Thread starter Thread starter Justin Hinerman
  • Start date Start date
J

Justin Hinerman

I have a program that uses word automation to open word,
open a document, print a selected document, and closes
word. Before I installed SP4 for Windows 2000, the
following code worked flawlessly:

Dim objWord
Set objWord = CreateObject("Word.Application")

objWord.Documents.Open strFileName, false, true, false
objWord.Application.DisplayAlerts = 0
objWord.Application.ActivePrinter = "HP_printer"
objWord.Application.PrintOut true,,0,,,,,1

objWord.ActiveDocument.Close false

objWord.Quit
Set objWord = Nothing

In DCOMCNFG, I have Word set to run under the identity of
Administrator, in order to have access to all network
resources.
This was on Windows 2000 SP3.

Since I installed SP4 for Windows 2000, this Word
automation does not work. Whenever I call the line in the
above code 'objWord.documents.open ... " the program
freezes and the word process hangs. The same happens if I
try to run this code in a macro in Word VBA. Whenever it
gets to the line that opens a file, and the file is on a
shared network resource, it hangs. Again, this worked
prior to SP4. Is there a new security setting in SP4?

I have tried uninstalling Office, restarting, and
reinstalling Office, but that did not work.

Any help would be GREATLY appreciated. Thanks!
 
Justin Hinerman said:
Again, this worked
prior to SP4. Is there a new security setting in SP4?

I have tried uninstalling Office, restarting, and
reinstalling Office, but that did not work.

Any help would be GREATLY appreciated. Thanks!
Click to expand...


There actually IS a new setting for SP4. It had been giving me problems similar to yours until I recalibrated the IDD software to run on an expanded datastream. I don't believe this is your problem, however. It appears to me that you need to reintegrate your administrator packages with the WD40CFG registry.
If this does not work then you have encountered a glitch that is common for pirated OS packages.
If this is the case, I don't know what to suggest. Buy the software? That would be a good start.
Seriously though. Reintegrating with WD40CFG is the only action I can suggest based on experience.

Good luck and Bon Voyage!
-Sniggitz-
 
Back
Top