><snip>
>
>Gaylen,
>
>>Perry you can make your arguments for switching to .net without having to denegrate VFP. I am sure there are plenty of negative things about .net, so why don't you issue warning about them also? All languages have their good and bad points. I prefer to dwell on the good and work around the bad.
>
>What seems to be an impossible mission is to have MS reveals in which cases VFP would be a better tool to use than .Net. We (vfp developers) know it but just some words from MS could really help in the sales of VFP and the overall perception of it.
>
>Still I don't really care because to me it's always been use the right tool for the job at hand. Sure It would be good for my ego to say .Net as much as possible when I come over here. Everybody wants to be a part of the in-crowd. But in the end it'll always be (for me) a financial decision.
>
>Financial decision because I worry about the overkill factor. For me (and my IT career) it would definitely be better to always push .Net and SQL Server. But I have a big problem, I respect the needs of my customers <g>.
>
>So I don't adapt the solution to the development tools but the development tools to the solution that needs to be built.
>
>At one time this was the way of thinking over here. But since .Net seems to be the best thing since sliced-bread there's been a weird (and unhealthy) way of thinking in the IT community.
>
>
>
>>Sorry if this is rather long. I broke several ribs playing soccer with my grandchildren yesterday and found it much more painful trying to lay down than sitting at the computer.
>
>If you grandchildren are old enough perhaps grandpa should think about changing to chess or chechers ;-)

Sorry to say it was a four year old.