We have VSS 3 set up to work with VB6 with which we have a fairly large program, written in VB6, we use daily and our Network Administrator moved us to a new server. The new server (we'll call NAS1) has copies of all files from (PDX1) which is where the VSS db is located. PDX1 is not removed yet, but we are all live on NAS1. The problem is that our project is still mapped to the VSS db on PDX1 and we need it moved to NAS1 before they turn off PDX1.
I am thinking that our current changes to our VB program are being captured on PDX1 and the files that are sitting there on NAS1 are not being updated at all, even though that is the live server. We go into VSS and the path shows to the PDX1 path. Trying to change to Add a path to the VSS file on NAS1 just results in a name of our VSS database with a ~1 added on to it. And, we don't have the Admin Password to get into the Admin part of VSS to do anything.
What I need to know is how we can transfer everything over? Is it possible? Or, since we do not have the Admin pwd, do we need to
1. Make a copy of the VB files
2. Remove all .scc files from each folder of those VB files to remove any reference to VSS.
3. Uninstall VSS on our machine
4. Reinstall VSS and then set up a new database with a new admin password.
5. Add the copied and .scc stripped project into the new database (on the new NAS1 server)
6. And go on with things
Any thoughts?
Bob Larson
Free Access Tutorials and Samples:
I am thinking that our current changes to our VB program are being captured on PDX1 and the files that are sitting there on NAS1 are not being updated at all, even though that is the live server. We go into VSS and the path shows to the PDX1 path. Trying to change to Add a path to the VSS file on NAS1 just results in a name of our VSS database with a ~1 added on to it. And, we don't have the Admin Password to get into the Admin part of VSS to do anything.
What I need to know is how we can transfer everything over? Is it possible? Or, since we do not have the Admin pwd, do we need to
1. Make a copy of the VB files
2. Remove all .scc files from each folder of those VB files to remove any reference to VSS.
3. Uninstall VSS on our machine
4. Reinstall VSS and then set up a new database with a new admin password.
5. Add the copied and .scc stripped project into the new database (on the new NAS1 server)
6. And go on with things
Any thoughts?
Bob Larson
Free Access Tutorials and Samples:
