As you know I try to avoid replying to your messages, but here again. . .

You are getting one heck of a lot of mileage out of this "right tool for the job" statement.

Frankly, as far as VB/ACCESS/VFP/FP is concerned, VFP has to 'win' (ie BE THE RIGHT TOOL) just about always! That's simply because, as many have said quite frequently, there is virtually nothing in VB or ACCESS that cannot be done with VFP, *plus* VFP has always had GREAT DB capabilities while VB is only just now getting them with ADO.

So, puhlees, stop using that dumb line.

I also find it ironic that you, in the case you cite elsewhere in this thread, "deliver what the customer wants" while you will not countenance the prospect that a VFP customer might loathe and otherwise dismiss any type of (external, such as SQL Server) SQL.
I can only guess that your answer is to force him into it or walk away from the work. After all, **IN THIS CASE** the customer is unenlightened as regards the benefits of 3-tier and of SQL Server in particular.

In addition, it may be fine for you to learn every language out there, but most of us are not particularly so inclined. We feel that we have a pretty darned good language in VFP and we want to keep it that way - to keep it growing to meet trends and customer demands. To restrict it to a "premier middle tier" application is a folly, which I have pointed out often enough. VFP simply stops growing in those areas where developers (and their customers) need it to. As you no doubt know, it is the UI that most customers see and base their requirements on what they have witnessed elsewhere. We, VFP developers, soon will not be able to meet their requests.

VFP was always the right tool for the job (at least when compared with VB/ACCESS). So please keep that phrase for where it truly is applicable, like possibly VFP vs C++ for a high-speed cruncher with lots of rendered graphics or VFP vs APL for mathematical work.

Jim N

>Hi Bob...
>
>>Thanks, John. I guess most of my experience is rooted so deep in xbase it's >hard for me to see any other type of solution. I'm trying to see the light... >I've begun to see the light. And that being said, as president of the user >group here in Phoenix I need to maintain some degree of loyalty. They don't >call me the Fox-Nazi because I don't have any opinion on the subject (:-)
>
>Thats cool, and I totally appreciate where you are coming from. I don't really see the issue with regard to loyalty. Using one tool over another - because it is the correct to use - does not signify by un-loyal. Rather, it signifies that you are a smart developer. You know...not using a screwdriver to hammer a nail....
>
>I know about your group. Scott Malinowski - who lives in Scottsdale - is one of my closest and dearst friends. Heck, he taught me my first Fox class. He is the guy who showed me the power of Fox. I know your group is Fox specific. However, I would highly encourage you to expand the group to think in terms of Visual Studio - not a specific product...