>>>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
>This is exactly the information I was looking for! Thank you, Darrel, I owe you one. If you ever drop by Lincoln look me up at the State office bild and we'll enjoy a steak dinner at the Bum Steer!
>Jerry


Hi Jerry,

Now there's an offer that's difficult to refuse :-)

Your message got me thinking and I went back to the online docs to see what MS recommends to do about managing DB's. They say not only to not Sourcesafe control the DB but also, to ensure that each developer does not maintain their own local copy of the DB. Otherwise it becomes a very tricky task to try and merge the changes made to the DB at a later point (That I have learned from experience). My problem was that to share the DB it would be necessary to put the DBC on a different drive than my source code. As soon as the DBC is on a different drive than the source, all references to the DBC that are stored in forms' dataenvironments become absolute instead of relative. This leaves me with one decision, do I want an absolute path that contains a drive letter and make sure all developers have the same drive mapping to access the data, or do I use UNC to guarantee that everyone is pointing to the same data. The problem with UNC is it permanently fixes the design time location of your data.
Anyway, I am working with a UNC absolute path to my data at the moment, I'll let you know if I find out I've made the wrong decision.

Darrel