I just wanted to add to my previous message.

I think Ian Simcock is right that the problem I have is in how I use Try Catch. Or the code the triggers this Try Catch.

Thank you.


>could it be that wofuncts has gone out of scope at the point when the error occurred?
>are you sure you might not have CLEAR ALL or CLEAR PROGRAM somewhere?
>if this is procedure library related, is there a chance that a RELEASE PROCEDUR could've been executed at some point?
>
>>Hi Ian,
>>
>>First, thank you so much for taking the time to write a detailed reply.
>>
>>I have been thinking about what you wrote all morning (here in the USA) and I still cannot duplicate the error.
>>I think I can only duplicate (and they understand the cause) if I can duplicate the error
>>"error reading...... wofuncts.fxp" That is, if the application cannot read this .prg/.fxp. But I can't figure out how.
>>
>>>Hi Dmitry.
>>>
>>>>Why would you think that 3 seconds after the 1st error the second one shows the error "Cannot redefine THIS."?
>>>
>>>Looking at your code, it appears that perhaps you misunderstand the scope of the Try/Catch. It doesn't just catch if the code between the Try and Catch fails, but also any code that calls. So it's possible that there is something going wrong in your dl_ErrorMessage function, or something it calls. Is there any chance that, since you have hard coded the source of the error in the logging code, that you have copied that error handling code somewhere else and have forgotten to change the name?
>>>
>>>Anyway, your error logging should not just log the Message property, but also the Procedure, LineNo and for completeness, the LineContents and Details properties so that you can see where the error actually came from.
>>>
>>>Of course if the problem is coming from a non code source (like VFP trying to refresh a grid and finding the cursor is gone) then even the the extra details might not help.
>>>
>>>Ian Simcock.