Craig,

I haven't had a chance to do much with VFP 6.0 other than play with the new features. Have you tried converting an existing app? I played around with one a bit and found at least a couple of immediate problems. The thing that worries me the most is the idea of running into bugs that aren't known. With VFP 5.0 you can find out what the bugs are and work around them. If the question was about an in-house app or even an app for a single client I probably would have said go ahead with VFP 6. However, I know all too well that once you get something out there to dozens of customers it can be a major problem if there are bugs you didn't know about. For instance, VFP 5.0 shipped with a nasty new bug that caused queries to return the wrong results when using the general collation sequence.

>
>LOTS of bugs were uncovered and squashed in VFP 6.0....some that have existed since FPW. Most people working with VFP 6.0 beta experienced problems with the new stuff, particularly the component gallery, but VERY little of the existing things were broken. I wouldn't have a problem use 6.0.