Thanks for the info. I'll give Markus' program a try. I've taken to leaving the project closed and checking class libraries out directly through VSS and modifying classes with "MODI CLASS ?" It seems ashame to have to work around the project like this, however.

>Michael,
>
>My company has also experienced this same problem with VSS and it only seems to be a problem when you're dealing with large projects. Basically, what happens is VSS has to iterate through every file in the project to determine its checkout status. Obviuously, as the project grows larger, the longer this will take.
>
>So what my company has done instead, unless we're adding something new to the project which forces us to open it so all the files are added properly, is that we check stuff in/out straight through the VSS Explorer. This is a LOT faster than opening the project and 9 times out of 10 we're just modifying existing classes or class libraries, not adding new class libraries.
>
>To get this to work properly however, we're using Markus Egger's VSS Boost program available at www.eps-software.com to make sure VSS knows there's a newer version of the file we just modified. (VFP doesn't do this for you if you modify a file outside of the project manager) Basically you run this program just before you check in your changes.
>
>Travis
>
>>Has anyone else had performance problems opening VFP projects which are under source control using Visual Source Safe? We have the source safe database on a fast server with multiple 100mbit cards to the network and it still takes anywhere from 2-8 minutes to open our projects. Suggestions?