>It does use the files in your local folders when it compiles. Source safe stores the files in a proprietary database. VFP only moves files in and out of source safe when you tell it to. When you build the application it uses the files you've checked out of Source Safe most recently. It won't automatically get the lateset files from Source Safe.
>
>>I've just started using Visual Source Safe with my VFP6 app. The first problem I run into is a program I run to get rid of all the printer info from the reports. I do this prior to compiling. All the files are now read-only so I get a cannot update cursor message. I went to the dos shell and unattribed the reports and ran my program. However, I'm not sure that these are the files it uses when I compile. I think it uses the files from the Source Safe folder. Does anyone know how this works? Thanks in advance.
>>Marcus.

Thanks for clearing that up Josh, let me see it I understand this for my situation. I need to strip the printer info out of each report before I compile. Because this is automatically saved with the report it will always be in my VSS copy of the reports. I will need to make sure I have the latest reports in my local directory, then un-attrib all the reports, run my program to strip printer info, then compile? Do you know of a better way to deal with printer info in reports? Thanks again.
Marcus.