Access Forms Run Slowly the First Time Opened Every Day

[Guest]

Hi - I have a question about a multi-user Microsoft Access database. The
back-end database file is stored on the file server. The front-end database
program is stored on the user's local computers. The first time that each
user opens up each form every day, it is very slow. The 2nd time and future
times, it runs fine. Has anyone encountered this before? Do you have any
ideas what may be causing this and how I can resolve this?

Thanks!

 

[Guest]

1. On the FE go to Tools, Options, General Tab and turn off Name Autocorrect
on all of your databases. IMHO it's a piece of do-do and the cause of many
problems. While there turn off Compact on Close if enabled. You'll be glad
that you did.

2. It could be a problem with not having a persistant connection. One trick
is to create a small table in the BE and a form for it in the FE. Open up
this form using an a macro named autoexec and hide it. Keeping the form open
keeps a connection open to the BE.

3. Access optimizes queries the first time that they are run. This usually
only takes less than a second though.

4. Try turning off the virus checker for testing purposes. If it's faster
try excluding scanning of mdb and md? files on user's PCs.

5. How far down the folder tree is the BE? The closer to the root or top,
the better. Also mapped drive letters work better for Access than UNCs.

6. If there are a LOT of records, sometimes it's faster to initially bring
up a subset of records in the form. Something like the last 10 days worth.

7. Subforms can also cause slowdowns.

 

[dbahooker]

Access MDB isn't adequate for real world use ANYWHERE for ANY REASON

grow some balls and learn SQL Server

Access Data Projects are the best environment ANYWHERE

-Aaron

 

[dbahooker]

specifically-- for performance and reliability reasons

i dont need to compact and repair my database

ROFL

 

[Tony Toews]

Hi - I have a question about a multi-user Microsoft Access database. The
back-end database file is stored on the file server. The front-end database
program is stored on the user's local computers. The first time that each
user opens up each form every day, it is very slow. The 2nd time and future
times, it runs fine. Has anyone encountered this before? Do you have any
ideas what may be causing this and how I can resolve this?

Just to clarify things here. Does this happen when waiting for the
first form to open up after the user has opened up the MDB/MDE? And
once the first form is opened it's fast enough then. Or does this
happen with each individual form the user opens up?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[susiedba]

Don't listen to Tony; he doesn't care about his end users

he makes them all wait 2 minutes when they open their apps.. waiting
for the MDB chipmunks to warm up lol

I mean seriously here..

You might be using the AUTO FE UPDATER; and it sits there and copies
tables and queries to frontends.. it could be a bunch of things.

In general, ADP is easier for administration / maintenance than MDB--
because you're not always copying queries and tables.

I dont make my end users wait 2 minutes to open my app.
Do you know why?

Because I keep all my queries and tables IN ONE PLACE- on A DATABASE
SERVER; which is where they belong

-Susie
ADP Nationalist

 

[Tony Toews]

Don't listen to Tony; he doesn't care about his end users

Hmm, sure looks like a posting by Aaron K*empf.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[dbahooker]

maybe they sound like Aaron BECAUSE AARON IS RIGHT