Source Safe problems, VFP 7

[psperry2]

A project previously under Source Control is now not acting like it is. I have a project called interview. This project can be verified to be under Source control by starting up the SourceSafe application.

I am using VSS version 8.0.50727.42 and VFP 7.0 with SP1

When use FoxPro to open the Project, the Lock symbols are all missing, and I can make changes without checking out the files.

On the Project Tab of VFP, I have the option now to add the project to source control. When I try to do that, I get prompted to Login to Visual Source Safe, so I do that and am prompted to select a SourceSafe folder or name a new one.
When I select the existing interview folder and click OK, I get the message "The project is already under source control. Use Join Source Control Project on the File menu to create a new copy of the project." So when I select Join Source Control Project..." from the file menu I am once again prompted to login to Visual SourceSafe. I then am presented with a list of available projects already under Source control and if I select Interview, I am presented with a Join Source Control Project screen.

The screen is divided into 2 sections, the Top section is labeled Source Control Project and the bottom section is called working Directory. Both come defaulted with the options I want, so I don't use either change button, I just click on the OK button. Then Nothing happens.

Can anyone tell me how I can re-connect this FoxPro project to its original SourceSafe Project folder without Losing the history of changes?

 

[Dan Freeman]

Instead of trying to add your existing project (PJX/PJT) file to VSS, re-join it to create a new one (File->Join Source Control Project...)

Answer yes when asked to overwrite your existing project.

 

[psperry2]

Will the overwrite cause a loss of history of changes?

My supervisor wants to avoid that.

 

[Dan Freeman]

No. You'll be overwriting the PROJECT, not any of the code.

 

[Dan Freeman]

Wait... something about that last question doesn't sit right.

Your most recent code changes should be IN VSS. They are, right?

 

[psperry2]

Yes they are. Everything is in. However I have some new changes I would like to put in but can't get started because of the Sourcesafe problem.

So whats in Sourcesafe is current with the project exactly.

Our procedures prevent me from changing our production system without the Sourcesafe working.

 

[psperry2]

Our project files are not in Sourcesafe. The PJX and PJT files. There is a PJM file in Sourcesafe.

 

[Dan Freeman]

OK, phew.

The pjm file *is* the project, as a text file specifically for VSS.

Joining the VSS project (from VFP) reconstructs a PJX/PJT from the PJM and then you should be able to check files in/out.

I can't say how you broke the link to VSS in your project, but re-joining will create a new project with the links in place.