Sounds like you are trying to do something with a combo that it wasn't designed for. Once the row source is created (be that value list or table or query based on a table) it becomes the list items as you've no doubt discovered. To add to the list with the Not In List event is fine, but to edit the list you should be going back to the source- and the source should have a primary key that does not change when the combo's displayed value is edited. If you bind this combo to a field and alter a value in the list after you've stored it, you can cause all kinds of problems. I'm not understanding why you don't just have R hand 3lbs and R hand 2lbs in the list. You can alter the combo value if it's bound to a field as long as the Limit To List property is not set to Yes/True, but as I said, you might cause issues down the road. Ideally, you would have a form for editing/appending values in lookup tables (not lookup fields in tables) or a form that does this for all such tables if there aren't too many of them.
Last edited by Micron; 12-06-2019 at 06:44 PM.
Reason: clarification
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.