[AccessD] design/development question on representing mtmrelationships

Charlotte Foust cfoust at infostatsystems.com
Wed Jun 30 10:29:30 CDT 2004


Susan,

What do you mean by the "one" side?  In a many to many relationship,
there are TWO "one" sides.  Logically, you can't enter a "many" side
without having a "one" side to link it to, can you?

Charlotte Foust

-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net] 
Sent: Wednesday, June 30, 2004 4:11 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] design/development question on representing
mtmrelationships


During a training session yesterday I had someone ask me what the
easiest and best way to represent a many-to-many relationship for data
entry. I admit, I was a little stumped and replied that the form/subform
was probably still the standard solution but he's got me wondering --
how does everyone else handle it? I can't see any reason to really defer
from the form/subform, but now I'm curious what creative solutions
others might use. 
 
The other question I have -- and this one's my own -- I know there are a
few easy ways to handle new primary key values when entering the many
side of the relationship first -- pop up forms probably being the most
common and even combo box controls that allow new values -- what do you
guys do? Do any of you force the users to enter the one side first,
which often seems a bit unnatural to the data entry operator? 
 
These aren't really technical questions, so much as they are just
design/solution type questions. I'm interested in hearing what other
people do. 
 
Susan H. 
-- 
_______________________________________________
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