After finally figuring out that I don't need triggers in SQL 2000 to
implement cascading updates and deletes, I have come across the following
Our customers are able to have orders invoiced to other customers. E.g.
Customer A can create an order, but he wants the invoice sent to Customer B.
Customer A can send invoices to many other customers and customer B can
receive invoices from many other customers. Result: an intersection table.
Customer 1---------oo CustomerInvoices oo----------1 Customer
If the customer ID changes, I want to have the CustomerInvoices table also
updated. But when creating this cascading relationship, SQL Server says that
there is a risk of an update cycle. I can perfectly well understand this.
This would occur when Customer A would be able to invoice Customer A. This
will be avoided in the business layer.
Is there a workaround for this. The issue is that this is not the only
relationship I have like this: there are at least 4 similar relationships,
so I'm really looking for a solution.
Should I go back to using triggers for this relationship? Or can I force SQL
Server into accepting this?
Global Communication N.V.
Please reply to the newsgroup.