I would say life's like that in episodes. And that you never know when the next episode is going to begin, or end. VFP.Net was one of those episodes (and has ended, of course). Some episodes last a long time, some are short-lived. The key just may be to move fast enough to catch the next wave, while also knowing which waves to forego, at least for the time being.

>That it was. I suspect deep down we're all romantics who just want the good times to go on. But life's not like that, is it?
>
>>Not once, eh: that hurts. And it does take years to hit the mid-market, building your way up, in order to gain credibility (the mid-market in my experience rarely uses more features than the low-end market).
>>
>>All in all, I'm glad I didn't wait until later to run with the Fox. In those earliest days, the developers hanging out on CompuServe's PCVENB were the legends of Fox history. It was a heady time.
>>
>>Hank
>>
>>>I jumped on the FoxPro bus when version 2.0 came out. PC Magazine came out with a rave review and it hit me at the right time. At the time I was an executive and former developer with a mainframe software company that had a lock on the big players in the grocery industry. I said we can reach the mid and small markets with an inventory control package that we sell for $50,000 and not half a million. Nobody wanted to hear that. But I bought FP 2.0 and fiddled with it in the evening and convinced myself it could be done.
>>>
>>>I was naive about marketing and didn't sell it once, even though it did everything the big iron version did and more. I thought if you build a better mousetrap the world will beat a bath to your door. Whoops. But that's how I became a PC developer.
>>>
>>>>I guess that applies to my adoption of FoxPro 1 -- I saw that windows in data applications was needed, not just desirable, and no matter that FP1 didn't really do it, I had faith it was going where I needed to go.
>>>>
>>>>BTW: I read about BB regularly from the time I started reading Time Magazine, which was about the time that Ike took office. <s>
>>>>
>>>>Hank
>>>>
>>>>>>>And I'd like if if WPF were going to be around for a while (well, it will be around for a while, it just won't be updated in any significant manner),
>>>>>
>>>>>Bernard Baruch, a sage investor (WAY before most of you were born) had a simple motto:
>>>>>
>>>>>"Buy too late and sell too soon."
>>>>>
>>>>>That's how most of us have to approach a new programming language. It just takes too much effort and time to allow for blind alleys and dead ends and the cost to the client for a bad choice can be huge.
>>>>>
>>>>>When it comes to making a serious investment in learning and deploying a new language:
>>>>>
>>>>>If:
>>>>>-there are some serious real world benefits (not "cool" stuff - although that's fun if it comes with the benefits)
>>>>>-at least 5 versions have been published.
>>>>>-thousands of serious business apps have been deployed and are still running and are being upgraded
>>>>>-at least 5 years have passed since its announcement
>>>>>-the publisher is obviously making some serious money with it.
>>>>>
>>>>>then, maybe a schlub like me can take a chance on it.
>>>>>
>>>>>That said, thank goodness that there are those quick-witted people out there who can blaze the trails with these things and let the schlubs see what's real and not real.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>And I'd like if if WPF were going to be around for a while (well, it will be around for a while, it just won't be updated in any significant manner),