If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
multiple subforms or updateable queries
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. |
#2
|
|||
|
|||
multiple subforms or updateable queries
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. TonyT wrote: 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. -- Message posted via http://www.accessmonster.com |
#3
|
|||
|
|||
multiple subforms or updateable queries
Correction to my statement re lookup tables: This was my perception of what a
lookup table is but apparently others view differently. June7 wrote: 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. -- Message posted via http://www.accessmonster.com |
Thread Tools | |
Display Modes | |
|
|