>J.
>SNIP>
>>I agree with your point of using the right tool, however the choices that a programmer has are not always that broad. Will I go learn C# for everything .Net or will I use VFP.Net if I had the option?
>
>Well, if a project that didn't need data munging and didn't need creation of an OCX came along and a person judged that VB (plain or .NET) was "the right tool" wouldn't VFP be just as "right" as the tool?
>

Exactly. Let's take the example of a Windows Explorer type of application. You would think that a general purpose language like VB could fit right in, (in fact there are gazillion examples of how to do this in VB) but VFP could be used just as well without the need for esoteric Windows API calls.

>
>>
>>I guess I'm dragging the point too far out, so let me just summarize that this VFP programmer will not let VFP die if it went .Net.
>
>Me either.
>
>>
>>Cheers,

PS Hey, it wasn't until now that I noticed the "H" in your sig. That's funny!

.. not that that's what I think of you or anything like that :)