Thanks for reply...
subpaul wrote:
workout I think is to delete the old one, and enter a new one.
Foo is master table and there are "n" tables referring to Foo...
Hence delete and inserting would not work in my case...
subpaul wrote:
I have never felt the need for this thought, when I have a primary key.
If a user enters a wrong value for the identifier, as this identifier is assigned, user cannot be forced to delete the same and enter all the values again....
subpaul wrote:
Why can't you just change the value of the foreign key?
Is there a way out by using native sql queries for a work around