Thanks Jonathan. I just happened to have it on because I was converting some DB4 tables to/from VFP. It just took me a few hours to figure out what was going on :(. But thanks for the fix!

Beth

>If you look at program SCCTEXT.PRG in your FoxPro install directory (this is the program that creates a textual representation of Visual FoxPro binary files such as forms, reports and classes), there is a procedure named CreateVcxCursor. This procedure uses the function FSIZE() to get the size of a field. When SET COMPATIBLE is ON, FSIZE() gets the size of a file instead of a field. Therefore, it is trying to look for a file that has the name of that field.
>
>I would recommend not turning COMPATIBLE ON. It really affects how a lot of functions work. Look at the help for SET COMPATIBLE to see the commands that are affected. However, you may have code written that relies on COMPATIBLE being on, so you need to look at that. If you can't get away from having it ON, then you could look at modifying SCCTEXT.PRG to save the COMPATIBLE setting, turn it OFF around the FSIZE() calls, then restore it.
>