>>>Guy,
>>>
>>>Look for a message that Ed Rauh posted in the last couple of days in another thread. From what I read there just the act of WinZip reading the file caused it to be committed to disk properly.
>>>
>>
>>So does using SourceSafe - at least the SCA is saved properly, and I just check it out to work on it to work on it and check it back in when I'm done - and in fact checkpoint myself often, which could be masking the SCT screwups.
>>
>
>If VSS and WinZip can do something to a file to make sure it's committed to disk, then can't we? There's got to be some file system operation (move/rename/read/write, whatever) that forces the file to be written. Once we peg what it is, we can add code to a project hook to make sure that all modified files undergo this operation.

What about flush?