I have a pool of people that need to be contacted based on a specific criteria. when I have only 1 person contacting them I just create a command button that generates a result set and the user presses it and just works the records.

When I have had a few people doing it, I would divvy up the records with the users id and then add userid to the search button and all would be good.

My problem now is I have a need to have many people work a list and do not want to initially assign a user to the pool of records, I just want a user to get the next available record and once they start working it I will have code assign it to them.

My problem is that when multiple people  press a command button without the unique user Id they all get the same list and the record locked feature gets a big workout (not sure if that is a problem) I think a better solution would be to have a button that only retrieves 1 available record at a time, and each time the user is ready to contact another record they would press the button again.

I believe my best solution would be to have a field that is used to show the record is available and when the command button is pressed it would loop through the records and grab just 1.
I am not sure the best  way to loop through the records to get just one.

Any thoughts on a better method or idea on best way to get 1 at a time would be greatly appreciated.

Thanks

You might also consider using a GlobalValue to hold a list of the records that need to be updated (by unique ID). As each client handles a record, it removes it from the list -- updating the list.