>Hey, What happened to my original message in this
>thread?
>
>Anyhow, I listed a couple of errors which poped up
>in an
>application I have. These errors appeared to
>by-pass both
>my Error Event routine and ON ERROR stuff.
>
>Errors such as:
>
>1001 - Feature not available.
>
>1925 - Unknown member object.
>
>1881 - Generic VFP error message???
>
>1538 - A stored procedure is executing.
>
>1546 - Cannot close table during execution of
>table bound expression.
>
>1645 - Report contains nesting errors. I have not
>been able
> to find any details about this one. I even
>have an
> error wrapper around the REPORT FORM
>command which
> did not catch this error.
>
> ON ERROR Store .t. to llRepFormErr
> REPORT FORM ...
> ON ERROR (Resetit to Old Routine)
> IF llRepFormErr=.T.
> ...
> WAIT WINDOW "Report Form Not Found or
>Error Detected in Report Form"
> ENDIF
>
>
>I am especially interested in any input you have


Steve

If I were you I would test my memvar flag to make sure it still retains true when it gets to the Error proc. Put in 'wait windows' in different places to test you memvar & track it. I suggest 'wait window' over Trace because it executes MUCH faster.

Tom

>to these errors. I really want to know why I
>could not trap 1645. What more ca