July 27, 200718 yr This one's had me stumped for a couple months. It SEEMS like it should be doable, but I can't get it. I would like to be able to validate ItemID on new assignments such that the same ItemID is never assigned more than once to any given translator (TransName). ItemID and TransName are associated via the ASSIGNMENTS table. All feedback humbly and gratefully welcomed. Sample file attached. Names have been changed, etc. Husk_of_PROJECTS_active.zip
July 27, 200718 yr Author Many thanks for the swift solution, comment! Your method 1 looks like it will do the job nicely, and without fuss. Exactly the breakthrough I needed! 1. In the Appointments table, define a text field, set it to auto-enter a calculated value = CustID & "|" & GetAsNumber ( AppointmentDate ) & "|" & AppointmentTime Uncheck the "Do not replace existing value.." option. Set the field's validation to 'Unique value'. uniqueCalc.fp7.zip (4.38 KB)
July 27, 200718 yr Comment Ditto for me. I've started using this technique recently and it is so simple and powerful. Strength through field-level validation. Interface validation is weak!
July 27, 200718 yr Interface validation is weak! True, but field-level validation is annoying and confusing to the user, so it's a dilemma. Probably best to use both, keeping field-level validation as the last line of defense.
Create an account or sign in to comment