Message
From
14/10/2016 09:54:52
To
14/10/2016 09:36:15
Miscellaneous
Thread ID:
01641891
Message ID:
01641957
Views:
33
>>>When connecting to SQL server from a VFP 9 application where is the time out set? in VFP application or in SQL server?
>>> How do I determine and change it? (I want to force a time out so that I can test my code).
>>>
>>>TIA
>>
>>Could someone explain what should happen to the SQL Connection handle variable when the Idle Times fires? For example, if I have the the following code:
>>
>>What would happen to nSqlConnHandle if the application is idle for 1+ minutes?
>>Or what would be returned by the following SQL:
>>
>
>According to VFP documentation, the connection is closed at least 1 minute after it becomes idle (and up to 2 minutes). It is automatically reconnected when an ODBC operation requires it.
>
>Keep in mind that the VFP connection handle is not the same as the ODBC connection handle. A reconnected timed out connection changes its ODBC connection handle (most probably) but not its VFP connection handle (the one that is really important for you).
Thank you for the explanation. I was trying to emulate the case when customer gets the error [Microsoft][ODBC SQL Server Driver]Communication link failure. But it looks like I cannot do it easily.
>>> How do I determine and change it? (I want to force a time out so that I can test my code).
>>>
>>>TIA
>>
>>Could someone explain what should happen to the SQL Connection handle variable when the Idle Times fires? For example, if I have the the following code:
>>
>>SQLSETPROP( nSqlConnHandle,"IdleTimeout", 1)
>>>>>>What would happen to nSqlConnHandle if the application is idle for 1+ minutes?
>>Or what would be returned by the following SQL:
>>
>>SQLEXEC( nSqlConnHandle, "SELECT CAST(1 as bit) As Test", "crsTestConnection") >>>>?
>
>According to VFP documentation, the connection is closed at least 1 minute after it becomes idle (and up to 2 minutes). It is automatically reconnected when an ODBC operation requires it.
>
>Keep in mind that the VFP connection handle is not the same as the ODBC connection handle. A reconnected timed out connection changes its ODBC connection handle (most probably) but not its VFP connection handle (the one that is really important for you).
Thank you for the explanation. I was trying to emulate the case when customer gets the error [Microsoft][ODBC SQL Server Driver]Communication link failure. But it looks like I cannot do it easily.
"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
"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