>>This is not as simple as that. As a developer before I change or add another tool to the tools I already use there has to be advantages for me when using that new tool. I don't want to use a new tool just because it's the new cool thing on the market.
>
>Have you looked at .NET ?

No I have'nt looked at .Net yet. Like I told you before I don't need that tool.
VFP is still the right tool for what I'm doing.


>It is not just the new cool thing on the market, it has so many features we don't have in VFP and would be impossible to built-in. Just a few example: Remoting, Strong typing, free threading, multi-threading, etc...

Impossible? really? Perhaps you could've said that MS decided not to implement those things in VFP.


>>The sad thing is that there is a market for VFP. They could market VFP for that market. But there's a big risk. The big risk is that when you expose something good in a given market it could be badly interpreted by other markets as a tool they could also use. MS does'nt want that to happen. So they'll push .Net to everyone and it's perfect because they'll be able to push SQL Server and many of their other tools.
>
>No. They are pushing .NET because this is their preference. As a company it would be non-sence to push 2 products designed to do the same thing.

From that point of view every language does the same thing. But it would be harder to do those same things depending on the development tool used <vbg>

>
>>So in the end that's a lot of money. Do you think Bill G. would still be on top of Forbes if MS marketed agressively VFP. They sell one VFP. The developer is able to build a complete app with it without having to buy nothing else and MS does'nt collect money after that single license is sold.
>
>
>Every time i sell my application, i also sell SQL Server licences and my app is mostly written in VFP.

Even for those that don't really need SQL Server? MS must like you a lot.

>>Another thing. With VFP I've seen many loner consultants able to compete with big businesses on delivered solutions.
>
>
>I don't know what this have to do with competing with big business. This is about a tool you are using... If you use the tool well and are good at it you'll be able to compete with anyone.
>
>
>>Do you really think that with .Net it'll be possible for small companies to compete with the big guys. Yes probably for some years but overall the days of the independant consultant are counted.
>
>
>This is the fear i was talking about.... VFP and .NET are only tools to help you build an application. Like a hammer would let you build a house, if you can't use a hammer, no matter what other tools you use, you house will crash.

The problem here is that new hammer they just released must preferably be handled by many persons to work effectively.