VERY Slooowww Split Db

[Guest]

I recently moved an Access db from a Win98 share to our Win2K Domain
Controller DC).
Before the move it was no problem for multiple users (2-5) to access it at
the same time. Incedentally this is a LAN enviroment.

Once moved to the DC it could only be accessed by one (sometimes two) users
at once. I then found out it's recommended to split the db, so I have now
done so.

The db back end is on our DC and a copy of the front end locally on each
workstation. Now when opening forms that access tables it is extremly slow...
I mean what normally will come up before you take your finger of the mouse
button now takes up to 30 seconds. This is just with one user, if more then
one user is accessing the db it can take longer. The form contains two sub
forms (i.e. three tables being accessed) which desribe various options on a
product. There are a few different varaiations of the form depending on a
model but they all take a fairly long time to load up.

I have visited http://www.granite.ab.ca/access/performancefaq.htm that was
mentioned in a few other posts here and modified the tables from 'Auto' to
'none'. That helped a bit but there is still a major slow-down. There doesn't
seem to be a Persistent connection problem.

 

[Arvin Meyer [MVP]]

A couple of things to try:

1. Take a copy of the front-end and the back-end and import each into a
brand new clean (empty) database file. This will leave any trash behind. You
should immediately notice a size difference over a compacted database. I
typically see between a 10% and a 25% reduction.

2. Add a persistent connection. Just open a 1 record table and minimize it.

3. Check your network for CRC failures. If packets are dropping, it will
take much longer to do a transaction between the server and a workstation.
The chief candidate of suspicion will be a NIC in either the router or the
server, because they affect all machines.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Guest]

Thanks very much for the response.

I noticed after posting that it turned out I was having a persistance
problem... I noticed later that the lock file was appearing and disappearing.
I created a table with a single value that I used as a version number. I then
linked this to the main menu which never closes while the database is in use.
This has fixed the problem and things are running smooth again.

Whooohoo!