On a form I developed, I want to do some cross-field dependencies. If
field1 = "xxx" then field2 must be "yyyy" and so forth. Apparently I
cannot do that in field properties via the validation as you cannot
refer to other fields in a form. Right now I am doing these in a
"BeforeUpdate" VBA routing. However, the update continues and the error
message becomes informational - not a "fatal" error.
Anyone have a better way of doing such, especially a way to stop the
update and ensure that the changes get made to the edit rule is passed?
Thanks.
Bob Alston
bobalston9 AT aol D O T com