09-22-2009 06:30 AM
Also, in case you transfer a VI to a different machine you need to ensure that you include all subVIs.
For this you should select "Save As" >> "Duplicate hierarchy to new location"
If you are working on the same machine ignore this.
09-22-2009 10:52 AM
09-23-2009 11:27 AM
xdaf wrote:Other possible reason: In your PC there are 2 different sub-VIs with the same name, and when you open the main VI, the "wrong" one is already in memory.
I'm quite convinced you'll solve your problems just putting some order in your VI hierarchy.
Awesome. In the dark old days when my team was trying to optimize code, we had several cases where the VIs were calling the same VI from different places. It was madness to try to sort out all the heirarchy problems! I believe this to be the problem also. Kudos of course.
Bill