09-19-2007 03:09 AM - edited 09-19-2007 03:09 AM
Message Edited by Teemu from Finland on 09-19-2007 03:11 AM
11-15-2007 10:32 AM
11-15-2007 12:54 PM
As a hint to our support staff, I have a vague and ancient recollection of a LabVIEW issue where you needed to upgrade your VI versions by mass compiling before opening the VIs after you installed an upgrade of TestStand that crossed a certain version boundary.
I think the versions to check the release notes and readme's for clues would be somewhere around the TS 2.0/2.0.1 and the LabVIEW 5.1/5.1f1 timeframe.
The problem was that earlier versions of LabVIEW didn't store ActiveX call information correctly such that certain usually compatible changes to a server (TestStand, in this case) could break a VI with ActiveX nodes, requiring the nodes to be respecified. However if you upgraded and compiled in the right order, you could avoid the problem.
Unfortunately, that's all I remember. This was many years ago.
11-16-2007 12:30 AM
Hi,
I thought you were prompted to mass compile all VI's when installing TestStand.
Regards
Ray