I think we are actually probably talking about "apples and oranges" here ("error handling" vs. "default error messaging").
If they currently have a specific error handling routine in place, yes that would bypass it as is written.
But to invoke an error handling routine in the first place, you would need a line like:
Rich (BB code):
On Error GoTo ErrorHandlingProcName
where
ErrorHandlingProcName is the name of the procedure
So, if they have one already in place, they could simply just invoke that again like this:
VBA Code:
On Error Resume Next
Range("A2:A15000").SpecialCells(xlCellTypeBlanks).EntireRow.Delete
On Error GoTo [I]ErrorHandlingProcName[/I]
Or, alternatively, they could add just update their current Error Handling Procedure to handle the error code produced by this situation.
If they do not currently have any error handling procedure in there code, they can use what I gave them "as-is". It will work.
Here is a simple example that shows that Excel default error messages return when using "On Error GoTo 0".
VBA Code:
Sub MyTest()
On Error Resume Next
MsgBox "Test 1: " & 5 / 0
On Error GoTo 0
MsgBox "Test 2: " & 5 / 0
End Sub
You can see from the test, that the first test (the one between those two statements) will be ignored, while the second one will return the typical division by 0 error message.