>I've said this before, and I don't mind saying it again, the future of VFP is in our hands. As long as we continue to use the product to produce the results that our customers are looking for, it will survive, because it will be profitable for Microsoft to continue to invest time and resources to improve it. Sitting on the "pit pot" and moaning about how much we're "unloved" won't.
>
>The future of VFP doesn't depend on whether or not it partipates in the CLR. From my POV, it would be a gross mistake to make VFP a CLR compliant language. The mindset of some people is that "everyting belongs on the Internet/Intranet". In truth this sort of thinking returns us to the days of "Big Iron". The fundamental reason that PCs rose to such popularity is the fact that they put power into the hands of the users. Every application does not necessarily belong on the corportate Internet/Intranet. The sad thing is that most people (fron my perspective) don't realize this and will fail to take advantage of it.


I'm glad to see this rant. I like VB, but the more I use VFP, I find I like it even better (though I have to admit the texts available all seem to be oriented to the FPD/FPW hacker who is moving up, not the beginner who just popped the VFPx cd in and started working), but as I've said in the past here and elsewhere--just use whatever tool gets the job done.