How to handle dynamic loaded subvis in builtin SCC

[TET]

I am new to LabVIEW 7 and the built-in scc tools. I have begun work on a vi that contains three subpanels, each of which loads a seperate subvi. I have used the path and string blocks to build a path to each subvi relative to the main vi. Now when I try to place the whole mess under SCC, the subvis are not seen as part of the project hierarchy, so they can't be added to the project.

As an experiment, I used the static vi reference block for one of the subvis, and SCC has problems with that when it adds an extra '9' to the front of the filename and then claims not to be able to find "9PHM_LFsim.vi" (understandably).

I might be able to put each subvi in a separate SCC project, but I was hoping to find a way to
bundle all of the vis together.

Thanks!

[JRA]

Have you tried making an llb with the files and checking that out and in?

[TET]

Two things worry me about this approach:

1) Chapter 7 (7-2) of the user manual includes a comparison of the individual file approach vs the library approach. Under "Advantages...Individual Files" it says you can use the built-in SCC on individual files. I read this to imply that I _can't_ use it on libraries.

2) I have multiple developers working on this project. If we SCC individual files, work can better go on concurrently with different developers checking in/out individual files. If changes have to be made to individual VIs through the single library collection, I wonder what a headache we build.

Thanks, though. I'll play with it a bit to see if I can get around these pitfalls.

Todd

[JeanPierre]

TET,

it is usual to have a separate project for each top level VI, including dynamic VIs. After, you can create a group including all VI projects.

It can become a mess when you work on several applications projects (not VI SCC projects)under the same SCC repository. In this situation, have a labview.ini file for each project to set a different default directory for each project (use the project directory) SCC stores its settings in the current default directory so it is easy to swap SCC settings just by starting LabVIEW with the project labview.ini file. You set the labview.ini file by creating a shorcut to LabVIEW and adding -pref "path\to\labview.ini" on the command line.

[TET]

Thank you! I think this is exactly what I needed.