>Using the following triggers a VFP error.
>I receive the message box from ERROR 2058.
>I can avoid it by using "loException" instead of "m.loException".
>Is this a bug?
>
>

>LOCAL lcAssignTo
>LOCAL lcTest
>LOCAL loException AS Exception
>
>* Triggers an error no. 2058 - because first CATCH statement handles?
>m.lcTest = ""
>* Uncomment this to NOT trigger the error - because second CATCH statement handles?
>*m.lcTest = "something"
>
>TRY
>    m.lcAssignTo = m.undefined
>CATCH TO m.loException WHEN EMPTY( m.lcTest )
>    ? loException.Message
>CATCH TO m.loException
>   ? loException.Message
>ENDTRY

This was posted earlier by Spencer Redfield. See Try/Catch/Finally/Endtry mismatch, error #2058 Thread #811323 Message #811323.