Sean Lange (7/29/2013)
Since you started a new thread and Chris pointed me back to this one I will post here.I would agree that trying to keep this data in multiple tables is very bad design decision. It will cause you nothing but grief and anguish. You will need to implement triggers in each of the tables in order to even have a chance at making this work.
Lowell asked if you are certain that the rows always exist in all tables or if there is a possibility that you will have to create them. I never saw an answer from you on that.
Personally I would run away from this design as quickly as possible. Normalize your data and keep one and only copy of the details. There are a number of people on this thread already who can and will help you normalize your structures but you are going to have to provide some details. By details I don't mean another description of the issue, I mean actual ddl, sample data and a bit more detail about these web pages.
Thanks for your reply. Sorry I am late in replying as I was still trying to figure out a way to achieve it but in vain.
The webpage I am working on contains of a main webpage which is linked to a table (master table). The other webpages (subpages) are each linked to a separate sub-table.
The tables linked to the subpages have prepopulated data and sometimes the data needs to be amended or changed.
The main webpage has Add and Edit button to add or edit the data. When the Add button is clicked, it displays dropdownlists each linked to the sub-tables and same with the Edit button.
With your logic to normalize the table, the data linked to the main webpage should not be stored in the master table as actual values, is that what you mean ?
What if someone needs to see the actual data in SQL database in the main table ? They would only find ID columns that link to the other tables in stead of actual values/data. This is the part I am not clear about, can you please throw some light on it.
Thanks.