Hi Bob

I recommend you not integrate VSS with the VFP project manager. Just run VSS and switch between the two.

I also recommend you keep procedures/functions in separate PRGs instead of combining them into procedure libraries and to keep classes in separate classlibs as much as possible. That makes it easier to check stuff in and out and rollback changes. It also makes it easier to work with other developers.

>I'm getting really poor performance from VSS6 and VFP7 and I wonder if anyone has any advice.
>
>I have a large project (about 1000 lines in the PJX) which is under source control. From my client station (over Ethernet), it typically took 5-6 minutes to simply _open_ the project in VFP7 and about 20 minutes to get the latest version of all modules. Bad enough, I thought.
>
>Last week I hard a hard disk crash and had to switch to a new development machine. It is almost twice as fast as the original (now 1.7 Mhz Centrino), a faster hard disk, and twice the RAM (now 1 GB). I reinstalled VFP7 and VSS, restored by project backups, etc. Now it takes an _hour_ to merely open the project and at least two hours to update the project. (Dunno, it is still working...)
>
>I did "Clean up the project" in VFP and that didn't help. It has been a couple of months since I optimized the database in VSS or the server hard disk - but that wouldn't explain why I'm getting so much worse performance on one client than on another.
>
>While loading or updating the project, the Task Manager says that the CPU is only working at 35% (most of which is VFP). What is holding it back? And is that the only issue?
>
>I'm not ready to upgrade VFP now and I'd rather not upgrade VSS either unless it is nece$$ary.
>
>Thanks for any advice.
>
>-Bob