> The update rule of SAPDB implicitly is 'ON UPDATE RESTRICT', i.e. the > update of a master row fails if any child rows exists. 'ON UPDATE CASCADE' > is not implemented. You can simulate the key update if you delete the row > and insert it again with the new key.
Thanks for the fast answer. Will cascading updates be implemented in the future? In the meantime, I have another project that I will have to redesign to use STAMPS as primary key. Stupid me for assuming "update" was implied. Brad Clements, [EMAIL PROTECTED] (315)268-1000 http://www.murkworks.com (315)268-9812 Fax AOL-IM: BKClements _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
