If that's the case, you brobably just have a corrupted screen file.

VFP stores much of it's information (including screen layouts) in a table. You can open a working SCX file as a table and browse the records to see how this works. If you crash while the table is open in VFP design mode, it can corrupt the screen table - the same way a table can be corrupted if you crash while altering records.

You can use table repair routines to repair the screen's table. I think you'll find a few table repair files in the downloads area, or you can use procedures outlined in the MSKB for VFP.

Let us know if you need more info...

>Michael -
>
>You're right on two counts (VFP 6 w/W2K), but the size of the .SCX hasn't gone to zero. In fact, it's a bit larger than the .SCX in the previous backup. This is why I'm hopeful for a recovery. As far as I know, I have all the Sevice Packs installed, but I'll check again anyway. Lastly, I haven't compiled the code yet, so I don't have an .EXE to work with.
>
>Thanks for your help.
>
>>I bet you're using vfp 6 and win2k - and that your scx file is 0 bytes. It was a known problem and if you patch your copy of VFP6 with the latest SP, you'll eliminate the problem.
>>
>>There is a way to restore the screen from your compiled exe or app here in the files section - if you need to.
>>
>>HTH