>The C0000005 error seems to be a very big problem with VFP 6 (or am I just taking it bigger than it really is).

It is a problem ... however ... I have rarely seen it occur in a user
environment ... and as such it is only you the developer that has
to put up with it.

>The question is, should I develop with VFP 5 while waiting for a real patch for VFP 6, or work with VFP 6 because maybe I won't get affected by the C0000005 error?

It is unlikely that you wont see it sometime .. :-(


>Is it too risky to develop serious stuff on VFP 6 right now ?

Definitely not ... the new capabilites in 6.0 are fantastic ...
and are well worth the effort putting up with occasional hickups during
development.

>I woulnd'nt want my clients to have problems with their systems resulting from >a bug with vfp6.

If you are just starting development on 6.0 then it would be a fair bet
that MS will have some sort of Service Pack out addressing such issues long
before your product is ready for client usage.