>Ack! Anyone had a similar experience?
>
>I've got an old FPW26 program that I now need to run using VFP9 SP2 runtime. Yeah baby, C0000005! And it is specifically happening on a BROWSE command. Every time.
>
>(XP SP3 here)
>
>I really don't want to tweak/re-write old fpw26 code in effort to circumvent this. I really want to see VFP9 work and not be brought to it's knees by a BROWSE command. Haha.
>
>Thanks for any input!
>Steven-
>P.S.
>* I issue SET RESOURCE OFF as the 1st line of code executed.
>* There are no Foxuser tables in the PRGs folder
>* Happens when running PRG within VFP9 command window
>* Happens when running PRG within VFP9 debugger
>* Happens when running .APP within VFP9 window
>* Happens when running .APP from a VFP9 "loader" .EXE
>* Happens on each XP SP3 computer I've tried it on (3 for 3)

C0000005 error occurs randomly from us.
As soon as you write a quite complicated application,
C0000005 becomes a feature of VFP.
A input sequence fire a C0000005,
redo the sequence and the C0000005 doesn't fire.

Another thing happens to us
with errors of temporary tables corrupt
inside transactional operations;
close transaction,
redo the operation and all is ok.