It seems to me you would need an additional field, to mark which records are "locked" or "checked out".

>I have a table called Resh (Results History). The records
>are grouped by batchid.
>
>Multiply users are going to make updates to this table, and
>I want to allow a user to pull a desired number of records
>from the Resh table. After the desired number of records are
>selected, I want to 'lock' the original records in the Resh
>table so that no one else can get them.
>
>For example, user Jane opens the app and see that there are
>5000 records in batch 123. She pulls 1000 records. User Joe
>now only sees 4000 records in batch 123, and pulls 2000, user
>Willy then opens the app and sees 2000 in batch 123 and pulls
>the rest.
>
>Since the working records are locked for the user, they can be
>pulled into a local table for faster performance.
>
>Also, the users have the option of adding records. The newly added
>records are stored in a network temp table, so that anyone opening
>the batch lood screen sees these records as if they are in the
>production data.
>
>Then, as a user makes an update, that update is also stored on the
>network in a temp table, so that the other users may also see the changes.
>
>I could use help with the SQL commands to pull the data.
>
>Many Thanks