>To anyone reading this...
>If you're a member of the Visual FoxPro Community and you'd like to make a >difference, I urge you to get involved. Start a VFP-related blog, answer >questions in the forums, get active and contribute to open source Visual >FoxPro initiatives such as SednaX, don't be willing to settle for less, and >last but not least blow doors off with Visual FoxPro on a daily basis. >Myself and thousands of other committed Visual FoxPro developers are making >a difference and believe me, you can too. Every little bit helps and >together we can do more in 1 year than Microsoft can do in 10 for our >beloved Visual FoxPro. To heck with the naysayers and their agendas... is >Visual FoxPro meeting the needs of your customers? If you answered YES, then >Visual FoxPro should continue to be your development tool of choice >regardless of what Microsoft is doing. I've found that if I take care of my >customers, my customers will take care of me.
What he said. I couldn't have said it better, even in French :-)
Why do programs stop working correctly as soon as you leave the Fox?