Hi Tracy,

it was in Gold Support. Here it is as posted but reformatted.

Problem solved. 

The problem was getting one file type, *.pjm, to check out concurrently, while 
having the other files types we use check out exclusively. In VSS terms, having 
multiple checkout for one file type (which we had to accomplish by using srcsafe.ini 
commands to make a particular directory multiple checkout, and all others not, in VSS). 

The (or a) trick in Vault is to: 

In Vault Admin, for the given repository (or all, your choice): 

a) make the entire repository concurrent checkout style (uncheck Require Exclusive Locks) 
b) take all but the single file type used in development out of the mergeable list of file types 

On the client, in Options: 

a) uncheck request exclusive locks 
b) indicate Make Readonly for checkout style 

Now, when the checkout dialog appears, request exclusive lock will be unchecked, when you know 
you really want it checked; but not to worry, as Vault will see all but the desired file type 
to be a "binary" file, and demand an exclusive lock anyway. 

Maybe all of this is not required; but since our work occurs through the COM API calls from 
our IDE in Visual FoxPro, I decided to make sure all defaults were what we needed on the client 
settings. Whether needed or not, it is working this way. 

Congratulations to the designers for making this workaround possible.

hth,

Hank

PS: while Support wasn't any help on this one, having the Support option is something I would suggest, since one's organization pretty much lives or dies with Source Control, especially in a distributed work environment.