Andrew-
Good advice. Actually, I *always* recommend leaving a recordset on a linked table open for the duration of the app. Access will re-use the already established connection. If you keep opening / closing stuff without keeping the connection, Access has to go through the overhead of re-building the connection each time - a time-consuming task. It's more for performance reasons than just checking the connection.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Mar 11, 2014, at 10:02 AM, <yahoo@craven.de> <yahoo@craven.de> wrote:
Hi Hendra, you're welcome.
John has answered your Question more clearly than I might have. There is however one point I'd like to make, using ADO with a connection string specifying the OLEDB Provider is not going to influence the ODBC Connections. It is also important to note that you started the conversation linking in tables from an MDB source and this is neither ODBC nor OLEDB which alters the discussion (sorry to complicate things again...)
One common trick presented around here is to keep a connection open to a small table in each of your databases you link to. If you have problems with dropped connections then this trick is said to help but in any case you can do a query on this/these connections from time-to-time or prior to doing any real work.
Yours,
Andrew
__._,_.___
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (12) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar