I would like to use a client-side connection pool with my VB.NET application. MS Access is used for the database. One user (a V.P.) is running the applicationvia Parallels on a Mac, which makes any delay much more noticeable.
However, the interwebs are a little sparse on implementation information for OLE DB connection pooling.As far as I can tell, the key here is to enable connection pooling with ODBC 3.0, via SQLSetEnvAttr.
Keeping a consistent connection string is no problem - It is stored in My.Settings, and is the same for each person.
But what is the actual code? At what point in the program do I call it? How do I close the pooled connections as the program exits?
The most helpful resource I have found is http://support.microsoft.com/kb/169470, but even that is vague.
However, the interwebs are a little sparse on implementation information for OLE DB connection pooling.As far as I can tell, the key here is to enable connection pooling with ODBC 3.0, via SQLSetEnvAttr.
Keeping a consistent connection string is no problem - It is stored in My.Settings, and is the same for each person.
But what is the actual code? At what point in the program do I call it? How do I close the pooled connections as the program exits?
The most helpful resource I have found is http://support.microsoft.com/kb/169470, but even that is vague.