I have read in many places it is a good idea to establish a persistent
connection when using a frontend file connected to a backend data file in a
multi-user environment. But I am confused about how this speeds things up.

Say I create a persistent connection on a menu form and then display another
form and open a connection to a table to populate that form. How are the
persistent connection form and the connection opened to populate the second
form related? Does the second connection use the persistent connection in
same way?

ABM <(E-Mail Removed)> wrote:

>I have read in many places it is a good idea to establish a persistent
>connection when using a frontend file connected to a backend data file in a
>multi-user environment. But I am confused about how this speeds things up.

The problem is opening and closing of the ldb file on the server.
This takes, relatively speaking, a huge amount of time.

>Say I create a persistent connection on a menu form and then display another
>form and open a connection to a table to populate that form. How are the
>persistent connection form and the connection opened to populate the second
>form related? Does the second connection use the persistent connection in
>same way?

Yes, the second, third and so on all do use the same connection to the
LDB file. How it works it terms of connections to the back end
MDB/ACCDB file I don't know. That's never been a problem I've had to
concern myself with.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/