InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 08:13:41 GMT20http://www.sqlservercentral.com/Forums/Topic1432951-392-1.aspxI guess your StudentAddress table is a link table between Address and Student tables, right?If so, when you edit the link you better delete and insert "link" rows if they change, not update them.Tue, 19 Mar 2013 18:11:18 GMTEugene Elutinhttp://www.sqlservercentral.com/Forums/Topic1432951-392-1.aspxWe are creating an address database to maintain student address info.I have two tables like this :The address table is a master table that holds all addresses. The studHomeAddress table will hold all students and their address- the addressID comes from the master address table. The primary key of the Address table is Address ID, the PK for studHomeAddress table is studentID and AddressID, we are going to have a screen for user to add or edit for each of the two tables.They can add and edit records, for both of the tables.For the first table Address, I think it is no problem. For the second table, if we want to change the address of the student to another one, then the AddressID will be changed for this record, but it is the PK, the PK for the row will be changed. Is that an OK design?Thanks,Tue, 19 Mar 2013 18:05:30 GMTsqlfriends