William,

I don't think Microsoft is working very hard to keep VFP alive, but I certainly don't think they intentionally released a buggy product in an effort to kill it. Did you start with the first release of VFP 5.0? It had some real show-stopper bugs. They didn't apply to every application, but I had one that suddenly developed over a dozen new bugs after upgrading. There was a thread here about whether someone whose company's future depended on releasing a reliable application should switch to VFP 6.0. Some said that it had fewer bugs than 5.0 and should be a very smooth upgrade. I said don't do it unless you have time to put it through an entire testing cycle and you can wait for the first SP if necessary. 6.0 may actually be less buggy than 5.0 over all. The problem is that we now the old bugs and how to work around them. The new ones are much worse.


>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.. . ..
>