MS Access Database must be corrupt

I have a MS Access database   (2007-2013 file format).  It is really behaving terribly.

1.  It has created a duplicate row with the same Indexed, duplicates "NO" field.
2.  It is consistently going into Recordset not updatable and locking the users from Updating any records or creating new ones.
3.  I have tried to Compact and Repair mutliple times.
4.  I tried to open a fresh new DB and tried to export the tables and received the following:
Reserved error <Item>; there is no message for this error. (Error 3000)

The database is split, I have a FE and BE.

PLease help!!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
1 Create a fresh db
2 import everything but the problem table
3 import the structure only of the problem table
4.  Link to the table in the old db
5 use append query to pull all the records, excluding the duplicated one

You may need to turn off relationships and/or indexes to make this happen

seamus9909Author Commented:
hi Jim

I followed your steps and received

"reserved Error (-1524), there is no message for this error"
Jason clarkDBA FreelancerCommented:
Probably some tables get corrupted in the curr BE ,which were not repaired by a compact. And reason for the occurrence of this error. If you have the recent healthy backup, you may replace with this. If you don't have the current backup available and unable to recover your data, Microsoft Access recovery tool will help you to recover your precious data.
 Acronis Global Cyber Summit 2019 in Miami

The Acronis Global Cyber Summit 2019 will be held at the Fontainebleau Miami Beach Resort on October 13–16, 2019, and it promises to be the must-attend event for IT infrastructure managers, CIOs, service providers, value-added resellers, ISVs, and developers.

Dale FyeOwner, Dev-Soln LLCCommented:
Just out of interest, do all of your users use their own copy of the FE, or are they sharing a FE located on your network.  If the latter, you need to change to the former.

seamus9909Author Commented:

Yes they all  use their own copy of the FE

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
seamus9909Author Commented:
@jason  yes i have tried recovering restores from previous days, it works for a bit then I get all kind of crazy behaviour as out lined above.

Can not figure out if its the query causing this or the data is hosed.  I have attached the fe and be verison if you wold be so nice to take a look.

On the FE it is from the Main CASES screen where you click to add a new record and boom the issue is apparent.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Pretty sure this is a corrupt DB....had another question I just looked at from Seamus about an LDB file getting left behind.

Seamus, one of the other reasons a LDB file gets left behind is it tells you what station cause the DB file to corrupt

seamus9909Author Commented:
HI Jim

What station?? I am not familiar with that.  I would agree I have a corrupt database however I can not seem to fix it, and the data can not be thrown away.  So I am trying to get this DB back up and running from the restore point I attached to this string. That database has all the records I need to maintain.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
When a user connects to a JET database, an entry is made in the LDB file and a user lock is taken.    The entry is the station/PC name that is connecting (network name), and the Access user (which in later versions is always 'admin').

If the connection is broken, the LDB file remains behind with the corrupt flag set.   If the flag is on, then using the LDB Viewer, you can tell what station had a broken connection.

 As far as the DB, either you need to re-construct it as I outlined, go to a backup, or look for a recovery/repair service, like

Jason clarkDBA FreelancerCommented:
As your data is corrupt. Try other option I specified, you may preview all your data and easily able to keep the file you need.
seamus9909Author Commented:
Would anyone be willing to have me pay them to try and help me fix this problem?
seamus9909Author Commented:
I fixed the solution with out the assistance of the experts
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.