Hi James,

Thank you for your input. I think your suggestion of restarting the DB service makes sense and is easy to do for testing. Great idea!

>Hi Dmitry,
>
>The only way that I could simulate a server connection timeout was to either restart the DB service or go into the DB management tools and disconnect my user. Restarting the service is the easiest if you are using a test DB that only you control.
>
>This paragraph will not work with remote views (I think). I created my own connection class a few years ago and what I found was the easiest way was to test the connection on each error that I get. If the test fails then I will try and reconnect and run the query again if the reconnect works. Otherwise, I just handle the error. I could probably test for the appropriate error number so I only test the connection when I get a disconnect but I was always afraid that there would be another error that could be cured by a reconnect and I don't think the overhead is that much.
>
>
>
>>It does seem like this is how it works. And if so, this is fine with me. But I am just wondering, what is the purpose of setting the idletime out? That is, what does the application achieve by that?
>>
>>And as always, thank you for your input.
>>
>>>The way I understand it is the vfp will disconnect after the IdleTimeOut, ie closing the connection
>>> But after that, if you to any operation that is using the handle, it automatically reconnects
>>>