Perry,
>
>I WAS ATTEMPTING TO HELP.
>I HAVE LISTED IN ONE OF MY POSTS WHAT I CONSIDER TO BE A VERY PROFESSIONAL SITE WHERE THERE IS A SPECIFIC FORUM FOR TEAM DEVELOPMENT.

Giving the link in your first post probably would have been better...

>As a matter of fact, I've checked this thread as of now. All the replies to the OP, not focused on my comments, are focused on Version Control, all of the comments.

You might check my post again. Source control is mentioned, but not in the majority of lines. I touched quite a few of your other topics <g>.
>
>I've help point him in the direction of many other topics that come to bear in large team situations. I'm the only one not mentioning something specific to source control.
>What benefit is it to the OP to receive 20 replies, all basically stating the exact same thing?

Because IMHO any large team programming is not only dead in the water like a 1 or 2 man team without source control, but already sunk without everybody having noticed it. So I reiterated consiciously. And if you ever had the "pleasure" of working in a distributed team with source safe "Shadow" you'll probably agree also find it a stupid/error prone way to conduct source control, so I mentioned it.

This is coming from someone:
having expirience in other languages
having worked in 30+ sized teams in vfp and other languages
has helped implement round-trip integration of Rational Rose into a vfp project as well as a javadoc-like approach
thinking your base observation HAS merit, but could have been pesented better (with the link directly) to help the OP
that working in a team with implementation inheritance is gradually different than working with interface inheritance or no OOP at all

If you re-check your posts: perhaps a twice as long original post would have been more constructive/better use of your time compared to the many posts, of which some sound mostly defensive to me?

regards

thomas