The jobs argument is the only one that holds any water, and this is the first post in this thread that states a useful argument. But on the other hand, if you feel you have enough work to finish your career and are primarily working for smaller companies (under 50Mil/Yr) there is little compelling reason to move on.

Bob

>And there you have it.
>
>>Greetings,
>>
>>I will wade into this and say that although I've been a VFP programmer since the beginning and we are 90% VFP... It's very appropriate from a business standpoint to begin transitioning to .NET. This is not because VFP is cannot do everything. It has to do with looking out for the availability of a large quantity of talent for the businesses that I work for.
>>
>>While personally I have no problem at all with VFP, five or ten years from now, businesses that have 100's of thousands of lines of code written in VFP will see a shrinking pool of talent available to support and extend those systems. Moving toward .NET helps protect a business from being cornered into a system that a fraction of people can support compared to .NET. From a business perspective, VFP leaves a company with far fewer options in finding resources than .NET. This is far more critical in making decisions than if VFP can or cannot do the job as a tool. An analogy would be buying a car that only 10 mechanics in the entire world can work on compared to a car that has 1000's of mechanics available. The cars may be equal in performance, but when it comes to maintenance and repair there is no doubt which one is going to be easier to find mechanics for.
>>
>>Greg
>>
>>>Fine, that works for you.
>>>My plan is to take my investment in Fox and ride it out until I cannot find work, that works for me. I use one platform for windows app, web apps, etc and can access multiple types of data (dbf, sql, oracle, MySql, etc)
>>>Again no example of anything fox cannot do.
>>>
>>>>I thought that answer is simple I will never invest any new time or new development on a language that will not have anymore new releases and is a legacy application for the future.
>>>>Dos applications can still run in windows and 16 bits apps also would u developt it ur new applications in FOXPRO for dos?
>>>>again I prefer to have 1 underlying platform so I can do all my data access in 1 language and then using it from a windows app, web app PPC app....
>>>>
>>>>>You are a leader using VFP, one product in .Net, switching to .Net to be perceived as technically hip and fresh.
>>>>>
>>>>>Again, what are you doing in .Net that can't be done in VFP, and if you wern't planning on slapping .Net all over the box, why would someone care.
>>>>>
>>>>>Bob
>>>>>
>>>>>>Exactly I said that before, we are the leaders in our industrie and we like to keep it that way.
>>>>>>
>>>>>>>BTW, I looked at your product line, mostly fox, well received by your customers. Why is it not all .Net, well you say that will take years of programming, there is one reason not to go there. Time, Money, Risk
>>>>>>>
>>>>>>>You also mentioned your employer feels to be in the .Net arena for marketing purposes, fine, but I don't see what else your gaining from moving to .Net, just MS hype your customers have bought into. But I agree it can be important to go with the herd, and if you feel you need to do this to sell your product, there is nothing wrong with this.
>>>>>>>
>>>>>>>How about some examples of what you can do in .Net to enhance your products that could not be accomplished in VFP in the same time frame (multiple years)
>>>>>>>
>>>>>>>Bob
>>>>>>>
>>>>>>>
>>>>>>>>Tracy that was my exact point, but u shouldn't blame the MVP's this is our profession we do it for a living, i'm not a MVP let me state that even before some one start saying that I think i'm better then anyone, I don't think that i'm not better or worst then any beguinner or MVP or expert, I'm what i'm and i'm proud of that.
>>>>>>>>Now as Professionals we must think with our head and not with our heart.
>>>>>>>>as I said before in my last devcon I saw the written in the wall, and I wasn't listaken as time prove it to me.
>>>>>>>>I didn't wanted VFP in the framework cause by then you would loose all the VFP advantages, I would like to see VFP as a standalone product with just integration with SQL like it was a VFP data.
>>>>>>>>now all the work is being incorporated into .net framework, most of latest ado.net changes and speed improvements have come from VFP and that is great, but for me isn't a enough reason to stick only with VFP.
>>>>>>>>
>>>>>>>>
>>>>>>>>>SNIP
>>>>>>>>>>My dream was to have VFP interact with SQL the same way it interacted with VFP data.
>>>>>>>>>
>>>>>>>>>We shared the same dream. I also wished that VFP would be IN dotnet - I don't care the reasons why it couldn't or shouldn't be - it will always have been my preference that it be IN dotnet - however it was managed. (I think the writing on the wall was overwritten in bright red bold letters when it was NOT and sadly I think our most valuable professionals helped nail the lid on the coffin at that time) My dreams don't typically come true as I haven't won the lottery yet. However, last night four deer walked in front of my car when I was backseat driving home (my 15 year old was actually driving (now that is a nerve-wrecking experience) - is that a good omen or a bad one? :o)