>For example, after a new employee is entered (hired) a work flow record would be created for the person that has the 'task' of say Creating Tax Records for the new hire. My thought was a bizrule could be added to each class that would have the code to deal with reading work flow rules and creating tasks.
>
>Or am I just kludging the design cause a biz rule class is an easy place to provide common functionality for many bizobjs?

PMFJI -

Yeah, in that situation it I wouldn't classify those as business rules. They are more like behaviors.

>Also, to follow, as you say something like 'validating an email address field' would you consider that a business rule, or data integrity/validation? If so, it there an easier way to tie validation like that to a field. I know that datasets are supposed to inheriet constraints from SQL server.

Good question. I would say it can be both. But, since the data in the database can still "function" even if someone entered a bad e-mail address, I'd be more likely to consider this a business rule.

>
>Thanks, I'll keep reading the doc... it looks very similar to VFP MM and like something I could pick up very quickly. I'll keep reading the docs, look for my order soon.
>

It has the feel of the earlier versions of MM (or even Codebook), before all the builders got added.