>>Some replies will tell that it's good to add another tool to your toolkit when in fact this argument is bogus.
>
>As a profossional developer, it is *always* a good idea to put another tool in your toolkit.

You're absolutely right. The real problem here is where do I begin and where do I stop?

Is .Net really the thing or isn't there something else being developed behind closed doors by MS competitors that will be the REALLY BIG thing?

So if I invest my time learning .Net and then 1 year from now .Net is not the thing anymore then what? I'll have wasted 1 year of my life learning what was supposed to be the BIG thing. So if instead of learning .Net I invest that extra time learning javascript because to me VFP is still doing a great job, is my decision really that bad? Not to me.

Perhaps to many others. But in the end we're just guessing what tools will be the best to put in our toolset. It seems to me that no matter what I learn I never have what they're looking for in the jobs section in the newspapers. There's always stuff where I'm wondering "What the heck is that?"

So perhaps I know something that others don't or I can feel it. Perhaps VFP9 will have marketing like no other MS development tool enver had before. Perhaps, if, maybe. We have a lot of those in the IT field.