How about just simply adding a yes/no checkbox field to the record? You can just check off the ones that are done, or at least where you left off.

What I have done in the past is use the SettingT table. You could make a button and when you are done for the day, click the button, it will save the ID to the SettingT table using PutSetting , and then you could load it when you are ready to work on it again with GetSetting. App Settings

Almost every one of my tables that I create has a field, like Richard suggested, for a Yes/No check box called Tsel and that stands for Client Selection (T = client). Every form touches that field with a check box in the top right corner so people that can only work in a form can flag a record that needs attention. Somebody working in the table could use the same field as a Yes/No for needs attention. I use it all the time in development for testing fixes or as a reminder.

Great suggestions.  Thanks all.

When I read the title, I immediately thought....TempVars!  I guess I've been properly trained.  LOL!!!

Here is my $0.02 on TempVars. They were a great feature that Access needed, that wasn't there in the first versions, although they had lots of variables both global and modular. The problem with those variables was once there is a reset, crash or the program has ended those variable values were lost.

I think you want to use TempVars for data that are relatively permanent independent of any particular form or report that you might run. I tend to load TempVars when someone logs on with some environmental variables that I always want to have available without having to do a lot of coding or calling subroutines each time one is needed. It comes in handy during development, when I reset using the VBA Editor. My menu form can then start again without having to reset all the environmental variables I have in my applications. Otherwise, global variables are there for objects that lack permanence.

TempVars isn't good for remembering data once the Access db shuts down, so they don't serve for the OP's question. That's what table fields are for.