>What about the famous, irreverent, concurrent, indomitable error C000005 with the new vfp Sedna version ?
>It will be 'include' 'again' into vfp Sedna ?
>If so, what can we do with that bad boy ?, maybe live with him ?

Huh? Explain to me please how did they "include" C05 to begin with? It is a Windows error, not VFP's. It is Windows way to say, I don't know what's going on. It used to be called 'General Protection Failure' (GPF).

What they did with VFP 8 and more on VFP 9.0, is tighten up memory and other problems, and dealt with more errors internally reported by VFP, leaving less instances where VFP cannot deal with it, passes it to the OS which in turn issues a GPF message (called C0005 now).

What you can do to minimize them if you get them is do more/better garbage collection and not leaving dangling object references.

Sedna is not a new release, but a set of enhancement routines. It will not touch the core so it will not have any effect on C05.