Chris,

I experienced something similar with another antivirus software. I was able to get the exact cause when observing events log on WindowsNT PC and the Antivirus Log file (matching the time when VFP blew up with events in question).
One of the problem was that while creating Excel files via automation there were password protected cells/sheets in Excel. And VFP blew up when antivirus tryed to scan the file. The problem went away as soon as I removed the password.

So try to observe the events log and log file to see the cause.

Another option was to stop the antivirus service from within the VFP application (see thread #815556 for details), but for obvious reason it was not chosen.


>After the last few worm viruses, some users have installed the latest McAfee updates. As a result, the vfp code to launch MSWord, open a doc, perform bookmark subs, ... now encounters errors. If McAfee is turned off, it works fine. And it worked fine prior to the latest McAfee update.
>
>The OEM version of McAfee does not appear to have the ability to skip certain folders or certain file extensions. Its ALL FILES or PROGRAMs. So i cant skip the worddocs.
>
>The worddocs that get opened are on the server while the users are on a workstation, in some cases its the same PC. Is it the delay caused by McAfee scanning the worddoc that is causing the vfp automation code to hurl? Has anyone implemented a delay mechanism after opening a worddoc but prior to issuing document manipulation commands?
>
>(will post the exact error when i get a copy of it)