Jay,

>Doug --
>
>I'd have to agree with you. And, Michael, many of us have wrestled long and hard about this very question. There are many threads over the past year to pursue for more info.
>
>I remember when the question was first presented at DevCon a year and a half ago. .NET had just been announced about 3 months before. The DevCon team scrambled to incorporate .NET into the proceedings, and ended up spending a day and a half strictly on the new framework. There was a lot of grumbling, about everything. It seemed like a "lose..lose" situation. If included, we lose most backward compatibility. If not included, it seems that we're being left behind.
>
>Since that time, it's been interesting to see the Fox team develop VFP in ways which integrate well with .NET. To me, it seems like a "win..win" situation. VFP has it's own distinctive identity and role in traditional database development, and it can integrate successfully with web services, .NET, etc.
>
>At this point, it's time in my career to branch out again. Getting as much info as possible on .NET. For strictly Web development, I'd steer towards that framework, with perhaps a role for VFP as middleware. At the same time, VFP looks really promising for n-tier database development, particularly if the desktop remains the primary target.
>
>Jay

>snip<

Yeah.. Understood.. Right now I just do not have the time. Even posting messages here is a time sink I've had to back off of. Ugghh.. Of course, if this pays off.... <g>