View Single Post
  #6  
Old February 21st, 2010, 01:28 AM posted to microsoft.public.access.tablesdbdesign
Al Campagna[_2_]
external usenet poster
 
Posts: 1,462
Default 1 to 5 relationship

Check out John's response... regarding using the BeforeUpdate event
to prevent a sixth entry per team.
There is no property that will limit a table to five entries per team.
--
hth
Al Campagna
Microsoft Access MVP 2007-2009
http://home.comcast.net/~cccsolutions/index.html

"Find a job that you love... and you'll never work a day in your life."

"Loterken" wrote in message
...
indeed i mistyped on my original post, corrected on the reply to myself
team is the 1 side, person is the many sides
so team has only 1 field (ID), the primary key (of course there are more
fields)
person has among others a field (TeamID), a foreign key
the problem is,that allows a team to have a whole lot of persons
but a team may not have more than 5 persons
i solved it by not allowing the user to give the same team to more than 5
users
i did that by using code in my program (vb6)
i am wondering if there is a way to have a constraint on the person table
that would not allow more then 5 teamID
i thougt of putting 5 person fields in the team table, but that would
violate 1NF