>> If I redefine the foreign keys in a different order (e.g. C, D, B) the
>> delete rule for the first one is correct ("SET NULL"), but the second
>> one is wrong again. It is the same for "CASCADE" except "SET NULL".> well, did you test it? > this sounds like an old SQL-Studio bug I opened the table definition in SQL-Studio and looked at the foreign key tab. So it seems to be this old SQL-Studio bug. I should better look at the system tables next Time... _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
