Migrating to Access 2007 is corrupting Access 2003 DB with VBA code

[Bre035]

I need a response really quickly. My company is migrating to Office 2007, but many of the departments have created Access 2003 database to use to complete multiple job functions. We have over 30 Access DB created in Access 2000/2003.

When a user with Access 2007 opens an Access 2003 Db with VBA code the database is being corrupted or the VBA code is. What can we do to resolve this issue?

I have a 4:00 PM meeting with PC services and upper management to try and find a resolution.

[NeoPa]

Bre035:
My company is migrating to Office 2007

Frankly, whoever made such a decision, without considering the impact in advance, should be considering their position. If I had someone working for me make such a move I'd be less than amused.

The databases need to be assessed and migrated one by one. You may find these links (Converting to Access 2007 or 2010, Interactive: Access 2003 to Access 2007 command reference guide) assists you in your chore.

Good luck.

[Bre035]

Huge company so, this decision comes from Upper Management without the thought of the business impact to multiple business units.

[NeoPa]

Been there, had that, lamented the fact that UM are often not the best suited to be UM ;-)

[Mihail]

Just an idea:
I suspect that you have less libraries installed now.
Try to fully (re)install Office (Access at least).
For me that solve the same problem as yours many times.

[NeoPa]

One of the problems that may effect some of your databases is possibly going to be mismatched references. Clearly these will need to be handled if they arise, but it is very unlikely that all your problems will fit into this category. That said, a reinstall will probably not hurt, and if it fixes a bunch of problems in one go it may well be worth the effort. I suspect that you'll still need to refer to the linked articles for some of your databases though, at least.

[Bre035]

Thank you all for the responses I left this issue up to them to decide what to do.