Sorry Stevie - WRONG answer!!!

One of the things we try to do as developers is to anticipate users' mistakes
and prevent or correct them. In this case, detecting a duplicate entry of a
merit badge is a trivial task - any any decent developer would include it,
and not "rely on the data entery person not to enter a duplicate merit
badge for any person."


Small wonder you have to grovel here for work, if that's the type of advice
you give.



Steve wrote:
When entering data into a database, you have to rely on the data entry
person at some point!

You need these tables:
TblPerson
PersonID
person fields

TblMeritBadge
MeritBadgeID
MeritBadgeName

TblMeritBadgeAward
MeritBadgeAwardID
PersonID
MeritBadgeID
DateMeritBadgeAwarded

You need a form/subform for entering data. Base the main form on TblPerson.
Base the subform on TblMeritBadgeAward. Set the LinkMaster and LinkChild
properties to PersonID. Use a combobox in the subform to enter MeritBadgeID.
Your form/subform will display a single person and a list of merit badges
awarded to that person. You can sort the merit badges in alphabetical order.
Now all you need do is rely on the data entery person not to enter a
duplicate merit badge for any person.

Steve


Hi all,

[quoted text clipped - 23 lines]

Dick

--
John Goddard
Ottawa, ON Canada
jrgoddard at cyberus dot ca

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/201003/1