>>I'm guilty of NOT practicing what I preach.... "Give me Details, details, details".
> >
> >In answer to your question, all of the updates have been applied (vfp6gal.exe, vfp6swiz.exe). I'm running verion 6.00.8167 (installed with Visual
> Studio) on a Windows 98 machine.
> >
> >I've been trying do regression testing on a collection of applications developed in VFP5 to see if I can upgrade the applications used by several
> hundred users (who are somewhat less than forgiving... imagine that)
> >
> >At this point I have UNINSTALLED VFP6 and reinstalled and still get the error. I'm sure the C0000005 monster was intended as a feature but at
this
> point it has become a feature killer instead.
> >
> >Again, suggestion are appreciated
> >
> >Mark
> >"The most common wounds are self inflicted"
>
> Does it only happen on this one machine?
>
>It is isolated to one machine, unfortuately it is the machine I use for the bulk of my development (Please no jibes about Windows 98).
>
>I've tried using a couple of the VS6 tools (ie the dependency tracker, etc) to find referenced to "buffdirty" to no avail, though I must admit to being a
novice at best when using the VS6 tools
>
>Mark

I'm sorry I can't be of more help, but it sounds like you've gone through the textbook fixes. I have little personal experience with this because I have
been very lucky with all my installs.

Maybe a call to MS is next? When resolving a problem like this, they usually don't charge or even deduct from your 2 free incidents.


Eric,

Thanks for the effort.

I'll post the resolution when I have it.

Mark