<i>However, it is a <b>huge</b> disadvantage when you try to force the framework to fit your notion of how you want things to work. That's why I say that it isn't a good idea to learn while creating a production app.
</i>
I'm not trying to FORCE anything -- just understand how to make my form work within it.
<i> The navbutton toolbar is designed to work with the primary bizobj of the form. Period. If your "child" bizobj is the one referenced in the form's oBizobj property, then yes, they will work. </i>
Fixed by adding my own simple navigation buttons.
However, if the navbuttons should work with the Primary bizobj for the form -- w;ether it is a child or not, they don't they only see the parent. --- I re-confirmed that the Primary BizObj of each form is the CHILD that the data on the form displays and the generic navbuttons disable themselves (I believe using the one record case)
Just FYI, that if your desired behavior is the buttons correspond to the Primary BizObj for form -- it doesn't
Lynette
ltillner /AT/ yahoo D.OT com
©2002 Lynette Tillner |
