>Hi!
>
>I'm using VFP with psqlODBC driver. It causes periodically C0000005 errors if number of reports are previeved using REPORT PREVIEW command in old, non object oriented mode.
>
>Stack trace in VFP9err.log file points to READ EVENTS command:
>
>

Fatal error: Exception code=C0000005 @ 18.11.2020 22:41:28. Error log file: C:\myapp\algus\VFP9Rerr.log
>	Called from -  vkontkst line 0  { vkontkst.fxp}
>	Called from -  truusbaa line 0  { truusbaa.fxp}
>	Called from -  ON...  line 0  { }
>	Called from -  read_events line 0  { c:\myapp\algus\alguss.exe}
>	Called from -  alguss line 0  { c:\myapp\algus\alguss.exe}
>

>
>

* http://support.microsoft.com/support/kb/articles/Q143/2/84.asp
>* The READ EVENTS is placed alone in a separate procedure because this is 
>* the only way to reliably determine the line of code currently executing. 
>* MESSAGE(1) will not return the line of code within an .exe file or show 
>* whether the source code is present or accessible when the program is run. 
>PROCEDURE Read_Events
>READ EVENTS
>ENDPROC
>

>
>After the error Visual Studio debugger is opened (if installed) and points to machine instruction in memory which probably tries to access address out of address space.
>
>Where to find VFPA or VFP source code for debugging ?
>Can we try again to force Microsoft to open VFP source code.
>Or is there other idea how to research and fix this error.

Microsoft will not fix a bug in VFP. All you can do is ask Chen of VFPA.
http://www.baiyujia.com/vfpadvanced/f_vfpa_about.asp
There is an email on this side where one might ask Chen for help. He is last and only resort. Except you like to run through the assembler yourself If he is interested, he will do.
If you have legal considerations, ask M$ first. While waiting for response, move to Germany. It's perfectly legal to fix the bug yourself over here (or order somebody to do it), as long as M$ is not responding. There is nobody at MS able to do it anyway, so who cares?