Best way to handle multi-user 'queue' application?

[planetthoughtful]

Hi All,

I'm building an app in Acc2K3 (with an SQLServer 2000 backend) that
will be used by several users to action error records in a queue.

The only real issue I need to accommodate is that each error record
should only be actionable by one user, so I need to build logic in that
if User A is actioning Record 0002, when User B finishes processing his
or her record, the next record presented to him or her will not be
0002, since that is already being actioned by User A.

Usually I would handle this by updating a status field to a value
equating to 'being actioned' in the error queue table, then reading
that record onto an unbound form, so that anyone who then completes a
record will not be presented with this record, since it has a status of
'being actioned' as opposed to 'waiting to be actioned.'

However, I'm curious how others would approach this situation? While
the situation is probably unlikely, I'm worried about the possibility
that User A and User B may finish actioning a record simultaneously,
and end up processing the same record.

Any feedback / suggestions appreciated!

Regards,

pt