Access Version error with ACCDE file

Murray Brown
Murray Brown used Ask the Experts™
on
Hi

I regularly copy an ACCDE file to a client computer with Office 2016.
I create it in my version of Office 2019
Today for the first time I am getting the following error on the client machine and don't know
why

Image1.JPG
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Mark EdwardsChief Technology Officer

Commented:
You usually get this if you did some modification to a file with a later version of Access and that modification is not supported by an earlier version of Access.  If you use a later version of Access, be careful what you do.  Be sure not to do any thing to the file that isn't supported in an earlier version.  (Good luck trying to keep all that straight....)

This is an age-old issue with using different versions of Access to support Access apps through the years.
Murray BrownASP.net/VBA/VSTO Developer

Author

Commented:
I made no changes to the database solution since the last time that it worked on my client's  machine. I saw the following article https://support.office.com/en-us/article/access-error-this-database-is-in-an-unrecognized-format-when-opening-access-runtime-application-accde-file-5ed21574-cbff-498b-878e-7bff5b77933f
John TsioumprisSoftware & Systems Engineer

Commented:
You could have some corruption...and do take a look if you have some kind of mixup like the client running Office 2016 but with Access lower version
How to Generate Services Revenue the Easiest Way

This Tuesday! Learn key insights about modern cyber protection services & gain practical strategies to skyrocket business:

- What it takes to build a cloud service portfolio
- How to determine which services will help your unique business grow
- Various use-cases and examples

President / Owner CARDA Consultants Inc.
Distinguished Expert 2018
Commented:
Firstly, whenever I see this error I refer people to https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/ since there is a well established 18+ month old bug that MS still hasn't fixed.  So this could be your problem.

On the other hand, you should never be downgrading a database (or any software in reality).  The golden rule of development is to do all your development in the oldest version that will be used to run the database file.  So if you have users that have Access 2016, you need to be doing your development in 2016.  If you have users running Access 2013, 2016 & 2019, then you'd need to do all your development using Access 2013.  Access is backwards compatible, not forwards (no software is).  Thus, newer version can use older versions, but older version are not guaranteed to work with newer version.  Also, when developing deployable solutions, I highly recommend using late binding for all your VBA coding to avoid reference/versioning issues.
Scott McDaniel (EE MVE )Infotrakker Software
Most Valuable Expert 2012
Top Expert 2014

Commented:
Regardless if this is corruption, I'd still encourage you to take heed of the warnings from Daniel and others. You should always work in an environment that is the same as, or older than, your target environment. Doing otherwise is just asking for troubles.
Jim Dettman (EE MVE)President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012

Commented:
One place where it's easy to get caught on version differences between 2016 and 2019 is BigInt (Large Number) support.   That's one of the main features added with 2019.

 As Scott said, best practice is to always develop in the same version or older.

Jim.
Murray BrownASP.net/VBA/VSTO Developer

Author

Commented:
thanks for the advice

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