>>>>Hi,
>>>>You must close all before adding your project to VSS. We didn't have problems adding our project to VSS. The other thing is it's
>>>>just your DBC not your tables will be added.
>>>
>>>Sonny,
>>>Thanks for the reply. I am glad it works for you. How did you get it to load the project from within VSS
>>>I had already tried closing all - that is - shuting down foxpro or at least the project file. When I do that there is no option from within Foxpro to add a project to VSS because no project is open. When I attempt to add a project to VSS from within VSS then just loading the project file doesn't trigger an automatic load of eveything in the project file. To make matters worse, when I select the ADD option the ADD dialog box, even though it uses the *.* pattern, won't allow wildcards, so I have to add them one at a time.
>>>
>>>I also tried creating the project anew from within VSS but ran into the same catch-22.
>>>
>>>I bet one thing for sure - the programmesr at MS who write this version control software have never had to use it.
>>>
>>>Jerry
>>
>>Well, closing all before joining the project was just to close the databases, classes
>>files. You must reopen the project to add it to VSS. Make sure you have all the same
>>directory tree in VSS before you include your project. I hope you'll be able to included
>>it this time. Because, I don't have a clue else why it doesn't work.
>
>I don't have a cluse either. I have added the project by choosing the "ignore" option when the "the database is open" message (even though it is NOT open) but the dbc is not added. I have added the dbc with the "Add files" option in VSS, BUT then the VFP project list doesn't know that the dbc is under the control of VSS (you can use the right mouse and see the "Add to source control" option) -- and it is not. I hope this is not a sign of things to come. One would think that an MS version control system would be able to add every file in a VFP5.0a project list without having to jump through elaboratge hoops. My loop tolerance is real low - I'll look at other version control systems first.
>
>Thanks anyway!
>Jerry

Jerry,
You may want to check out the October 97 issue of FoxPro Advisor. It has just landed on my desk and there are a couple of articles on Source Safe and using it in/from VFP. It discusses (amongst other issues) how to deal with database containers etc in VSS. One comment relating to the problem of 'open databases' from this article ... "Database containers are especially pernicious. You can CLOSE DATABASE ALL until you're blue in the face, but if the database was ever expanded in the Project Manager, the database files are still open as far as VSS is concerned."

Hope this helps with part of the problem.

We had some very frustrating times with VFP/VSS initially. The main area that caused us grief was the 'sharing'. ie: our application framework, standard class libraries etc are shared amongst our various projects.

I'm not sure that the way we have handled shared files is the best way but if you want some details reply to this and I'll try to give a reasonable summary.
If you are going to be using the 'sharing' features of VSS I really recommend you read all the doco carefully to determine exactly how it works before you start.

We've had to accept a few "features" of VSS that aren't very sensible (IMHO) but we have found that it works very well once you do things the way VSS likes to do them.

Maybe the next version of VSS could be called VHJ (visual Hoop Jumping :-))

Good Luck
Craig