MarkK
bit cruncher
- Local time
- Yesterday, 21:07
- Joined
- Mar 17, 2004
- Messages
- 8,571
FWIW, it's unusual to have a subform on a subform on a subform. When you look at actual workflow in a computer system, a user typically performs a task, usually repetitively, like entering a new order, that is most commonly concerned with a thing and its first level of child related things. An Order has OrderDetails, a Class has Students, a Company has Employees, a Job might have JobSections, or JobExpenses.
Once you drill down to the third level, make a new main form. So yeah, a Student has many classes, but if the main form is Class, and the subform is Student, don't add Classes as a nested sub-sub-form of the student subform. Make a Student main form with Classes subform. See what I mean? It's a different workflow. Give it a different interface.
That third level is too deep. A bridge too far. IMO.
Once you drill down to the third level, make a new main form. So yeah, a Student has many classes, but if the main form is Class, and the subform is Student, don't add Classes as a nested sub-sub-form of the student subform. Make a Student main form with Classes subform. See what I mean? It's a different workflow. Give it a different interface.
That third level is too deep. A bridge too far. IMO.