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.
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.
The puzzling thing here is that our users do NOT experience any crashes!
Is there any trick to e.g. add any info to the messages that vfp7 writes to vfp7err.log?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
