Vidar,

I use this approach as the primary UI for most of my apps. I have a one-to-many treeview class that maps data into pageframe pages as well as grids. I also use a special cursor class with my business object.

The cool thing about it is that each node of the treeview hierarchy sets the record pointer of each of the one-to-many parameterized views. Therefore, each page of a pageframe can host a record (or record set if using a grid) of each one of the views in the hierarchy.

While this approach may not make sense for all apps, it has many benefits where applicable:

[1] Not only does it force data normalization, but requires data design in terms of processes which is later represented in the UI.

[2] Provides an intuitive UI which is easy to understand and navigate.

[3] Reduces the need for other forms (albeit a few modal dialogs). The whole thing can reside on a top-level form.

[4] Simialr to other UI designs found on the Internet as well as other popular software.

[5] Other benefits which escape me at the moment.



>Ofcourse, but it isn't data bound. I would like be able to directly traverse a table using a treeview front end in the grid.