>>I am now thinking of doing away with the SQL Server triggers and do the cascading updates and deletes in the VFP application.
>
>(1) Would we be programmers if we were to quit ?
>(2) There must be a way
(1) Gracias por animarme.
(2) So far the only solution way I found is to implement a Delete trigger so that my child foreign keys would be set to empty string (''). And to use foreign key constraint (in SQL Server) to do Cascading update. This seems to work for 90% of the tables (guesstimate). Except that (as I posted in the past) SQL Server does not allow for setting up some foreign key constraint cascade. For those few cases I will need to find a solution.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
