Anthony,

>So I’m thinking that either it should be hooked up and was forgotten to, or it was added just as an example and I the developer can hook it up if I need to.

Yes I agree this was probably used as an example and not carried out as a pure "BizRule Class" way of doing things. Look in the userid TextBox.Valid method on page2 of the cUsersForm for how the call is made in this case. The MM framework has incorporated at least a couple of ways of determining if a value is unique throughout its evolution. One is tied to a control on a form, the other to the bizrule class. This one appears to be a combination of the two.

The Rules class has worked very well for me for a variety of validation checks. It's simple, keeps everything in one place and is part of the bizobj instead of the form. The only thing I don't like is clicking the cancel button on a form does not stop the validation check. You must satisfy the check before you can navigate off of the page. I haven't spent any time looking into how to change this behaviour. Suggestions?

I did learn a valuable lesson when working with unique search views within a bizobj which prompted a personal note in my Developers Guide: "You must define the primary key field for each of the search views in the business object builder. Leaving any of them empty will cause lots of tiredhead!"

Steve