Slow opening of tables.

I have Access2000 with WindowsXP

I have just renamed several tables in my application, and this then required
me to follow though and re-do relationships and rename objects in derived
queries and forms.

Now I find that the tables open much more slowly than before, even after
several database compacts and tests by the table wizard.

The forms and queries open as fast as before, and only the tables give
trouble.

In fact all the tables in the database screen now open more slowly.

Can anyone show me what is wrong, and is there an alternate proper way to
rename a set of tables?

Regards,Frank

The problem is almost certainly the Name AutoCorrect mis-feature, which is
supposed to track and handle issues caused by renaming, but is very buggy,
incomplete, and a performance disaster.

Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect.
Then compact the database.

If that does not solve the issue, create a new (blank) database. Immediately
turn off the Name AutoCorrect options, and then import everything from your
old database.

For more infformation on this mis-feature and more than a dozen bugs it
triggers, see:
http://allenbrowne.com/bug-03.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Frank Martin" wrote in message
...
I have Access2000 with WindowsXP

I have just renamed several tables in my application, and this then
required
me to follow though and re-do relationships and rename objects in derived
queries and forms.

Now I find that the tables open much more slowly than before, even after
several database compacts and tests by the table wizard.

The forms and queries open as fast as before, and only the tables give
trouble.

In fact all the tables in the database screen now open more slowly.

Can anyone show me what is wrong, and is there an alternate proper way to
rename a set of tables?

Regards,Frank

Thanks, I tried what you suggested but to no avail.

But I fixed it by deleting some old remmed out tables from the past (one by
one) and there was one particular one white took a long time to delete and
this may have been the culprit.

In future I will store all my old trial and obsolete tables in some other
place, remote from the current application.

Regards Frank





"Allen Browne" wrote in message
. au...
The problem is almost certainly the Name AutoCorrect mis-feature, which is
supposed to track and handle issues caused by renaming, but is very buggy,
incomplete, and a performance disaster.

Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect.
Then compact the database.

If that does not solve the issue, create a new (blank) database.
Immediately
turn off the Name AutoCorrect options, and then import everything from
your
old database.

For more infformation on this mis-feature and more than a dozen bugs it
triggers, see:
http://allenbrowne.com/bug-03.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Frank Martin" wrote in message
...
I have Access2000 with WindowsXP

I have just renamed several tables in my application, and this then
required
me to follow though and re-do relationships and rename objects in
derived
queries and forms.

Now I find that the tables open much more slowly than before, even after
several database compacts and tests by the table wizard.

The forms and queries open as fast as before, and only the tables give
trouble.

In fact all the tables in the database screen now open more slowly.

Can anyone show me what is wrong, and is there an alternate proper way
to
rename a set of tables?

Regards,Frank

Okay. Glad you were able to work around the issue.

If it was not Name AutoCorrect, it could have been Subdatasheets, or the
caching of paths for the Connect propety (if you have attached tables).

Tony Toews has a Performance FAQ that explains these issues at:
http://www.granite.ab.ca/access/performancefaq.htm


--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Frank Martin" wrote in message
...
Thanks, I tried what you suggested but to no avail.

But I fixed it by deleting some old remmed out tables from the past (one
by
one) and there was one particular one white took a long time to delete and
this may have been the culprit.

In future I will store all my old trial and obsolete tables in some other
place, remote from the current application.

Regards Frank