SNIP>
>I don't see why people are afraid of picking up new tools, at least that's the impression I get, we all know how great VFP is, and what it's capable of, but we also need to cover our own backs, that is the bottom line.
>
SNIP
Hi Kevin,

For me at least it's not at all 'fear' of picking up a new tool, but factors like the following:

1) My deep preference is to get significant expertise in any tool that I use. It took me a long time for each of my 5 previous "primary tools" including VFP and I am eticent to do so yet again.

2) MS' marketing slogans like "right tool for the job" is 'bought' by many but is in fact a marketing slogan only! VFP is fully capable of being 'the right tool for the job' for virtually any APPLICATION project. Furthermore, adhering to that make light/moderate skill levels the norm and that is not a helpful situation to any business.

3) It is evident in the extreme that .NET is:
--- a very "wide" concept encompassing virtually all of MS' current producs and services;
--- a very NEW concept that has not yet even solidified at MS;
--- expected by MS to replace all existing software/applications at all shops some time hence.
These are NOT factors that should have everyone jumping into .NET with both feet any time soon. MS is going to burn a lot of money getting it RIGHT and the market could reject the whole thing before they do. And why would one want to suffer through MS' gyrations in that process?

4) My main interest is NOT promoting MS' product line but getting work for myself.

You know, I started getting into VB (6) when MS pulled the rug out from under it with VB.NET. I would rather set my own agenda than let MS do so and then switch to something new and different on a dime. That's great for MS but crappy for me.

There's lots of time yet before .NET catches on and if/when it does then I'll think seriously about getting involved with it.

cheers