Version access database was created in

LianneVoelm
LianneVoelm used Ask the Experts™
on
I want to know what "version" of Access a database created in.  SO I created one using Access 365 which is the version of Access i am using.  When i go to the immediate window and type Debug.print version it shows 16.  but When i type debug.print Current.db.version it shows 12.   Can anyone clarify?   Thanks!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Infotrakker Software
Most Valuable Expert 2012
Top Expert 2014
Commented:
Remember that Access contains multiple components. One of those is a database engine, and that's what Currentdb.Version reports to you. For anything from 2007 on it shows 12.0

Access also contains the "Access" program, which is responsible for the user interface portions, VBA, etc. That's what Application.Version shows  - the version of Access you're using.

https://docs.microsoft.com/en-us/office/vba/api/access.application.version

16.0 is Access 2016/2019/O365

https://www.fmsinc.com/MicrosoftAccess/history/features.htm

Also, none of this will really tell you what version the system was created on. Those values report the versions of the system where you issue those commands, so if I ran them on my 2010 machine I'd get 12.0 for the db, and14.0 for the Access version. If I ran that same database on my 2019 machine, I'd get 12.0 for the db and 16.0 for the Access version. Only way you'd know the full history of that database is if you're storing that somewhere, like in custom properties, a table, etc.

Author

Commented:
Thank you so much. That was very clear!
Mark EdwardsChief Technology Officer

Commented:
There is also the CurrentProject.FileFormat, which gives you pretty much the same as Currentdb.Version, but without the decimal point and trailing zero (12 instead of 12.0)  File Formats are explained here:
https://docs.microsoft.com/en-us/office/vba/api/access.acfileformat
This page gives the various file formats that Access can determine:
File-Formats-Enumeration.PNGIn its efforts to make it easier to keep running your files in later and later versions of Access, Microsoft adopted a file version that is consistent with versions 2007 and later (12).
It may be noted that when you create a new database file, without a titlebar override, you get the earliest and latest versions based on the file type and the version of Access it was created in.  However, files created in Access 2007 and opened in Access 365 also have the same versions in the titlebar.
New-File-Version-Titlebar.PNGYou don't see 2003 listed because it's part of 2002, which is really 2002/2003, although the "official" enumeration description is "2002".
You also don't see 2010 and later because they still use the A2007 file format.
Major issues with file versions center around earlier versions of Access (97-2000) trying to be run in later versions of Access that no longer support these earlier versions.
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Scott McDaniel (EE MVE )Infotrakker Software
Most Valuable Expert 2012
Top Expert 2014

Commented:
I'd say that CurrentProject is more of a "window" in the Access application, while CurrentDB deals strictly with the database component. There's some cross pollination, of course, and many properties exposed via CurrentDB are also implemented in CurrentProject.
Mark EdwardsChief Technology Officer

Commented:
However, just because the file versions are the same from 2007 thru 2019/365 doesn't mean you can't run into compatibility issues between files done in, say A2010, then modified in A2016.
Here's a link to a situation discussed in the Office Dev Center where a developer used his home computer with A2016 to work on a file from his office computer (A2010).  (poor chap, what a mess that created!)
https://social.msdn.microsoft.com/Forums/office/en-US/bbc87806-49a2-47de-a3d1-7eff16ee3ea9/backwards-compatibility-between-access-2016-and-access-2010-help?forum=accessdev
I wonder if there was ANY way to tell the two files (pre-2016 and post-2016) apart.
The link above also has a link to list of features discontinued in A2013:
https://support.office.com/en-us/article/Discontinued-features-and-modified-functionality-in-Access-2013-BC006FC3-5B48-499E-8C7D-9A2DFEF68E2F
Mark EdwardsChief Technology Officer

Commented:
Now that you got me started on it, here's some reasons for using CurrentProject vs Currentdb:
Getting-DateModified-Using-CurrentPr.PNGIf anyone is NOT familiar with CurrentProject, I recommend you spend some time researching it....
Mark EdwardsChief Technology Officer

Commented:
And just when you thought it couldn't get any better, here's something else found by Google:
https://www.wisdomjobs.com/e-university/ms-access-tutorial-203/the-currentproject-and-currentdata-objects-8286.html

Inside this little tidbit, I found this:
More-Info-on-File-Version.PNG
I was able to verify here with my test lab.  Check Currentdb.Version to see if the file has been modified to a later version that CAN'T be run by an earlier version....
Mark EdwardsChief Technology Officer

Commented:
Come to think of it, there are all kinds of lists about "What's New in Access XXXX", etc., but does anyone know of a list of version-specific changes starting with A2007 and later that will prevent your database from being "backward compatible" with an earlier version of Access?  I see many a rant in forums like these about this issue, but no one seems to know what they are or can make a list of them.  (OK Luke C..... that's your cue!)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial