Hi, Guy....

So, then you wonder, if Microsoft is attempting to maintain good will....wouldn't it make more sense to:

1. charge *more* for the upgrade (if they feel they need to and
2. eliminate the restriction of using the earlier version

Honastly. I just can't figure this out. The money thing works both ways. Over the years, I have bought and used FoxPro from versions 1.0 to VFP 7.0. I have spent thousands on MS operating systems, application tools, etc, and as a sysadmin, I've recommended or had my clients/employers spend millions of dollars on Microsoft products.

Usually, upgrade pricing is a incentive and reward to developers/users to continue using a product. Especially with developers, it doesn't make a lick of sense to then restrict them from using an earlier version of a tool to maintain an earlier application. If the upgrade is a good one, the tendencey will be to upgrade the old applications to the new version anyway....causing, (dare I say it)....ADDITIONAL REVENUE over and above what might otherwise have been spent, with no incentive.

This is nuts.


>I have mixed feelings about this.
>
>On one hand it seems draconian... and a punch in the stomach to developers (at least to those who are not regular subscribers to MSDN).
>
>On the other hand, the difference in price is what? A couple of hundred dollars?
>
>If I'm a serious developer with many clients, or if I only work for one company that does anything beyond trivial use of VFP, then a couple of hundred dollars is probably trivial in the big picture. VFP is still the cheapest game in town. (Except for Linux!)
>
>Guy