>This is one of those "does this make sense" posts as opposed to a specific question.
>
>
>Now typically with a BizObj maintentenance form that has a pageframe with multiple pages, and a BizObj on each page, you disable the BizObj on the form that comes along for the ride from the form class. But after pondering how to fit my new status log into the Design in a way that all the different page-based BizObj's can work with it when they need to I had another pretty cool thought (or so I think...) Why not make the form's default BizObj manage the status log, and set it as a child object to my process specific BizObj's on each page. As far as I can tell in my prototype this should work, but I've never done a form with 17 BizObjs (2-3 yes, but geeze not 17!)
>
>So I'm wondering if this make sense - using the form's default BizObj to manage the status log BizObj that will be a child BizObj to all others - or do I need to take a few steps back and rework my design and add the status log view to each of the other BizObj's? Any other comments welcome too.


Hmm...I >think< I understand what you're asking. I don't think I'd add a status log view to each bizobj, sounds messy. I'm wondering why you'd need to make the StatusLogObj a child of anything. I think I might just create the StatusLogObj when the form instanciates, then place the object reference in the form itself. Then before the page is displayed make a call to THISFORM.oStatusLogObj.HasProcessRun("ProcessName") (or something like that) to make your decision on what is displayed.

Just an idea...