multiple subforms or updateable queries

[TonyT]

Hello,

Is there a 'best practice' when it comes to creating forms based on many
different tables? Generally I try to use as few subforms as possible, using
them when I can no longer create a single updateable query. (Often resorting
to code when I know I should use a subform).

Also, how many subforms do you typically use on complex forms? And how often
do you use subforms within subforms?

I'm going round in circles trying to work out the most efficient way of
doing a form at the moment that is based on one table, that is a parent of
another table, that then has numerous other lookup tables, link tables, child
tables and another parent table itself. It's the many to many link tables
that cause the headache, I'm thinking they should each have their own suborm
and then further subforms within them if required.

Any guidance on the best theoretical approaches much appreciated.

 

[June7 via AccessMonster.com]

Certainly varies according to need. I have one project with a form that has 5
subforms. I have never had to resort to subsubforms. Perhaps use of popup
forms in dialog mode would be applicable in some cases. Lookup tables should
not be an issue as they are simply a source of RowSource data for combo and
list boxes.

 

[June7 via AccessMonster.com]

Correction to my statement re lookup tables: This was my perception of what a
lookup table is but apparently others view differently.

Certainly varies according to need. I have one project with a form that has 5
subforms. I have never had to resort to subsubforms. Perhaps use of popup
forms in dialog mode would be applicable in some cases. Lookup tables should
not be an issue as they are simply a source of RowSource data for combo and
list boxes.

Hello,

[quoted text clipped - 14 lines]

Any guidance on the best theoretical approaches much appreciated.