On error resume next

[Johan]

I have a macro which call other macroes.
In the end of the code it "cleans up" with the following code:

on error resume next
c:\arbeidsliste\sjekk.txt
c:\arbeidsliste\sjekk.bat
c:\arbeidsliste\send.bat
on error goto 0

The problem is that if one of the file is missing the code stop and display
error message.

Any one have a solution?

Johan

 

[Rick Rothstein]

Your code cannot look like you posted... VB would tag the three lines
between the On Error statements as invalid syntax. Why don't you show us
what you are actually executing so we can see what you trying to do.

 

[Johan]

Rick Rothstein skrev:

Your code cannot look like you posted... VB would tag the three lines
between the On Error statements as invalid syntax. Why don't you show us
what you are actually executing so we can see what you trying to do.

Sorry I did some error in my typing, the code is:

on error resume next
kill c:\arbeidsliste\sjekk.txt
kill c:\arbeidsliste\sjekk.bat
kill c:\arbeidsliste\send.bat
on error goto 0

Johan

 

[Dave Peterson]

You still have major syntax errors.

It's better to copy directly from the VBE and paste into your message.

That said, try this:

Inside the VBE
Tools|Options|General tab|check "break in class module"

(I'm guessing that you have break on all errors checked.)

 

[Rick Rothstein]

I have always used "Break on Unhandled Errors". I've not use very many Class
Modules in my coding across the years... does "Break in Class Module" work
the same way outside of the Class Module as "Break on Unhandled Errors" (the
Help file is not very clear on this point)?

 

[Dave Peterson]

I saved this from a Chip Pearson post:

In general, it is better to use "Break In Class Module" rather than "Break
On Unhandled Errors". With break in class module, you'll enter debug mode on
the exact line within a class that caused the problem. With break on
unhandled errors, you'll break on the code that called the method of the
class, which is of little use for debugging. Of course, this is irrelevant
if you don't have code in any classes.

 

[Rick Rothstein]

Okay, so it sounds like in non-Class Modules, they work the same... I'll
have to change my setting. Thanks.

 

[Dave Peterson]

I changed mine when I read Chip's message, too!

Okay, so it sounds like in non-Class Modules, they work the same... I'll
have to change my setting. Thanks.

 

[Chip Pearson]

Okay, so it sounds like in non-Class Modules, they work the same... I'll

have to change my setting. Thanks.

Remember, too, that UserForms are considered class modules (as are the
Sheet moduels and ThisWorkbook), so if your userform's code has an
error and you don't have "Break In Class Module" enabled, the debugger
will take you to the line of code

UserForm1.Show

That is probably the hardest line of code in the world to screw up,
and so if you're not tuned into how the debugger works, you could
spend all day trying to figure out what's wrong with that line of code
(because nothing is wrong with it).

MS should change the wording in the Options screen to "Break In Object
Module".


Cordially,
Chip Pearson
Microsoft Most Valuable Professional
Excel Product Group, 1998 - 2009
Pearson Software Consulting, LLC
www.cpearson.com
(email on web site)