Windows 2000 vs Windows XP query time?

[Hondy]

Hi

I have an Access database that runs fine on a Windows 2000 PC but its really slow on Windows XP PC's.

The Windows XP PCs show a max CPU usage on about 9% where as the Windows 2000 PC's show some real useage of the CPU (around 70%)

Does anyone have any clues as to why the XP PC's dont run as well as the 2000 PC's? It's not a network issue and I have tested this on a number of PC's

It seems as though the CPU on the XP PCs is not being utilised very well, the system idle process is top of the CPU usage then Access.

Thanks!

 

[genomon]

We run both with ease. Concentrate on the database and connections, especially if you are using backend tables on a network. How about some details? Split mdb, remote db, Access version, what the database does, etc.?

"Don't be irreplaceable. If you can't be replaced, you can't be promoted."

 

[Hondy]

The version of Access is 2002 form Office XP Pro, the database is SQL 2005 and holds fairly static data which is retrieved via pass through queries and presents to the access form using ODBC.

It seems to have happened since we upgraded to SQL 2005 but as I said it works fine on Windows 2000 clients so the only thing in common is XP and SQL2005 together.

Any clues?

 

[genomon]

Some things to look at:
Conflicts with antivirus software on the XP machine.
XP DSN set up differently for the linked SQL tables.
If you are using pass-through queries in VBA, use ADO connection objects instead of DAO, and make sure the priority of project library references is set correctly.

"Don't be irreplaceable. If you can't be replaced, you can't be promoted."

 

[Hondy]

thanks genomon, how do I set the library references priority?

 

[genomon]

In the VBA IDE click on tools|references. The ADO reference needs to listed above the DAO reference. There are up/down arrows to right of the list box.

"Don't be irreplaceable. If you can't be replaced, you can't be promoted."