>Hi, Chris...
>
>Thanks for responding.
>
>The first answer surprised me a bit, because I would have thought that if I checked out a module for the evening at 8:30 PM and our backup runs at 9:30 PM, that the backup would not run, since (I had assumed) keeping a module checked out means the file handle is still 'open' and thus can't be accessed by a backup. Is my assumption wrong?
>
>Thanks again,
>Kevin

Source safe doesn’t really open files. It more creates them from its database. It is really a database that keeps a copy of your files with each changed version being stored with a new revision level. (This is a conceptual on how it does it. They state it has some reverse delta storage scheme. I don’t algorithmically how it keeps track.) When you check something out, it writes a copy from the database to your working folder. You could think of it like storing your program files in a foxpro memo field and when someone checks a file out you do a STRINGTOFILE(), pathed to the person’s working folder and then set a flag letting others know that someone has it checked out. That’s why you can have multiple checkouts and source safe will, hopefully, merge the changes of multiple developers.