Steve

Hopefully I am not telling you something you already know...

There are 2 ways to trap errors in VFP. First is the
Error method which only works if an error occurs within
a VFP method. Then there is ON ERROR which can handle those
errors outside methods. BTW, Error Method had priority over
ON ERROR so hopefully both won't fire. If no Error method
exists then ON ERROR should fire. Between these two I have
had pretty good luck.

I hope I helped

Tom


>I wuz just wondering how everyone else handles
>errors.
>I have, what I think is a robust, error handler
>which traps
>most errors. I have some problems catching some
>specific
>errors which may be untrappable (I am not sure?).
>It is these potentially untrappable errors that I
>am concerned about. I followed the layout in
>TasTrade example with an error handler in my base
>form base class. Some examples of errors which my
>error handler does not currently capture are:
>
>1238 - No Parameter Found. A form launching
>sequence bug in my system which should go away
>after I make the fix. But,
>why my error handler did not work is beyond me.
>
>1734 - No control source found/Property not found.
>
>1645 - Report contains nesting error. I have no
>clue to this one? It only happens occassionally.
>Also I have a
>error routine wrapped around the Report Form
>command which
>does not seem to catch this problem. It has only
>happened
>one time on my client's system.
>
>1538 - Stored procedure is executing. Well I get
>this
>every now and then. Usally when a user saves a
>record
>and a stored procedure is fired and they try to
>close the
>for