Hello!

[Martin Handler]

I´m using Labview´s Source Code Control System in a large Project (Source
Code > 200MB). Access through a Network is extremly slow, so that i am
looking for better solutions, how I can reduce check in- and check out-time.
Has anybody of you more experience in SCC and can tell me a way to make it
faster??
Another way would be using Visual Source Safe. Can I use the features of SCC
like automatically updating the project with new Sub-VIs in the hirachy? And
is it faster to use Visual Source Safe instead of the Built In System?

I hope someone can help me.

Martin Handler /Austria
martin.handler@avl.com

[Rick Nelson]

This won't help much, but I always hear Visual Source Safe is easy to
use and LabVIEW's isn't very good in comparison. I use VSS instead of
LabVIEW's SCC and have no (well, not many) complaints. Fortunately,
LabVIEW will automatically update VIs if you load them. Say, for
example, version 2 of a VI is posted in VSS, you can do a "get latest
version", then just open up that VI (or any parent VI), and then close
right away, and hit Yes to the "save changes?" question.