XP Performance (or lack of it !)

[Ruppie]

Any ideas welcomed !

Having converted from Access version 2 to 97 and finally XP its really annoying to find its much slower in a multi-user environment.
I've read through loads of tips like ADO/DAO, Name autocorrect etc... which all help but how come its much slower at the 'core' e.g tables - just opening them in datasheet view. Has something gone wrong in converting? (record locking is set to 'Shared', 'No locks')

I have a single access database holding just the data sitting on a server.
Users have front end access databases loaded onto their PCs.
When one user is on the system its fine, more than one user it gets incredibly slower.

Simple tasks(which involve no forms or queries) like using linked table manager take 3 seconds(18 tables) for one user, but if another has a table open it goes up to a silly 95 seconds ! (this wasn't the case before XP)

Any clues greatly received.

 

[KenReay]

Hi

Have you looked in Microsoft Site Knowledge Base

I have found that the points there relating to persistent connections etc have fixed any performance problems withA97 to Xp conversions




Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[Ruppie]

Hi Ken

Thanks. I've been through the articles today and found a few refernces to persistent connections. Having made each of the front ends open up a connection to the back end when the first form loads, further processing (opening a datasheet, linked table manager) takes only a few seconds rather than minutes !
This is so fundamental. I'm not sure how my network manager is going to feel about all these open connections though.
This must affect anyone who splits there data.
Microsoft should put a health warning on the box !

Thanks R.