On Jan 30, 2008, at 12:37 PM, Adrian Klaver wrote:
> I set up a test field validation to learn how it works. It tests for
> an empty
> string and then does self.notifyUser(). It works well except for one
> case. If
> I navigate to record that already has an empty string in the field I
> am
> validating, then tabbing through that field does not invoke the
> validation.
> If I Ctrl+d and do self.validateField(self.Common) where Common is
> the RegID
> of the field then the validation fires. I was wondering what causes
> self.validateField to fire when navigating through the form?
It only validates changed values. The assumption is that if the value
hasn't changed, there isn't anything to test: either it's existing
data and the user shouldn't be responsible for what's already there,
or it's data that validation has already caught and handled, so there
is no need to re-catch it. For the latter case, imagine that you want
to display a warning if some type of value is entered, but not
prohibit it. Once the user sees the warning and acknowledges it, they
shouldn't have to repeat that if theytab through the form again.
-- Ed
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
