DLookup taking too long

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I have designed many Access Client Server Applications before where I have
the 1 MDB file on the Hard Drive and the data MDB file on the server and have
the Tables Linked.

For this one client when I do the same when 1 user logs in they are fine.

But when anyone else does it takes them about 5 minutes for the Startup Form
to open. I researched & found out that for each Dlookup I have in my code it
is taking about 4 seconds to execute that 1 line of code. So that is why it
is taking so long for my Form to open. What is the cause for this ?

I have used Dlookup in many of my other applications & it works fine. And
also again it only slows down when after more than 1 user is logged in. And
the weird thing too is if 1 user is logged in and then when another tries if
the original user logs out, then they it will speed up again.

Thes are some of things I tried/looked into:
- They have a good server, 3ghz 1GB RAM
- IT person made sure users had full rights to folders
- I tried compacting and repairing
- I tried brand new Access files and copied over all objects.
- It is a small database, hardly any data in it.
- They have Access 2000, Service Pack 3
- Both the Client and Data mdb file on the Server have Defualt Open Mode set
to Shared

I am stummped. Does anyone have any advice ?

Any help would be greatly appreciated.

Thank you,
Jeff
 
In addition to the good information on the site Nikos posted, you told us at
least part of the problem without know it. This is the key sentence:
Both the Client and Data mdb file on the Server ...
The Client mdb should not be on the server. It should be on each user's
desktop. When you are doing heavy data access like a DLookup, you are
doubling the network traffic.
 
Back
Top