|
|
Posted by Erland Sommarskog on 06/29/05 00:52
Pritcham (dontwanttogivemyname@hotmail.com) writes:
> My difficulty is that they want to be able to store names/details of
> people looking for work (candidates) BUT these people may also be a
> contact (i.e. the agency could be dealing with a contact at a company
> who is also looking for a new job themselves). They would also like to
> (naturally) have these candidates details held against 'current
> employer' customer details so there may be situations where a candidate
> is JUST a candidate (i.e. not currently working and therefore not
> associated to a company), OR they may be a candidate AND a contact, and
> you may have contacts who are JUST contacts (i.e. not actively looking
> for work at the moment).
>
> I'm basically just trying to figure out the options I have for storing
> the contact details and candidate details.
>
> FYI I need to store the same details for Contacts and Candidates (i.e.
> name, job title, contact numbers etc) but Candidates require extra
> information to be stored about them (work experience, qualifications
> etc).
My gut reaction is that you should have a Persons details, where you
have all common information about persons, and then Contacts and
Candidates would refer to that table and augment it with the specific
information.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|