>Is it me or Visual sourceSafe is simply unrealable and should be avoided at all cost. We started to use it about a year ago and since then we went from using it within VFP to outside VFP. When using it inside VFP, We got verrrry slow response from it when checking out or in. Using VSS outside VFP with VSS explorer to check files in and out solved the speed problem but one problem which is common to both method is data corruption.
>
>And corruption it is... Man, every month or so we have to rebuild the VSS Database from scratch, it get so corrupted it is unusable and unrealable. Maybe we are not using it properly, maybe we are just ignorant... Well, trying to solve this problem i red every single doc about it in MSDN and many other FAQ,s but i still don't get it. Maybe our setup isn't right. Our VSS server is NT Server 4 SP6 Using TCP/IP Only, and we connect our Win98 clients using network Drive.
>
>Is anyone here has the same problems ?, If yes, how did you solve the problem ?, Anybody using any other products which prooved to be better.
>
>VSS is a great concept, we couldn't work without it, source control, when working with a development team is essential but is our source database gets corrupted, what's the point !!
>
>I am very frustrated with this, this morning, again..., i have to rebuild our database. Damn VSS !!!


Using VSS will slowdown your development some, but you should not have the problems you are describing. There are several KB articles on using VSS with VFP. You can get to them at http://support.microsoft.com.