I've read somewhere that it's a good idea to close the connection when you're done with it and reopen it when you need it again

If you have a class, it could close the connection after each request - but then it may close/open too many times if you have successive operations
I think that IdleTimeOut does that for you.

Kind of algorithm saying that : if I haven't done anything in the last minute, the odds are that I may not need the connection in the next few minutes or so. In that case I'll close it and reopen it when the next request comes

You, using the connection, may know better and be able to tell it when to close (and when not to). That is more granular.
When you use IdleTimeOut, you don't have to think




>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
>>