>SNIP
>>As for the type of applications I am writing, believe me when I tell you that there are many Fox apps that could run just fine in Access. Access gets a bad rap, unfairly so...What I am writing is a simple client-tracking application that could be written in VB 6, VB .NET, Fox, Access, etc.
>
>John,
>
>See John, it isn't really a case of "best tool for the job" now, is it??
>

When I do the job for free, as a learning experience (sans a cost/profit motive), I pretty much can use whatever tool I want.

But I do agree the whole "best tool for the job" is just a fascade...

When your tool is a hammer, you see the world's problems as a 10d nail.

>
Surely you can agree that in the high majority of cases one tool is as good as the other in terms of getting the job done. In this case you have motives that make .NET the choice, but there is nothing "right" about that in terms of the tool's strengths.
<

I don't know about that. I would say I am operating at about 75% the productivity rate as I would be in VFP. At this stage of the game, I think that is pretty good.