>Are you even using local or remote views? Or are you using tables?

No views, im just doing very simple things with free tables,
in fact, the very dbfs that I copied from the old Clipper app.
And I am changing the table structure as little as possible,
just trying to get something working and useable in VFP
as quickly as possible.


>I was instructed to carefully clean-up by saying loParentForm = NULL
>(I am guessing that is the reasoning for immediately assigning NULL
>to an object after you are finished with it). Am I correct? Is this
>NULLing of objects the bottom line to fixing C5 errors in VFP6 apps?

>Well, nulling objects you've assigned during runtime to custom properties is >important to release any outstanding object references that might keep a form >from closing.

>For example, if a form has a custom property called oRef, that is intialized >to some other object during runtime (for easy access), then I must >assign .NULL. to oRef when the form is destroyed. Otherwise there will be an >outstanding reference to that object, and my form won't close.

But Im just curious to know.... was it the failure of
apps to NULL out objects after using them that cause all
those VFP 6 C5 errors? I saw a lot of talk in the news
groups regarding C5, but I had a hard time visualizing what precisely was
causing thos C5 errors, and what exactly was done to
remedy the situation and clean up the apps.

Thanks for all the help!

Bill Buell