If the workspace contains a single project it is not required to add the .dsw file in SourceSafe.
Whenever the .dsw file is missing it is automatically generated selecting
files of tipes "Projects(.dsp)" in the Open Workspace dialog.
The probem may change when have more projects in an workspace,
but just avoid this, and you'll have no more headaches.
It's true that you can get away without adding the DSW file to SourceSafe, but you are probably better off keeping it under source control. This is especially true for workspaces with many projects. The project build dependencies are kept in the DSW file and if the project is going to be shared by a development team it will be required in order to keep the build process reliable from one developer to the next. It's kind-of like not putting the makefile under source control, it's a very bad thing.
You'll find that once you add the DSW files to VSS it will want to change them at first as all the project interdependencies are added and source control links added. But once the workspace is stable you'll find that you almost never have to check it out, unless you are adding projects or changing the dependencies.
Thanks, I think that is what has happened.
When I check out the dsp and dsw files then check them back in, the annoying prompts go away.
Looking at the .dsp file, the change that has been made is to set up Scc_ProjName and Scc_LocalPath.
I will need to check this is OK for all my colleagues, but as long as they all use ther same directory structure it should be OK.
Thanks a million..........Martin