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

Shamil Salakhetdinov shamil at users.mns.ru
Tue Feb 28 14:12:58 CST 2006


Yes, John, what media are used for the source data to populate your "about 3 
or 4 of the major tables"?

Shamil

----- Original Message ----- 
From: "Hale, Jim" <Jim.Hale at FleetPride.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Tuesday, February 28, 2006 9:56 PM
Subject: Re: [AccessD] Entering data in related tables in a single form


> Is the data on paper (and must be input by hand) or electronic forms 
> (where
> maybe it could be parsed quickly with Monarch?)
> Jim Hale
>
> -----Original Message-----
> From: John Colby [mailto:jwcolby at colbyconsulting.com]
> Sent: Tuesday, February 28, 2006 12:41 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Entering data in related tables in a single form
>
>
>>I suppose your base is in "bounders camp" while looking  for this "quick
> and dirty form" solution :)
>
> LOL, yea, given I am an unholy bounder, going unbound would not qualify as
> quick and dirty.
>
> I have discovered that as long as you include the PK/FK pairs, and 
> populate
> the data in the parent/child order it seems to work.
>
> This is a moderately complex database, normalized, with lookup tables etc.
> and I need to get about 3 or 4 of the major tables populated with new 
> claim
> / claimant / policy data from a ton of new claims on an "emergency" basis
> (2000 claims input in then next couple of days).
>
>
> John W. Colby
> www.ColbyConsulting.com
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
> Salakhetdinov
> Sent: Tuesday, February 28, 2006 1:36 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Entering data in related tables in a single form
>
> <<<
>> seem to remember trying this ages ago with less than stellar results.
>>>>
> John,
>
> What issues do you mean? (It should work well in MS Access with properly
> organized forms (with subforms) and maybe with a few lines of code)...
>
> I suppose your base is in "bounders camp" while looking  for this "quick 
> and
> dirty form" solution :)
>
> Shamil
>
> ----- Original Message -----
> From: "John Colby" <jwcolby at ColbyConsulting.com>
> To: "'Access Developers discussion and problem solving'"
> <accessd at databaseadvisors.com>
> Sent: Tuesday, February 28, 2006 9:02 PM
> Subject: [AccessD] Entering data in related tables in a single form
>
>
>>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
>>
>>
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> ***********************************************************************
> The information transmitted is intended solely for the individual or
> entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or
> other use of or taking action in reliance upon this information by
> persons or entities other than the intended recipient is prohibited.
> If you have received this email in error please contact the sender and
> delete the material from any computer. As a recipient of this email,
> you are responsible for screening its contents and the contents of any
> attachments for the presence of viruses. No liability is accepted for
> any damages caused by any virus transmitted by this email.
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com 




More information about the AccessD mailing list