dbTalk Databases Forums  

Bad performance after changing to Access 2003

comp.database.ms-access comp.database.ms-access


Discuss Bad performance after changing to Access 2003 in the comp.database.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Beat Scheidiger
 
Posts: n/a

Default Bad performance after changing to Access 2003 - 09-02-2004 , 01:36 AM






So far we were using Access 97.

We query data in a VBA procedure. This procedure puts together a SQL
string and opens a recordset with it.
We use only DAO libary.

Now we changed from NT opereating system to XP.
After converting the database to Access 2003 this query is about 10 to
20 times slower.

Can somebody tell me a raeson for that? Thanks a lot.

Beat Scheidiger

Reply With Quote
  #2  
Old   
Ron
 
Posts: n/a

Default Re: Bad performance after changing to Access 2003 - 09-02-2004 , 09:52 AM






I'd pop it back into the 97 and try the 97 version on your XP system. Could
be the difference between NT and XP. Gotta find out which is broken
first...

hang in
ron

"Beat Scheidiger" <beat.scheidiger (AT) swisscom (DOT) com> wrote

Quote:
So far we were using Access 97.

We query data in a VBA procedure. This procedure puts together a SQL
string and opens a recordset with it.
We use only DAO libary.

Now we changed from NT opereating system to XP.
After converting the database to Access 2003 this query is about 10 to
20 times slower.

Can somebody tell me a raeson for that? Thanks a lot.

Beat Scheidiger



Reply With Quote
  #3  
Old   
Ron
 
Posts: n/a

Default Re: Bad performance after changing to Access 2003 - 09-02-2004 , 10:05 AM



Oh, and one more thought. Starting with Access 2000 I think, there was a
really neat thing called Name AutoCorrect. Was supposed to automatically
track all your table/field name changes and automatically change any
reference to that name change. Only thing is, it either doesn't work, or it
slows everything down SO MUCH that it's unbearable. Common suggestion with
a speed problem is to de-select that feature (it's wise to do so even
without a speed problem).

I don't know where it is in 2003, but in 2000 it's in Tools/Options/General.
Deselect everything associated with Name AutoCorrect and try your query, see
how it goes.

hang in
ron

"Beat Scheidiger" <beat.scheidiger (AT) swisscom (DOT) com> wrote

Quote:
So far we were using Access 97.

We query data in a VBA procedure. This procedure puts together a SQL
string and opens a recordset with it.
We use only DAO libary.

Now we changed from NT opereating system to XP.
After converting the database to Access 2003 this query is about 10 to
20 times slower.

Can somebody tell me a raeson for that? Thanks a lot.

Beat Scheidiger



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.