Excel 2003 On Error Resume Next doesn't work for me

I just migrated all of my apps from Excel 2000 to Excel 2003. Now the VBA
code fails whereever I had an On Error Resume Next statement. It's as if that
statement is being ignored. My current error is a MAPI_E_NOT_FOUND error,
which is triggering a run time error even though I have an on error resume
next line above it. Any ideas as to how to trap this error in Excel 2003?

On Error Resume Next only works with Trappable errors. I suspect, that if
it isn't working, then you are getting an error that is not trappable.

--
Regards,
Tom Ogilvy


"Leadee" <[email protected]> wrote in message
news:[email protected]...
> I just migrated all of my apps from Excel 2000 to Excel 2003. Now the VBA
> code fails whereever I had an On Error Resume Next statement. It's as if
that
> statement is being ignored. My current error is a MAPI_E_NOT_FOUND error,
> which is triggering a run time error even though I have an on error resume
> next line above it. Any ideas as to how to trap this error in Excel 2003?

Thank you for the info. So what is the solution to work with non-trapple
errors?

"Tom Ogilvy" wrote:

> On Error Resume Next only works with Trappable errors. I suspect, that if
> it isn't working, then you are getting an error that is not trappable.
>
> --
> Regards,
> Tom Ogilvy
>
>
> "Leadee" <[email protected]> wrote in message
> news:[email protected]...
> > I just migrated all of my apps from Excel 2000 to Excel 2003. Now the VBA
> > code fails whereever I had an On Error Resume Next statement. It's as if
> that
> > statement is being ignored. My current error is a MAPI_E_NOT_FOUND error,
> > which is triggering a run time error even though I have an on error resume
> > next line above it. Any ideas as to how to trap this error in Excel 2003?
>
>
>

Avoid the error.

--
Regards,
Tom Ogilvy

"Leadee" <[email protected]> wrote in message
news:[email protected]...
> Thank you for the info. So what is the solution to work with non-trapple
> errors?
>
> "Tom Ogilvy" wrote:
>
> > On Error Resume Next only works with Trappable errors. I suspect, that
if
> > it isn't working, then you are getting an error that is not trappable.
> >
> > --
> > Regards,
> > Tom Ogilvy
> >
> >
> > "Leadee" <[email protected]> wrote in message
> > news:[email protected]...
> > > I just migrated all of my apps from Excel 2000 to Excel 2003. Now the
VBA
> > > code fails whereever I had an On Error Resume Next statement. It's as
if
> > that
> > > statement is being ignored. My current error is a MAPI_E_NOT_FOUND
error,
> > > which is triggering a run time error even though I have an on error
resume
> > > next line above it. Any ideas as to how to trap this error in Excel
2003?
> >
> >
> >

> Avoid the error.

Very well put.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com


"Tom Ogilvy" <[email protected]> wrote in message
news:OZo24hB%[email protected]...
> Avoid the error.
>
> --
> Regards,
> Tom Ogilvy
>
> "Leadee" <[email protected]> wrote in message
> news:[email protected]...
>> Thank you for the info. So what is the solution to work with
>> non-trapple
>> errors?
>>
>> "Tom Ogilvy" wrote:
>>
>> > On Error Resume Next only works with Trappable errors. I
>> > suspect, that
> if
>> > it isn't working, then you are getting an error that is not
>> > trappable.
>> >
>> > --
>> > Regards,
>> > Tom Ogilvy
>> >
>> >
>> > "Leadee" <[email protected]> wrote in message
>> > news:[email protected]...
>> > > I just migrated all of my apps from Excel 2000 to Excel
>> > > 2003. Now the
> VBA
>> > > code fails whereever I had an On Error Resume Next
>> > > statement. It's as
> if
>> > that
>> > > statement is being ignored. My current error is a
>> > > MAPI_E_NOT_FOUND
> error,
>> > > which is triggering a run time error even though I have an
>> > > on error
> resume
>> > > next line above it. Any ideas as to how to trap this error
>> > > in Excel
> 2003?
>> >
>> >
>> >
>
>

Unfortunately, I can't avoid the error. It is based on whether or not someone
has entered a Custom Attribute field value into the user's outlook profile on
the Exchange server. Since we're talking about potential human error, it is
something I must attempt to trap. If I could test for a null value, that
would be wonderful, but that also produces a run time error. I may be SOL and
just hope that the person entering the values doesn't miss one. With hundreds
of users, this is very likely though. Thanks for your suggestions.

"Tom Ogilvy" wrote:

> Avoid the error.
>
> --
> Regards,
> Tom Ogilvy
>
> "Leadee" <[email protected]> wrote in message
> news:[email protected]...
> > Thank you for the info. So what is the solution to work with non-trapple
> > errors?
> >
> > "Tom Ogilvy" wrote:
> >
> > > On Error Resume Next only works with Trappable errors. I suspect, that
> if
> > > it isn't working, then you are getting an error that is not trappable.
> > >
> > > --
> > > Regards,
> > > Tom Ogilvy
> > >
> > >
> > > "Leadee" <[email protected]> wrote in message
> > > news:[email protected]...
> > > > I just migrated all of my apps from Excel 2000 to Excel 2003. Now the
> VBA
> > > > code fails whereever I had an On Error Resume Next statement. It's as
> if
> > > that
> > > > statement is being ignored. My current error is a MAPI_E_NOT_FOUND
> error,
> > > > which is triggering a run time error even though I have an on error
> resume
> > > > next line above it. Any ideas as to how to trap this error in Excel
> 2003?
> > >
> > >
> > >
>
>
>

Also, this does not change the issue whereby my "on error resume next"
statements worked with most other errors in Excel 2000, but not in Excel
2003. That is a somewhat separate issue, but begs an answer just the same.


"Leadee" wrote:

> Unfortunately, I can't avoid the error. It is based on whether or not someone
> has entered a Custom Attribute field value into the user's outlook profile on
> the Exchange server. Since we're talking about potential human error, it is
> something I must attempt to trap. If I could test for a null value, that
> would be wonderful, but that also produces a run time error. I may be SOL and
> just hope that the person entering the values doesn't miss one. With hundreds
> of users, this is very likely though. Thanks for your suggestions.
>
> "Tom Ogilvy" wrote:
>
> > Avoid the error.
> >
> > --
> > Regards,
> > Tom Ogilvy
> >
> > "Leadee" <[email protected]> wrote in message
> > news:[email protected]...
> > > Thank you for the info. So what is the solution to work with non-trapple
> > > errors?
> > >
> > > "Tom Ogilvy" wrote:
> > >
> > > > On Error Resume Next only works with Trappable errors. I suspect, that
> > if
> > > > it isn't working, then you are getting an error that is not trappable.
> > > >
> > > > --
> > > > Regards,
> > > > Tom Ogilvy
> > > >
> > > >
> > > > "Leadee" <[email protected]> wrote in message
> > > > news:[email protected]...
> > > > > I just migrated all of my apps from Excel 2000 to Excel 2003. Now the
> > VBA
> > > > > code fails whereever I had an On Error Resume Next statement. It's as
> > if
> > > > that
> > > > > statement is being ignored. My current error is a MAPI_E_NOT_FOUND
> > error,
> > > > > which is triggering a run time error even though I have an on error
> > resume
> > > > > next line above it. Any ideas as to how to trap this error in Excel
> > 2003?
> > > >
> > > >
> > > >
> >
> >
> >

"Leadee" <[email protected]> wrote in message
news:[email protected]...
> Also, this does not change the issue whereby my "on error resume next"
> statements worked with most other errors in Excel 2000, but not in Excel
> 2003. That is a somewhat separate issue, but begs an answer just the same.

Select Tools/Options/General from the VBE menu and make sure the Break
on All Errors option isn't selected.

--
Rob Bovey, Excel MVP
Application Professionals
http://www.appspro.com/

* Please post all replies to this newsgroup *
* Unsolicited e-mail replies will be ignored *

Break on All Errors option seems to be the default in Excel 2003, and I did
have it set that way. Setting it to a lower setting didn't fix my CDO error
mis-handling (because it seems to be a non-handled error), but it DID fix the
ON ERROR RESUME NEXT errors that became ignored when I moved from Excel 2000
to Excel 2003! Thank you very much. I appreciate your input.

"Rob Bovey" wrote:

> "Leadee" <[email protected]> wrote in message
> news:[email protected]...
> > Also, this does not change the issue whereby my "on error resume next"
> > statements worked with most other errors in Excel 2000, but not in Excel
> > 2003. That is a somewhat separate issue, but begs an answer just the same.
>
> Select Tools/Options/General from the VBE menu and make sure the Break
> on All Errors option isn't selected.
>
> --
> Rob Bovey, Excel MVP
> Application Professionals
> http://www.appspro.com/
>
> * Please post all replies to this newsgroup *
> * Unsolicited e-mail replies will be ignored *
>
>
>