Access 2003 forms VERY SLOW when opened in prior versions

I have an interesting phenomenon that is occurring.

I have Access 2003 installed on my machine, and most of my clients are using Access 2000 or Access 2002. If I take an existing database that was created in a version of Access prior to 2003, and either update forms/reports or create new forms/reports in 2003, when I attempt to open them again in the prior version of Access (i.e. on my client's machine/server) their performance is severely compromised. They run extremely slowly, particularly to open the form. The same form/report when run in 2003 works quite quickly, and if I re-design it in the prior version of Access, it runs OK on the old version, too.

I am using quite a bit of code under my forms.

I have searched the Microsoft website, and was unable to find any documentation on why this was occurring, and was wondering if anyone had any input on what the problem was? or if anyone else has experienced this, and had a solution as to how to fix it. This is a bit challenging, as all of the things I design are ultimately NOT going to be used on my machine, but I LOVE the new design features in 2003.

Thanks.
Vee

PS: Please try to refrain from blatant Microsoft bashing -- I know, it's difficult --, as this is what I  use, and know, and I really like it.
Thanks.
LVL 1
VeeVanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Data-ManCOOCommented:
1.  Try the decompile switch.  Create a shortcut to your database and use /decompile at the end.  When the database opens confirm that you have no missing references and then perform a compile and then click the save icon on the tool bar.

2.  I would also perform a compact and Repair.  

3.  You might also try importing all objects into a clean database.  Don't forget to set any references.

Thanks
Mike
0
firebird-scCommented:
I had a similar problem. The following helped a lot:

Tools/Options/General    Uncheck "Track name AutoCorrect info"

Hope that helps

firebird-sc
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
VeeVanAuthor Commented:
I'll try both of those and get back to you.

Thanks.
V
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.