[AccessD] Confused by One to Many versus One to One

Tony Septav TSeptav at Uniserve.com
Wed Jan 7 16:48:21 CST 2015


Hey Susan
All the best for you and your family in the Hew Year.

How much we forget the good things in life.

Tony Septav
Nanaimo,BC
Canada

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: January-04-15 6:42 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Confused by One to Many versus One to One

I hadn't thought of it, but you're probably right. I think I already have
the index in place to tell the truth. :) Thanks for mentioning it!

Susan H.

On Sun, Jan 4, 2015 at 6:49 PM, Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> Susan,
>
> You could probably use one in your in Salato database if it were larger.
> Keep disposal details
> in a second table for example.  :)
>
> On 4 Jan 2015 at 11:10, Susan Harkins wrote:
>
> > I don't have the serious development experience that most of you have,
> > so my 2 cents is really just 2 cents, but in my experience, 1 to 1
> > relationships are the result of business rules and not something the
> > data itself requires. I've only had to deal with one once. Charlotte,
> > I think we wrote about them, didn't we? I tried to find something
> > online, but couldn't. Perhaps it was in Inside Access -- just don't
> > remember.
> >
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5577 / Virus Database: 4257/8847 - Release Date: 01/01/15



More information about the AccessD mailing list