Multiple Libraries and version question

[GaryN]

We're upgrading some of our software to LabView version 7.1 and when we try to do some operations, usually after building the executable, we get the VI not executable because it's the improper version of LabVIEW error message. It works fine as a VI, presumably because the VIs in questionare being converted to 7.1 (from 6.1) on the fly. I've tried to set the paths to point to the more current version but that doesn't seem to work. Even on computers where 6.1 has been removed the VI libraries (at least some of them anyway) seem to stay. Any suggestions on how to fix this? Is there another place I can change the paths other than the paths option box? Thanks.

Gary

[xseadog]

In your upgrade have you mass compiled your libraries?

chow
xseadog

[GaryN]

---

@xseadog wrote:
In your upgrade have you mass compiled your libraries?

chow
xseadog

---

I think it's safe to say I haven't because I'm not sure what you mean. When I build my executable I do first compile the library that it uses wit hall the necessary VIs we've written. The problem comes in the LabVIEW system libraries. Looking at one of the systems now, there are three or four libraries with the same name and similar locations (one might be in \VI.LIB\ while the other is in \LabVIEW 7.1\VI.LIB). They are usually different sizes with different edit dates. It seems as though it was using one of them when we were using LabVIEW 6.1 but when we changed to 7.1 it continued using the 6.1 library and I can't change it unless I try to open it while another VI is running (so the run-time opens it). Then I can open it and see rthe broken arrow and find out what's broken and then navigate to the proper version of that VI. This is very annoying and time consuming.

[Chris_Cilino]

I think xseadog is talking about the "mass compile" option in LabVIEW. When you upgrade, you must mass compile before using LabVIEW. The good news is it's super easy to do. The bad news is it'll probably take your computer about 3 hours to do it.

To mass compile, open LabVIEW and go to tools>>advanced>>mass compile. A file dialogue box will then appear asking you which directory you'd like to compile. Select the LabVIEW 7.1 directory. DO NOT select the National Instruments directory. If you do you'll be waiting for 3 or more days. The "Select Current directory" button means the directory you're currently viewing, not the directory you've highlighted in the file dialogue box.

Post and let us know if this helped.

Chris C

Applications Engineering

National Instruments

[GaryN]

---

@Chris_C. wrote:

I think xseadog is talking about the "mass compile" option in LabVIEW. When you upgrade, you must mass compile before using LabVIEW. The good news is it's super easy to do. The bad news is it'll probably take your computer about 3 hours to do it.

To mass compile, open LabVIEW and go to tools>>advanced>>mass compile. A file dialogue box will then appear asking you which directory you'd like to compile. Select the LabVIEW 7.1 directory. DO NOT select the National Instruments directory. If you do you'll be waiting for 3 or more days. The "Select Current directory" button means the directory you're currently viewing, not the directory you've highlighted in the file dialogue box.

Post and let us know if this helped.

Chris C

Applications Engineering

National Instruments

---

I'll remember this for next time. What I did instead was delete all the older libraries that I could and made the program look exactly where i wanted it to for the llbs. I set the \LabView 7.1\vi.lib folder as the default folder to look in for them and emptied the \LabVIEW 6.1folder and \vi.lib folder. The mass compile probably would have been more elegant and finesse but it worked out for me. I'll do that on the next computer we upgrade. Thanks alot.

Gary D