>>How do you handle check ins and check outs? How about generation of text files from forms, classlibs etc?
>
>Check out is exclusive; you can't check out what someone else holds, period. You may branch, you may go renegade, you may shelve a version if you want, but in the end you have to reconcile the changes yourself.
>
>Get SccTextX.
>
>We just gave up on it, because it needs to be run after each check in. First of all, it doesn't get you the binaries. If you set it to get them, then it'll report differences even when they should be ignored (just recompile, or changed ActiveX object ID). So you still have to keep the vcx and vct in, and then you need to take steps to keep the vca in sync as well... only for sake of being able to diff the files. We had a wrapper written which would generate the vca only when you want to diff, but like I said in the previous message, the trouble begins with finding which version of the vct is in sync with the version of vcx you're looking at.
>
>In the end, the combination of good intra-team communication and a little discipline makes most of these attempts to automate Vault pretty much unnecessary.
>
>But if you manage to get that done, post here :).

Thanks Dragan.

Alex