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!
Anne