Hey Miyako > I may be missing some critical elements of your design, but given the basic > construct of a tab control parent and a subform child: > > - I would remove "goto page" as the tab control's standard action and keep > the parent on page 1 at all times. > - I would either use the same process variable for the tab and subform, or > else execute subform:=subform in the tab's object method. > - I would use a single subform with multiple pages rather than switch > subforms. > - I would centralise code to switch pages in the subform's on bound variable > change event. > - I would refrain from using GOTO PAGE(*) and adhere to the data change/bound > variable change model as much as possible.
My instinct wants to keep the pages as separate subforms as I like how it works (well prior to this issue). But I am willing to reconsider moving all the pages into a single form and try it and see. If I went that way then I would’t need a container to manage swapping the subforms as there would only be a single subform. I could have that directly placed upon the parent form. I think I will take a few more days off and when I return look at it with fresh eyes. Appreciate, John… ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
