Visual Studio quit doing this;

<asp:ObjectDataSource ID="ObjectDataSource1" runat="server" ConflictDetection="CompareAllValues"
        DeleteMethod="DeleteCustomer" InsertMethod="InsertCustomerReturnID" OldValuesParameterFormatString="original_{0}"
        SelectMethod="GetCustomersByFilters" TypeName="BLL.CustomersClass" UpdateMethod="UpdateCustomer" OnDeleted="ObjectDataSource1_Deleted">

Protected Sub ObjectDataSource1_Deleted(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.ObjectDataSourceStatusEventArgs)

End Sub

and started doing this;

<asp:ObjectDataSource ID="ObjectDataSource1" runat="server" ConflictDetection="CompareAllValues"
        DeleteMethod="DeleteCustomer" InsertMethod="InsertCustomer" OldValuesParameterFormatString="original_{0}"
        SelectMethod="GetCustomersByFilters" TypeName="BLL.CustomersClass" UpdateMethod="UpdateCustomer">
        <DeleteParameters> 

Protected Sub ObjectDataSource1_Deleted(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.ObjectDataSourceStatusEventArgs) Handles ObjectDataSource1.Deleted

End Sub

 And I am having a problem with using Image ButtonTypes in CommandFields of DetailsViews in pages that were compiled recently.  It tries deleting the record more than once. 

 Anyone got any ideas?  I've been stuck on this for about a week and would REALLY appreciate the help.

I believe that both methods are still valid with VB.NET.  The problem that you're having seems to come from associating the function with the event twice, once in the page source with OnDeleted="ObjectDataSource1_Deleted", and once in the code behind with Handles ObjectDataSource1.Deleted.  Try removing one of these and see if your function only gets called one time. 

Yah, I imagined this and tried what you said but the problem with the double-deletes still persists when using Image ButtonTypes on any page that I changed.  This doesn't explain why when I double-click in the Events dialog box to create a new event or to modify an existing on that VS either creates the handler with the Handles keyword or adds it to the existing handler.  It didn't use to do this and whatever changed is probably causing the problem with the Image ButtonTypes as well. 

I may have been VPN'ed in from home at the time of this "mess everything up for me" started.  If this brings anything to mind.

I have also run through the Repair/Reinstall on the VS installation CD.

Handles is correct behavior for VB actually. VS Orcas also behaves this way.