There are a couple of ways you can achieve this setup.
1. Setup a centralized Robot repository.
Share a directory on a server, i.e. \\robotstuff\projectName, then point Rational Robot to it (create a repository) with the administrator. Create accounts for everyone, and have them use this repository.
2. Setup CVS.
Although this method is harder to achieve, I am currently using CVS on my projects, and it works out rather nicely. We no longer have to worry about stepping over eachother's scripts, or why something keeps opening as read-only... [img]images/icons/smile.gif[/img]
I did take me a while to set this all up, since Robot and CVS don't get along too nicely, but it is possible, and it does work.
3. Setup the repository to point to SQLAnywhere. Have all the script creators use the SQLAnywhere repository. The down-side is that Robot ships with a sample database, which I believe you can not edit. I have never tried to, however, so it may be possible.
4. It sounds like you already have a bunch of scripts in separate repositories. Unfortunately, there is no easy way of gathering the existing scripts into one project, since the files are actually maintained using an access database. There is one work-around for this which will make things go a little faster.
Create your new centralized (network shared) repository (as you would create a regular one,) and put all of the scripts (*.rec) in the "DefaultDataStore/TMS_Scripts" folder. Write down all the script names. Start Robot, Add New, and write in the name of one of the files (WITHOUT the .rec extension.) Click OK. The file should now appear in the editor. Repeat until all scripts are added to the new repository. Don't forget to copy any user created files from the TMS_Scripts/SQABas32 directory. You will also need to copy all of the Verification Points from the TMS_Scripts/VP directory as well. The naming convention is setup so VPs have the same name as the script, followed by the VP name.
Another way to manager scripts is export and import. You must be having test cases related to scripts. Export these test cases and then import them in the new one. This way scripts as well as VPs in the script are also imported.
Hope this helps.
A highly advanced bug is indistinguishable from a feature.