Hello, 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. > 2017/12/25 1:37、truegold via 4D_Tech <[email protected]> のメール： > I have a parent form which has a subform container. Above the subform > container is a tab control object (5 tabs). Clicking on a tab selects the tab > an triggers (underlying code) a change to the underlying subform. Works great. > > But I discovered I need one of the subform pages, let’s call it “Edits”, to > change, based upon a different context, to either a different page or a > different subform using code. The key here is that some action in the parent > form needs to cause the subform container to display a different form. ********************************************************************** 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] **********************************************************************
