>>>>Hi,
>>>>
>>>>Would it be correct to assume that when SQL Select from VFP against SQL Server fails and the error is
>>>>
>>>>

>>>>Communication link failure
>>>>

>>>>
>>>>that the problem was that the SQL Connection timed out by the time user executed the SQL Select? Or if not, what else would be causing this type of error?
>>>>
>>>>TIA
>>>
>>>No, when the timeout is occurred then the error will be:
>>>"Timeout occurred", something like this.
>>>
>>>Communication link failure usually means that you do not have connection with SQL Server anymore.
>>>Some LAN troubles or if the SQL Server is on WAN maybe Internet connection is lost?
>>
>>A follow up question, please. Do you think if - on determining that this is the error message - I add a code to try to establish the connection to the SQL Server again?
>
>Usually before we issue any SQL command we try something that SHOULD return result.
>(That is very well stolen from Andy Kramek and Marcia Akins)
>

>IF SQLEXEC(handler goes here, "SELECT @@IDENTITY","crsTest") < 0
>   ** What? we have no connection
>   ** do what ever you wish. Quit the Application
>   ** try to re-establish connection
>ENDIF
>

Another question (hopefully last in this thread). I found (by looking through many error email messages I received) is that my app sometimes gets error "Communication link failure" on Tableupdate(). The tableupdate() is called to update the SQL Server table via Cursor Adapter. Do you recommend to call the above code (testing connection) before the Tableupdate() too?