This question has been asked dozens of times in recent weeks and months. I would guess there are no fewer than 1000 messages on this topic in the last 6 months. The search feature of UT is intended for searching a specific or general topic or question.

The other reason I posted that kind of reply is that we do not control the future of the product (unless we all stop buying it). Those who know about future version(s) of VFP are under a MS Non Disclosure Agreement (NDA) and are restricted in what they can say. Consequently, those who are not privy (and therefore not under a NDA) have no way of knowing. The I have a friend who knows a reliable source at MS [seen is some of the latest threads] is also total hogwash.

Let's say you had a wiz-bang development tool that only a very few developers were using and it would do exactly what your customer wanted according to their requirements, 3 to 5-year plan, available funding, etc. Would you not use it even if its future 1 or more years down the road was unclear?

Let's also say Visual FoxBasic (VFB), introduced in the market place April 1 a few years ago by Carl Warner (I think), would no longer be a supported or manufactured product as of June 1 of this year. If I were currently using that product to crank out applications for my customers, I would continue using the most recent version to continue developing apps if it was the best tool for the job. I would only cease its use if a comparable or better tool became available. Hell, I would go back to Clipper 5 if that was the best tool for a particular job. Of course, we all know that will never happen. :)

The bottom line is, if VFP is the best tool for whatever you are to provide to a customer, you should use VFP regardless of MS's plans.