Wrox Home  
Search P2P Archive for: Go

  Return to Index  

pro_vb thread: Code breaks unexpectedly


Message #1 by "Scott L" <bangorme@h...> on Mon, 17 Mar 2003 16:38:41
Thanks Marco, that helped.  I found that there was an important error being 
deemed unimportant by the error handler.  That ignored error bunged things 
up.

A lesson I'll never learn when it comes to error handlers: don' ever think 
you can't miss one.  ;)

Thanks again.

Scott

>Scott,
>
>I do not see anything wrong in the code per se, so it is not easy
>to debug without knowing more details.
>
>The one_Vital_Error label is not called, probably you do it in the
>error handler?
>The ErrorTrap label is missing, so we do not know how you handle
>the errors. Keep in mind that you cannot put another On error
>statement when you are already in an error handler section of
>the code. You have to split the code into modules to do that.
>One suggestion: change your project options to "Break on all errors"
>so it is easier to debug your code. Or comment out the "On error"
>statements, so that the IDE stops right where the error occurs and
>gives you the error code as well.
>
>Blame this to the poor VB error handling scheme (and at the same time
>thanks VB that it has one...)
>
>Marco
>
>


_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*  
http://join.msn.com/?page=features/virus


  Return to Index