Hi Susan

Server performance fluctuates depending on the tasks of the users. IMO, SourceSafe integration is more server intensive than using SourceSafe directly. Copying all files two and from the server is another potential drain.

Doing the build using a mapped drive will make the time vary depending on the server's ever-changing workload.

I suggest you try having sourcesafe be the only copy of the files on the server. It is all backed up too. Then go to a separate machine, get latest files and do the build there. IMO, the amount of network traffic for that should be significantly less than doing the build via the mapped drive.

>I wondered if anyone had come across the problem where the time taken to build the exe increases when there has been little change in the project.
>
>I am working in Vis Fox 7 and the source for the project sits on a server and is controlled by Visual Source Safe which sits on the same server. The normal method of making any amendments is to get the latest copy from source safe onto my local disk, make the changes, book back into source safe and then get the latest version from source safe into the master project on the server. I have a mapped drive to the server on my pc and build the exe from my pc (Foxpro is not installed on the server).
>
>When the project was first set up on the server, there was no problem with the build time but it has now changed from 3 minutes to 30-40 minutes. The performance on the server was checked while the exe was being built but it all looked fine. We decided to move the source onto a stand alone pc and when rebuilding the exe on there (again via a mapped drive on my pc) the build time was 4 minutes.
>
>The source was then copied back onto the server because it was decided it was a more secure location in terms of automatic backups etc. When the exe was built for the first time, it only took 4 mins. The only changes to the project have been to one form which I have changed 7 or 8 times this morning and each time the build took only 4 minutes but then suddenly the time has gone up and it now takes 25-30 minutes for each rebuild.
>
>Any ideas?