@Richard D how would you read a recordset and assign the data from the record into the field if you have seperate container control for each page panel??
i understand if the different page has information from different table but what about one record with lots of information for each page panel. this apply to new record or editing existing records.
Just like everything else, you have Load/Save methods on your Containers that you pass the information to. We do this with ActiveRecord ALL the time. And if there's any validation that we need to for the UI the validate method is in the Container as well. So yeah, your Window load method will be a lot of:
dataobject = db.somequery
But this has the advantage of isolating the code to the container. So if the window overall has 1000 controls but Container1 has 20 controls, debugging the Container is much easier and any exceptions related to code in that container are much easier to figure out then if your Window is dealing with all 1000 controls.
If the UI on Container1 has to change because of something on Container3 we implement an event on Container3 so the parent Window/Container can get the event and tell Container1 to do whatever changes.
I think many Xojo developers underutilize Container Controls. They are very powerful and very useful - especially with a UI that's busy and complex. I gladly trade off needing more code to make it simpler to work with (if that makes sense).