upgrade from access97

[MajestikPredator]

Hello all,


Our access 97 database is long overdue an upgrade.

our operating system is windows 2000 server and clients are running on windows XP.

We have no 3rd party add-ons or anything. Everything was developed in access 97.

if we upgrade will the apps still work?

is there a particular process that needs to be followed when upgrading and should we upgrade to access 2016 or any earlier versions?

any advice would be much appreciated.

[JoeM]

What version are you upgrading to?

The only issues I really encountered with upgrading was if you were using some of the Access security features. A lot of that went away with 2003 or 2007 (I cannot remember which).

Also, there were some minor changes with what file formats you could export too. I think the DBF option went away.

Other than that, I cannot recall running into any other issues.

[CJ_London]

you wont be able to upgrade 97 to 2013 or beyond. Upgrade to 2003 or 2010 first.

security features stopped in 2007 but were still supported if db already used them. However this support has also gone away from 2013 onwards

[MajestikPredator]

thank you for the replies.

am I able to upgrade to version 2007 then 2016?

[NTC]

In addition to the other posts: you have a real issue if you intend to attempt to remain on XP. I believe you are in a box and are better off remaining in your current mode until the time when you are ready to also move to the newest OS with Win 10. XP just doesn't have the memory. Probably this means all new hardware.

When the time comes; The embedded upgrade feature of Access as noted by Ajax isn't really an option when attempting to leap frog all the way up to 2016 edition, and purchasing intermediary versions is dicey as well. What you do is start a brand new db in the current edition and then import objects. Tables & queries will import without a problem. It is forms & modules that you'll need to inspect/trial code. Libraries have changed, the menu bar is gone - so if there is a lot of custom code then you'll need to deal with it. Alternatively just building new forms may be no more difficult. Report objects are typically not as code heavy as forms - but will require the same approach.

[CJ_London]

am I able to upgrade to version 2007 then 2016?

yes - but take into account NTC's comments about XP

[CJ_London]

one other thought - you'll need the source file (.mdb) you won't be able to upgrade a complied file (.mde)

[MajestikPredator]

we shall definitely be upgrading the way operating system. My concern is that for some of the apps, there are no source files. this was way before my time i started to work for the company.
im assuming that mde files will not work on version 2016?

[CJ_London]

im assuming that mde files will not work on version 2016?

no, mde files will only work with the version they were written in (97 in your case). They might work with versions up to 2003, perhaps 2007 or 2010, but very much depends on what libraries they use and whether or not they use functionality that has been deprecated in later versions.

As a side point, when you move to 2016, choose the 32bit option, not the 64bit option. 64bit offers no advantages over 32bit in terms of performance, you are likely to have many more coding changes to make and certain functionality may not be available at all. Google 'Access 32bit v 64bit' for a fuller understanding.