I have a db I wrote for tracking inventory. I have a form that allows the user to scan or type in a serial number, I then use a query to find the item in the db. I have a subform that shows the item/items with additional details about the item. Once the item is found and the sub form is populated the user can check a yes/no field for that item to track that is has been removed from inventory. This form works fine, the users have been using it for months now. Their request is to speed this process up. They have to scan each item, then check the box, then scan the next item, check the box ...... This can be time consuming. They would like a batch update feature. So what they want is to scan an item, then it show up in the subform, scan another time, it then shows up in the subform, on on and on. After adding as many items as they like, they want to push a button to transfer all items out of stock(ie check the yes no tick box for all items scanned). So my current query runs on the inventory table and returns the matching serial number record. Now I know that I could write Some VBA code that just keeps adding an OR to the where clause with additional serial numbers. This seems to be the fastest way to make this change. However I would assume there is some limit to how long an SQL statement can be, or how many ORs that can be in a where clause. If not then I have to assume if they scanned in hundreds of items at once and the SQL statement just kept getting larger and larger that may be a problem. So my question is more of a best practice question as as apposed to how to question. Is contentiously adding an OR clause to the SQL statement like that OK? Or does anyone have other ideas on how to do something like this? Thank You