Some good info guys. I will try capturing the error, and see what I can do with it.
I have begun building the completly upbound solution - but agree, it is a lot of work, and not as slick to the end user as my current solution. My current screen filters for date, shift and associate. How do I go about implementing your INSERT with code in this example, with a continuous form.

I would also like to try and understand what is...

I have researched a lot about page and record locking, and I think I have my setup correct. Rewritting the database to work in an entirely different fashion is a possibility, but I like how this database currently works (when it works - which is 99% of the time) - wondering if I can find a true solution.
Is there something to do with multiple default fields? - given the behaviour I described in the original post.
I have indexed a number...

I have a continuous bound form on a FE stored on desktop of each user PC. The BE sits on a local network drive.
I have the default record locking to "No Locks" and Open Database Using Record Level locking.

All appears to work well, but periodically (several times a day) a user will get the message "Could not update; currently locked" (no error number).
This error seems to only occur as the first character...