I have an application I developed that is deployed in dozens of customer sites. The application is designed to be "SQL '92" compliant and uses ODBC connection (at MDAC RTM V2.5 or later) to either SQL Server or to a Microsoft Access database file (using the ODBC Jet DB engine). The application is written in MS VB 6 and uses both RDO and ADO.
When connected to an MS Access database through the ODBC driver and on a network (MS TCP/IP protocol), there is excessive "thrashing" over the network even when the application is idle. I maintain a common connection object - leaving it connected in the best interest of performance - avoiding a re-connect for new transactions.
Is there a way to prevent the thrashing without a disconnect ?