LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Search Window Appears On Dynamic Call

Hello All,

Our company uses a very large application with many libraries and Dynamic Calls to the top level VIs in the libraries. When this application was first built, it did not include the top level VIs as Dynamic VIs in the Source Files section of the build script. Everything worked fine. However, more recently I have been making changes and Updates to VIs in the libraries. Now when I build and run the application, I get a brief search window when VIs in the Libraries are called. It is so quick that I cannot see what it is looking for but it is noticeable. I can eliminate the search window by including the top level VI as a Dynamic VI during the build. What did I forget or overlook that causes this error?

Thanks in adva
nce,
Glen
0 Kudos
Message 1 of 4
(2,609 Views)
A good approach would be maybe to create a develop top level VI which contains all the top level VIs of your entire project. Open it up, press shift and the run arrow to masscompile everything in memory and then do a File->Save All. (Create a backup of the entire directory first, for instance by packing everything into a ZIP file, for your safety)

Chances are that now the internal paths are all fixed up and should work.

Rolf K
Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
Message 2 of 4
(2,609 Views)
Do you think that saving the LLBs while the main (top level)VI is open would have the same effect?
0 Kudos
Message 3 of 4
(2,609 Views)
Well, saving an LLB is not something you can do just like that. You can save VIs of course but doing so by hand one for one is probably not what you want to do.
Instead by masscompiling all VIs of the entire project in memory you mark them as needing to be saved and then Save All will take care of saving them to their original location.
One other thing you could do as well is using the "Save with Options" dialog. Select Entire hirarchy to new location, maintain hierarchy or something like that and you will get a complete directory hierarchy which will basically show you from where LabVIEW pulled the different VIs. This is quite handy to find out of tree references of VIs, which can happen sometimes if you are not careful with opening VIs while you
work on a project.
Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 4 of 4
(2,609 Views)