>In addition to what Mike said, here is something else to consider and it works great and I have noticed no issues with performance since I implemented it. However we have never had more than 60 users connected at a time.
>
>Added a property in the app mgr to store the connection handle. Then created an _access method for the connection handle property to test the connection. So each time the handle is used the connection is tested first. It basically checks to see if the connection is still good by returining a bit value from the server, this could, for example, be a value that the front end tests for to see if the administrator would like to boot everyone off the system. It uses a do while loop to continue trying, if the connection is lost, explaining to the user there is a connection problem and gives the user an option to cancel if desired or continue trying. If the .exe's run locally on the workstations instead of across the network, reboots of the server are ok and the app would continue to work when the re-boot is finished. I have also tested by adding additional code and can switch servers on the fly. With this method of course one would not want to do this unless they were doing
>transactional replication to another server. If only the idletimeout worked in sqlsetprop this could be used as well to timeout the connection to reduce the number of connections held in SQL due to inactive front-ends. Perhaps someday this will be fixed.

Ok, thanks for the input