Hi, Peter.

>Thanks for replying so quick. The HOW and WHEN of the decision is now clear to me. However, what I completely miss in your reply is the WHY of the decision. What are the REASONS. I need some arguments. There will be moments that a prospect or client comes to me and says: "Hey, I've heard VFP is dead!". What can I say then? "Yeah, they no longer see it as a strategic product". I'd really like to have more, and more impressive, arguments ready.

I think the why is clear in his answer:

>>Not sure how to answer this. We've said for years that VFP wasn't a strategic product. We said that one reason I owned VS Data was to get the VS team (and particularly VB) understand VFP and vice verse. We said that we were working on LINQ as well as Sedna.

Companies don't usually develop non-strategic products. I guess that with VFP, they supported the community by adjusting the product to newer programming paradigms (since VFP 7) like n-tier architecture, web services, xml messaging, etc. If you followed this path along the last versions, your eventual move to their main strategic platform (.NET) shouldn't be so hard.

So the answer to clients could be rephrase along these lines, in my opinion.

Regards,