Problems with compiled Access database

I have a database that was working fine compiled.    The db is split into front end and back end.     Recently, the back end has been corrupting, requiring us to perform a repair.   This happens when more than 5 users start working on it.

I decided to run the db's uncompiled and have no problems, with multiple users.    We are running the front-ends from a network share using a shortcut.     I have also tried it by having a local copy of the front end.   Either way, after more than 5 users start working on the system, the back end corrupts, when someone exits and comes back into the database.

I have noticed that the locks file doesn't seem to be working like I would expect.    I recall that when you opened the lock file (or a copy) when the Db is open, it used to list all the users in the db.    Now it only seems to list the last user to open the db.    Is this normal behavior?

All of the computers are running 32 bit Windows 7 and Office 2010.      

Any suggestions for how to get the compiled version working again.      My thought is perhaps an office/windows update has somehow broken this feature from working.

Any suggestions?
LVL 3
Gary Fuqua, CISSPOwnerAsked:
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.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
We are running the front-ends from a network share using a shortcut.
The preferred way to run a split database is to install a physical copy of the FE on each user machine, with all of those FEs connected to the same backend. Trying to run a shared copy from a network location is a futile effort, and can result in constant corruption.

Backends corrupt for a number of reasons, but one of the most common is a dropped network connection. Be sure your network is healthy and robust.

Users require read/write/create/destroy permissions on the folder hosting that BE file. From what you've written, it almost sounds as if someone does not have permissions on that folder.
Dale FyeOwner, Developing Solutions LLCCommented:
As Scott mentioned, "make sure your network is healthy and robust".

Is anyone accessing the BE via a wireless connection?  This can cause problems as well, as wireless connections can get easily dropped, leading to BE corruption.  I had this happen when a user copied an application to a laptop, and was walking around the office with the application open.  He would invariably drop his connection causing severe backend corruption.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
As the others have said, you need to focus on the network.

I'd doubt the compiled vs un-compiled state has anything to do with it, but it is conceivable.  With the users sharing the FE, it's possible that the compiled code has become corrupt.   You can either:

a. create a new DB and import everything into it.

b. Use /decompile when starting Access followed by a compact/repair to make sure that all compiled code is dumped.

  After that you should compile ensuring there are no errors and users should not be sharing a single copy of the front end.

Jim.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

Gary Fuqua, CISSPOwnerAuthor Commented:
Moved the database FE to the workstations.   Still have the same problem.
We made sure all the power setting for the computer are set to always stay on.  Specifically, the network adapter power settings were set to "never shut down" to save power.

I don't have complete control of the domain network, so I can't do the testing myself.     I was thinking of suggesting following tests to the techs responsible:

1.  Run and log an extended ping from the server to the workstations.
2.  Shut down anti-virus on server and workstation.    Maybe white-list the FE & BE.    What else should be white-listed?
3. Verify that there isn't any real-time backup getting in the way.

Any other specific tests / steps I should consider?
Gary Fuqua, CISSPOwnerAuthor Commented:
Also verified that users have "Full Control" on the folder where the back end is stored.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
You hit all the main points that typically give you trouble.

Jim.
Gary Fuqua, CISSPOwnerAuthor Commented:
It turns out that the problem was the Kasperski Anti Virus software.   When the anti-virus software was removed the problem was gone.   Put the software back, the problem recurred.   We changed antivirus programs and the problem is gone.

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
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Interesting and would not have been the direction I would have thought given that it seemed to be dealing with the number of users.

Glad to hear you finally tracked it down though.

Jim.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Agreed - thanks for posting back and letting us know.
Gary Fuqua, CISSPOwnerAuthor Commented:
This is what worked.
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.