MS Access 2016 - Fine on Win7 - Recurring Unrecognized Database Format on Win10

[cmcfarland_67]

Hello Everyone:

I'm a document management consultant and have a client with an Access based application that is giving them trouble.

Not an Access developer myself, but have worked in and around it some over the years so figured why not try to help.

Here's the condition:

Their MS Access 2016 application worked just fine when hosted from a Win7 box, but it's been moved to a Win10 system and now gets frequent Unrecognized Database Format errors.



Seems like the only real difference is the hosting OS, so maybe there's something to dial in at the OS level to smooth things out for them.

What do you think?

Thanks!

[ranman256]

it could be a switch to Access on 64 bit Win OS. Does the code have PtrSafe in it to prevent the errors?
but the Unrecognized format is usu from old access trying to read a New version .accdb.

[pbaldy]

Could be this too:

https://www.devhut.net/2018/06/13/ac...gnized-format/

[cmcfarland_67]

Thanks for the responses, Guys.

I did find out that on the Win7 box it was running under Access 2013, and that they bumped up to Access 2016 when they moved to the Win10 box. Maybe they do have this issue because of this shift to a newer version. I hope so, really, as it seems that the OS level tweaks are a little more involved. I could always pass that stuff to their IT support, too, and avoid having to do the actual work and the responsibility and time that comes with that work.

[cmcfarland_67]

Once again, I really appreciate the insight here.

My question is this now: Given that the system used to run under Access 2013 when it was on the Win7 box and that they bumped up to Access 2016 when they moved over to the Win10 box, are the OS tweaks still a possibility for making things stable or would that stuff really not matter too much since they're using Access 2016 to interact with the database that was created and used historically with Access 2013? Maybe they just need to get Access 2013 on the Win10 box? What do you think?

Thanks!

[pbaldy]

My gut feeling is that the Access versions aren't the problem. If anything you could have trouble using 2013 to open a 2016 db. I wouldn't expect the reverse to be true. I always develop in the lowest version, and often have people with later versions using the app.

[cmcfarland_67]

Aha! I had it backwards. Newer Access interacting with Older Access product is probably fine. Thanks!

[pbaldy]

I wish I had a good solution, though the above link seemed like the most likely suspect. Hopefully somebody will jump in with more/better ideas.