Sudden Error: This object requires a newer version of the Microsoft Access database engine

[Bewinxed]

Hello, Had a database made in Office 365 and while I'm on leave the department reported that they're getting this error:


This object requires a newer version of the Microsoft Access database engine

After investigating, the error originates from one of the tables in the database, All the other tables are fine.

What I have tried:

• compacting/repairing the database.
• Opening with Office 2021/2016/2010. (db version is 14.0).
• copying the table/exporting (anything done related to the table gives the same error).

Is there any way to recover the data in the table? I'm stuck I'd prefer to not lose the data since the last backup.

[isladogs]

It sounds like one or more fields use one of the newer datatypes - either date/time extended or large number (bigint) which weren't supported in earlier versions.
First make a backup.
Then, if you can open it in the latest version, go to design view and change the field(s) concerned to Date/Time or Number as appropriate. You may lose precision. Save.

Now go to Access options and untick support for those two datatypes. Compact and repair.
It should now open in earlier versions

[Bewinxed]

It sounds like one or more fields use one of the newer datatypes - either date/time extended or large number (bigint) which weren't supported in earlier versions.
First make a backup.
Then, if you can open it in the latest version, go to design view and change the field(s) concerned to Date/Time or Number as appropriate. You may lose precision. Save.

Now go to Access options and untick support for those two datatypes. Compact and repair.
It should now open in earlier versions

Hello, I don't know why this happened suddenly as the frontend/backend weren't changed.

The problem is the error still pops up even when I try to open the table in Design Mode, And still happens whether the option you mentioned is ticker or unticked.

Same result even in O365/2010/2016/2021

[CJ_London]

could be corruption - is your db split FE and BE with each user having their own copy of the FE on their local machine and the BE on a shared server? Or is the app located on one drive or similar?

[Bewinxed]

could be corruption - is your db split FE and BE with each user having their own copy of the FE on their local machine and the BE on a shared server? Or is the app located on one drive or similar?

One FE on each device and a single BE on the shared server

If it's corruption, is there any way to get the data out?

[CJ_London]

presume when you say you have compact/repaired you are talking about the BE

Colin might have a way to recover corrupted data - but if you can't export the data, I doubt it.


Is this a problem with all users? If no, indicates an issue with the FE or the local access environment
does the table include calculated, multi value fields or long text? - if yes, it may be the hidden tables used by these are corrupted in some way

Have you tried a query

SELECT * FROM problemtable

or perhaps

SELECT cstr(field1), cstr(field2).... FROM problemtable

and perhaps try a column or two at a time or a few rows (use the top predicate) to see if you can identify which fields might be the problem

only other thought is if your field names include reserved words - they can cause misleading errors on occasion particularly in later versions of access where 'common sense' rules are more rigorously applied

[isladogs]

If it is corruption, I'm willing to look at the table and see whether I can fix it. It depends on the degree of corruption so no promises but I can try.
If you can't export it, try doing the opposite. Make a copy of the DB then remove all other objects apart from that table.
Then make another copy and compact it. Then forward it to me.

[Bewinxed]

If it is corruption, I'm willing to look at the table and see whether I can fix it. It depends on the degree of corruption so no promises but I can try.
If you can't export it, try doing the opposite. Make a copy of the DB then remove all other objects apart from that table.
Then make another copy and compact it. Then forward it to me.

I sent it to the email in your signature, It won't compact/repair showing the same error. I left the problem table in the file only.

Thank you in advance.

[isladogs]

PROGRESS REPORT:
I've spent over an hour on this trying several different methods .... but so far only with partial success.
One approach is still running and is likely to take several hours more before it is complete

So far, I'm getting the same error as you even after I've done several repairs

I can see the corrupted record and the rest of your data but haven't yet managed to extricate the valid data to a clean table.
Can you tell me how many records you have in that table?
Also, do you have a recent backup? If not, why not?

Finally which version of Access were you running when this got corrupted? If Access 365 ...then what is the build number?

FURTHER UPDATE
I've managed to get 758 records from tblCaseFiles. Does that sound right?
I've also got a load of assorted 'junk' which means nothing to me...but might mean something to you

Record ID=964 is completely corrupted and unrecoverable
This is part of the last uncorrupted record:

[Bewinxed]

PROGRESS REPORT:
I've spent over an hour on this trying several different methods .... but so far only with partial success.
One approach is still running and is likely to take several hours more before it is complete

So far, I'm getting the same error as you even after I've done several repairs

I can see the corrupted record and the rest of your data but haven't yet managed to extricate the valid data to a clean table.
Can you tell me how many records you have in that table?
Also, do you have a recent backup? If not, why not?

Finally which version of Access were you running when this got corrupted? If Access 365 ...then what is the build number?

FURTHER UPDATE
I've managed to get 758 records from tblCaseFiles. Does that sound right?
I've also got a load of assorted 'junk' which means nothing to me...but might mean something to you

Record ID=964 is completely corrupted and unrecoverable
This is part of the last uncorrupted record:

Awesome! yeah that sounds about right, the version is Access 365 16.0.13127.21668 x64-bit

I'm curious on how you're able to go through them, I'd love to learn.

I'm happy to get as much data as I can back, It's still pre-production and I didn't implement auto backup yet, my bad.

[isladogs]

OK - I'll email it back to you later this morning.
I wasn't able to read the corrupted record and have now deleted it.
The table now opens without any error. I've compacted it and the file size is now much smaller.
Hopefully the rest of the data is complete.

[isladogs]

I've emailed the recovered data to you just now. Apologies for the delay

[Bewinxed]

I've emailed the recovered data to you just now. Apologies for the delay

Thank you mate, You're a life saver.

Problem solved.

[isladogs]

Happy to help. At one stage I really thought it was unrecoverable ��