>> ... if record A [sic] in table 1 gets updated, record A [sic] in
table 2 gets the same update also. <<
Look up DRI actions in BOL and set up an ON UPDATE CASCADE action.
Rows are note records; columns are not fields and tables are not files.
If you were not thinking in terms of a file system, you'd know that the
"unit of work" in SQL is the **schema**, not the table (file). You
would see tables one and two as part of a whole and you would look for
mechanism to maintain a relationship between them.
The worst way would be to use a trigger. They give no help to the
optimizer and the code is highly proprietary as well as procedural.
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
*** Sent via Developersdex http://www.yqcomputer.com/
Don't just participate in USENET...get rewarded for it!