Qry /forms Question

[GaryPanic]

OK guys - newish project
i have a new project and I cna approach it from a couple of angles - but would appricate an alternative view

i have an instance where I could have an product (insurance)
the accounts and clauses /tax etc are sorted ...
but the actual product(s) has some variables

the largest product has 11 sections in
each section could have up to 10 elements in it
example
Section 1
Building Value, Premium Rate, and Excess
Contents Value, Premium Rate, and Excess
Stock Value, Premium rate, and excess
etc......... ( upto 10 /12 elements each with a value, rate and excess )
Section 1 Premium - the sum of the above etc --this I am thinking as having a stored value at the moment - - but that aside

My first thoughts where 1 large table but it would i think be too big I think to easliy manage - Table thing and long approach -
so i though chop the sections into bit sizes (some of the sections have 4 fields in and other more )

i have 30 items and 30 rates and 30 different excesses - making 90 fields or so

so my form I can enter in data name address etc....
and I have tested adding in a simple outline of the data all based on qry's (2 so far) - my main question is ,, is there a limit to the number of qry's I can stich together on making the form ?and entering data that populates the underlying tables

if there isn't then i could group some of the sections together

(I don't really want to have 11 sections / tables and 11 qry's - but i can club some of these together )



To make it more awkward - but there are 5/6 products some have most of the products and some only have 6 fields out of the 90 or so - I intended to put the data field on tab's and if x product is selected then only that tab will be visible ( easy)
any pointers/tips
regards

 

[Beetle]

My first thoughts where 1 large table but it would i think be too big I think to easliy manage - Table thing and long approach -
so i though chop the sections into bit sizes (some of the sections have 4 fields in and other more )

i have 30 items and 30 rates and 30 different excesses - making 90 fields or so

Maybe I'm missing something, but I'm struggling to see how you have any given table with more than a few fields in this model.

You have clients, so you need a Clients table;

tblClients
*******
ClientID (PK)
FirstName
LastName
BirthDate
Address
City
State
* a few other fields necessary to describe a Client

Each Client can have (maybe) more than one Policy, so you need a Policies table;

tblPolicies
********
PolicyID (PK)
ClientID (FK to tblClients)
PolicyType (life, auto, property, whatever)
StartDate
Term (6 months, 1 year, whatever)
* a few more fields to describe a Policy

Each Policy can have more than one Section, so a Sections table;

tblSections
********
SectionID (PK)
PolicyID (FK to tblPolicies)
Description (Section 1, 2, etc)
* a few other fields (if needed) to describe a Section

Each Section can have more than one Element, so a table for that relationship, plus maybe a lookup table for the Element descriptions;

tblSectionDetails
************
DetailID (PK)
SectionID (FK to tblSections)
ElementID (FK to tblElements)
ElementValue
ElementRate
ElementExcess

tblElements
*********
ElementID (PK)
Description (Building, Contents, Stock, whatever)

Again, I might be missing something, but as far as I can gather from your description, the above should be a basic model for this project.