Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
When you use the "On Error GoTo" approach to trap an error, is it
necessary to "clear out" the error in some way before a later instance of the same type of error can be trapped? I have a program that loops through an excel table, and the error handling seems to work the first time bad data is encountered (in this case, when the cell has a string "N/A" rather than the expected currency data type) but then when it hits a second instance of the same error (Run TIme Error '13' Type Mismatch) it stops dead in its tracks. Any suggestions? |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
how error-trap "no cells were found error" | Excel Programming | |||
ON Error goto fails on 2nd error | Excel Programming | |||
On Error doesn't trap Application.Run error | Excel Programming | |||
How can I still go to the error-code after a On Error Goto? | Excel Programming | |||
Error Handler not handling error... | Excel Programming |