Executable cannot find VI's after build in LabVIEW 8.6

[Vision_Armenia]

Could anyone answer, how can I fix the bug in my LabVIEW 8.6 ? ... To be short, when I want to make an executable from VI, I create empty project, put VI, right click on build specifications and make Application (EXE). It is working in other PC and in my laptop, too, but using LabVIEW 8.5. When I do the same with LabVIEW 8.6 in my laptop, after building when I click on executable, it's starting to seach for standart VI's, as in vi.lib, instr.lib, etc ... why? ... and the file size is smaller, than in EXE, from other PC, which is perfectly working on my laptop, too. ( 302kb when I build on my laptop and 434 kb, when I do the same in other PC). Can anyone explain what is the problem? I checked all paths in Options are OK. Thank you in advance.

[DianeS]

Have you actually opened your VI in LabVIEW 8.6 so that it can link up to all of those functions that it's looking for? 

Open your VI in 8.6.  Make sure you still get the white arrow indicating nothing is broken.  Relink to anything that might need relinking (don't know if this is a problem here or not, but it very well could be.  Save the VI in your 8.6 project.  Then build your executable.

[Vision_Armenia]

DianeS.

You are wrong. If arrow is broken, you couldn't even build the application.

Yesterday I tried to repair my LabVIEW, but it still the same. The problem is that the same project is working in other PC, where all LabVIEW Options are the same, it is working also in my laptop with LabVIEW 8.5, but not in LabVIEW 8.6. Probably I have to uninstall all LabVIEW 8.6 and start to install it from zero.

Anyway thank you for the anwer.

[DianeS]

So you tried what I suggested and it didn't work?

When you write a VI with 8.5, LabVIEW finds all of the user.lib, vi.lib, etc. functions in C:\Program Files\National Instruments\LabVIEW 8.5.  When you transfer that VI to 8.6, it will look for all of those functions in C:\Program Files\National Instruments\LabVIEW 8.6.  Since you state that it is searching for those very files, it would appear that it is looking in the wrong place -- the 8.5 directory (which may or may not exist on your new machine...I don't know).  Opening your VI in 8.6 should redirect LabVIEW to look in the 8.6 directory for those functions.

I have had a situation, fairly recently as it happened, where I was missing some support files (instrument drivers, to be specific) on one of my machines.  I did pretty much exactly what you are describing here -- created a new project, stuck my VI in it, and built the executable.  The build went off without a hitch, but when I tried to run it, the "run" arrow was broken.  So I may indeed be wrong, but it's worked for me at least once!

Anyway, if you've already tried opening the VI in 8.6 and then building the executable, then probably you're right and something is funny with your 8.6 installation.  Good luck.

[ColeTrain]

Elektrik,

The differences in sizes to your two executables can partially be attributed to the difference in the size of the run-time engines that you are including in your builds.  Are you using the full versions of both the 8.5 RTE and 8.6 RTE?

[Vision_Armenia]

Thank you DianeS for trying to help me in this issue. In my first message I didn't mention that I am surely running that VI before creating application (EXE), so all dependenceis come to the project. The problem is in my LabVIEW 8.6 builder as I think, which didn't connect dependencies. I don't know where to look, it seems that something happened in my  Windows XP register files. I am sure, if I will uninstall LabVIEW and install from zero, it will work, but it will be awful to do all that things with activating all LabVIEW products which I have ... that's why I asked and then tried to repair ... strange, that even after repairing, he didn't work ... he is starting to look that VI's in application directory, instead of original paths, as <vilib>, <instrlib>, etc ...

[Greg_S.]

Hi,

If you go to dependencies in the project manager and look the paths of files in dependencies are they from ...\labVIEW8.6 ? or from 8.5 ?

You said that this project is working in other computer, so you did an exe from LV8.6 from other computer right ?

If right reinstall, perhaps a mass compile of all directory LabVIEW8.6 can have a small chance to correct.