Sorry that you feel that way - we only kid around with people we like...
Hey I hope this is making a little more sense now so everyone will quit bullying me.
Anyway, my take on temp tables is that I used them for very short term in-out data movement and mostly when I needed a way to be able to retrieve a partial record with one or more 'locked in' values not allowed to be changed. Once though, it was to build a calendar sort of input form where I had to present row data as columnar inputs, so temp tables were the way to go. Sounds like you want to have them exist for a number of days or however long it takes to use up all of that original loaf. If you followed the suggestion to make the temps and bound controls drive the validation (i.e. they had the same restrictions as the main tables) I see no advantage to having them for your case. For records in progress more than a few minutes, I don't think it makes sense, based on the description of your process. Be that as it may, I would not use dashes in their names as you've indicated. This violates the general rule of no special characters in any names, save for the underscore.
As for how to present the tables, one advantage of the tab control is that you can keep the records loaded on each tab. If they're related, that could be a good thing. The other idea would dump one set in order to look at another.
I think what you've just asked is there such a thing as a recordset. When you declare a recordset you allocate memory space to that variable. When you SET it to some data source (query or table) the memory space is occupied by the records, which is why it is important to code to destroy recordsets regardless of whether execution of the procedure is normal or interrupted by an error. I read your last post as if you intend to have these sets open for long periods of time, which is not advisable to say the least. Sorry if that's incorrect, but regardless, it's easier to work with tables (temp or not) than it is to manipulate recordsets - especially if the work requires data validation. That's my take, hope it helps.is there a random access memory within VBA for records that could hold data