Front end is slow to open for second and subsequent users that con

  • Thread starter martin@hands on
  • Start date
M

martin@hands on

We have a split database with the front end on the local PC's and backend on
the server. For the first person to open the database the speed is fine but
the next user that opens the database has to wait about 20 seconds for the
database to open but once in everything seems fine. This is not a local
machine issue as if you open the database on first on the machine that was
slow it opens fine.
While this isnt a major issue I am being asked the question why!! and my
explanation has been that it is probably to do with the way in which the
database is setting up the locking for multiple uses to access at the same
time but what I would really like is an article or something I could read up
on that would explain exactly what is going on and maybe even a solution.
Thanks
Martin Briggs
 
B

Brian

martin@hands on said:
We have a split database with the front end on the local PC's and backend on
the server. For the first person to open the database the speed is fine but
the next user that opens the database has to wait about 20 seconds for the
database to open but once in everything seems fine. This is not a local
machine issue as if you open the database on first on the machine that was
slow it opens fine.
While this isnt a major issue I am being asked the question why!! and my
explanation has been that it is probably to do with the way in which the
database is setting up the locking for multiple uses to access at the same
time but what I would really like is an article or something I could read up
on that would explain exactly what is going on and maybe even a solution.
Thanks
Martin Briggs
Click to expand...

You don't say what version, but I have one application that I maintain in
Access 2002 where I used to encounter something similar. The startup form
is very large and complex, but I established through trial-and-error that
all I needed to do to "fix" it was to make a design change to the form (ANY
design change, however minor), and then it was OK again for some weeks or
months.

Eventually I was doing a bit of a review of all the client's databases, and
I noticed that this particular one still had the Name AutoCorrect nonsense
turned on. I turned it off, and the problem hasn't occurred since. I can
only conclude that when people made design changes elsewhere in the
application, the AutoCorrect was screwing up something in the startup form,
although the symptoms were exactly as you describe: fine for 1 user, very
slow to start for subsequent users, but fine once they were in.

A long shot maybe, but it might help.
 
M

martin@hands on

Thanks for the links I will review these as soon as I have an opportunity
Martin
 
M

martin@hands on

Hi Brian
The version is 2002 so I will try what you have said
Many thanks
Martin
 
Top