>I'm in a catch-22.
>We have just installed VSS 5.0 and I was adding the first project. I had opened VFP5 and opened the project file. Then, I selected the menu option to put the project under VSS control. Things were adding along nicely until VSS encounted the DBC file. It barfed a lung with the msg that I can't add the DBC while it is open, so "Close the file and then add it." Well, you (or at least I) can't close the DBC without taking it from the project. So, the only way I can add it is to close the project. Then, from VSS, I select the add files option and select all four files associated with the DBC. Here is the rub - VSS shows the files in its project list, but VFP DOESN'T show that the dbc or its tables have been added to the project (i.e., no blue padlocks show up, or no red check marks when you check them out.) You can check them out from VSS, but since VFP doesn't see them as being a member of the VSS control file it doesn't show an checkout options. The VFP project list DOES,
>however, give you an option off of the right mouse button to add the DBC to the project file (which proves that VFP doesn't see the DBC as being under control of VSS). IF you take that option you are still rejected.
>What's the cure?
>Jerry

The cure is don't try and Source Control the DBC using the project integration. You don't really want to source control your tables and their data as your source safe DB would balloon and if you try controlling the DBC it can only track it as a binary file as SCCTEXT does not create a textual representation of it. One alternative that I have worked with, as long as the DB is relatively simple with not many views, is to use GENDBC to create a textual representation of the DBC and then source control that. You can control it as text and therefore can do a visual difference on it.

However, having said all that. You can add the DBC to source control from the project. The way you get around the "DBC already open" is to collapse the data branch until you only see the database. Close the project file. Do a CLOSE DATA ALL and then reopen the project file. Then go to the database, right click and say add to project file.

When you add the file to Sourcesafe directly, VFP doesn't know it is under control because it is not listed in the .pjm file.

Darrel