>>Fernando,
>>
>>My goal is not to posture for MS at any level. I'm simply giving what I believe to be a very practical example that contributes to this thread. It's as much a disservice to only present a positive image of Foxpro as it would be only to present a negative one. Would I encourage anyone to start using Foxpro as their primary development language? No. Do I believe that it is a valuable tool that has basically supported me for the past 13 years? Yes. It is a great language and tool, but it is not the future and unfortunately for some of us the future matters a great deal.
>>
>
>Hi Jay,
>
>"Would I encourage anyone to start using Foxpro as their primary development language?"
>Yes I force all my coder to past VFP cource.
>Why because main advantage of my firm creating MIS - web or client server is that in difference of other firms we gain from our DB expertize.
>If behind some ASP.Net, C# or VB.Net UI is not written stronge datamanipulation code the system is good for nothing.
>That was one of the reason that VFP is fate to success in long run
>
>my 2 cents

Do you believe that Foxpro is the only language capable of strong data manipulation? Or that SQL Server does not handle data well? I love Foxpro, but I could not in all honesty recommend that someone just starting out use it as their primary tool. Nor would I recommend someone move from another visual language to it. That is not the future. Just because JVP takes a lot of heat for not having practical data to back up his claims doesn't necessarily mean he's that far off base. Our own shop is looking to move to another technolody in the next couple years. I will use Foxpro as long as it is practical for me, but I'm also starting to learn VB.Net and ASP.Net. Just in case, you know...