The 'validation' is what you referred to in your first post
the form will remember restrictions I made in VBA for certain variables
so you should know what they are and where they are.
Probably in your AfterUpdate event on the form (occurs after you commit the record) you need to remove the restrictions/validations since you say you did these in code. Validations for fields that were created in the table design itself will apply regardless if the form is based on a query or the table itself, and will override code validations if those don't satisfy the table validation rules. However, the need to have validation for a field in one record but not for the same field in another record seems odd. I suspect there is an underlying design problem if this is the case.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.