At the moment, this is correct.  There was an issue a while back with multiple handlers be managed and when this change was made the CheckRulesOnCurrentRow stopped showing the red error window.  This is something that is on the "to-look-at" list.

Yes, if I manually check CheckRulesOnRow(True), the broken rules do display beside the appropriate field, but I do not get the error information window, but if I just call Save(), I do not get the broken rules.

Tim

It's most likely a configuration issue, or an issue with the IsChildForm property being set on the child form.  When we use the ChildFormDialog, it is generally because we want to be able to edit a child record and return from the form without saving the record.  However, you want to test the business logic before the form closes.  So, we generally call the CheckRulesOnRow() method and test the return value to return from the form. 

So, if you manually call CheckRulesOnRow(), does the error provider display the broken rules?

I have a application which uses a child form to edit BO fields.  On the business object I have added some broken rules logic.  When I save the business object, I can see the broken rules logic is executing properly, and it does add the broken rule, however the application doesn't navigate to the broken rule.  (Warnings do not appear on the screen). 

The 'AutoNavigateToFirstBrokenRule' property on both business objects = True and the data is NOT saved.  Any Ideas's... 

I have other applications working fine using the same logic, but for some reason this particular program is not stopping to show broken rules.

Thanks

Tim