>The way everything is seperate in .Net is nice, you have your language, then you have a set of classes, which are seperate, the Database is always seperate, not tightly bound - it's not a bad thing, it adds a lot of flexibility and until you can fully appreciate where .Net is coming from, most people won't get it.

.NET will be good as long as MS operating systems dominate the US project market. Problem is - new OS's are displacing MS (look at the stock price), and .NET is not needed on those platforms. Fortunately, VFP seems to work well on other OS's. VFP is desired on those platforms. But as long as you've got MS servers, I am sure you will be able to pick up a little .NET here and there:-)

Microsoft now finds itself in a position similar to IBM in the late 70's. The cost to lease an MS backbone and the expense [of masses] of relatively inexperienced OO coders to support that backbone is getting prohibitive.

Keep your VFP skills. They might prove helpful down the road.

>
>Kev