Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3323056 By: hkollmann
Easier would be your own error object. All sql errors - which you could parse - could get to the "sorry, cannot delete selected record because dependent child record(s) already exists" text. On the other hand you can use the event mechanism to inject your own delete event. This could be an decedant from the default one with error handling. Both possible. Second is trickier to configure but with less programming. Henner ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=55830 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
