>I just started work for a new client who is considering implementing VSS. I have never used it and only have a vague idea about how it is implemented. There are four VFP developers including myself.
>
>My main question pertains to procedure libraries. I understand there is a notion about checking out a file or set of files. But suppose each developer is assigned to work on a different project, but they have to make changes/additions to different procedures within the library. How will VSS handle that? Should I suggest to them that they use individual prgs? Does VSS handle this situation well?

When you need to make a change to a library, you check it out of VSS. This "locks" it so other developers can't also check it out and make changes (well, actually they can, but they'll be warned that someone else is making changes). Once you're done making the changes, you check the library back in. You don't leave the library checked out for huge amounts of time if other people need them; if you do, you might want to think about segmenting your libraries differently so that you don't have this problem. If two developers DO check the same file (which you can only do if it is a PRG-based library, not VCX), VSS gives you the ability to merge the changes of the two files together so that neither developer losses work.