Unable to define/update master copy

[matheisk]

I'm new to vss so bear with me.
My problem is that I don't seem to be able to update the master copy of my vb project files.
I have done the following:
In VSS 6.0
1) Created project.
2) Added vb project files (I expect these files to become the master copy of my project) to vss project.
3) Set working folder for vss project.
4) Got latest version of project files to working folder.
In VB 6.0
5) Opened the working copy of project.
6) Checked out a file (Now I can see in VSS that the file is checked out from the working copy folder).

After I have done changes to out checked file and check the file back in, the changes are saved to working copy of the file but not to the master copy of the file.
What am I doing wrong?

Matti

 

[cptscottie]

I can confirm that I also have this problem. Does anyone have the answer?

 

[matheisk]

I think I got it now. The master copies of the files are stored in vss database when files are added to vss project.
However you can't really find the actual files (.vbp, .frm, ...) in vss database. The data of the files is stored in dababase in some other format and one needs to use vss explorer to get the latest version of the master copy of the data in its original format (.vbp, .frm, ...).

 

[cptscottie]

I think I was talking about the more general problem of files being checked into vss and vss not updating the master files, regardless of whether VB was used or not.

I found a solution, and I'm not sure if this is documented anywhere (I'm sure it is). You have to set up what is called "shadow folders" that point to the directory you want vss to update when files are checked in.

You set up shadow folders via the vss admin program.

Once you do this, you need to copy the csrcsafe.ini file to each client's common/vss directory on their local machines.

Hope this helps.