>>Try the following : copied from a Word macro.

With Options
>>   .AllowFastSave = False
>>   .BackgroundSave = False

>>
>While the FastSave option does appear to save time in large or complex documents, the Help file indicates that it's not good practice to always save with FastSaves (it saves a list of changes separately from your stored work). Allowing background saves won't free up the file by the OS any quicker than foreground saves -- this is needed because the ERASE command is failing.
>
>IAC, I tried these, and, on my machine, they didn't help. In my other message to David, I think the timing issue may resolve itself when doing an explicit Document.Close(), followed by an Application.Quit().
> - della

---

I'm having a hard time reconcilling ".BackgroundSave = False" and "Allowing background saves".

BackGroundSaves is true by default - this default behaviour allows control to return to VFP before the save is complete and causes the concurrency problem. Set it to false, do the save, close the file, close word, this should not be a big deal.