Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I am having trouble trapping certain kinds of errors in Visual Basic macros.
Specifically I can't seem to trap errors related to the "EditGo ToSpecial" variety. For example, if two columns are selected, and I try to locate rowdifferences between the columns using: Selection.RowDifferences(Activecell).Select will work fine if there are row diffrences. If there are no differences, I get error 1004, which I can't trap using "On Error" handling. I have the same problem if the Macro tries to look for Blank cells. Does anyone have a solution for how to trap and handle these errors? |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
EditGo ToSpecialBlanks | Excel Discussion (Misc queries) | |||
Edit Paste Special Formulas | Excel Worksheet Functions | |||
Error Handling - On Error GoTo doesn't trap error successfully | Excel Programming | |||
Edit--Find special characters | Excel Programming | |||
Error handling with a handling routine | Excel Programming |