ProcessCommandListChangeset shows all files modified

[smartbear]

We have a customer who says all their files (or many more than expected) are showing as modified. We're calling ProcessCommandListChangeset to enumerate these changes. The log file from the Vault API is attached. We're calling ProcessCommandListChangeset at 1:25:34 in the log file, and it runs until 1:26:17. Can you tell why this is happening?

Thanks,
Eric

[Beth]

Vault will look at the timestamp of the file to determine whether the file was modified. The first thing to check is what is changing your timestamps.

If you don't want it to use timestamps, then you would set Vault to use CRCs to determine changes. That setting can be changed in the Vault GUI client under Tools - Options - Local Files.

[smartbear]

Beth,

I don't think the customer's timestamps have changed on these files. The Vault GUI client is working as expected - showing only changed files, regardless of whether the Detect using CRCs option is selected.

However, the API is returning all files in the returned list of changed files. The customer does have the Detect using CRCs option set checked (for files smaller than 10MB, which these are).

Eric

[Beth]

Can you clarify for me a bit more?

Is every file and folder listed when you use the API ProcessCommandListChangeset?

What happens if they run LISTFOLDER from the command line client? Information on that command can be found here: http://download.sourcegear.com/misc/vau ... LISTFOLDER. Does it also list every file?

An example might be C:\Program Files\SourceGear\Vault Client\vault LISTFODER -host yourVaultserver -user yourlogin -password password -repository "Default Repository" $/MyProject.