Forum Discussion
MS Access Database Decommissioning
On one level, it's impossible to suggest when this particular database application might need to be modified because we have no visibility to the way it's designed, built and used. That's what determines its usability in any given version of Access.
However, in a more general sense, we can comment on things that matter.
It is in the Access 2007-2016 file format, meaning it's an accdb created sometime in the last 18 years. We'd need to know which version of Access was used to create, 2007, 2010, 2013, 2016, 2019, 2021, or 365, to know more than that. Moreover, we'd need to know what features were used in creating it, such as Modern Charts, or Large Number Support, and so on.
The more recently it was created, the higher the likelihood it could contain newer features. On the other hand, a few features have been deprecated over the years. You would already know about that because you apparently are currently using it. Given that it is currently in use, I speculate that it doesn't include any now deprecated features. It's fine, and should still be fine in the foreseeable future.
Ultimately, it's safe to say that it's as "modern" as any existing Access database application and in no need of updating or modification for that reason alone. You might want to update or modify it if your organization's needs have changed, but that's a different matter.
There may be additional considerations, about which you would need to provide details. For example, if this accdb uses 32 bit specific components or code, you would need to modify it should you switch to 64 bit Access at some point in the future. But until and unless you do that, there's little or nothing to update.
And finally, the bottom-line test: Try to run the accdb as-is in the latest version of Access, either Access 365 if you have the subscription version, or most likely Access 2021 if you have the perpetual license version. (Your organization may have Access 2024 if you have deployed that version.)
If there are problems, you will know you need to update. If there are no problems, it's good to go.
George, thank you for your time and recommendations. Yes, it has heavily been used at the present time under the MS365 MS Access application. There are no major enhancements or features that could be out of ordinary. 😀
I'll check the 32 but to 64 bit though.
Thanks,
It's probably good to keep in mind that backwards compatibility is an important consideration for Microsoft products. You can even run mdb files created back in 2003/2004 under M365 Access.
Since you are now using this database with your current M365 installation, it's quite likely that you have either have 32 bit Access installed, or that nothing in the database uses 32 bit only features.
What matters in that regard, would be if your organization did switch to 64 bit Office in the future and you'd have to deal with any issues at that point. Making an accdb 64 bit compatible is not difficult, although it could be time consuming.So we do not have to upgrade the database from 2016 to 2019?
