Hi Yousef,

I've run into this a few times..
In my situation it has always been due to a server failure causing corrupted data in the DBF header or fields:

1. I have found an invalid field type in the header (instead of C/N/D/M etc, there was a non-printable character)
In this case you could manually edit the file and replace the errant byte with the proper value - this has worked for me).
2. A field contained a control character, typically an EOF marker.

The error is VFP's way of saying "I don't know how to handle this, so I'm shutting down".

If you do not have a recent backup, you could scan the fields for non valid values and remove them.

I think that the corruption you refer to has happened prior to the error message and is not the result of exiting after getting the error message.

Hope this helps



>We have a VFP 5.0 app that runs on a file server. Several instances of the .exe may be running at the same time each accessing a separate VFP database, processing some files, and updating the database.
>We have recently encountered an "Internal Consistency Error" message box popping up while the application is running. All we can do at this point is to click the OK button on the message box after which the application shuts down. This results in some cdx files getting corrupted (some tags actually get wiped out of the cdx!) and the database becoming invalid.
>Any ideas on what could cause this are greatly appreciated.