>>There's still the option I suggested a while ago - give each connection a GUID when it's created and look for cases where the same connection is used by more than one hit?
>
>I have eliminated the fact that this could be caused by reserved words. I adjusted for most of the places where that applied. But, this was not the source of the problem. I ran a stress test tonight by launching four simultaneous processes against the server at every second. The result was a total disaster. I got about 26 errors per minute. It is always the same types of errors. Here is the list of the types of erros:
>
>Command contains unrecognized phrase/keyword.
>SQL: Column 'FieldNameHere' is not found.
>Function name is missing ).
>Index does not match the table. Delete the index...
>Variable 'FieldNameHere' is not found.
>Syntax error.

The common denominator seems to be that all the errors are from the OLEDB provider. If the errors stemmed from multiple page based objects using global functions then I'd expect to see some errors that were not VFPOLEDB related (but that's just an assumption - maybe your oApp has few functions that are not ADO related - and those may suffer corruption without error).

Anyway, see my reply to your subsequent post.
Regards,
Viv