Form loads extremely slow - Import to new DB fixes it

  • Thread starter Thread starter Andrew Backer
  • Start date Start date
A

Andrew Backer

Having a problem with one of my forms taking *ages* to open. To fix it
I have to create a blank database and import everything. After doing
this, and setting up my references, everything works fine.

I can't tell why it starts doing it. I have quite a few forms, but it
only happens on one or two of my most complex ones. These are forms
with 3 tabs, lots of controls, and 3 - 5 subforms. I will be working
in a totally unrelated area and not know it has happened. When I go
do a little QA (this specific spot) I will discover that it has
cropped up again.

There isn't anything special happening on the one form that is a major
problem. The record source is set to "select * from query", where
query only returns one record. The subforms are linked, or have their
source set in the onOpen event.

When I trace the code I get the the DoCmd.OpenForm, then it just seems
to hang for a few minutes. The next place it lands me is in the
OnOpen event. I have no problem opening it in design mode, and every
other form in my db works just fine.

Can anyone suggest any possible fixes? I am up for just about
anything except a complete recode.

Thanks,
Andrew Backer



..---
| Andrew Backer
| abacker _@_ comcast _dot_ net
`--------
 
Hi Andrew,

Have you turned off NameAutocorrect?
http://support.microsoft.com/?id=290181

Tom
_______________________________________


Having a problem with one of my forms taking *ages* to open. To fix it
I have to create a blank database and import everything. After doing
this, and setting up my references, everything works fine.

I can't tell why it starts doing it. I have quite a few forms, but it
only happens on one or two of my most complex ones. These are forms
with 3 tabs, lots of controls, and 3 - 5 subforms. I will be working
in a totally unrelated area and not know it has happened. When I go
do a little QA (this specific spot) I will discover that it has
cropped up again.

There isn't anything special happening on the one form that is a major
problem. The record source is set to "select * from query", where
query only returns one record. The subforms are linked, or have their
source set in the onOpen event.

When I trace the code I get the the DoCmd.OpenForm, then it just seems
to hang for a few minutes. The next place it lands me is in the
OnOpen event. I have no problem opening it in design mode, and every
other form in my db works just fine.

Can anyone suggest any possible fixes? I am up for just about
anything except a complete recode.

Thanks,
Andrew Backer



..---
| Andrew Backer
| abacker _@_ comcast _dot_ net
`--------
 
Hi Andrew

The most likely culprit is Name AutoCorrect.
Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Other known issues with Name AutoCorrect:
http://members.iinet.net.au/~allenbrowne/bug-03.html

Subdatasheets could also be an issue, but the fact that simply recreating
the database solves the issue suggests that it is caused by tracing all the
GUIDs through Name AutoCorrect.

For other ideas, see Tony's "Performance FAQ" for Access:
http://www.granite.ab.ca/access/performancefaq.htm
 
Thanks again allen, and you too Tom Wickerath.

Named AutoCorrect may very well be it, and I will make sure to keep it
in mind next time this happens. I had already re-imported into the
new database, so the problem had gone away, but I did find that it was
turned on though. I think it may have been turned on by default last
time I had to import all my objects into a new database (form
corruption.) I had turned this off after going through that most
helpful FAQ. In fact, the FAQ saved me, especially in the sub tables
case, when I had to put this new system in and the performance was so
bad it was unusable. Made a 1000% difference.

I have now added these property lines to my startup routine :

db.Properties("Perform Name AutoCorrect") = false
db.Properties("Track Name AutoCorrect Info") = false

so... this will hopefully not be a problem in the future. Thanks for
pointing it out again. These kind of issues are despair inducing,
since there is no 'logical' explanation :)

Hi Andrew

The most likely culprit is Name AutoCorrect.
Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Other known issues with Name AutoCorrect:
http://members.iinet.net.au/~allenbrowne/bug-03.html

Subdatasheets could also be an issue, but the fact that simply recreating
the database solves the issue suggests that it is caused by tracing all the
GUIDs through Name AutoCorrect.

For other ideas, see Tony's "Performance FAQ" for Access:
http://www.granite.ab.ca/access/performancefaq.htm
Click to expand...

..--------------------------------------
| Andrew Backer
| abacker _@_ comcast _dot_ net
`--
 
Hi Andrew,

Unfortunately, Name Autocorrect is turned on by default for all new databases in Access
2000/2002/2003. So, when you imported all objects into a new database, "wa-la"...you got Name
Autocorrect turned on again. There is no way to disable this default setting for new databases.
The setting is on a per database basis. Your startup routine will help protect against some user
inadvertently turning it back on, in the event that they have access to the Tools > Options menu.

Let's hope that Microsoft lets us set the Name Autocorrect behavior for new databases, in the
next release, as a user option. In fact, Tim Getsch, Microsoft Access Program Manager, heard this
request tonight at our meeting of the Pacific NW Access User's Group.

Tom
___________________________________


Thanks again allen, and you too Tom Wickerath.

Named AutoCorrect may very well be it, and I will make sure to keep it
in mind next time this happens. I had already re-imported into the
new database, so the problem had gone away, but I did find that it was
turned on though. I think it may have been turned on by default last
time I had to import all my objects into a new database (form
corruption.) I had turned this off after going through that most
helpful FAQ. In fact, the FAQ saved me, especially in the sub tables
case, when I had to put this new system in and the performance was so
bad it was unusable. Made a 1000% difference.

I have now added these property lines to my startup routine :

db.Properties("Perform Name AutoCorrect") = false
db.Properties("Track Name AutoCorrect Info") = false

so... this will hopefully not be a problem in the future. Thanks for
pointing it out again. These kind of issues are despair inducing,
since there is no 'logical' explanation :)

Hi Andrew

The most likely culprit is Name AutoCorrect.
Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Other known issues with Name AutoCorrect:
http://members.iinet.net.au/~allenbrowne/bug-03.html

Subdatasheets could also be an issue, but the fact that simply recreating
the database solves the issue suggests that it is caused by tracing all the
GUIDs through Name AutoCorrect.

For other ideas, see Tony's "Performance FAQ" for Access:
http://www.granite.ab.ca/access/performancefaq.htm
Click to expand...

..--------------------------------------
| Andrew Backer
| abacker _@_ comcast _dot_ net
`--
 
Back
Top