How to fix 'Unrecognizable database format'
I have an access application developed in Microsoft Office Professional 2010 Access version 14.0.7192.5000 (32 bit). It has a backend database. I install using SageKey Installation Wizard which includes the Microsoft Runtime 2010.
It installs and runs fine on most versions of Windows and office, including Windows 10 and Office 365, including 2 in my office. BUT on just a few client machines running Windows 10 and Office 365, it gives an error 'The expression you entered has a function name that [the application] can't find.'
I tried to open the backend database in Access 16 and got 'Unrecognizable database format'
Can anyone tell me why and how to fix it?
Many thanks in advance.
CRB
It installs and runs fine on most versions of Windows and office, including Windows 10 and Office 365, including 2 in my office. BUT on just a few client machines running Windows 10 and Office 365, it gives an error 'The expression you entered has a function name that [the application] can't find.'
I tried to open the backend database in Access 16 and got 'Unrecognizable database format'
Can anyone tell me why and how to fix it?
Many thanks in advance.
CRB
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hmm, this kind of message is rarely a good news.
Make a backup of your database.
Try to open it with a full access, then compact it.
If that fail, I'm afraid the database is corrupted.
Make a backup of your database.
Try to open it with a full access, then compact it.
If that fail, I'm afraid the database is corrupted.
<< BUT on just a few client machines running Windows 10 and Office 365, it gives an error 'The expression you entered has a function name that [the application] can't find.'>>
This is a sign of broken references. Something in the target environment that you have set a reference for in the app is not the same.
<<I tried to open the backend database in Access 16 and got 'Unrecognizable database format' >>
This may not be a corrupt DB. What format is your DB in? Access 2013 and up will no longer read a JET DB in 3.x format.
Jim.
This is a sign of broken references. Something in the target environment that you have set a reference for in the app is not the same.
<<I tried to open the backend database in Access 16 and got 'Unrecognizable database format' >>
This may not be a corrupt DB. What format is your DB in? Access 2013 and up will no longer read a JET DB in 3.x format.
Jim.
Is this a shared back end, opening on some machines but not on others, all with the Windows 10 / Office 365 setup? Or are you able to copy the 'broken' back end to another computer and open it successfully? If so, I would think that you are missing some component in your Access installation on the troublesome computers.
I would address this issue to SageKey support.
Also be aware that with Access 2016, when they added BigInt support, there is an upgrade of the db version. This is currently only available in O365. Someone with a retail version of Access or the runtime would get the "Unrecognizable database format" message.
little info on that here:
https://support.office.com/en-us/article/using-the-large-number-data-type-5b623f6e-641d-4e97-8bdf-b77bae076f70#compatibility_considerations
Jim.
little info on that here:
https://support.office.com/en-us/article/using-the-large-number-data-type-5b623f6e-641d-4e97-8bdf-b77bae076f70#compatibility_considerations
Jim.
BTW, if you back up a bit on the page from that link, it tells you how to check the DB version.
Jim.
Jim.
ASKER
Thank you all, very much. I am digesting this and trying some of the suggestions. Bear in mind that I can only do this on client machines, so it takes a bit of time. I also have the problem that the client data is protected by law and I may not be able to put their data on my machine.
This is threatening my business as clients are already looking for other products, so I am taking this very seriously.
I will get back to you.
This is threatening my business as clients are already looking for other products, so I am taking this very seriously.
I will get back to you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Many thanks to all of you. Glad to see that MS have fixed the bug.
In the end I recreated the system under Access 16, which would have been messy for downloading from my website. At least it worked and proved that the database was not corrupt.
It's so good that you hung in there.
CRB
In the end I recreated the system under Access 16, which would have been messy for downloading from my website. At least it worked and proved that the database was not corrupt.
It's so good that you hung in there.
CRB
ASKER