Is there a way to lock or reserve files in Vault Basic 2013 so they cannot be checked out?
We have several parts/assemblies that we use over and over again that keep getting checked out/checked in repeatedly. We have been using vault for 4 months or so now, and some of these are getting up to version 30. Also, with these being checked out by different people all the time, there is the danger that these stock parts will be modified, and cause problems with other projects.
I was thinking of making a "dummy" vault account that can always have these files checked out, so it will prevent the check in/check out/changes of other people. I know that I could put them in a read-only library, but last time I dealt with libraries, when you did have to make a change it was difficult because of the read-only properties in the library.
Long answer is the 3rd part of your post is correct. I checked out to Administrator all of the files I didn't want other users from touching. This 'locks' them, sort of. A user can still touch the local copies but they cannot check the changes back in.
So it only half fixes the problem. I am in day 5 of upgrade to 2013 and Vault Workgroup, coming from Vault Basic. Using the Lifecycle States is a much better method of locking files. Same still applies to local file though. You can still edit them. You still dirty the file. But you CANNOT check the file into Vault.