I was hoping to get some feedback on a scenario I'm faced with.

We have a system that needs to process barcoded cards. The users will grab a box of cards to assign some cards to a sales rep. They go into the system to create a group and wand in the cards they want to assign. There is another table that contains all the valid barcodes and if they were assigned or not.

This next part I'm a little fuzzy on since they project has been going on for some time and I'm just getting involved. But anyway's, I believe the process to put all the valid barcodes into the table doesn't check for dups. So what they are asking me to do, is add code to the grouping process to verify that a dupe hasn't occurred. I.E. that while someone is in the process of assigning a barcode, that someone else hasn't assigned it while they were in the process.

What are some recommendations for placing the 10-15 ids in a table, then once save is clicked, marking those ids as used. Should I just use the main table and mark as they are being scanned, then unmark if the user selects cancel? Build a view and append records, then have the TABLEUPDATE() fail if when it goes to update, the record is already marked as assigned?

Any help appreciated,

PF