Commented Issue: FoxCodePlus 3.04 - C0000005 issue [33520]

I have seen this happen twice today. This can usually happen when using a BindEvent and expecting the code to be in a stable place.

To avoid this I have found the Event Target must call a second method being the Event Handler.
I see you have
bindevent(0, WM_KEYUP, this, "GetKeyPressed")

If you changed this to
bindevent(0, WM_KEYUP, this, "GetKeyPressed_Event")
and added the procedure
protected procedure GetKeyPressed_Event
lparameters pln1 as Integer, pln2 as Integer, plnKey as Integer, pln4 as Integer, pll5 as Boolean
This.GetKeyPressed(pln1, pln2, plnKey, pln4, pll5)
endproc

It should avoid it.

It is a timing problem in VFP itself. The "this.Intellisense.Showed" is most likely the failing line. Intellisense is known to be part of the object, however the pointer to the "Showed" property is not available to the current place.

Please check the other BindEvent handlers too.
Comments: ** Comment from web user: TracyP **

"Are you using VFP in background ?"

Hmm, My project is a large one. Instead of running tests in the current environment, I run them in a second VFP session. Flipping back and forth between them is common. If my code errors, it errors in the test environment, preventing troubles in my environment that I write code in.