SourceGear Support

I suppose that's possible, but it is a short term solution unless we can somehow cause the script to be executed automatically with the check-in process. I assume that the latter is not possible. For the short term, we could use a windows version of the unix touch command. I would like to be notifie...

I was able to bring up VSS -- and I was mistaken. There is no option that I previously mentioned. However, I did look at some of the license files in VSS and they all had a 1970 date, which makes me think that VSS was defaulting them if they were out of range or something. Specifically, here's the d...

Is there a way to automate the batch file run so that it happens automatically (i.e., executed as part of the check-in) or is this something that would need to be done manually? I no longer have SourceSafe installed on my current laptop, so I can't point you to the option. However, I do know for abs...

What I mean is that we use a licensing package to edit license files (which are in Fortress -- we check them out, modify them with the licensing package, but are then unable to check them back in because when the licensing program saves the files to disk, the modification time/date on the file is se...

The log is attached. After reviewing the log, it seems the problem is with the file date on the file being checked in. You see, we use a licensing package that sets the files to bad values. In the past this has not been a problem because SourceSafe had an option to set the file date to the check-in ...

Have been using Fortress successfully for awhile now but recently began receiving the following error messages from clients when attempting to check in any file. I am not an expert, so I will need instructions if I need to provide any additional information, such as server-side logs. [6/28/2009 8:12...