LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Source Code Control - Check in problems

Some of my vi's have been marked as "Server copy has changed" and some have even been marked with "both local and server copies have changed". When this is the case I cannot find any way to check in my VI without getting an error. Looking for a work around - help.
0 Kudos
Message 1 of 4
(2,809 Views)
kh,

Which version of LabVIEW are you using? Built-in SCC have been rewritten from 6.0 to 6.1 and there are different issues related to each version.

With 6.0 I have encoutered a bug that wrongly checked most of my VIs as "local copy has changed" as soon as they are in memory with panel closed. I worked with NI Support and we found no workaround. Unfortunately, this behavior stayed even when the VIs were upgraded in 6.1 so that my problem was a dead end. I switched with great success to CVS, another source code control software.

I do not use 6.1 but if you do, make a search on NI's site and you'll find hits that address a SCC bug. If I remember correctly, checking out a VI, making a small change and checking it in again often solved the problem.

G
ood luck.


LabVIEW, C'est LabVIEW

0 Kudos
Message 2 of 4
(2,809 Views)
Thanks for your reply.

I am using 6.1.

I think I have tried all possible combinations of checking out, making changes and saving. Though none of this is working, perhaps due to the fact that the actual VI I want to check in is out of sync with SCC. Apparently the SCC is checking on several datestamps.

Can you please help with a hint where to search on the NI site for this bug report??

One more - thanks
0 Kudos
Message 3 of 4
(2,809 Views)
I have found nothing relevant to what you described. You should contact NI Support directly at http://www.ni.com/support/ . Go through the steps until you can fill in a form for email support.

In the mean time, try to mass compile all your VIs, create a brand new project in a brand new master repository. If the problem is still there then you are in the same situation as I was. Contact me at drolet_jp@hotmail.com, I'll send you the support request number I had with NI so you will be able to give them for reference.


LabVIEW, C'est LabVIEW

0 Kudos
Message 4 of 4
(2,809 Views)