>I guess we are on the skepticism bandwagon over the state of VFP and what M$ wants to do with it. Here is what brought us to this side of the table (comments, suggestions and insight are appreciated). We led the charge to convert to VFP 6.0 and VS 6.0. In retrospect, we should have relied on our experience with upgrades but our intuition suggested that this upgrade shouldn't be any worse than 5.0. Well.. . ..
>
>1) We became the victims of one of the 17 first documented bugs. When you execute multiple SQL queries in a group of code, each subsequent query "suffers a degradation in speed to complete the query". The degradation was double the speed in our experience. Trust us that we tested the same code and data on the same machine, and tried to give both 5.0 and 6.0 the benefit of the doubt as to comparable operating environments. M$ solution(interim) was to change all "where" statements to "having" and that would solve the problem. Well....... it now takes between 3 and 4 times longer to execute the query in 5.0 vs. 6.0

I too am waiting before upgrading multi-user apps to vfp6, I know first releases tend to be a little buggy. But in regard to your query comments, this is certainly not true for all SQL in 6. I have a small app where I do SQL more than 10,000 times, as much as 1,000,000 times in some runs, and I have no degradation. In fact, the 6 SQL runs noticeably faster than in 5, possibly because there are string comparisons...anyway, not everything is slower in 6 :)