Visual Basic/VB, Err.Raise Problem

Err.Raise Problem

Author	Message
Al Sardell #1 / 2	Err.Raise Problem Trying to trap errors using err.raise from VB6 Prof. Ed. Even though "break on unhandled errors" is set, the following dialog box is presented when an error is detected in a simple program designed to signal too much input for a SSN. Run-time error '-2147220503(800403e9)' SSN Too Long Continue (grayed out!) End (gasp!) Debug (gasp again!) Help The specific statement is: Err.Raise vbObjectError+1001,"Person","SSN Too Long" If the vbObjectError portion is removed, the message changes to read: Run-time error 1001 SSN Too Long Continue (grayed out!) End (gasp!) Debug (gasp again!) Help That is, VB 6.0 seems to treat the err.raise as virtually fatal and posts only the message but gives no viable recovery options. Setting the break on error options differently only worsens the matter. I can find no information on this problem at the Microsoft site so I do worry about it somehow being a 'local' problem. Am running NT 4, SP4 as well as the above. Would greatly appreciate any assistance as this behavior inhibits general error handling coding we are trying to implement.
Mon, 20 Aug 2001 03:00:00 GMT

Matthew Will #2 / 2	Err.Raise Problem Al, Press Ctrl-L and have a look at the call stack. If the error is being raised, and there is no errorhandler in the call stack, then it will either break (stop) in the IDE, or die if compiled. Matthew Quote: > Trying to trap errors using err.raise from VB6 Prof. Ed. Even though "break > on unhandled errors" is set, the following dialog box is presented when an > error is detected in a simple program designed to signal too much input for > a SSN. > Run-time error '-2147220503(800403e9)' > SSN Too Long > Continue (grayed out!) End (gasp!) Debug (gasp again!) Help > The specific statement is: Err.Raise vbObjectError+1001,"Person","SSN Too > Long" > If the vbObjectError portion is removed, the message changes to read: > Run-time error 1001 > SSN Too Long > Continue (grayed out!) End (gasp!) Debug (gasp again!) Help > That is, VB 6.0 seems to treat the err.raise as virtually > fatal and posts only the message but gives no viable recovery > options. Setting the break on error options differently only worsens the > matter. I can > find no information on this problem at the Microsoft site so I do > worry about it somehow being a 'local' problem. Am running NT 4, SP4 > as well as the above. Would greatly appreciate any assistance as this > behavior inhibits general error handling coding we are trying to implement.
Mon, 20 Aug 2001 03:00:00 GMT

Page 1 of 1

[ 2 post ]