FWIW, I agree on all points -- but 11-5 from your other post may be a stretch :). Our paths sound somewhat similar, but you seem to have quite a bit more .Net exp than do I so far. I don't do as much client work as I used to and, since I have a .Net expert working for/with me here with an extensive background in VB and ASP before that, I mostly assign him to our web apps and I assign myself to maintain the rather large and ugly VFP/Oracle apps. When new projects come up that don't need to appear inside the menu of one of the VFP apps, if the .Net guy is booked, I use .Net myself to handle them (C#). I'm looking forward to making a big push in my learning with VS 2005 (further fueling, I'm sure, FWIW, the notion here that you can't really build an app with .Net today). And not because I don't like VFP or think it's inferior -- but because IMO I am more marketable knowing more than one tool and because I feel IMO that, like hammers and saws, there are times when one tool is possibly better suited to a particular purpose. OTOH, as I'm sure that you and others here are, I'm pefectly capable of using even a tool that's poor for the purpose to do a nice job and I've certainly done that in the past (both from my own choices and from outside decisions). I don't expect touting .Net to be popular here anymore than you probably do and I'm actually quite pleased that VFP experts are still so passionate about VFP. Were that not the case, VFP opportunities likely would be a much smaller % of the market than they already are. I'm just happy to have a place where I can learn from others, post my opinions at time, and have people's different perspectives available to help me learn more than I could in my own little box.

Kelly