Hi Alexander,

Now in VFP8 when a object is free of reference he is destroyed ( that was not true every situation in VFP6 or VFP7. )

Don't add a small delay in object destructor, but simply avoid usage of code like loObject.Release() with RELEASE THIS as code in the method . Remove all reference to the object you want to destroy and he will gone without crash.

The changes I do in my project are
- Using native collection class
- Using BINDEVENT if possible
- Avoid programmatic release code


Marcel

>Hi Marcel,
>
>If possible, could you provide any info regarding the changes in your project? It might be helpful for us. I heard about a couple of shaman spells (like adding small delay in object destructor), but may be you know any real solution.
>
>>The move to VFP8 was also a C0000005 festival. Just recompile in VFP8 a project running ok in VFP6.
>>It's take me one week the to stabilize my project mostly by rewritting my object collections.
>>The way VFP8 handles object creation/destruction seem's different.
>>
>>Marcel
>>