Agreed.


>As long as a decision is being made that is predicated on the best interest of the business - then no issue exists.
>
>Just as people should not stick with VFP for the sake of sticking with VFP, peole should not go to something else just becuse it is not VFP. Put another way, people should not go to .NET just because it is .NET.
>
>
>
>>>>So you agree...
>>>
>>>No...If a developer/client decides to stick with VFP for the sake of sticking with VFP and not going to .NET - that in no way diminishes what can be done in .NET.
>>>
>>>Note the following:
>>>
>>>Fox Myopia <> .NET not being able to do the job well
>>
>>Who said anything about .NET not doing the job well?
>>
>>That aside, I didn't say client/developer, I said client. A client who will not invest in .NET after having spent two years and a half million dollars on the VFP app they have which was just released last month. Continued development/maintenence will be in VFP, no debate. You cannot do anything in .NET today for this client. Which tool may be better is irrelevant to this scenario and it also has nothing to do with Fox Myopia, it goes to the reality on the ground today.
>>
>>>>>
>>>>>Your comment Eric does not go to the merits of the tool...
>>
>>I don't give a damn about the merits of the tool. You asked a question. I gave you an answer.
>>
>>Conider this:
>>
>>.NET Myopia <> VFP not being able to do the job well