This helped a lot. My solution was not too eloquent. I made a query that
found the next record in the series and then I used SetValue on the form to
populate a field, had it go to a new record and then back to the record in
question. That caused the next person to run the query to look to the next
record because the query thought that one was already populated. If you have
a better solution I am all ears...this one seems a bit clumsy to me.

"Jerry Whittle" wrote:

Are these records actually new or records already created and needing
updating or something?

If already there, I'm assuming that there's something in the query that
looks for a field which shows the record complete or something. If someone is
working on the record, but it isn't complete yet, that field will be open or
something and the query will pick on it. You may have to immediately save the
record with the field in question populated to stop this from happening.
However if someone opens the record then changes their mind, you may have a
problem with records getting skipped over.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"rwtrader" wrote:

I am trying in a multi-user environment to have each user able to add data to
the next available, unlocked record. I am thinking this is a query, but not
sure. I am set to share the database with record-level locking. I have a
query that finds the next available record, but when another user runs the
query, it chooses the same record even though another user is entering data.
Obviously it creates an error later, but I want to avoid the error altogether
by having each sequential user that runs that query to enter data on the
next, unlocked (unused) record. Can anyone help? I am not sophisticated in
Access, so the simpler the solution, the better...thanks!