Juan,

I'm at a loss, it must be something about NT4, but I see you've gone to SP4 there too. Do you have other machines you can test on? I now that until I went through the proper shutdown of the oWord object that I was winding up with several instances of Word, I only found this out when it complained of a lack of memory after about the tenth instantiation *bg*

Do you have VB? You might be able to use that Object Browser to better figure out what's going wrong. The VFP debugger is quite useless when it comes to ActiveX objects.

>Once again I've spent my whole day trying to figure out why my oWordDoc object gets instatiated but yet, it is corrupted.
>
>I downloaded and applied Office 97 SM2. That did not help! However, this is what I have narrowed my problems to:
>
>It appears that some OLE service gets corrupted in my OS. I understand that this can happen when you kill a process such as Word97 through the Task Manager (Ctrl-Alt-Delete). If that were the case when I reboot my system, this object's corruption should not happen again. Well, it does! But only from time to time even though I have executed the same identical sequence of events. I've taken snap shots of my OS's task/services (TLIST) after boot up, and after the VFP failure to instantiate the oWordDoc object. Everythings looks the same.
>
>My conclusion:
>
>None what's so ever! This is not consistent and therefore hard to explain. Although, obviously it is a corruption of an OS's OLE service.
>
>As I write to you, I've been able to get the intantiation of the Word.Document object to work and all of my 1000 bills are generating without a problem. Will I be able to do this again? Maybe, after I reboot 3 more times!
>
>I will keep you posted in my progress. In the meantime, thank you very much!