>>In an existing app I'm debugging an issue that causes a C5 error.
>>
>>On some machines an error message pops up just saying "Microsoft Visual FoxPro has stopped working. A problem caused the program to stop working correctly" etc.
>>
>>On others a different, more detailed message comes up (see attached image). In this case it seems to also write a VFP9Err.log file to ..\Common Files\Microsoft Shared\VFP\
>>
>>I can repro the issue on my Win10 x64 laptop, but of course I get only the simple/non-informative message, VFP9Err.log does not get created.
>>
>>How can I cause the VFP9Err.log file to be created on my laptop?
>
>Create a better bug :)
Heh. That got me trying to remember the SYS() function to intentionally cause a C5 crash, turns out it's SYS( 1079 ):
http://www.sweetpotatosoftware.com/spsblog/CommentView,guid,04154aac-db86-4a65-acfd-8691ca1cb4fc.aspx
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
