![]() |
#1
|
|||
|
|||
![]()
A little background -- I've automated a few processes with our mainframe, and have a program that ftp's reports and creates *.doc files. This has been working very well for the past few years, just recently started receiving the above error. After some research, it looks like a security patch from MS is the culprit.
http://support.microsoft.com/default...b;EN-US;973904 However, the steps to fix it don't apply--since it requires modifying the registry to allow WordPad to open the files. I'm basically using MS Word 2007 to open the *.doc file, not WordPad. It's worked great up until that security update. Anyone have any suggestions? Thanks in advance ![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
![]() |
student09 | Outlook | 1 | 11-12-2010 06:26 PM |
slow to start word | kn0wm0r3 | Word | 0 | 09-27-2009 10:40 AM |
Outlook Wont Start | w6000 | Outlook | 0 | 09-02-2009 07:13 AM |
slow start | kevb | Office | 1 | 08-15-2008 12:13 PM |
Word Crashes immediatly on start up | Brett | Word | 2 | 05-04-2008 07:49 AM |