>We currently have very many c5 and c6 errors in the vfp7err.log.
>
>

Fatal error: Exception code=C0000005 @ 10-10-18 01:23:41 PM. Error log file: \\ys0023sa\mps\mpsix\app\5.08.04\VFP7Rerr.log
>Fatal error: Exception code=C0000005 @ 10-10-18 01:23:41 PM. Error log file: \\ys0023sa\mps\mpsix\app\5.08.04\VFP7Rerr.log
>Fatal error: Exception code=C0000005 @ 10-10-18 01:23:41 PM. Error log file: \\ys0023sa\mps\mpsix\app\5.08.04\VFP7Rerr.log
>Fatal error: Exception code=C0000005 @ 10-10-18 01:23:42 PM. Error log file: \\ys0023sa\mps\mpsix\app\5.08.04\VFP7Rerr.log
>Fatal error: Exception code=C0000005 @ 10-10-18 01:23:42 PM. Error log file: \\ys0023sa\mps\mpsix\app\5.08.04\VFP7Rerr.log
>Fatal error: Exception code=C0000005 @ 10-10-18 01:23:42 PM. Error log file: \\ys0023sa\mps\mpsix\app\5.08.04\VFP7Rerr.log
>Fatal error: Exception code=C0000005 @ 10-10-18 01:23:42 PM. Error log file: \\ys0023sa\mps\mpsix\app\5.08.04\VFP7Rerr.log
>etc.

>

Hi Peter,

>There are also many errors WITH programlines-information. And although the example from above suggests otherwise, there are also periods that no errors are written.
>
Check your source code to WITH .RETURN.. ENDWITH bug.

>The puzzling thing here is that our users do NOT experience any crashes!
>
It's possible.

>Is there any trick to e.g. add any info to the messages that vfp7 writes to vfp7err.log?
No.

MartinaJ