Glad to help!

Trent,

Thanks for the tip. That got me where I wanted go. I'll have to remember that most SF methods are overridable.

-Larry

Larry,

On the BO, override the OnBeforeDelete method.  Be sure to call the Base.OnBeforeDelete(...) method at the top of the method.  You will then have a properly formatted event arg that tells you whether the record is going to be deleted or not.  You can either create your own event or place your code here to do what you need.

I'm looking for a way to execute code in the BO once I know the user has comitted to the delete (and can't cancel) but prior to actually deleting the record from the data base. Something like a "DeleteConfirmed" event. Any suggestions?

-Larry

Yes, Larry, this is by design... the BeforeDelete even is used to cancel the delete, and when the end-user clicks "No" on the auto-delete confirmation, then e.Cancel is set to True. The only way for the message to be shown before the delete confirmation message box would be for the message box to be hard-coded within the business object itself. So, the message box is designed to be shown within an event handler of the BeforeDelete event.

I’m using the AutoDeleteMessageConformation feature on a SF maint form. What I’ve found is that the BeforeDelete event on the primary BO is raised before the AutoDeleteMessageConformation message on the form (I’m letting the form call delete on the BO).  Is this the way it is designed to work? I think it would be more useful to have the message raised first and if the user cancels the delete, not raise the BeforeDelete event on the BO.  

-Larry