Looking to migrate Access XP/2003 to Access 2016

Question

Hello All.... I am not quite sure if i am posting in the correct forum so accept my apologies in so in advance.

We are currently using Access XP/2003 with the .mdb format and are looking to migrate the database over to Access 2016. I have been doing some research yet however i am not quire sure if i have found the information i am looking for. I do not know knowledge in the database sector of work so this is all brand new to me. I would like to know, do i need some advanced knowledge and experience before i can migrate Access from xp/2003 to Access 2016.

What problems can i expect in this process? Is it somewhat a seamless process?

Many thanks for all the information in advance. 

Answer 1

Hi,

Not sure about "seamless." It might depend on the complexity of your database.

In any case, I believe the proper way to upgrade your database is to first convert the file using Access 2010 before using Access 2016.

If your database is using any deprecated features (like the Calendar Control), then you'll have to modify the design to use newer features or discard it and use a different approach.

Just make sure you keep a backup copy of your files in every step to be safe.

Good luck!

Answer 2

Thank you much for your response, yes conversion would be the first step which i am getting more clarity on as i dig in further. 

Would you know if importing the data as we go into Access 2016 as opposed to migrating it over be some what less complex?

Is database knowledge/background a must here? 

Many Thanks! :)

Answer 3

No, the data should transfer/migrate fine. Access 2016 changed the names of some of the data types but direct conversion to their old counterparts will still work.

For the data only, you might be able to go straight from XP/2003 to 2016. I think only MDBs created with Access 97 are the ones needed to go through 2003 first before 2016 can use them.

Cheers!

Answer 4

Good Morning Seawhisper,

In addition to theDBguy's response, if you have any user level access or login controls you will most likely want to leave those out and build new ones if needed. You may wish to consider just creating a new db and transfer the data to it. Depending on how complex it is and how many records. You could also contemplate sending the objects out as text and then bring them into your new shell from text. While the files are as text you can modify some of the characteristics manually f needed.

---

Just takes a click to give thanks for a helpful post or answer.
Please vote “Helpful” or Mark as “Answer” as appropriate.
Chris Ward
Microsoft Community Contributor 2012

Answer 5

One more thing that will be unpleasant...If you are using any custom toolbars or menus these will end up under the Add-ins tab on the Ribbon. While they will still work they won't just show up when they should. The best approach is to convert them to custom ribbons. Doing this manually is very painful. I would use the converter at Ribbon Creator

---

Bill Mosca
www.thatlldoit.com
http://tech.groups.yahoo.com/group/MS_Access_Professionals

Answer 6

the less customized it is in terms of vba written - the less painful it is to upgrade.  If it was built using all basic features of the 2003 era (forms, reports, queries) with little to no vba - it may upgrade totally without a hitch.

there is no down side in copying it, and do that conversion - and then stepping thru the app as would a normal user - - just to see where/if errors get thrown.  At that point you'll need Access skills to resolve.

Answer 7

Thank you for sharing that link Bill.  In all these years, I never saw that Utility (yes, I must be blind) and happily for me I currently need it.  It will save me some work ( making my client happy - less billable hours).  Thank you for being a wealth of knowledge and willing to share it!

---

Daniel Pineault, 2010-2017 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 8

Hello Seawhisper,

What's the state of the thread? Do anyone's suggestion could work for you? Please feel free to let us know your current issue.

Best Regards,

Terry

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 9

Hello All,

My apologies for the delayed response as i was out of the office. Thank you much all the suggestions, all information shared is quite valuable especially for someone that has no familiarity with Access. I understand there is very little information on this out there and that is because as i understand, Access is hardly being used organizations out there, we happen to be one of the choose one. I should begin working on this issue in the next 2-3 weeks and will keep you all posted with my progress.

Warmest Regards,

Seawhisper

Answer 10

Hi,

Good luck and let us know if you hit a snag. Cheers!