Access97 to AccessXP - Slow

[Rick]

I am having problems with response time since converting
from Access97 to Access2002. A report that takes 1 to 2
seconds with the Access97 container is now taking 10-15
seconds with the Access2002 container. Forms tied to
queries and tables are also a lot slower. I do have the
latest service packs installed but it doesn't seem to
help. Are there any other know issues or fixes?

thanks,
rick

 

[Stewart Tanner]

Rick XP is slower.

Is this a multiuser system or on a network?

There is a known problem with XP and record locking that causes performance
issues with linked tables.
Try opening a table or query and leaving it open all the time and see if
this helps.

 

[Guest]

It's a multiuser system on a network.

-----Original Message-----
Rick XP is slower.

Is this a multiuser system or on a network?

There is a known problem with XP and record locking that causes performance
issues with linked tables.
Try opening a table or query and leaving it open all the time and see if
this helps.




.

 

[Lizzy]

Is there another work around for working with a multiuser
database on the network? I too have noticed that mine run
slower. I can't leave a table or query open all the time.

Thanks!
Lizzy

 

[Stewart Tanner]

Lizzy,

there is no reason why you can not have a table open all the time. Just
create a 1 field, 1 record table in your backend, attach it to the FE and
open it hidden at application open and close it at application exit.

Stewart

 

[Guest]

if you're attaching to access containers make sure they
are all converted as well

 

[Albert D. Kallal]

There are two things to check:

As mentioned, FORCE a connection to stay opened (you don't mention if you
are testing this on the same computers and same network...if you are not,
then this issue may have NOTHING to do with the switch from 97 to 2002...you
can not assume that the performance change is due to a version change if you
are not using the same network and same os in the new case.

However, the first thing as others have mentioned is to FORCE the connection
open at all times. As mentioned, this can be any old table in the back end,
and you simply keep this connection open at all times (the OS in windows has
a very large security overhead now...and keeping the connection open usually
fixes this problem).

The other known issue is the use of functions in queries..and they can take
a performance hit in a2000 and beyond (you just move the functions to the
report...and "out" of the query in that case).

Hopefully the above connection trick fixes your problems...in my
experience, I get a as good performance as I did before when the above trick
works...