ASP.NET, SQL Server, WPF, C#, VB.NET

I have a database with two tables, linked via a key field.   The tables have 
 
a relationship established with referential integrity.   The tables contain 
 
data. 
 
I need to add an additional table (TableC) that links to TableA & TableB, 
 
using referential integrity, and I will also need to update the 
 
Relationship. 
 
Tables A & B have the same number of records.    I do not need the new 
 
TableC to have records matching the current data in Tables A&B, but to 
 
contain new records. 
 
Any watch-outs when during synchronization with establishing a new 
 
relationship with the three tables, two tables containing data and the new 
 
third table starting out empty? 
 
Thank you.

"rg" <rg01@goodnews.net> wrote in 
 
news:#HtGlrvtGHA.4472@TK2MSFTNGP02.phx.gbl: 
 
Unless you're changing a relationship on tables with existing data, 
 
I'd think there'd be no problems. 
 
If you *are* doing that, do the relationship change one step at a 
 
time, synch, then do the next step. You want to propagate each 
 
design change around the whole replica set before continuing with 
 
the next one. 
 
It's probably safe to do all design changes in one synch, as long as 
 
you can be sure there are no *data* changes in the same tables or 
 
related tables in the same synch. If any of your changes involve 
 
something like change foreign keys and then deleting the parent 
 
record, be sure to do that in two steps (change the foreign key, 
 
synch, delete the parent record, synch) or you'll produce errors. 
 
But if you're only adding relationships between existing tables and 
 
a new table with no records in it, I see nothing to worry about. 
 
-- 
 
David W. Fenton                  http://www.dfenton.com/ 
 
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Thanks David. 
 
I'll give that a try, I appreciate it! 
 
"David W. Fenton" <XXXusenet@dfenton.com.invalid> wrote in message 
 
news:Xns9814A3CF56F4f99a49ed1d0c49c5bbb2@127.0.0.1...