Thanks again Hank. If you had to give me one or two recommendations what would they be? They don't have to be free, just not super expensive.

TIA,

Alex


>VSS is prone to corruption in the text files used for storage: there is a utility, Analyze, just to take care of this. That it needs such a utility speaks volumes. That said, we used VSS with SourceOffSite for years, and lived with the occasional (once or twice a year) problems.
>
>Vault is SQL Server backed. That has been the end of our corruptions problems.
>
>Hank
>
>>Hello Hank and others in UT,
>>
>>I haven't used SourceOffSite or any other Source Control other than for superficial testing, so I'd welcome a recommendation:
>>
>>What would you choose today for source control for VFP development so that it is easy and intuitive to check components in and out with the system taking care of as much of the housekeeping as possible. What do you think of SourceSafe itself (the version that came with Visual Studio 6.0)?
>>
>>TIA,
>>
>>Alex
>>
>>
>>>There is only one little trick (which I posted on the Sourcegear Vault forum a few years ago), in order to get VSSp-like behavior with regard to single-user checkouts and non-merge checkins.
>>>
>>>If you've used SourceOffSite, you'll know that there are extraneous VSS API error dialogs (it says an error occurred, none did). They have sworn to me that this is a VFP problem, using the SCCAPI in a non-documented manner. Anyway, with Vault it occurs much, much less.
>>>
>>>If you run into a problem with installing or moving the repository, their Support is incredible, in my experience.
>>>
>>>Hank
>>>
>>>>Hi Hank and others,
>>>>
>>>>Can you expand a bit on your experience with Vault and the VFP IDE, please. I haven't used Source Control before but am starting an ambitious project where it will be a must.
>>>>
>>>>Alex