Access 2007-2016
Access 2000-2003
Access Seminars
TechHelp Support
Tips & Tricks
Access Forum
Course Index
Topic Glossary
Insider Circle
Home   News   Tips   Glossary   Templates   Forums   Help   Logon   Order   Contact Us  


Microsoft Access Forum
By Richard Rost   Richard Rost on Facebook Richard Rost on Twitter Richard Rost on Google Plus Richard Rost on LinkedIn Email Richard Rost

This forum is for the discussion of Microsoft Access.

Access is my personal specialty. Have questions? Comments? Want to discuss how to do something? Post it here. Also, I get a LOT of questions sent to me in Email from people around the world. I'll post the interesting ones in here. Feel free to comment on them.

Click Here To Subscribe to this forum and receive an email update whenever new posts are added, just scroll down to the bottom of this page and enter your email address in the comment form.

Permanent Link
Keywords: microsoft access forum
Post New Topic

Read Page Level Locking by Anne @ 6/2/2018
Record Locking Question:  Access Expert 21 for Lesson #5 was VERY helpful.  We are in a mulit-user environment with most users using Access Runtime.  The FrontEnd is on each users' C drive.  The Backend tables are on a shared network server.  All of our database forms (that have a RecordSource) have the Record Locks -> set to Edited Records.  The complied program is set to "Open databases by using record-level locking."   This works great some of the time.  However, each day the locks appear on more than the particular record that is being edited. This is problematic.  We think this happens when we

a . We import data and run routines (vba adds/updates tables) which (according to google) always use Page Level locking.   and/or
b.  We run production reports (the background vba handles delete/add to temporary tables for processing complex crosstabs . . . ) or any routine that has Updates/Appends "action queries"  and again (according to google) Page Level locking kicks in.

It appears that the .laccdb file switches from row-level locking to page level locking . . . From that point all users working are getting records to work that are "locked"  internally (but not programmatically ).  When the program tries to save the User and programmatically lock the record, it can not save the update because the record is locked internally.  So here are my questions:

1.  Is there a way to programatically identify and  "skip" records that are locked internally . . . until we get to one that is not locked internally?  and/or
2.  Is there a way to programatically check and change the page-level locking back to record-level locking after the routines that have "action" queries are completed? Right now, the only solution I can think of is to have all zillion users exit the program (runtime).  Be sure the .laccdb file is gone.  Then log in again.  Not very practially because everytime management runs the production reports locking switches to page locking.
3.  Do you have a suggestion outside this box that might work?

P.S.  If this is covered in one of your courses, I'll be happy to purchase it!
Show Just This Thread        Post Reply

Collapse All Topics


Post Your Comments or Subscribe
    If you would like to be notified of new posts on this forum,
    just enter your email address below. It will be kept private.
If you just want to subscribe to get email updates when this forum is updated, then enter your name and email address and check the Notify Me box below. If you would optionally like to add your comments below to be posted, they are welcome.
  Your Name:  Required
  Your Email:  NOT Public


Sorry about this step. It's just to keep the spam bots away:
  Verify: What is 4+5:
  Notify me when the this forum is updated
  Remember Me for my next comments
Please do not use this form for Customer Service inquiries! If you have questions about your account, shipping info, courses you've ordered, need passwords, etc. please use the Customer Service Center instead.

I value your comments. They will be displayed on this page (above). Your name will be displayed, but your email address will not be.
As always, I promise to never give away your personal information to anyone else, ever.

NOTE: If you don't leave your name and email address, DON'T expect a reply. I can't promise a personal reply to everyone who posts here. I TRY my best, but I cannot guarantee it. If you don't leave your real name and email address, I won't even bother. I usually just hit DELETE. -Richard



You may want to read these articles from the 599CD News:

11/20/2018Microsoft Access Developer 12
8/25/2018NEW: Access Dev 9, 10, 11
8/25/2018Microsoft Access Developer 11
8/25/2018Microsoft Access Developer 10
8/25/2018Microsoft Access Developer 9
8/23/2018Access Dev 11 is ONLINE
8/17/2018Access Dev 10 is ONLINE
8/15/2018Access Tip: Search Form
8/15/2018Access Tip: Locked v. Enabled
8/15/2018Access Dev 9 is ONLINE

Visual Basicindex
Account Login
Online Theater
Lost Password
Free Upgrades
Insider Circle
Student Databases
Change Email
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search Our Site
Waiting List
Production Schedule
Collapse Menus
Live Chat
Customer Support
WalkThru Tutorials
Consulting Services
About Us
Affiliate Program
Richard Rost
Free Lessons
Mailing List
Video Tutorials
MYOLP Memberships
Idiot's Guide to Excel
Volume Discounts
Payment Info
Terms of Sale
Gift CDs
Live Chat
General Info
Support Policy
Contact Form
Email Us
Mailing Address
Phone Number
Fax Number
Course Survey
Facebook    Twitter

Google Plus    LinkedIn

Blog RSS Feed    YouTube Channel
Richard Rost Microsoft MVP