>>Hi, Jim.
>>
>>>When you've got a tool that lets you do everything you need to do to make good robust applications that serve users well, you tend not to see any need (other than expanding Microsoft's coffers) to move to a whole new parqadigm.
>>>
>>>I was happy to move from COBOL to OS/Assembler. I was happy to move from dBaseIV to FoxPro. It tool me some time, but I was glad to get into VFP. I wouldn't mind learning another language. But on my own terms, when I need to (by my own factors) and not because my supplier has cut off development.
>>
>>And what changed now. If you have everything you need in VFP, you'll still have it for many years to come, plus many potential extensions the community will surely keep providing over time.
>
>First, it's now back to sales where the potential purchaser will say "I heard Microsoft has dropped development of VFP. Why should I get a product with no future?". This time the "dropped" is true!
>
>Then there's the continued development of tools that many of us have integrated into VFP. To date we've largely been able to have Word or Excel integrate easily for the users. Now that is over. As Word and Excel progress we cannot offer compatibility any more (users prefer latest file formats and may in fact need them in future).
>
>Ironic that this news comes the day after I started a new job... in a COBOL shop!
>

Not using COBOL, I hope!