Performance differences with Access 2003

[Nigel G]

I've just converted a long standing application from Access 97 to Access
2003 and on startup it is much slower than Access 97. The startup process
checks for the integrity of required linked tables and then if all are
present and the links are OK shows the user the rest of the application.

None of the code here has changed but a system running at an acceptable
speed before (MSA97) is now almost unworkably slow. PCs are the same,
network the same. When BE databases are moved to local PC system seems to
respond fine, so there's obviously some issue with checking the remote
links.

Are there any areas I should be looking (coding? network settings?), or
other known issues here?

TIA
Nigel

 

[Albert D.Kallal]

re-linking at startup is generally long process, and not one I would do each
time

However, the solution is to link the first table, and then OPEN it to a
recordset.

This also means that to keep the performance of the database, you will want
to open up a persistent connecting in your startup code.

If don't do the above, then that performance issue will crop up in other
areas also....

It is known issue, and I even seen this problem in a97

Talk a good read of the following performance faq, so you can elimoonate
some other iusses

http://www.granite.ab.ca/access/performancefaq.htm

 

[Nigel G]

re-linking at startup is generally long process, and not one I would do each
time

Talk a good read of the following performance faq, so you can elimoonate
some other iusses

http://www.granite.ab.ca/access/performancefaq.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal

Albert

Thanks for the pointer to the performance tips - some useul information.

I think some other issue exists however as the system worked fine as 97 and
the only change has been the conversion to 2003.

The linking process I mentioned only re-links if a link is broken (tested by
attempting to read the table). Without the links the app. will not function
so a check is made on startup. This has not changed in the 2003 version

nigel

 

[Chris Mills]

Linking, if an issue, is only a time problem at startup. Do you have general
run-down performance?

When I converted from A2.0 to A97, I had major performance problems such that
I had to revisit all indexes, take all shortcut actions I could, things like
that. Same again for A2000. Avoided A2003.

You complain only of a startup problem, which is avoided by removing the
network. Therefore (thinks...) could these have something to do with it?

Since A2000, there is sometimes an unsolved problem whereby expressions
(rather than calling code) in things like object events, can cause a hang for
10~20secs or so. Independent of processor speed. Are you suffering a "complete
hang-up" for a timescale like this? When you do something particular? It's the
main reason A2000 made me bald, but only where I scratch my head.
(One fix to reduce this problem, but not eliminate it, is to break up code
modules into smaller code modules. If you don't suffer this particular
problem, which is obvious when you get it, like bird flu, good for you!)

Chris

 

[Albert D.Kallal]

I think some other issue exists however as the system worked fine as 97
and
the only change has been the conversion to 2003.

No, the issue is known, and has been widely experienced for 3 versions.

I not 100% sure of the exactly details, but has to do with interaction of
the security file system, and the fact that for each table link, the ldb
file is created, and then tried to lock.

We are not talking about 1 version here, but for that last 3 versions.

The linking process I mentioned only re-links if a link is broken (tested
by
attempting to read the table). Without the links the app. will not
function
so a check is made on startup. This has not changed in the 2003 version

Yes, but the above changes little here. If you are re-linking all tables, or
looping through them to "test" the link, then you will experience the delay.

My answer to you is to simply try opening up a table to a reocrdset, and
then run your code. - note the performance change....

And, if you are re-linking, then obviously you can't open up a table until
you got at least one table linked.....

 

[heying]

I've just converted a long standing application from Access 97 to Access
2003 and on startup it is much slower than Access 97. The startup process
checks for the integrity of required linked tables and then if all are
present and the links are OK shows the user the rest of the application.

None of the code here has changed but a system running at an acceptable
speed before (MSA97) is now almost unworkably slow. PCs are the same,
network the same. When BE databases are moved to local PC system seems to
respond fine, so there's obviously some issue with checking the remote
links.

Are there any areas I should be looking (coding? network settings?), or
other known issues here?

TIA
Nigel