SOLVED

Record Locks and Other Frustrations

%3CLINGO-SUB%20id%3D%22lingo-sub-3074085%22%20slang%3D%22en-US%22%3ERecord%20Locks%20and%20Other%20Frustrations%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3074085%22%20slang%3D%22en-US%22%3E%3CP%3EHi!%26nbsp%3B%20I'm%20really%20just%20looking%20for%20advice%2C%20please%20be%20easy%20on%20me%20as%20I'm%20a%20total%20rookie%20when%20it%20comes%20to%20Access.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20trying%20to%20use%20Access%20both%20to%20store%20data%2C%20and%20as%20a%20GUI%20for%20the%20non-technical%20in%20our%20company%2C%20to%20use%20data%20related%20to%20our%20products%20and%20procedures.%26nbsp%3B%20I%20cobbled%20together%20some%20VBA%20to%20make%20a%20front%20end%2C%20and%20have%20all%20the%20data%20on%20a%20separate%20back%20end.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrankly%2C%20all%20of%20that%20works%20together%20well.%26nbsp%3B%20The%20issue%20begins%20when%20multiple%20users%20are%20trying%20to%20edit%20data.%26nbsp%3B%20It%20seemed%20like%2C%20for%20a%20few%20months%2C%20everything%20was%20fine%20and%20locks%20would%20only%20happen%20when%20a%20record%20was%20being%20directly%20edited.%26nbsp%3B%20Now%2C%20if%20someone%20is%20using%20the%20database%20at%20all%2C%20it%20locks%20everything.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20am%20I%20doing%20wrong%3F%26nbsp%3B%20Should%20I%20be%20looking%20at%20using%20a%20different%20application%20than%20Access%20for%20a%20multi-user%20environment%3F%26nbsp%3B%20Etc.%26nbsp%3B%20Any%20help%20is%20appreciated.%26nbsp%3B%20I'll%20clarify%20what%20I%20can%20if%20anyone%20has%20questions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3074085%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eaccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3074115%22%20slang%3D%22en-US%22%3ERe%3A%20Record%20Locks%20and%20Other%20Frustrations%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3074115%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20December%20Microsoft%20introduced%20a%20bug%20in%20some%20security%20updates%20that%20causes%20this.%20For%20most%20Access%20versions%20and%20variants%20there%20are%20updates%20with%20fixes%20available.%20Have%20a%20look%20at%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Foffice%2Ferror-in-access-when-opening-a-database-on-a-network-file-share-6cbc1560-62c2-46e7-9980-d079a46f5acc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%20support%20article%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EServus%3CBR%20%2F%3EKarl%3CBR%20%2F%3E************%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fyoutu.be%2FwpPYu6G_xcY%2520%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EAccess%20News%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.donkarl.com%2Fdevcon%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EAccess%20DevCon%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi!  I'm really just looking for advice, please be easy on me as I'm a total rookie when it comes to Access.

 

We are trying to use Access both to store data, and as a GUI for the non-technical in our company, to use data related to our products and procedures.  I cobbled together some VBA to make a front end, and have all the data on a separate back end. 

 

Frankly, all of that works together well.  The issue begins when multiple users are trying to edit data.  It seemed like, for a few months, everything was fine and locks would only happen when a record was being directly edited.  Now, if someone is using the database at all, it locks everything.

 

What am I doing wrong?  Should I be looking at using a different application than Access for a multi-user environment?  Etc.  Any help is appreciated.  I'll clarify what I can if anyone has questions.

5 Replies
best response confirmed by SamCampbell (New Contributor)
Solution

Hi,

 

In December Microsoft introduced a bug in some security updates that causes this. For most Access versions and variants there are updates with fixes available. Have a look at this support article.

 

Servus
Karl
************
Access News
Access DevCon

@SamCampbell This sounds very much like the recent bug that was released in the December Windows Update. It is also described in detail here.

 

Consult the Microsoft page for details on applying the update(s) which fix the problem. 

Thank you very much!@Karl Donaubauer 

Thank you very much!
obviously this is a day-to-day production?