Prevent thrashing on ODBC connection to MS Access DB

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 ?
GuruWillyAsked:
Who is Participating?
 
SidFishesConnect With a Mentor Commented:
umm..ya..use sql server ;)

access/jet is oh so chatty and even when not a lots going on it has a lot to say...not sure there's a whole lot you can do...
0
 
GuruWillyAuthor Commented:
Reply to SidFishes from GuruWIlly:
Thanks for taking the time to comment, but it is not the answer I was hoping for.  Perhaps I am just out of luck and need to build in a disconect/reconnect control.  Problem is there are dozens of SELECT, UPDATE and INSERT Queries in various module, so I would have to sprinkle the new code "liberally".
0
 
SidFishesCommented:
well...keep the q open...there are some good people here and they may have more ideas...
0
All Courses

From novice to tech pro — start learning today.