>Not to beat a dead horse, and I'm not picking on VFP, but does anyone have any thoughts on the future of the language? If the world goes the .Net path and VFP is not apart of .Net then aren't VFP developers in trouble? It just seems like MS is starting to phase out VFP.
>
>Any thoughts?
>
>Jim
Hi Jim,
See
this one for example.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison
