>
Too many people here will be thrown off becuae the author cited Fox in his list of legacy stuff.
>

Clearly....< s >

>
Most of us went through the exact process he describes - keeping up with our FPW bread-and-butter while transitioning to VFP, and we all find ourselves keeping up with our < insert any existing technology > bread-and-butter while transitioning to < insert any technology that we are about to learn >.
>

Ah... you, and a few others got the point....I was beginning to lose faith....

>
Personally, I'm busy trying to guess which technology area will give me the most career choices in my local area (or in the company I'm in now) in three years, and finding ways to gain practical experience in that technology (playing around may not be enough). The choice seems to be between learning another development tool (VB.NET, C#) or learning another database tool (SQL Server, Oracle).
>

Focusing on more career choices - that is a good foundation to base your decisions upon...

>
Since I'm going to have some opportunities to learn/use SQL Server in my current job, that seems to be the road to take.
>

You cannot go wrong with SQL Server. I just finished teaching a 5 day SQL Server DBA class - it was a lot of fun...

>Everyone here would be wise to carry out the same process. You're not preaching VB, you're preaching that we should carry out this process.
>

Correct. Thanks for having a clue!! < g >