In my case, I would be the one changing the binary on any system. So on the one hand, changes of those files would be rare, on the other, I don't mind VSS just overwriting the file without trying to merge. Therefore, I don't see why VSS should prevent me from doing this. Get Latest Version prevents me from accurately tracking changes. For example: Suppose I change a bitmap on one machine but don't check the file in till next week, at which time I have made so many other changes that I forget this one.

>I don't know if it can be done, but I can't think why it should be done! If a binary file is checked out more than once, how is VSS supposed to help you resolve conflicts?
>
>What you can do, is to do a "Get Latest Version", but in the options, select "Make Writable". The file won't be checked out, but you'll be able to modify it. Then, implement your changes on the other computer before checking back in again.
>
>HTH
>
>>I use Visual SourceSafe although I am the only developer on this database. I use and all version of foxpro and VFP but do not implement VSS under fox. Sometimes I find I want to develop something on my desktop and there is already another project under development on my laptop. I want to be able to check out all files including binary on both at the same time. Is this possible?
>>
>>TIA