>Don't forget to factor where in the life cycle VFP is. Being able to get into the front door is a factor. Even if there was a lot to learn, if I can't find work using the product, does it really matter...???

We can declare VFP dead if and when it actually dies. I won't make business decisions based on unsubstantiated speculation. Until then, I will invest my efforts actually creating applications, thereby building a large enough user base to tide me over with service agreements, should I need to spend a few months learning something new.

In my case, I see it as benifical to wait...the longer MS has to refine the product, the easier it will be to learn and use. The bleeding edge is always expensive to stay on. I'm perfectly happy to let you pioneers rassle the polecats and injuns for me, then build my homestead when its safe and sane out thar on the frontier.

That is, if, and only if, things are demonstrably finer on the frontier than they are back home. I've pursued enough greener grass in my life to know that the greenest grass is often, upon closer inspection, festooned with cattle droppings.

FUD you may say derisively. I say, approaching new things with caution is healthy, so long as you don't use it to justify avoiding all new things. If your wagon is rolling along just fine, it doesn't make much sense to risk jumping to another. Jumping because you have a nervous feeling about your wagon possibly catching fire is the mirror image of FUD...the unFUD. Call it FOO...Fear Of Obsolecence. At it's extreme, FOO is as bad or worse than FUD.