Earlier today I posted a question with the following subject:

Multiple BP tables and no VOC table???

Well, I got an answer to my question even do it was not what I would like, but then I started doing some thinking and I came up with a couple more issues which I have no idea how to get around, here goes:

We currently have a Version Control Process which controls everytime a program, file, dictionary, etc… get installed and checked out for changes, well here is the issue:

Every programmer has his on work files in AREV which allows them to change checkout a program to his own file…test-it…compile-it, in arev we just change the pointers to the programmers file for testing and everything works…

So my question is, if there is only one BP file and everything gets cataloged into the SYSOBJ file, how do I check something out for changes while everyone else is still working and running the initial version I checked out without affecting them, I thought about a couple of ways, but they still don't make since… one would be to change the program name when you cehck-it out to checked_out_recname and also make the change on line 1, but then the program could not be called and tested from other programs calling-it…

Another question i have is, if we were to have a volume created for each programmer and when that programmer logged into OI it would attach there own SYSOBJ & BP file, would this work… this is bring up a lot of issues that I don't know if we are ready to move on??? if anyone can understand what I just wrote here, please give me your input???

Thanks

Jack

Taking the original team work design element of OI into consideration here.. the individual programmers have copies of OI on their computer. When they want to work on a piece they "Check out" the piece to work on from the central repository, thus setting the Repository "checked out" flag. Whilst this is set nobody may check it out or modify it until it is checked back in. This is a standard feature of the software - no longer emphasised in demo but still there.

The Sprezzatura Group

World Leaders in all things RevSoft

Another option, though it could have some drawbacks, it to load up an MFS on the system files. In theory you could then use this to direct the programs to their respective output files.

It's a risky option, only in that by placing an MFS on a system file can be dangerous. However, it is another option to consider.

The Sprezzatura Group

World Leaders in all Things RevSoft

to tell you the truth I think this is one of the good features of the repository. I know that COWBOYS don't like that stuff that gets in the way of slinging code AND the thought of TEAM WORK makes them shutter .. but it works well. For those of us who learned to share at an early age

dsig@sigafoos.org onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 971-570-2005

OS: Win2k sp2 (5.00.2195)

OI: 4.1.2

View this thread on the forum...