How can I Add Extra Safeguards if Objects which have not been Checked Out can be Modified in a Controlled Location?
Applies to: VC/m
Situation
There are some situations where it is possible to edit objects which have not been checked out. This may happen, for example, when working off-line from VC/m, when not all editors are interfaced to VC/m or when the components are not write-protected. In these situations, extra safeguards can be applied to ensure that no changes are lost.
Solution
You can force VC/m to make the extra checks by modifying the behaviour of the check-out transfer as follows:
- On the check-out transfer route from the library to the development location, add the development location as a dependent location.
- For each physical location which the development location maps to, set the dependency check type to "Physical". This causes VC/m to physically compare the files before transferring.
VC/m will then give an error message when you try to check out any component which has already been changed in the development location.
Last reviewed: Dec 7, 2004
Back to VC/m Knowledge Base Articles
