Visual Basic - Err.Raise dilemma

Author

Err.Raise dilemma

Frank Rizzo

2005-12-13, 9:55 pm

I have a curious problem. In the app, if an error occurs, the
application calls Err.Raise ErrorNumber, ErrDescription,... method,
which hits an error handler in the function, which logs the error and
then calls Err.Raise , which is in turn caught in the caller function,
and so on until the error bubbles up to the top and is caught by the
general error handler. This seems to work fine in the IDE, but when I
compile the app and run as an EXE, somewhere along the line (like on 3rd
or 4th err.Raise call) the original error number and description are
lost and replaced by Error #5, which is kind of generic vb error.

Is there some kind of limitation on the levels of err.Raise? Or am I
missing something simple here?

Thanks

Michael Cole

2005-12-13, 9:55 pm

Frank Rizzo wrote:
> I have a curious problem. In the app, if an error occurs, the
> application calls Err.Raise ErrorNumber, ErrDescription,... method,
> which hits an error handler in the function, which logs the error and
> then calls Err.Raise , which is in turn caught in the caller function,
> and so on until the error bubbles up to the top and is caught by the
> general error handler. This seems to work fine in the IDE, but when I
> compile the app and run as an EXE, somewhere along the line (like on
> 3rd or 4th err.Raise call) the original error number and description
> are lost and replaced by Error #5, which is kind of generic vb error.
>
> Is there some kind of limitation on the levels of err.Raise? Or am I
> missing something simple here?

There is no limitation. Check and see if the error logging function could
be generating the error.

--
Regards,

Michael Cole

Sponsored Links