Local Client Folder contents do not match

Patrickf · Post by **Patrickf** » Tue Apr 22, 2008 5:03 pm

In Vault 4.1.0, I have a folder which does not display all the contents that others see. For example, folder ABC has files X1, X2, Y1, Y2, Z1, Z2. All other users can see all these files while I can only view X1 and X2.

Further, I try to check out a file that the others have, which I do not, it gives all sorts of prompts. This is involving Toad and Code Control Groups. For example, if I want to check out Y1, it prompts to get database version. After finally getting it to check out, it is does not check in properly. What I notice is the file is added to my local working directory on my local hard drive but does not show in Vault.

Lastly, if I sign in as the admin in the Vault client, I can see the full contents of the folder. My personal sign on is set to be an admin.

Beth · Post by **Beth** » Tue Apr 22, 2008 9:19 pm

Even though you have admin rights it is possible for the highest level admin account to have limited your access on some items. Log in as admin and not your regular user name to the admin web page and check that you don't have any kind of denied access on those items.

If that checks out, what happens if you perform a Get on a higher level parent folder?

Further, I try to check out a file that the others have, which I do not, it gives all sorts of prompts. This is involving Toad and Code Control Groups. For example, if I want to check out Y1, it prompts to get database version. After finally getting it to check out, it is does not check in properly. What I notice is the file is added to my local working directory on my local hard drive but does not show in Vault.

I'm not sure I understand what is going on here. Can you post a screenshot to further explain this?

Beth · Post by **Beth** » Wed Apr 23, 2008 8:53 am

One other thing to consider. Do you have any pending deletes or moves for those files you don't see sitting in your Pending Change-sets? If so, then your client will act like that delete was already done even though you hadn't committed it. That prevents users from having other changes to that same file sitting in the pending area, because it can't apply other updates after it's deleted.

Patrickf · Post by **Patrickf** » Wed Apr 23, 2008 11:37 am

Thank you Beth. All the pending change sets did not want to commit. So, I simply undid them all. It looks like some items were left over from before we updated from version 3.5 to 4.1.

I am now reviewing and updating Vault by re-synching to the existing items I want in Vault. It seems to be working now.

Do you have any pending deletes or moves for those files you don't see sitting in your Pending Change-sets? If so, then your client will act like that delete was already done even though you hadn't committed it. That prevents users from having other changes to that same file sitting in the pending area, because it can't apply other updates after it's deleted.

Beth · Post by **Beth** » Wed Apr 23, 2008 4:25 pm

Thanks for the follow up on this.