Coverting old Access 2003 database - Part II

[Cosimo]

As I mentioned in an earlier post, I have an Access database I built over a period of years. I started the database in Access 2.0 and continue to build the database in Access 2003.

I retired the database almost twenty years ago, but recently I decided to convert it to a more recent version of Access so I can use it again.

I had a copy of Access 2007 which I installed and used to convert the database from mdb format to accdb format.



I had a few minor issues, which I seem to have resolved.

I would still like to convert the database to a more recent version of Access, a version that is still supported by Microsoft.

And I am unsure of the next steps.

First, was it a mistake to use Access 2007 as the first step in the conversion process?

I ask because 2007 was the first Access version offering conversion of mdb to accdb. So I'm wondering if there might have been some bugs in the conversion process that MS fixed in Access 2010.

Should I obtain and use Access 2010 to do the conversion over again from scratch (which I don't mind doing if that's the surest way to do the job right)?

And if so, should I first uninstall Office 2007 Professional or just install Office 2010 Pro. over Office 2007 Pro?

[Welshgasman]

I think 2007 is the lowest version to convert mdb.?
I have done so for various people who had 2010 and up, and could not do it themselves.

[June7]

I can open MDB in Access 2010 and save as ACCDB with the "Save and Publish" option.

What issues did you encounter? A 2010 conversion will likely have same issues.

[Micron]

Pretty sure Islagogs has mentioned this before, so I'll say that converting by using 2007 was the right move. You should be able to upgrade all the way to the most recent version you can install. However, I would keep each converted file in a backup folder - never convert the only version you have in cases something goes wrong. You might have some fixing to do wrt outdated references (Access should take care of those) or code that could fail because the syntax isn't quite right but you got away with it. We've seen app updates do that from time to time.

[Cosimo]

Pretty sure Islagogs has mentioned this before, so I'll say that converting by using 2007 was the right move. You should be able to upgrade all the way to the most recent version you can install. However, I would keep each converted file in a backup folder - never convert the only version you have in cases something goes wrong. You might have some fixing to do wrt outdated references (Access should take care of those) or code that could fail because the syntax isn't quite right but you got away with it. We've seen app updates do that from time to time.

Thank you, Micron.

I back up continually.

Now that my database seems to run OK in Access 2007 after conversion from mdb to accdb format, what should I do next on the way to being able to use and modify my database in a version of MS Access that Microsoft still supports?

Right now, I believe Access 2016 is the oldest version that MS still supports (until 2025); should I acquire and install MS Access 2016 next, or should I first install an intermediate Access version, like Access 2013?

[June7]

Don't need to buy 2013/2016 before moving on to later versions. Buying 2010 or 2013 as intermediate to 2016 or later is waste.

Can continue with 2007 if it has features you use and don't want to lose (like Collect Data and MS-Graph and pivot tables/charts) - at least until you develop replacements for those features. Although since you just converted from 2003, 2 of those probably weren't available.

So, jump to 2021 or 365 unless you want to wait for next desktop version.

[Micron]

Since you asked me directly, I'll second all of that! If I was going to move from mdb created in anything prior to 2007 to accde I'd do that then move to the latest app version that suited me or the organization. No need to do it in steps AFAIK.

[Cosimo]

Don't need to buy 2013/2016 before moving on to later versions. Buying 2010 or 2013 as intermediate to 2016 or later is waste.

Can continue with 2007 if it has features you use and don't want to lose (like Collect Data and MS-Graph and pivot tables/charts) - at least until you develop replacements for those features. Although since you just converted from 2003, 2 of those probably weren't available.

So, jump to 2021 or 365 unless you want to wait for next desktop version.

Thank you.

Unfortunately, I cannot stay with Access 2007 because I have to use a supported version of Access on my business PC for insurance purposes. So it sounds like I'll go straight to 2016.

When Access 2016 is no longer supported (I think that will be in 2026) then I'll go to the next version that is supported.

[Cosimo]

Since you asked me directly, I'll second all of that! If I was going to move from mdb created in anything prior to 2007 to accde I'd do that then move to the latest app version that suited me or the organization. No need to do it in steps AFAIK.

OK, thank you. That will make it all easier!

[isladogs]

Just to add my POV. As 2016 will reach end of support in the next year or so, I wouldn't bother with that either.
Suggest you download a trial copy of 365. You have 30 days to evaluate it before you need to start paying anything.

The latest versions can still open & convert any Access db from A2000 MDB format onwards so if necessary you can run the conversion again from your original file

[Cosimo]

Just to add my POV. As 2016 will reach end of support in the next year or so, I wouldn't bother with that either.
Suggest you download a trial copy of 365. You have 30 days to evaluate it before you need to start paying anything.

The latest versions can still open & convert any Access db from A2000 MDB format onwards so if necessary you can run the conversion again from your original file

Thank you, but isn't office 365 cloud based and a subscription service? I haven't yet decided whether or when I want to deal with all that and what I suspect will be an even greater learning curve to get up to speed.

I have way too much on my plate right now as it is. I can pick up a licensed copy of Access 2016 on ebay for ~$50 to get me going with what I need ASAP.

In my spare time over the next year I can plan for what I'll do after 2016 is no longer supported; but in the meanwhile I'll be able to put my database back into service.

[isladogs]

Office 365 is a subscription service but it consists of desktop apps as in 2016 plus lots of additional cloud based services.
There would be no additional learning curve in using 365 compared to 2016
However, its your choice

[Micron]

"Microsoft 365" is not cloud based but it is subscription based. You do get 1 (?) TB of storage on One Drive but that's as close as it gets. I've been using 365 for 8 years and AFAIK, Access does not come with 365, it is separate and I had to add it on. At least that is the case with Family/Personal/Student subscriptions. Other subscriptions (e.g. professional or whatever) might include Access - I don't know but you could research the whole subject.

[isladogs]

Almost all 365 subscriptions include Access. Family and Personal both include it. IIRC the Student version doesn't include Access

[Micron]

It's not shown in the icons but it is in the list of apps. How odd.