The PJM issue is just having the right Vault settings set. And if every project tries to use Vault, that means you can SCCDATA that is making that happen. There is no other way for a source control provider to be called other than through what is in that memofield in the first record of the PJX.

Other than preferring integration (that's why they have vanilla and strawberry, right?), checkins through the PJX/SCCAPI integration products the SCA/VCA/MNA files, which together with a good source compare tool (Beyond Compare my favorite) allows for decent history checking.

I also use Vault for non-integrated usage: I don't integrate Vault with my various web sites, e.g., although I could.

Hank

>It's not the wrong provider, it's that it wants to open _every_ project with it, even my local projects which never even moved to another directory, let alone machine. And even when it opens it right, there was still the maintenance of the pjm file, which was initially nearly impossible to get created, and then once it was created, couldn't get it to be maintained automatically. There seemed to be a few non-intuitive steps in both creation and updates of this file (read: couldn't get it to work no matter what we did), so we abandoned the whole thing and went non-integrated.
>
>I have no doubt that you got it integrated right, but, frankly, we use Vault for several other things (mostly documentation) and there are many files which were never a part of a .pjx - so every team member has to learn Vault client anyway. And the three seconds delay and two modal dialogs every time I open a project is just too annoying, so I'll just keep this as is and worry about more pressing problems. This one I consider solved to my satisfaction - less automatic, but more control, the way I'm more comfortable.