IMHO, I would use VFP5. I've use both on my machines and at least on my computer, VFP5 haven't bombed yet whereas VFP6 have numerous times already. Unless you need to use a new feature that's in VFP6 but not in VFP5, VFP6 will run VFP5 apps with no changes. You could design it in 5 and run it in 6 and test and see what happens.

For me, I'm seriously thinking about "downgrading" my VFP6 app that's almost ready for deployment to VFP5 because of all the crashes. How's that for progress???

>I just bought a framework that works with VFP 5 or VF6.
>
>I a presently working with VFP 3.
>
>The C0000005 error seems to be a very big problem with VFP 6 (or am I just taking it bigger than it really is).
>
>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?
>
>Is it too risky to develop serious stuff on VFP 6 right now ?
>
>I woulnd'nt want my clients to have problems with their systems resulting from a bug with vfp6.