>>Ok, but you also can find bunch of similar things within any version of any product. The context of issue was about stability of VFP5a against another version, and this example does not hurt it much, sorry.
>
>Ed,
>
>The issue is that VFP 6.0 is the current version adn 5.0 is a past version. 6.0 will get serivice packs and 5.0 will not. The bottom line being that anything that is a problem in 5.0 will remain a problem forever, while problems in 6.0 will likely get fixed.

This is very understandable. However, the hard fact is that VFP5a is pretty stable products with just few minor bugs with known workarounds. It's another fact that VFP6 does not have the same level of stability yet and we can just guess what will be achieved here. Maybe some bugs will have to wait for the next version, who knows? When someone starts real project s/he should be concerned more about current situation.