>Hi,
>
>I'm working in a really big team, all VFP and only VFP (actually in the bank there are others teams that works with others tools, but mine is working only with VFP). We are something like 25 (developers, business analyst, testers, support, etc).
>
>I'd like to share some experience with people working in a big VFP team like us. Is there someone that can share some experience with me?

The largest fox team I worked with had seven programmers. Actually one other had more fox programmers, but by the time I got there they were told by someone in M$ to switch to VB/COM/ADO/ASP, so the VFP part of the equation was just about three of us at the time. And the VB code actually never took off, the company sank :).

In any case, there were two crucial things: the common code had to be checked and cross checked, and it had to be the same across the board. While the topography of the teams varied from one big project with programmers hitting parts of it as they came, to dozens of apps for hundred customers, the common codebase had to be rock solid.

In each case there was a framework, either a homegrown or commercial. Commercial ones would get tweaked anyway. The protocol for each change in the framework had to be strict. Every time we had a breach of protocol, it bit us. For example, if a programmer started working on a newer version of some system routine, he had to keep that local to the app he was working on, under a slightly different name. Once it passed muster (i.e. worked anywhere it was applied), it would be copied over the master routine, and the local version was deleted. Then it had to be distributed to all the apps and would be in the next build of each.

Source control only makes this easier - it still takes discipline.