>We have an application installed at several hundred sites on everything from Win-95 to XP. Years ago (under either 6.0 or 5.0) we used to see a lot of problems with invalid FOXUSER.DBF files which, once deleted, worked fine.
>
>We have just upgraded our EXE to 7.0 SP1 and are now seeing a lot of FOXUSER.DBF corruptions again. We build a CONFIG.FPW into the program, which does point to a valid directory.
>
>Another difference (besides upgrading to VFP 7.0) with our latest release is that our EXE will sometimes launch another VFP EXE and utilize DDE to communicate with it.
>
>Does anyone have a workaround for this? Has anyone else seen this with VFP 7.0?


Jack, does your application actually require the FOXUSER.DBF at all? If not then use SET RESOURCE to just switch it off and not use it at all. Alternatively in your CONFIG.FPW have a RESOURCE=OFF statement.

Having said that, there is no reason that a normally running VFP exe/app should corrupt the FOXUSER.DBF file. Something else is corrupting the file such as abnormal program termination.