>Ever since I have moved to Window 2000, if the O/S crashes - yeah it does even though its not supposed to - for any reason, any open VFP form, and any form whihc HAS BEEN open since the last reboot is trashed. When I look at the SCT file with a text editor, it looks like the file has been overwritten with an single ASCII character. (I haven't looked at it with a heax editer to see which character)
>
>When I first put Win2K on a machine, it was under FAT32, and if I bypassed scan disk, it was usually possible to make a backup, although sometimes thw files were crosslinked any unusable. since I installed on a clean drive with NTFS, a crash means a tolal loss for every thing since the last backup.
>
>BTW, I have installed Win2K - Retail version, and VS6 SP3 (now SP4) on 2 different machines, with diffferent hard drives, vidiel card, CPO, and MB chip set, with the same results. That should eliminate the hardware as a cause.
>
>Another developer tested his machine, by turning off the power with forms open for editing, and did not suffer corruption. (I have had this occur when the power switch on the UPS was bumped to the off position and have tested this way myself. My files were destroyed in this scenario.)
>
>It seems I must have something set incorrectly in VFP or Win2K. Has anyone else seen this and found a solution.

Too anyone who has experienced this pernicios bug:

I spoke with a couple of Test Engineers at the VFP DevCon in Miami a week or so ago, and one of them was able to duplicate it on a machine in the Lab at DevCon. He assured me he would find and fix it when returned to Redmond. Int he mean time I recieved a reuest formt he Tech Support engineer handling my open incident, requesting a test. The steps he asked for are as follows:

1.) reboot box cold
2.) open FoxPro... open and edit 1 or 2 files
3.) close FoxPro... let sit for a few minutes
4.) run NTFILEMON.EXE from http://www.sysinternals.com for a minute or two. save output to file
5.) hard crash the box, reboot and check for corruption
6.) if corruption occurred, zip the filemon log and ftp it to me. We can then open the log in excel and check the accesses to that file.

If ayone has time to run this test, and e-,ails me the test file, I will pass it on to Tech support.

Steve Buttress, MCP
ProMatrix MVP - Life
ProSysPlus Developer