Thomas,

That's a good idea if the bizobj only has one method to trigger, click it for testing I'll have to remember that little jewel. These objects could also bring up a context sensitive menu on rightclick to choose what BR method to run.

>Making them visible is just a way to fire rules individually. You'ld get the same effect if you AddObject() a standard commandbutton onto your container calling your standard busrulemethod on the buttons .parent in the click - which probably is a better design, since it allows aggregation in the "small" rule objects as well. Since "my" click also fires my polymorph "busrulemethod" both approaches are not too different - but it helps tremendously to be able to fire specific business rule methods directly from the GUI to find the errors... Give it a try sometimes: if you have a pageframe, add a page with your bus rules container[s]and add controls to interactively fire them. Presto: RAD for the bus layer <g>. Much better than to set breakpoints and let the debugger stop you into the interesting parts.
>
>>If they are created via CreateObject() they can't be visible.
>Which is not a bad thing in the finished product, if you never want to use the debugger and the visible "interface" later on. It cuts to ways <g>.