Performance Problems

[CTD]

Good performance on NT box and Access 97 (front and back
ends)
Poor performanc on XP box with converted 2003 front end,
03 or 97 back end.

Server holding back end has been tested with both 2000 and
2003 with no difference.

DAO code running very quickly on both

Connection to back end, specifically updating/appending
tables running very slowly (up to 300% slower)

When running both front and back end locally on xp box,
speed is also slower but acceptable.

Any suggestions?

 

[Roger Carlson]

Several things to try:

1) remove any Sub Datasheet Name from the tables.
see here: http://support.microsoft.com/?kbid=261000
2) turn off Name Auto Correct (Tools>Options>General Tab)
see: http://support.microsoft.com/?kbid=200600
3) have a hidden form that is bound to a very small table open at startup
4) delete and recreate table links
5) make sure you have Jet 4.0 SP 6 installed. (not SP 4 or 5)
6) make sure virus scanning software checks only local drives

 

[Tony Toews]

Good performance on NT box and Access 97 (front and back
ends)
Poor performanc on XP box with converted 2003 front end,
03 or 97 back end.

Server holding back end has been tested with both 2000 and
2003 with no difference.

DAO code running very quickly on both

Connection to back end, specifically updating/appending
tables running very slowly (up to 300% slower)

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

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

 

[CTD]

Thanks very much for the reply. All of the steps you have
outlined below were taken prior to the performance
problems. In addition to those steps, I've also unchecked
error checking. Two additional things to note:

1. It has been suggested to us that starting with Access
2000, unicode was introduced which could be adding to the
amount of data being passed between front and back end?

2. We did a packet trace while running a specific process
on both a NT/97 (front and back) and converted XP/2003. In
the NT/97 configuration 12 megs is being passed between
client and server. On the XP/2003 configuration 75 megs
were being passed. Back end server remained constant, all
current service packs have been applied. Could this be due
to #1 above and/or some kind of data type conversion?

I should also note that we are are a platinum support
customer and have yet been unable to resolve this problem
with Microsoft.

Any help is again GREATLY appreciated!!!