Hi Jim..

The file vs. server based argument was something offered up by Mike Helland. I for one don't think it is a big issue.

As for what MS thinks, I really don't know what MS is thinking on this issue. If I had to guess, I would say the goal is to make the community feel they are being supported. One of the best ways to make a development community feel that they are supported is by innovating the product by way of new releases.

It is important to note however that all of this has to be managed very carefully. There is only so much that can be done to the core product. Let's remember that VFP is a mature code base. The more you tinker with it, the more likely it is to cause problems that will cost more money to fix.

Like any product, if enough people don't upgrade/buy a product, the product disappears. With respect to the service pack, since it is a patch, people will have to upgrade to 7 first and then apply the service pack via download. With this in mind, it would make absolutely no sense to wait for an upgrade.

While not trying to inject FUD into this mess, the fact is, if people want to see VFP continue, they better upgrade. I for one don't see an issue with saying this. It is nothing more than simple reality. Replease the word VFP with Office, Windows, or .NET for that matter. If the public does not consume those products, they will cease to exist as well.

As far as promotion is concerned, I don't think you are going to see anything more than you do now. Then again, I may be wrong. I have contended that VFP is a product that should not have to be marketed all that much. The people that will upgrade already use the product. An interesting statistic would be to know the number of people that did not use VFP - started to use it quite a bit since they already had it through MSDN. I don't know if you could ever find this number out. If you could, it would probably cost too much - thus obviating any utility gained.

I for one don't have delusions of protecting an intellictual property interest in VFP as some others have. The issue is upgrades - pure and simple. If there are 10 people out there who need the VFP OLE-DB Provider, they will need to buy the product. That means 10 additional customers that would otherwise not be had. I cannot argue with that raw number. I guess my question is whether those additional customers are worth ticking off the existing community. As is often said - perception is reality. Poll the VFP community as to whether the VFP OLE-DB Provider should be freely downloadable along with the other MS OLE-DB Providers - and I think you would find an overwhelming response of yes. The reasons may be different - but the end result is the same.


As I said to Mike, I think it was a badly executed decision...