>I noticed that many developers seem to have upgraded until VFP version 6, but then stopped. At work we still use version 6. I suggested upgrading, but it seems they are not too keen on the expense. A while ago, the reason was rather the compatibility with operating systems (version 8 or later is not designed to work with Windows 95), but by now, that should be irrelevant.
>
>I was wondering, for what reasons other develoeprs remained with version 6. Is it the upgrade cost? The Windows versions supported? Not enough time to learn the new features? Or some other reason?

As a self-employed contractor I run into this dilemma all the time. In fact, tomorrow is my last day on a 12 month contract working on an application that was originally written in 2.0 DOS, run through the converter to Windows and then again to VFP. The version I was given as a starting point was in VFP 6 and a year later... it still is. The company has a MSDN Universal Subscription so cost is not the concern. It is still the operating system that is driving the decision. More than 50% of their users are still on Windows 95,98 or ME. And their customers have no intention of upgrading without a much more compelling reason.

And to emphasize my point, my next contract is upgrading an application used by the Elks Lodges to, you guessed it, VFP 6 for exactly the same reason. The large majority of their users are still running 95, 98, or ME.

I try to think of them as future customers that will upgrade... eventually.