Hello
I have a case where Partners are some kind of Super-Users and are
stored in a SQL Server database. Best is IMO to put both in the same
table:
table Customers:
CustomerID[pr.key]
[blabla]
PartnerID
But of course I have to reference the partnerid from another table and
I want SQL Server to maintain the integrity rules. I could split
Customers en Partners into different tables, but that would not be
wise i think.
Or I could just reference the CustomerID from the other table and
-know- that we are talking about a partner, but in that case it it
possible to reference a customer that is not a partner, and i want to
avoid that.
Any ideas?
Freek Versteijn