Since I have a zip drive on my PC, I back up projects to zip disk as checkpoints during the day. I let Win2K eject the disk via explorer so it knows to flush cache. Once that zip disk is out of the drive and in the pouch, and then Win2K crashes, it's pretty doubtful that the abnormal termination will affect what's on the zip disk.

I've never actually experienced this corruption problem, but I'm using Win2K Server and I've only had one crash in 6 months of use (and that was caused by a beta version of WebDrive from Riverfront Software [a great product, I might add]).

>>>Guy,
>>>A safe workaround is to put any forms or reports that you have worked on into a Winzip archive, then extract them, somehow this then makes em behave like normal.
>>>Its an extra step that is worth while until the service pack or patch, but it has been a while since "they" have known about this, so there is probably no easy answer other than to work around it.
>>>HTH
>>>regards.
>>
>>Do you mean just zip my project with a tool like WinZip? If I do that, are you suggesting that I unzip it for the next session of work? Or do I just use the original project files because zipping it earlier forced everything to be written to disk properly?
>>
>>Guy
>Hi Guy,
>No, Zipping does nothing special, other than giving you an archive, BUT when you Unip, somehow the file is then safe and closed like you have grown up with. So any shut downs or crashes leaves your Forms and Reports OK, not corrupted like the ones that have been modified and which you thought had been safe for hours or days, so just be in the habit of zipping your forms as soon as you exit from modifying them.
>I'll bet they have a fix in the pipeline by now, and that it turns out that we were just a few unlucky ones with the "wrong" combination of "new" hard drives.
>
>regards