>I am one of those experts in 2.6 who keeps slipping back on the Visual learning curve. Can someone impart some wisdom, rules of thumb, etc. about designing views for a complex form with a main parent table, a couple of children, and many (10-15) normalized (surrogate keys) lookups.
>IOW Do I use/design basic parameterized views from each table and relate them or do one complex view that contains all the related data?
>What else should I consider when doing views for this moderately complex type of form?
>Any comments will be appreciated.
>Brent D. Smith

To handle a single one-to-many, or a complex one-to-many, my data entry forms have a property that stores the name of the parent view/table, and an array property that stores the names and PKs of child p-views. A method is used to change the record pointer or requery the main view, and that method loops through the array containing child views, and requeries each of them. If grids are bound to the child views, the grids are refreshed after the child view is requeried.