"Howard Kaikow" wrote:

> I'm using the code below, but an error is not getting trapped.
> Where can such errors occur?
> In another process?
>
> Try
>     SomeCode
> Catch ex As Exception
>     Dim strMsg() As String = Split(ex.ToString, vbCrLf)
>     With lstStuff
>         For i = 0 To UBound(strMsg)
>             .Items.Add(strMsg(i))
>         Next i
>     End With
> End Try
>
> --
> http://www.standards.com/; See Howard Kaikow's web site.
>
>
>

"Howard Kaikow" <kai***@standards.com> wrote in message
news:OCnzMjQmGHA.4864@TK2MSFTNGP04.phx.gbl...
| I'm using the code below, but an error is not getting trapped.
| Where can such errors occur?
| In another process?
|
| Try
|    SomeCode
| Catch ex As Exception
|    Dim strMsg() As String = Split(ex.ToString, vbCrLf)
|    With lstStuff
|        For i = 0 To UBound(strMsg)
|            .Items.Add(strMsg(i))
|        Next i
|    End With
| End Try
|
| --
| http://www.standards.com/; See Howard Kaikow's web site.
|
|

"Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_***@tsbradley.net> schreef in
bericht news:ue0j%23$amGHA.1488@TK2MSFTNGP02.phx.gbl...
> Howard,
> My understanding is that only "errors" that do not inherit from
> System.Exception are not trappable. Or exceptions that cause the system to
> "halt", such as OutOfMemory, StackOverflow, ExecutionEngineException. Some
> exceptions, such as ThreadAbortException are trappable, however require
> special means to stop (Thread.ResetAbort).
>
>
> Especially when you use:
>
> | Catch ex As Exception
>
> However if you use:
>
> | Catch
>
> Then "errors" that do not inherit from System.Exception are trapped also.
> Unfortunately you don't know what the exception is as it doesn't inherit
> from System.Exception.
>
> The only place I understand that you can get an "error" that does not
> inherit from System.Exception is from C++.
>
>
> I want to say this changed on .NET 2.0, that .NET 2.0 will wrap any
> "errors"
> that do not inherit from System.Exception for you.
>
>
>
> --
> Hope this helps
> Jay B. Harlow [MVP - Outlook]
> .NET Application Architect, Enthusiast, & Evangelist
> T.S. Bradley - http://www.tsbradley.net
>
>
> "Howard Kaikow" <kai***@standards.com> wrote in message
> news:OCnzMjQmGHA.4864@TK2MSFTNGP04.phx.gbl...
> | I'm using the code below, but an error is not getting trapped.
> | Where can such errors occur?
> | In another process?
> |
> | Try
> |    SomeCode
> | Catch ex As Exception
> |    Dim strMsg() As String = Split(ex.ToString, vbCrLf)
> |    With lstStuff
> |        For i = 0 To UBound(strMsg)
> |            .Items.Add(strMsg(i))
> |        Next i
> |    End With
> | End Try
> |
> | --
> | http://www.standards.com/; See Howard Kaikow's web site.
> |
> |
>
>

"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
news:uk33pacmGHA.1488@TK2MSFTNGP02.phx.gbl...
| Jay,
|
| I have seen some none trappable errors in the handling of the system.data
| and by instance Date functions in version 1.x. In those functions there is
| used the exception handler to handle some errors as functionality, and by
| that making it outside those procedures not trappable anymore (where it
was
| as far as I remember me in the system.data something with null values). I
| could see them by setting the option to break on any error.
|
| I thought  (hope) that this kind of programming is changed in version 2.0
| (not with the date functions, that is well done)
|
| Cor
|
| "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_***@tsbradley.net> schreef in
| bericht news:ue0j%23$amGHA.1488@TK2MSFTNGP02.phx.gbl...
| > Howard,
| > My understanding is that only "errors" that do not inherit from
| > System.Exception are not trappable. Or exceptions that cause the system
to
| > "halt", such as OutOfMemory, StackOverflow, ExecutionEngineException.
Some
| > exceptions, such as ThreadAbortException are trappable, however require
| > special means to stop (Thread.ResetAbort).
| >
| >
| > Especially when you use:
| >
| > | Catch ex As Exception
| >
| > However if you use:
| >
| > | Catch
| >
| > Then "errors" that do not inherit from System.Exception are trapped
also.
| > Unfortunately you don't know what the exception is as it doesn't inherit
| > from System.Exception.
| >
| > The only place I understand that you can get an "error" that does not
| > inherit from System.Exception is from C++.
| >
| >
| > I want to say this changed on .NET 2.0, that .NET 2.0 will wrap any
| > "errors"
| > that do not inherit from System.Exception for you.
| >
| >
| >
| > --
| > Hope this helps
| > Jay B. Harlow [MVP - Outlook]
| > .NET Application Architect, Enthusiast, & Evangelist
| > T.S. Bradley - http://www.tsbradley.net
| >
| >
| > "Howard Kaikow" <kai***@standards.com> wrote in message
| > news:OCnzMjQmGHA.4864@TK2MSFTNGP04.phx.gbl...
| > | I'm using the code below, but an error is not getting trapped.
| > | Where can such errors occur?
| > | In another process?
| > |
| > | Try
| > |    SomeCode
| > | Catch ex As Exception
| > |    Dim strMsg() As String = Split(ex.ToString, vbCrLf)
| > |    With lstStuff
| > |        For i = 0 To UBound(strMsg)
| > |            .Items.Add(strMsg(i))
| > |        Next i
| > |    End With
| > | End Try
| > |
| > | --
| > | http://www.standards.com/; See Howard Kaikow's web site.
| > |
| > |
| >
| >
|
|

"Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_***@tsbradley.net> schreef in
bericht news:elzOySkmGHA.748@TK2MSFTNGP02.phx.gbl...
> Cor,
> Where the errors being eaten by how data binding works?
>
> I don't remember the specifics but I remember that some exceptions in
> System.Data area are eaten by how data binding works.
>
>
> Or the exception was getting by your exception handler?
>
> --
> Hope this helps
> Jay B. Harlow [MVP - Outlook]
> .NET Application Architect, Enthusiast, & Evangelist
> T.S. Bradley - http://www.tsbradley.net
>
>
> "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
> news:uk33pacmGHA.1488@TK2MSFTNGP02.phx.gbl...
> | Jay,
> |
> | I have seen some none trappable errors in the handling of the
> system.data
> | and by instance Date functions in version 1.x. In those functions there
> is
> | used the exception handler to handle some errors as functionality, and
> by
> | that making it outside those procedures not trappable anymore (where it
> was
> | as far as I remember me in the system.data something with null values).
> I
> | could see them by setting the option to break on any error.
> |
> | I thought  (hope) that this kind of programming is changed in version
> 2.0
> | (not with the date functions, that is well done)
> |
> | Cor
> |
> | "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_***@tsbradley.net> schreef
> in
> | bericht news:ue0j%23$amGHA.1488@TK2MSFTNGP02.phx.gbl...
> | > Howard,
> | > My understanding is that only "errors" that do not inherit from
> | > System.Exception are not trappable. Or exceptions that cause the
> system
> to
> | > "halt", such as OutOfMemory, StackOverflow, ExecutionEngineException.
> Some
> | > exceptions, such as ThreadAbortException are trappable, however
> require
> | > special means to stop (Thread.ResetAbort).
> | >
> | >
> | > Especially when you use:
> | >
> | > | Catch ex As Exception
> | >
> | > However if you use:
> | >
> | > | Catch
> | >
> | > Then "errors" that do not inherit from System.Exception are trapped
> also.
> | > Unfortunately you don't know what the exception is as it doesn't
> inherit
> | > from System.Exception.
> | >
> | > The only place I understand that you can get an "error" that does not
> | > inherit from System.Exception is from C++.
> | >
> | >
> | > I want to say this changed on .NET 2.0, that .NET 2.0 will wrap any
> | > "errors"
> | > that do not inherit from System.Exception for you.
> | >
> | >
> | >
> | > --
> | > Hope this helps
> | > Jay B. Harlow [MVP - Outlook]
> | > .NET Application Architect, Enthusiast, & Evangelist
> | > T.S. Bradley - http://www.tsbradley.net
> | >
> | >
> | > "Howard Kaikow" <kai***@standards.com> wrote in message
> | > news:OCnzMjQmGHA.4864@TK2MSFTNGP04.phx.gbl...
> | > | I'm using the code below, but an error is not getting trapped.
> | > | Where can such errors occur?
> | > | In another process?
> | > |
> | > | Try
> | > |    SomeCode
> | > | Catch ex As Exception
> | > |    Dim strMsg() As String = Split(ex.ToString, vbCrLf)
> | > |    With lstStuff
> | > |        For i = 0 To UBound(strMsg)
> | > |            .Items.Add(strMsg(i))
> | > |        Next i
> | > |    End With
> | > | End Try
> | > |
> | > | --
> | > | http://www.standards.com/; See Howard Kaikow's web site.
> | > |
> | > |
> | >
> | >
> |
> |
>
>

"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
news:ee0aGlmmGHA.4052@TK2MSFTNGP05.phx.gbl...
| Jay,
|
| It comes ever time more near, but I have checked it as far as I could see,
| and it was because there was internaly used a try and catch.
|
| You ask yourself maybe how I could see that. Just because there was a
little
| stop the first time when it did occur, that was the reason I investigated
| it. It was by somebody in one of these newsgroups, I did not have the
| problem, so it was only a small test which is already destroyed a long
time
| ago.
|
| Cor
| .
| "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_***@tsbradley.net> schreef in
| bericht news:elzOySkmGHA.748@TK2MSFTNGP02.phx.gbl...
| > Cor,
| > Where the errors being eaten by how data binding works?
| >
| > I don't remember the specifics but I remember that some exceptions in
| > System.Data area are eaten by how data binding works.
| >
| >
| > Or the exception was getting by your exception handler?
| >
| > --
| > Hope this helps
| > Jay B. Harlow [MVP - Outlook]
| > .NET Application Architect, Enthusiast, & Evangelist
| > T.S. Bradley - http://www.tsbradley.net
| >
| >
| > "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
| > news:uk33pacmGHA.1488@TK2MSFTNGP02.phx.gbl...
| > | Jay,
| > |
| > | I have seen some none trappable errors in the handling of the
| > system.data
| > | and by instance Date functions in version 1.x. In those functions
there
| > is
| > | used the exception handler to handle some errors as functionality, and
| > by
| > | that making it outside those procedures not trappable anymore (where
it
| > was
| > | as far as I remember me in the system.data something with null
values).
| > I
| > | could see them by setting the option to break on any error.
| > |
| > | I thought  (hope) that this kind of programming is changed in version
| > 2.0
| > | (not with the date functions, that is well done)
| > |
| > | Cor
| > |
| > | "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_***@tsbradley.net> schreef
| > in
| > | bericht news:ue0j%23$amGHA.1488@TK2MSFTNGP02.phx.gbl...
| > | > Howard,
| > | > My understanding is that only "errors" that do not inherit from
| > | > System.Exception are not trappable. Or exceptions that cause the
| > system
| > to
| > | > "halt", such as OutOfMemory, StackOverflow,
ExecutionEngineException.
| > Some
| > | > exceptions, such as ThreadAbortException are trappable, however
| > require
| > | > special means to stop (Thread.ResetAbort).
| > | >
| > | >
| > | > Especially when you use:
| > | >
| > | > | Catch ex As Exception
| > | >
| > | > However if you use:
| > | >
| > | > | Catch
| > | >
| > | > Then "errors" that do not inherit from System.Exception are trapped
| > also.
| > | > Unfortunately you don't know what the exception is as it doesn't
| > inherit
| > | > from System.Exception.
| > | >
| > | > The only place I understand that you can get an "error" that does
not
| > | > inherit from System.Exception is from C++.
| > | >
| > | >
| > | > I want to say this changed on .NET 2.0, that .NET 2.0 will wrap any
| > | > "errors"
| > | > that do not inherit from System.Exception for you.
| > | >
| > | >
| > | >
| > | > --
| > | > Hope this helps
| > | > Jay B. Harlow [MVP - Outlook]
| > | > .NET Application Architect, Enthusiast, & Evangelist
| > | > T.S. Bradley - http://www.tsbradley.net
| > | >
| > | >
| > | > "Howard Kaikow" <kai***@standards.com> wrote in message
| > | > news:OCnzMjQmGHA.4864@TK2MSFTNGP04.phx.gbl...
| > | > | I'm using the code below, but an error is not getting trapped.
| > | > | Where can such errors occur?
| > | > | In another process?
| > | > |
| > | > | Try
| > | > |    SomeCode
| > | > | Catch ex As Exception
| > | > |    Dim strMsg() As String = Split(ex.ToString, vbCrLf)
| > | > |    With lstStuff
| > | > |        For i = 0 To UBound(strMsg)
| > | > |            .Items.Add(strMsg(i))
| > | > |        Next i
| > | > |    End With
| > | > | End Try
| > | > |
| > | > | --
| > | > | http://www.standards.com/; See Howard Kaikow's web site.
| > | > |
| > | > |
| > | >
| > | >
| > |
| > |
| >
| >
|
|

"Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_***@tsbradley.net> wrote in
message news:ue0j%23$amGHA.1488@TK2MSFTNGP02.phx.gbl...
> Howard,
> My understanding is that only "errors" that do not inherit from
> System.Exception are not trappable. Or exceptions that cause the system to
> "halt", such as OutOfMemory, StackOverflow, ExecutionEngineException. Some
> exceptions, such as ThreadAbortException are trappable, however require
> special means to stop (Thread.ResetAbort).
>
>
> Especially when you use:
>
> | Catch ex As Exception
>
> However if you use:
>
> | Catch
>
> Then "errors" that do not inherit from System.Exception are trapped also.
> Unfortunately you don't know what the exception is as it doesn't inherit
> from System.Exception.