Run-time error: no cells found. Handling this error?

[OfficeUser]

I get a runtime error using this macro:

Private Sub DeleteRows()
On Error Resume Next
Columns("C:C").SpecialCells(xlCellTypeBlanks).EntireRow.Delete
On Error GoTo 0
End Sub

It produces an error if there are no rows to delete. How do I prevent the error from happening? This macro is triggered from within a separate macro like this:

Run "DeleteRows"

Thanks for the help!!

 

[Fluff]

It sounds like you already have an active error, when you get to that row, otherwise the

On Error Resume Next

Would handle the error.
a) could you post the entire code for the calling macro.
b) Have a look here regarding error handling
http://excelmatters.com/2015/03/17/on-error-wtf/

 

[OfficeUser]

Perhaps you can answer this, but if I put 'On Error Resume Next' at the top of the procedure, why do I still get the run-time error? Not saying this is the method I should / would use, but according to the article it should not show the error...I'm confused.

 

[OfficeUser]

I no longer call this procedure from another macro. I now set it to run with a shortcut key, but am still getting the error.

 

[Fluff]

if I put 'On Error Resume Next' at the top of the procedure, why do I still get the run-time error?

Because of this

(From Excel Matters) While the current procedure’s error handler is active, or there is an active error condition, no further errors can be handled by that procedure.

The current procedure includes any subs that are called by, or call other subs.
Untested but try

Private Sub DeleteRows()
MsgBox Err.Number
On Error Resume Next
Columns("C:C").SpecialCells(xlCellTypeBlanks).EntireRow.Delete
On Error GoTo 0
End Sub

What does the message box say?

 

[OfficeUser]

The box says: 0

For now, I simply insert a blank line between rows one and two and the code works, and allows everything to operate as needed. It works but now I want to understand how to handle errors. Thanks for taking time to help.

 

[Fluff]

I no longer call this procedure from another macro. I now set it to run with a shortcut key, but am still getting the error.

With this in mind, I must admit I dont understand why you still get an error, especially bearing in mind that the msgbox showed 0.

 

[NoSparks]

I suspect the msgbox showed 0 because the OP used the shortcut key to run the DeleteRows sub.

The way I follow this, the error is in the sub calling the DeleteRows sub.
In post #2 Fluff asked

a) could you post the entire code for the calling macro.

but that didn't happen.

 

[OfficeUser]

Actually I didn't. I ran the macro by going back to the very original file where this macro is called from another routine. I figured it would be best to work from the original file.

I appreciate your follow-up, but it is a bit brash...just saying.

 

[Fluff]

Deleted