Access initially slow...

[Big2]

Hi Guys,

I've been searching for an answer for a long time, but i have a database with approx 100 forms, 100 tables (most linked to SQL Server) only a small proportion are front end tables, 50 or so queries, 20 or so modules.

Anyway the problem is, is that the database is slow, to open and to develop in, i have a decent system to develop on with a 3GHz CPU and 1 GHz RAM, but i dont get this problem with any of the other access databases i deal with.

It's kind of a lagging effect, then once it has been written into memory it's quicker... but why would that be different between the systems, as most the systems i deal with are fairly similar in size and in complexity.

For example when loading the logon screen, which is a simple unbound form, it seems to lag, there is 1 combo box which has a front end table as its row source, like 6 records. Then a username and password text boxes which are not bound to anything. Why should this be lagging? After like 2/3 secs its then ok, once ive logged in and then go back to this logon screen its fine, so i think it has something to do with memory.

Anyone else had anything similar happen to them and did they do anything to minimise this lagging effect?

Any ideas or comments are welcome,

Thanks.

 

[RuralGuy]

Have you done a Compact and Repair on the db? How about the undocumented /decompile option? Do you have Tools>Options>General Tab Name Autocorrect turned OFF? Failures caused by Name AutoCorrect Have you tried importing your db into a fresh new empty mdb? It takes about 60 seconds and might solve some problems.

 

[Big2]

Hi Rural guy, yes i've tried all those things, it's so annoying.

The only one left to try is importing everything into a new database file and seeing if that helps at all.

Thanks.

 

[Rabbie]

Have you tried defragmenting the drives the DB is stored on?

 

[Big2]

Not really because the frontend is held all over the place at different organisations ranging from 50 people using it to around 3/4 people using it so i wouldnt be able to request that drives are defragged for charms.

As another note, i also tried to do the subdatasheet stuff that i read on Microsofts website about access... in linked tables in design view, properties, setting the subdatasheet name to [None] instead of [Auto]. I wrote a routine that did this automatically on every table when the user has logged in, i'm still unsure if this has helped in any way. Just incase other people havent heard or have heard about this.

I will try the reimporting the objects into a different DB anyhow.

 

[John_W]

I had this problem and tried all the recommended fixes without effect till I got to the one I'd thought least likely to work - I moved the back-end closer to the root directory, so shortening the path to it. Also I renamed it to follow the 8.3 naming convention. I was amazed at the difference this made - it totally solved the problem.