>Doug-
>FWIW, I see the same behavior. I don't have a suggestion, yet.
>
>>Anyone have any problems opening a Word document from an OLE Bound Control into Word 2000?

This was a bug with all previous versions of Word and VFP - it's a VFP problem (it doesn't happen in VB [ouch!] nor Access). MS list it as by design so I doubt it will ever be fixed: pester the VFP team to fix it in VFP 7.

(I always get on my high horse about this one).

If you link to the file there is no problem, although then, of course, you can't centrally store your files.

I store the file(s) in binary memo fields, save to (local) disk when the user wants it, launch Word against the file, wait for the file to be unlocked and then reload it: DANGER WILL ROBINSON!! Word sometimes unlocks the file (just for fun) when autosaving it, so you'll need to check that it's still locked once you think it is locked, if that makes any sense.

To be honest, this seems to be the only way you can detect that Word has closed the file: even if you embed it there is no equivalent of the Access OLE_UPDATED(code) function, which would let you know whether it had been saved, closed, etc., which might be important for your application.