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.

>I've just run across something very weird and am wondering if anyone else has seen it. I have a project under VSS control. If I have SET COMPATIBLE ON and try to check in a vcx I get an error - 'Error#1 in createvcxcursor (11); File does not exist.' If I then SET COMPATIBLE OFF, I can check the class in as usual. It doesn't seem to happen with any other files.
>
>I'm running VFP 6.0 SP4.
>
>Thankfully, I'm not really married to SET COMPATIBLE ON - just thought I'd stick this out here in case anyone else gets this error and wonders why.
>
>Beth