>>>The description for Event ID ( 1001 ) in Source ( Windows Error Reporting ) could not be found. It contains the following insertion string(s): 108596569995, 1, APPCRASH, Not available, 0, SYSMANAGER.EXE, 4.5.3.0, 47139f24, CTSCHE~1.OCX, 6.0.0.0, 3caddfa6, c0000005, 00011ee9, , ,
>>>C:\Users\ibirrell\AppData\Local\Temp\WER5A1E.tmp.WERInternalMetadata.xml, C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SYSMANAGER.EXE_ac15a9427849ae5698022abb852b369e9e0859c_00000000_06fa75f3, , 0, 2c55f1c8-f866-11e6-a93a-484d7ed12fa7, 0, 9263045ba7ea0d16285a5a8fa7da2e6d
>>
>>vfp9rerr.log should be in the same dir with the vfp app/exe in the client's machine. The C000... errors should be logged there.
>>Otherwise, I wonder if you could find more info about the OCX crash in the user temp ... WER5A1E.tmp.WERInternalMetadata.xml
>>*
>>The ctSchedule error code are listed at http://www.dbi-tech.com/download/demos/html/solsched7/flashhelp/wf_njs.htm
>>*
>
>Thanks, Sorin. I've asked for these files right now through email.
>
>Normally I don't communicate directly with the clients....

Correction: vfp9rerr.log should be in the same folder with the vfp runtime dlls, which may not be the same dir as the app/exe folder.
*