Dr. Watson error with unknown cause

[FoxRookie]

I am hoping someone can provide a little insight to an inconsistently consistent error that occurs in our app that I can not find the source.

We have a VFP 6.0 app that runs some old fox 2.6 screens. The error occurs from our citrix servers as Dr. Watson, but natively we will get a windows fatal error message. The particular module that is erroring has open as many as 5 screens; each subsequent screen is a 'child' of the prior screen. The final screen can be repeatedly saved with new data while the others are open. The error usually occurs after the user has saved 3 to 4 instances of the 5th screen and almost never before this point.

The Dr Watson log shows the fault occuring at the same point in the thread for each instance of the error. This happens regardless of the user or machine that is being used. The fault indicates that our app is attempting to access memory outside its memory space (i think?). Here is the Dr Watson code:

function: <nosymbols>
0c005421 55 push ebp
0c005422 53 push ebx
0c005423 8b1d4cf02e0c mov ebx,[0c2ef04c]
ds:0c2ef04c=77f646ca
0c005429 c1e702 shl edi,0x2
0c00542c 85f6 test esi,esi
0c00542e 0f84ab000000 je 0c0054df
0c005434 85f6 test esi,esi
0c005436 8b6c2410 mov ebp,[esp+0x10]
ss:011ee18f=????????
0c00543a 0f848f000000 je 0c0054cf
0c005440 8b15a47d300c mov edx,[0c307da4]
ds:0c307da4=010a0000
FAULT ->0c005446 8b0e mov ecx,[esi]
ds:07acd402=????????

I know little about assembly language, so this is pretty meaningless to me.

Is there a way I can trace the Dr. Watson error back to our code or some other diagnostic technique that can be used to unearth the source of my problem?

 

[DSummZZZ]

I don't think the folks in Redmond can even interpret Dr. Watson assembly dumps.

I have had fatal errors when trying to run Fox 2.x screens also. Usually READ DEACTIVATE is the culprit.
Dave S.