[AccessD] Entering data in related tables in a single form

Rocky,

There are a hand full of tables that this data will initially go into.
There is a new table called "underwriter" which is "parent to" Policy (what
insurance company wrote the policy).  There is also policy holder (what
company / individual owns the policy?).  Then the policy table.  There is a
claimant table (who is filing the claim) and a Claim table (details about
the claim).  Claim is child to claimant as well as child to policy (kind
of).  

There is actually a ProductType lookup which contains a "business block"
name, and the policy is related to the claim through a M2M with this product
type.  Insurance is a strange duck.  Lawyers write contracts (policies),
which might be just short term disability, just long term disability or
both.  Thus the same policy could have claims against it for short term and
long term and they are processed differently.  There are in fact about 15
product types and counting.  So Policy and Product type come together in a
m2m and the PK of that is a FK in the claim table.  THAT is the ugliest
piece of this whole database.  Well... Maybe not but you don't want to hear
it.  ;-)

All of these tables potentially need data inserted.  In fact tables like
Underwriter have just perhaps a dozen insurance company names in it, which
will then be selected by a combo in the policy form.  Policy holder though
already has several thousand records and will have an unknown number added
from these files.

So no, definitely not a simple structure here.


John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin -
Beach Access Software
Sent: Tuesday, February 28, 2006 9:23 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Entering data in related tables in a single form

John:

Can you force the user to create the parent record (at least as far as the
insert event so you have a PK) by making the sub-forms bound to the child
tables disabled until the parent record is created and you have the PK in
hand?

Is it one primary parent table with several one-to-many child tables?

Rocky


John Colby wrote:
> I need a quick and dirty form to enter data into a whole set of 
> related data tables.  Policy holder, policy, claim, claimant etc.
>
> Is this possible?  Obviously I have relational integrity turned on so 
> the PKs have to exist in the "parent" tables before they can be used 
> to enter data into the child tables.  I seem to remember trying this 
> ages ago with less than stellar results.  Has anyone here done 
> something like this, and if so how?
>
> John W. Colby
> www.ColbyConsulting.com
>
>
>   

--
Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com