>My question pertains to my younger brother and originally he was thinking in terms of being a small-business independent programmer/consultant in which case I had him started on VFP (BTW, IMHO I think this is where VFP will "exist" in the foreseeable future).
>
>Since he changed his mind and now wants to become a "corporate" programmer I immedately switched his focus to VB/MSSQL and probably ASP once he becomes comfortable with VB/MSSQL.
>
>As far as .Net, although I haven't even had time to install the beta on any of my machines yet (I got "real" work and slipping deadlines), I though perhaps he should bite the bullet and go straight to .Net but...
>

I think it's interesting that almost no one recommended VFP, and rightly so. For most situations, it seems that VFP is not the best choice for new developers, especially in a corporate environment. That doesn't leave VFP much of a prospect of growing its ranks. The likelihood of existing developers switching to VFP is probably less likely than any of us switching to another tool. I wonder how long it will be before VFP runs out of steam. Not too soon I hope. For now, I'll keep using the tool that works best for me.