LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Built executable doesn't find the VI in the data.llb

Error Code: 7
Soure: Open VI Reference in CallsCompileMib.vi->Lookup Names.vi->SNMP_CompileMIBs.vi->SNMP_Compile+.vi->Sequence Editor - UTT List.vi->Sequence Editor - Main.vi->Jupiter Sequencer.vi<APPEND>
VI Path: <b>C:\DAQTron\Jupiter\CompileMib.vi</b>
Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared library.
 
It looks as though the executable isn't looking in data.llb for the VIs. There's a host of VIs that fail to load when called from out menu. Is this just a path issue in our code? I added all the necessary VIs dynamically and they are in the llb.
0 Kudos
Message 1 of 4
(3,243 Views)
How are you deriving the path to the VI in the llb?  Remember that the x.llb must be part of the path... IE.  C:\myProject\x.llb\y.vi and not C:\myProject\y.vi.  If you are using the path of the executable, the path will be something like C:\myProject\z.exe\main.vi. 
I hope this helps, otherwise could you add some specifics?

Paul
0 Kudos
Message 2 of 4
(3,234 Views)

This sounds like it is the case. In LV7.1 the way we are referencing the VIs worked. It seems that it's not working the same way in 8.2.1. Instead of telling the program to open desired.vi I guess I need to append data.llb to the front and open data.llb\desired/vi.

Thanks for the help. I was beginning to think this was the case anyway, but you've all but confirmed it.

0 Kudos
Message 3 of 4
(3,230 Views)
I'm the OP. Here's what I believe is happening and I don't know if there's an easy way around it, though I sure hope there is.

In LabVIEW 7, you have the option to build a "small target file with external file for subVIs". This is the method we used to build with. It seems as though the built application knew to look in the data llb for the VIs it was looking before because in our old code, we don't give the Open VI reference a path, just 'Desired.vi' when running the application. This has worked for us for years.

When I build in LV8.2 nothing responds if it's called dynamically. It seems as though the additional build options as far as destinations are concerned has changed and the application no longer "knows"' to look in the data.llb library. If I build the application with a path to the data.llb and use it as a folder, the dynamic subVIs open and run as expected.

Is there any way to essentially tell the application to look in the data.llb? Is there a setting somewhere that I'm missing? Or do I have to make a more explicit path (based on my executable's directory)?

Thanks.
0 Kudos
Message 4 of 4
(3,220 Views)