Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 Old Forums
 CLOSED - General SQL Server
 Problem with relationships
 Forum Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

Ask SQLTeam Question

0 Posts

Posted - 05/02/2005 :  07:28:49  Show Profile  Visit AskSQLTeam's Homepage
john writes "hi!
I am using WIN XP-PROF, sql-2000. I stuck with a problem.
I designed tables like the ones below ..

Personal Details table
MemberID Name Tel Fax
1 Karthik 0201... 1240..
2 Watson 02081.. 1245..
3 Andrew 343... 3444..
....and so on for ten more members (say).

and other table goes like this

Selected Credits table
CreditID Title Director Description
1 Band Aid 20 Karthik 60mins Documentary.Channel 4
2 Cosmic Relief Karthik 60mins Documentary.BBC TV

This is a CV design page of directors. Now each candidate can enter as many selected credits as they like say maximum 6 or 7.So if karthik has directed 6 films (say)and Watson has directed 5 films (say) and so on the rest .
My Question is how should i relate each person with his own selected credits. I need to display his CV with all his selected credits and personal details. I need to do for 50 people like that . I cant relate them in any way to extract the information of single person.
Are there any ideas to solve this problem.
I would really appreciate your help
thanks in advance.

John "

Flowing Fount of Yak Knowledge

6065 Posts

Posted - 05/02/2005 :  13:42:52  Show Profile
I'm not sure I understand the problem but...

If each row of the selectedCredits table can only belong to 1 MemberID then you could add MemberID (as a foreign key) to the SelectedCredits table.

If 1 row of the selectedCredits table can belong to more than one MemberID then you will need an association table ie: MemberCredit (memberid, creditid)

Is that what you're looking for?

As far as your "problem with relationships", join the club.

Be One with the Optimizer

Edited by - TG on 05/02/2005 13:45:20
Go to Top of Page
  Previous Topic Topic Next Topic  
 Forum Locked
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000