We only have 3 people. We use VSS and it is less work than that. (It is also much less prone to error.)
pamela

>VSS is really the way to go if you want to be able to revert to previous versions etc. It also provides a good way to do team development. However, we found it too cumbersome for our small programming team to use. What we do is we keep a "live" copy of our development project on the server. We split up the work into segments between the programmers so that we are not all working on the same program/screen/class/etc. at the same time. We just keep track of what each programmer is working on in a spreadsheet that we can all access on the server. Then we track in another spreadsheet every file that we change and a brief description of the change we make. Once we complete the version we make a copy of the "live" copy of the project into a folder that says the version number (i.e. "Version 2.1". And we then setup up two new spreadsheets for the next version and start over again.
>
>That way if we have to revert to a prior version we have a backup in the Version 2.1 folder. Everything is done manually so it's not automatic like VSS. But we found it to be easier to use since we have a small staff.
>
>If we had a larger staff with larger projects, I think we would definitely use VSS.
>
>-Don
>
>>Hi -
>>
>>Are there any general rules/guidlelines that can be implemented to track version control for a visual foxpro project besides version number and without using visual safe source?
>>
>>I just need to keep track of any changes made to programs/ forms. I would also like the ability to revert to an older version if required.
>>
>>Any help is appreciated.
>>
>>Thank you.
>>Neetu Kumar