Paul,

The user would not have access to the business rule validation. The user should never see these messages, if I do my job right, because the have nothing to do with the interface. I just want the system to tell me I didn't set a link field instead of me having to check everything manually. Isn't that what programming is all about, having the computer do the work?


Thanks

Rex
>>Kevin,
>>
>>In the manual you say to use the PreSaveHook to populate default values, say in the KMoverObj. If you use the business rule objects to cover all cases, one of the rules should be that the foreign keys are not left blank. This is why the PreSaveHook needs to be run before the business rule check. If this is a problem, you could always run the rules check within the PreSaveHook.
>>
>>Just a thought
>>
>
> I don't know that I'd ever use business rules that way. Filling in the FK's is a job my application should be doing - it's not something that the user should have access to. I tend to think of the business rules as validating all the data the user can enter or have access to via the UI. FK's don't seem to fit in that category, especially if you need to write special code anyways to fill them in based on some UI element. In those cases, I'd validate against that element, not the DB structure.