Prior to 2010 you could do that only on a form normally in the afterupdate of the first control. However, if the values were changed in a table or query there was no way to trap that change. 2010 now has data macros at the tables level. Now with data macros you basically can trap a change in data at the table level. See here:
one question
if the first control changes to true you want the second to become false.
if the first control changes back to false then do you want to do nothing?
If so in the afterupdate of somefield
if me.somefield = true then me.someotherField = false
or if true becomes false and false becomes true like Andy shows
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.