Beware! Converting Access 2003 Project to Access 2010 Project - Blocks of VBA Code Removed with no Warning

Question

Hello and thanks in advance!

I recently decided to upgrade several Access 2003 Projects (.adp which use SQL Server as backend data server) to a newer version - Access 2010. The conversion was surprisingly easy - so I thought.

In the past, when opening an Access file in a newer version, I always go to the VBA code window and try to Compile. Generally this produces a few errors, lines of code containing functions or references that were depreciated in the newer version of Access. I would just come up with a workaround, a different way to do the same task but with code which is supported in the newer Access. I would correct the References to the current versions and voila! Good to go!

I followed this time-honored tradition this time. Clicking Compile produced no errors, so I thought "Fantastic!".

After I began using the applications though, I found functionality that was missing. I discovered that many of the "code behind forms" had been removed (with no warning), so that now the forms had no code modules attached.

BE SURE TO SAVE A COPY OF THE ACCESS 2003 .ADP FILE in case you need to recreate the missing code.

Has anyone else discovered this? Any special procedures in "upsizing" to prevent this?

Answer 1

Hi Larry4747,

The First I want to tell you that support for Access 2003 has Ended.

is both version of Access 2003 and 2010 using same bit of Application? like both are using 32 bit Application of Access.

I want to confirm from you that are all the VBA code get deleted or only some of the code get deleted?

did it happened every time or you are just facing this issue in particular Access Database?

if it happen every time then we can provide a feedback regarding this issue to Access User Voice. so if there is some problem with upgrading Access 2010 they can know about it and try to solve after they having sufficient requests.

Till then Backing up of an old database file is the only option for us that we can follow so that we can get our VBA code if it loss.

Regards

Deepak

---

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Answer 2

Hi Larry4747,

you can give your feedback to Access User Voice Regarding this Issue.

Please visit the link below to give Feedback.

Access User Voice

Regards

Deepak

---

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Answer 3

Interesting - just saw a similar question here.

I realize this question is marked as 'answered'  but wanted to throw in some thoughts...

I've never seen code project corruption result from upgrading Access 2003 databases to 2010, which I have done many times (.adp and .mdb).

I posted a few scenarios which I believe can cause this form of corruption in my comment on this more recent question:

Code project corruption

Note that these were cases where the code project was *completely* wiped out, versus parts of it going missing.

---

Miriam Bizup Access MVP