First, I'd change the design of the database because currently each
company can only have one salesperson. Remove the SalespersonID field
from the Companies table and add a CompanyID to the Salespeople table.
Then you can have more then one salesperson with the same CompanyID,
which is a one-to-many relationship between Companies and Salespeople.
You could then implement this in your .NET code as having a Company
object which holds a reference to a list of SalesPerson objects, for
example:
List<SalesPersonsalespeople;
This type of relationship between Companies and Salespeople is called
"composition".
--
Chris Fulstow
MCP, MCTS
http://chrisfulstow.blogspot.com/
Nemisis wrote:
Hi all,
I am trying to work out whether my objects whould contain child objects
or just an ID property to the linking object.
I have the following table in my SQL database
tblCompany
ID
Name
SalespersonID
Then a have tblSalesPerson
tblSalesPerson
ID
FirstName
LastName
If i am going to design this, is it best OOP practice to include the
SalesPersonID within the Company object, or would i create a
CompanySalesperson object within the company object.
If anyone has a good article to read on this, or can explain it too me,
i would really really really appreicate it. Ta