In my experience the number one cause of GPFs in VFP 3 and 5 is not releasing your object references.

To clarify: VFP is supposed to garbage-collect for you. In 3.0 it certainly doesn't. In 5.0 the situation is better but far from perfect.

Example: If object A has a property oParent (or any object property pointing to any object), then in the Destroy() of object A you should say
THIS.oParent= .NULL.

The full story is this: If objects at the same level of lexical scope have a relationship between them, then you should clean up the pointers in that relationship yourself.

By lexical scope, I mean if objects that are destroyed together. In essence, if an object in a Form points to an object on a page in a Pageframe in that form, then these are at the same level of lexical scope by virtue of being members of the same form.

I'll bet you a keg that this is your problem.

Lurkers, note: The quote is *AFTER* the reply. In this forum, I spend more time scrolling throgh crap I've already read many times Grrrrr.
*---------------------------------------------

>We are a long way through development of a large app but cannot eliminate general page fault errors in many areas of the program. using VFP 5.0a but had it in older versions.
>
>Does anyone have any ideas ?
>
>Stuart Law, Tailored Business Systems Limited. UK
>slaw@tailored.co.uk