>Hi Scott ----
>

** Thanks John.

>Allow me to reply :-)
>
>>
>>I think that this is a fascinating discussion. I've talked to people before about this, and there never seems to be a consensus. Microsoft says use the best tool for the job. Most of the VFP crowd say use VFP for everything including changing your oil and walking your dog. I had ties to VB before I ever started using VFP and I have chosen the route of learning multiple programming languages. Does this make me a mediocre programmer? Well, I guess that depends on who you ask. Maybe I am, but if I had been focusing on VFP only I'd probably still be mediocre....
>>
>
>The right tool for the right job is the best approach. VFP people are paranoid (rightfully) about MS support of VFP as an equal in the VStudio line and tend to circle the wagons. IF you're proficient in both VB and VFP it does not make you a mediocre programmer, on the contrary. It makes you a strong solutions developer.
>
>>Beyond that, do you ignore other tools or other ways of doing things? Do we have time to learn more about DCOM, MTS, ASP, N-Tier development? Do we ignore Visual InterDev? Can we spend a little time learning PL/SQL? I can't see us having time to do all of this either....
>>
>
>I think we are beholden to the latest architectures and technologies, yes. Assimilate and ignore knowledge as you see fit.
>
>>I've seen people who try to use one tool for everything no matter what, because that's all they know. This can be limiting.
>>
>>I think that VFP is a great tool for database work. It is my choice, but I also enjoy using VB. This is a complicated issue to me.
>>
>
>This is a complicated issue, no doubt. The overriding rule is, though, meet the needs of the client. Design and implement a system that does the best job at the best cost with the best robustness. There are no other considerations. True, honest consultants don't do otherwise.