>>>When running in the VFP IDE for debugging, I disable the ON ERROR error handler, so that any error occurring outside of the TRY CATCH will enable you to debug directly on the spot of the error.
>>
>>Reading this thread, I got an idea. The error thrown up indeed loses some of the info which was available in the context... and from that I mostly miss the stack at the time when error happened. Now this may be a way out...
>>

aStackInfo(aa)
>>loExc.AddProperty("ast[1]", "")
>>DIMENSION loExc.ast(alen(aa,1), alen(aa,2))
>>acopy(aa, loExc.ast)
>>throw loExc

>
>That would not resolve it as the error might have been raised way deeper than the TRY CATCH, catching the error. There is no way to get the actual stackinfo at the line the error occurred once the CATCH fires.

Of course, but it would give at least the location (stack-wise) of that inner t-c, which is otherwise lost on Throw.