Speaking of Dynamic Screens... :-)

I see what they are doing but it seems like they have just recreated the parent_id and child_ID approach that microsoft uses in their forms, classes, project and menus.

I have created, and am in the process of, completing an object which performs much of the same process. I use a data driven approach to design.

One object is a "redirector" pageframe, which redirects the add, change, delete, save and restore process to pageframes that are dynamically attached to it.

The pageframes that are attached to it, use a total of three pages with no visual tabs.
Page 1. A simple data driven grid design which allows sorting on columns. This is where you choose your record.

Page 2. A simple data entry form which every one is used to. No need to turn those objects on and off because the only way to enter this page is to edit the record or add the record.

Page 3. A unique reordering List box, which allows reordering of code tables to the way you want them displayed. Optional of course. e.g. If you are from Canada you would want the country list to start like Canada, United States, .... If you are from United States, United States, Mexico, Canada...

Multiple pageframes as listed above are attached to the redirector, programmatically through the data driven design. Each page on the redirector, is given a title and a hot letter (remember FoxPro 2.6 hotkeys) to access the page. Custom page objects were designed to allow for special requerying of the data when the page became active (remember this is dynamic).

My starting out page has three objects on it. All of the other objects are added programmatically/dynamically. I still need to create a few more objects to round out the data driven design.

What is the benefit of a data driven design? Want to see an application get built in a week? Lots of data entry; but if the objects do what they are suppose to do...