Persistent Connection

  • Thread starter Thread starter Peter Hibbs
  • Start date Start date
I wouldn't call it an actual bug (there's going to be overhead involved in
opening the connection), and I'd say it's just as good an idea for other
versions of Access.
 
Yes, it does apply to every version where you may experience a performance
problem. I think that the issue is not with the database as much as with the
network connection to that database. The one time that I ran into that
problem was when some users were located in another building over 100 yards
away from the main building. If packets needed to be resent, it killed
performance, so keeping an open connection reduced network slowdowns.
 
Douglas said:
I wouldn't call it an actual bug (there's going to be overhead involved in
opening the connection), and I'd say it's just as good an idea for other
versions of Access.

What do you recommend as the best way to establish a persistent
connection in Access 2007?

James A. Fortune
(e-mail address removed)
 
James A. Fortune said:
What do you recommend as the best way to establish a persistent connection
in Access 2007?

I'd say the same way as in previous versions.
 
Douglas said:
I'd say the same way as in previous versions.

Do you mean either using a bound form or opening a recordset?

James A. Fortune
(e-mail address removed)
 
Peter Hibbs said:
Tony Toews says that on Access 2000 it is advisable to keep a
persistent connection open to the BE to improve performance on a
network set up. See this site for more info :-
http://www.granite.ab.ca/access/performanceldblocking.htm

The question is - does this also apply to versions later than A2000 or
have Microsoft now fixed the bug (if it is a bug).

It's not really a bug but more of a feature. And the problem involves
the locking and unlocking of the ldb file. So yes this applies to
all versions of Access unless you're running another database engine
such as SQL Server.

Tony
 
OK, thanks Tony.

Peter Hibbs.

It's not really a bug but more of a feature. And the problem involves
the locking and unlocking of the ldb file. So yes this applies to
all versions of Access unless you're running another database engine
such as SQL Server.

Tony
 
Back
Top