Source Code Control problem

[Melissa Niesen]

I'm having problems with LabVIEW's SCC package. The lock/unlock mechanism does not seem to function correctly. After I fix it, the locking works for a little while and then totally disappears. I don't think any of the VIs that are not checked out are locked anymore. This is very annoying. Now several VIs are changed but the server copy is not.

Could this be caused by LabVIEW updates? Can allowing the update to update VIs automatically change the state to unlocked? That is the only reason I can think of right now. I haven't worked on some of the changed VIs for quite a while, but I did update to 6.0.2 not too long ago.

What's the best way to go about getting these VIs back under SCC control?

Thanks,
Melissa

[TommyB]

Melissa:
I'm trying to get some more information about how you're using the built-in
SCC. I use it all of the time and never have any problems other than it
being terribly slow. When you go to work on a VI are you checking it out
first or just unlocking it? The upgrade to 6.0.2 should not affect any of
your VIs. The update will only affect those VIs in library files and
directories.
-Tom

Melissa Niesen wrote in message
news:50650000000800000029200000-991728092000@quiq.com...
> I'm having problems with LabVIEW's SCC package. The lock/unlock
> mechanism does not seem to function correctly. After I fix it, the
> locking works for a little while and then totally disappears. I don't
> think any of the VIs that are not checked out are locked anymore.
> T
his is very annoying. Now several VIs are changed but the server copy
> is not.
>
> Could this be caused by LabVIEW updates? Can allowing the update to
> update VIs automatically change the state to unlocked? That is the
> only reason I can think of right now. I haven't worked on some of the
> changed VIs for quite a while, but I did update to 6.0.2 not too long
> ago.
>
> What's the best way to go about getting these VIs back under SCC
> control?
>
> Thanks,
> Melissa

[Melissa Niesen]

Tom,
When I run into a VI I can't edit because it is locked, I am reminded to check it out. (The whole purpose of the SCC locking mechanism, I assume.) I never unlock anything from the VI properties. When opening a VI for editing, I generally don't check with SCC first to see if I have it checked out because of the slowness. I rely on locking to alert me when I need to check it out.

Maybe I should just check everything out when I'm editing. I'm the only one working on this project and I use SCC mainly for version control.

Thanks,
Melissa