That I understand, but u focus my point in the end where you said that a newer operating system may not run VFP, you said now way down the road, but that we can't know, how many times did people asked to ken levy and other microsoft guys if they where pretending in abandom VFP?
they never respond that that, they alwats tried to escape to the answer, then when they released VFP 9 they said that the final version we aren't going to develop any new VFp version.
Now VS.net 2005 will have prbs running on Vista, Microsoft said will resolve that on a post vista release, but will not deal with VS.NET 2003 can u garantie that VFP will work 100% when not even their flag development tool does? WHAT happens if will not work 100% and u have do do a bunch of workarounds?
are you and your comapny wiiling to bet the future on that?
I'm not.

>I never said I wanted to make the jump, but that I felt compelled as an IT person to bring this option to the table for all the reasons all of us have mentioned in this thread. I solicited opinions from people I respect that have made the jump, even some notable and vocal .net people, and gurus amoung the fox community. I argued in it's favor as not to show my clear preference for staying in fox. My boss's only problem with fox was it might be hard to replace me. The only positve of .Net for him was that there may come a time where MS's newest operating system may not run VFP well, which is possible but way down the road.
>
>As for the leader remark, it wasn't personal I was just pointing out the irony in your words. I forget we have an international audience sometimes and not everything translates.
>
>>YES i'm a leader for myself and sincerely don't care with what you or any other person thinks, never care and will not start now.
>>You said before that u said to ur boss that u should upgrade everything to .net and he said no, why was .net so good at that time that made you wanted to upgrade everything and is the evil monster and low class imature development tool now?
>>What changed? Was the fact that u wheren't allowed to do the jump?
>>This isn't a case of .NET against VFP.
>>
>>
>>>Yes you are a LEADER in following the mass of people MS has convinced to jump on the .Net bandwagon. You mock those who say Fox is the best tool for everything, when you say .Net is, neither is true.
>>>
>>>>Exactly my point some one sidf in past post u can be a leader or a follower trying to state that their where leaders cause they staing in VFP while I was a follower cause started to move top .net some years ago.
>>>>I've always been a leader at least a leader of myself and that is what matters to me, each one should be a leader of him self and never be satified with what he knows or thinks he knows.
>>>>and all this .net talk is pure rubishsince isn't .net that is in stake u can use what language u prefer, but as a leader of ur self and maybe of the people that may work with u and the company u work for u have responsabilities, now u can choose to be a follower and put ur head in the sand and say VFP is the best tool out there for everything and doesn't matter that it no new versions will be released aand this is all my point, I think my company will have work for the next years so I should I say something, when times comes we will see. That is the type of mentality i'm against and can't understand.
>>>>
>>>>>First off... My opinion on this topic was directed from the business point of view. As a VFP developer I well aware that my VFP skills will be in demand for quite sometime. Putting my company however in front of my own interests I'm ethically bound to move them to technology that allows them more resources. You can't serious expect a 12,000 foot boat facility to pick up and move to the city because they need VFP programmers! :)
>>>>>
>>>>>Also, you say "IMO .Net is not there yet,"
>>>>>
>>>>>With all due respect, my question would be what makes you think that companies like Dell or Merril Lynch are building massive ecommerce and investing sites on .NET technology that is unproven? I'm not saying this to knock VFP at all, it's the tool I know best. But it seems that you are implying that you somehow know more about .NET than the architects of some of the biggest sites on the Internet. While you can certainly choose or not choose to move to .NET I hardly think Dell computers is going to tear down their ASP.NET site and replace it with a pure VFP equivelent. One would have to ask if .NET is not there yet for you, why is it there for companies with far greater requirements than you most likely have.
>>>>>
>>>>>VFP rocks and I know it will be a long time before I will be as efficient in .NET. Companies however need pools of talent so they don't pay top premium dollars to get programmers to maintain their system.
>>>>>
>>>>>Greg
>>>>>
>>>>>>A mature programming language will not have major changes in core features with each release and will protect investments in code with high regard for backward compatibility, and will have developers with 5 years or more coding experience in that language. IMO .Net is not there yet, and won't be there with their next version either.
>>>>>>