Ed Leafe wrote: > I think that we shouldn't code to exceptions. The only reason that > the call to activeControlValid() was needed is because of the order of > event firing didn't match what we needed. Most of the time, though, it > works just fine.
Not coding to exceptions, but adding something perhaps overlooked. The fact that Nate is calling moveToPK() *from the UI* tells me that we have a candidate for a UI wrapper. > I also don't think that controls on a form should know about PKs, > datasets, and the like. It wouldn't know about PK's, any more than it knows about row numbers, as in the moveToRowNumber() function. > They should at most call a form method to > handle their being clicked or typed in or whatever. They shouldn't > have to know that their node contains a PK and that when they are > clicked they need to talk to a bizobj, etc. They should simply call a > form method in their handler, and let the form take it from there. Right, by calling self.moveToPK(). Paul _______________________________________________ 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/[email protected]
