>>>>There is an intermittent bug that only happens about 1 in 100 cases at customer site,
>>>>I was hoping I could use Coverage to find the bug, but it doesn't work in RunTime Environment.
>>>>
>>>>Other than having to install the entire VFP development on those machines, is there an alternate way to achieve this?
>>>>One thing I could do is to sprinkle lines of code in different parts of every module involved and create a semi-coverage that way.
>>>
>>>Is there any way you can detect the error, during run time, when it happens?
>>>
>>>If so you can call a routine that records the call stack, contents of memvars, open tables etc. in much the same way many enhanced error handlers record that information.
>>>
>>>If the bug is actually causing a VFP error then you could enhance your error handler.
>>
>>Thanks for the tip. The bug actually is somehow intermittently (about one in 100) in RunTime my save process REVERTS BACK the changes made.
>>
>>So it is not an ERROR to capture. The only I can find out why is to register the Code execution and see at which point it causes the changes to revert back.
>>
>>So now instead of using COVERAGE I am putting in a bunch o single command CALLS in the SAVE process to register where the program is going in the hope of when it happens the user will to upload the LOG..
>
>If your SAVE code isn't too complex, another option would be to copy it here. Someone might spot something.

Yes, that would have helped, but unfortunately it spans over many classes and commands. There is a lot that gets done in the Save process