>>So, if I understand you correctly, this is a problem with the VFP cursor, not SQL Server per se, right?
>
>Yes. In general, if you see a VFP error the error is on VFP. For ActiveX, SQL servers (not: MS SQL SERVER. Any) or the like VFP raises special errors, where you need to ask the server for extended error message.
>If you got a C0..05, the code that represents VFP fails.
>If you got a bluescreen, first guess is your hardware.
Nobody complained and nobody sent me an error screen. The error was recorded in the error log. The error was the result of the TableUpdate(). It returned negative.
Then I got the error information using AERROR(aErrorInfo). My problem is that I did not capture that ODBC error (aErrorInfo[1,5]). This would tell me (the error log if this was a VFP or ODBC error). I will add this error number to my error log.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
