I know. But I'm amazed at the pettiness they exude. Correct me if I'm wrong, but I never once said anything to the effect of using another language.

My entire point was the vast majority of large dev teams are not using VFP. Therefore you should enquire of those using other tools to determine best practice. End-of-Story.

John Ryan seems to think that if you don't have anything specific to add to VFP and large teams keep your trap shut. Which is entirely missing the point.

I do have information to share with him as far as best practices go. It just happens to be on another website other then the UT.



>Perry:
>
>You should have learned by now, that the big guns on this site don't want to hear about other solutions, or facts, logic and experience for that matter. You're wasting your time trying to interject anything other that vfp into these discussions. they are very happy in their little pond where they can make the rules, and God forbid, they try to expand their horizons.
>
>
>>What the heck is it with you guys. I never once suggested that this question was unacceptable, never once suggested that he should not use VFP.
>>
>>My only suggestion was that in large corporate environments that employ teams of greater then 10 on a project, the tool is rarely VFP, and he would probably get more input into large team development asking in other forums.
>>
>>Its not a he said/she said type of comment, not a comment to incite. Just a statement of facts. Prove me wrong, fine. The comment was based on many years experience.
>>
>>