Strasser replies: Thanks...Your suggestion will not allow grouping such as "for source A, who did she suggest I call?
--- In [email protected], "Keith Browning" <[EMAIL PROTECTED]> wrote: > > Wow I see many copies of your question here. > Having the same multiple message problem with other Yahoo groups too. > > Back to your problem. > Could you make a database using one name and address etc. > Have a bunch of check boxes or something to denote different statuses for the person. > The information relating to a "status" could be held in that status related table > ???? > Keith > > > > > ----- Original Message ----- > From: "wsfstrasser" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Thursday, March 29, 2007 10:29 AM > Subject: [ms_access] ER question: same person wears "different hats". Job applicant <==> Reference > > > I know same person should not be entered twice, but I don't know what > else to do. > I have a little job search database. > Applicants are in one table. > > Also have to keep track (group and do counts on) people who act as > "sources" for job applicants (source = person who suggests I make > contact with an individual who might apply for a job). > Similarly have to keep track of "references" for job applicants > (she/he worked for me). > > Frequently individuals "wear different hats": > 1) apply for several jobs > 2) and/or suggest people who I should contact as job applicant > 3) any/or act as reference for job applicant > > Reports include who was best source? who was used as a reference the > most? which applicant was suggested the most by sources? how many > and who were the references for the applicants for job positions? > > My solution was to create a tblApplicants and a tblNon-Applicants > related in a "many:many" relationship. > > Records of individuals in tblNon-Applicants include the following 2 > check boxes. Individuals recorded in tblNon-Applicants can act as > either a source or act as a reference or act as BOTH, for multiple job > applicants. > > Reporting works fine, but any change in an individual's phone number > or address must be done in both tables: tblApplicants and > tblNon-Applicants. > > Any ideas? > Database is working with the two tables but, although changes and > searching for discrepancies for the same individual recorded in both > tables is automated, the redundant data makes me very uncomfortable. > Thanks in advance. > > > > > Yahoo! Groups Links > > > > > > __________ NOD32 2150 (20070328) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com >
