>>Please help me understand something:
>>
>>Say you check the SQL Connection (as you indicated) using SQLEXEC(Applic.SQLHandle, "") and then, if it fails,
>>you run the code that calls SQLIDLEDISCONNECT(). Here is how I understand it:
>>
>>
>>if SQLEXEC(Applic.SQLHandle, "") < 0
>> ASQLHANDLES(aSqlhndls)
>> FOR EACH nOdbchdbc IN aSqlhndls
>> =SQLIDLEDISCONNECT(nOdbchdbc)
>> ENDFOR
>>endif
>>
>>
>>After the above code, if I understand correctly, all SQL Server connections are disabled. So, the application need to reconnect to the SQL Server.
>
>Not exactly, rather than the connections being broken, they have been set to idle. When the connection is accessed again, whether that is though SQLEXEC(), a CA or Remote View, it will attempt to reconnect again. You can set the connect to never timeout, so it will wait indefinitely for the the connect to come back to live.
>
Thank you.
"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
