Problem with multiple backup copies of database

I have a client that has an Access Database that is used by 5 multiple users via the network server.  This has been running ok for 5 years but recently (started 2 weeks ago) the database has started creating multiple backups (eg backup..., backup of backup..., backup of backup of backup etc). This has happened twice over the last 2 weeks. It seems to create a new backup when a new user goes into it.

It was created in v2013 and the users have v2016. I can't access the original I get the error message 'id is not an index in this table'. I can however open the backup file.

Does anyone have any idea why this has started to happen?
LillyCAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Alex GreenProject Systems EngineerCommented:
The second you open a database in a newer version it tries to update the source of the database, give them 2013 again or be prepared to update the code running the DB.

Regards,
Alex
0
LillyCAuthor Commented:
Please clarify what do you mean by updating the code (VBA code?) and how it can be done?  I have sent them fresh 2013 version couple days ago but it happened again this morning.

thank you
Lisa
0
Alex GreenProject Systems EngineerCommented:
So when you open up an access database with a new version, it upgrades the database, you'd have to restore the previous version and then open it in Access 2013. When it's updated it can't be reverted.
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

Dale FyeOwner, Developing Solutions LLCCommented:
Alex,  I'm not sure this has anything to do with the backup issue that Lilly is experiencing.

@Lilly,

I believe what Alex is referring to is that if a user with A2016 opens an Access front-end it will update the references in the VBA editor to those used by Office 2016.  If another user running A2013 attempts to open the same FE after the A2016 has modified the references, then you will get errors because Access cannot properly adjust the references back to the Office 2013 versions.

Are users sharing the same front-end database, or just the same back-end?

Do you have anyone attempting to open the front-end via a WiFi connection?  Running Access over a WiFi connection can cause this type of corruption.
0
LillyCAuthor Commented:
They have 2016 and I have 2013. They have been using it for last year, the multiple backups only start appearing two weeks ago, so it does not not look like its a version issue.

Can multiple backups be stopped somehow?

Thank you
0
LillyCAuthor Commented:
Thank you both for your comments.

Dale - I will ask if any of the users are using wifi connection, just to clarify the users are using v2016 and I'm developing in v2013.  The latest version of their database has not yet been split as there has been regular changes.
So currently they are all accessing the latest unsplit database, but this hasn't created a problem before only in the last two weeks.
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<I get the error message 'id is not an index in this table'>>

 Th DB is corrupt in some way.  Create a new DB and import all the objects into it.

<<Does anyone have any idea why this has started to happen?>>

 It may be related to a recent windows update that causes problems for MS Access assuming nothing else has changed in your environment.  What you'll want to do is disable leasing on the server:

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-%EF%BB%BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d

 and see if that clears up the issue.

Jim.
0

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
Dale FyeOwner, Developing Solutions LLCCommented:
You also need to split the db.  Everyone should be working with their own copy of the application front end.
0
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.