I understand your fears, but I haven't had any problems. The "software" is what is stored in source safe (not in my working folder) and it is imposible to modify it without checking it out. I think that's the major feature; not the read-only flag stuff. In fact, you can set an option in VSS so that it doesn't make the files read-only when you check them in. VSS also lets you get latest version and make the files writeable. If the read-only flags help you keep track of what you have checked out, that's cool. I wish I could use them but they aren't practical for my setup.

>Mark,
>
>I've used VSS over a modem and it certainly does call for some improvisation. Still, this approach defeats one of the major features of source control software which is to make it difficult for people to modify code they don't have checked out.
>
>>>Hmmm... This makes me really nervous. It will only be a matter of time before you forget that you're not working with a checked-out copy. The next thing you know you'll make a bunch of changes then blow them away when you check out or update the files.
>>
>>been doing it this way for almost a year now and haven't screwed up yet! (knock on wood)
>>
>>my approach is framed by the large project size (248 files) and the fact that I use VSS over a 33.3 modem connection. I can't imagine having to check all the files out everytime I want to build an app to test my changes!