FindVaultTreeObjectAtReposOrLocalPath case sensitive

smartbear · Post by **smartbear** » Mon Jan 28, 2008 2:42 pm

Calling FindVaultTreeObjectAtReposOrLocalPath is case sensitive to working folder names, i.e., if I try to find the tree object for c:\work and the working folder is mapped to C:\work, then FVTOAROLP doesn’t find it. I have a workaround to do a case-insensitive match of a path in GetWorkingFolderAssignments first, then pass it to FVTOAROLP? Is there a better approach?

Post by **jclausius** » Tue Jan 29, 2008 10:08 am

In the Vault 4.1 code base, I can say this is not the case.

Can you shed some light on what you want to accomplish? Perhaps we can solve this together.

smartbear · Post by **smartbear** » Thu Jan 31, 2008 2:46 pm

A user has selected a unmodified file for which we want to determine the change history. To determine whether this file is under Vault control, I'm doing a FindVaultTreeObjectAtReposOrLocalPath with the local filename to get a VaultClientFile (VaultClientTreeObject) to work with. This call only works if the case of the folder matches the case defined in the GetWorkingFolderAssignments (regardless of the actual filesystem case).

This is in the 4.0.5 VaultClientIntegrationsLib.jar