yeah, but VFP is 10x better than VB6. VB6 is probably the reason for Webforms and web controls and all that "programming to an abstaction" crapola that ASP.NET relied on for 10 years until MVC came along. All that stuff is so last century. At least VFP can pretty easliy work with the new technologies while VB6 probably can't.

>I read in the MSDN magazine: "Microsoft recently extended 'It just works" compatibility for VB6 applications through the full lifetime of Windows 8" - not to mention Vista,WS2008 and W7. I don't think we will see the same announcement for VFP :-}
>
>>"MICROSOFT DOES NOT CARE ABOUT"
>>
>>I see no evidence of this. Yes, the product was discontinued, but every large company has discontinued products. It doesn't mean they don't *care* about the product or their customers. They have a legal and fudiciary responsbility to shareholders and if a product is deemed to not be profitable or strategicly important, it is discontinued. Everyone from Microsoft I talked to around the time the announcement was made expressed concern about FoxPro devs.
>>
>>>Not sure what you mean. VFP code and data will continue to work on Windows. All evidence points to this. Silly to think otherwise unless you're paranoid or just want everybody to follow you for whatever weird reason.
>>>Will the original GUI work always - not as likely. Re-fit your VFP code and data for the web and mobile on windows unless you must do otherwise for political reasons. Learn jQuery and jQuery Mobile if you need new skills for a job (and combine that with VFP for bang-up applications!)