>>>Since there is no apparent way to change a READONLY attribute associated to a file from a VFP function, I need to use the OS. I know I can do this at least three ways.
>>>
>>>RUN ATTRIB or BATCH file
>>>Windows Scripting
>>>API calls
>>>
>>>This is for my development machine, and using the RUN command causes the wonderful black boxes to bop around my screen. I am taking the ReadOnly off my data tables, DBF, CDX, and FPT files. I run this, everytime I start the test application, as SourceSafe sets the files as ReadOnly.
>>>
>>>If you were to do this, which method would you use?
>>
>>I wouldn't store my .DBFs, etc in sourcesafe. I'd convert them to XML and save that in sourcesafe, as VSS does a much better job of dealing with text files than binary.
>
>This is a good idea. We're just getting started with Visual Source Safe. However, the tables are included in the project. So the when the project is in VSS, it puts those in there to. Is there a way to put a hook in to convert them to XML?

You might be able to use a project hook, but we always did it as a manual process. We didn't have any of our tables in the project.