Source Code Control question

[Jim77215]

I've been using Labview built in source code control (SCC) for a few months now, and after a few hardships, have pretty much got it working like I need it to. One thing I have noticed though, that I can't figure out, is this scenario: If I check out a vi, from SCC, and modify it by adding a new subvi to it, when I check it back in, the new subvi doesn't seem to get into SCC. Has anyone else noticed this? What might I be doing wrong? I would have thought that checking the vi back in would have been sufficient to get the new sub into SCC.

[KileenC]

Hi,

When you add a top-level VI into LabVIEW Source Code Control (SCC), any subVIs that are called by the top-level VI should be automatically added as well. You’ll want to make sure that the directory where the subVI is saved is in the working directory. Also, only statically called subVIs are seen by the LabVIEW SCC; dynamic VIs will need to be added manually.

There is an excellent KB discussing this topic:
KB 2HUI256E
http://digital.ni.com/public.nsf/websearch/2B2555D2B6070B8B86256B530005E40B?OpenDocument

Hope this helps!

Kileen