Access Xp Second user slow connecting to the back end db?

[Ramzi]

Hi All;

I have this situation using M.S. Access Xp on a split database, and I am
facing a slow performance when more than one user connects to the DB.

-The first user connects to the database and run the initialization commands
(a number of Append SQL statements and some DCount and DLookup) within two
to four seconds only.

- The second user and the other users connect and run the same procedure
within 40 to 50 seconds??



The settings are as follows:

-The front end MDE is located and run from each PC connected to the data
(Back end) on the server. (\\Server\Folder\Data.Mdb the path is not so
long).

- All tables Subdatasheet Name property is set to [None].

- Tables>Options>General>Track name auto correct is set to OFF.

- The antivirus program is disabled.

- I make Decompile for the program and data frequently.

- My service pack is SP3 and updated from the internet automatically to the
latest.

- I am using windows Xp on all PCs.

- I have Access 97 installed on the computer and runs from different
directory.

- I am using Ethernet card 100.



Please , Please if any one can help me in this case it will be highly
appreciated, because I am having a hart time with my customers complaining
from slow performance.



Truly yours

Ramzi

 

[Ken Snell \(MVP\)]

You need to use a persistent connection to the backend database to improve
this performance. See this article at Tony Toews' website:
http://www.granite.ab.ca/access/performanceldblocking.htm

Post back if you have questions about this.

 

[Albert D. Kallal]

I would check the following list:

http://www.granite.ab.ca/access/performancefaq.htm

After you check the above list, in your startup form, setup a persistent
connection. A persistent connection usually solves your type of issue
performance wise...

You can setup a persistent connection by declaring a GLOBAL recordset var,
and then open a table to that global recordset set. This needs to happen
before any of your other code runs. So, pick any table from the back end (it
don't matter which one), and **keep** it open at all times.

If you have a routine that returns the path to your backend, then you can
also open the database to a database var (this just means you don't have to
pick a particular table and open it).

 

[david]

A network optimisation in Windows allows the first user to act as if
they have exclusive access to the database, which allows the network
to cache all actions locally.

Once you have a second user, you have to treat the file as a shared
resource, which is much slower.

To get your performance back, you have to optimise your application
to avoid disconnecting and re-connecting to the database.

(david)