can't find dynamically loaded VI

[efarr]

I'm updating a code from LV6.1 to LV2011. The application runs fine before I build it and install it on another machine. When I install and run it on the other machine, it tries to open a file by reference, but it can't find a VI named DSA8300.vi. I get the following error message.

Open VI Reference  in InitScope.vi->PATAR.vi-><APPEND>

VI Path:  <B> c:\PATAR3.0.2\Range_RC3\Plugins\Scopes\DSA8300.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. 

But I checked my build properties, and the file has been properly included in the build spec as a dynamic VI. What else can I check?

Thanks very much.

[P@Anand]

Check the folder dynamic vi for the file after building whether it is present. Create an indicator for the path where you call the dynamic vi and check it whether it calls the same path where the file is available after build.

[efarr]

I tried some things, but I'm still confused. 

In the Destinations section of the Build Properties, there are about a hundred subdirectories shown where the application will be stored. But when I build the app, only about five directories are created. It seems like most of the directories are missing.

In the "Additional Exclusions" section of the build properties, I unchecked all the boxes, so nothing would be excluded. I got the same behavior. 

One of the missing subdirectories is "Scopes", which would be the logical place for the missing  VI. 

The app builder seems to be leaving out a buch of files (or at least directories), and I can't figure out why.

[MoReese]

---

@efarr wrote:

I tried some things, but I'm still confused. 

In the Destinations section of the Build Properties, there are about a hundred subdirectories shown where the application will be stored. But when I build the app, only about five directories are created. It seems like most of the directories are missing. Is this the installer you are referrring to? This only shows where your application will be installed.  It does not create all those folders listed.

In the "Additional Exclusions" section of the build properties, I unchecked all the boxes, so nothing would be excluded. I got the same behavior. 

One of the missing subdirectories is "Scopes", which would be the logical place for the missing  VI. Did you create a folder called Scopes in the Installer? Is this where you expect the VI to be located?

The app builder seems to be leaving out a buch of files (or at least directories), and I can't figure out why.Which files and/or directories is it leaving out?

---

[efarr]

Let's review. I'll try to be more clear. 

1. App works OK on the machine I developed it on. Ran it three ways: a) Raw VIs; b) built app. (before installation); and c) installed app. 

2. I installed the app on a second machine, which has no VIs and no LabVIEW. On that machine, it can't find a dynamically linked VI during a call by reference. 

3. On the suggestion of the P Anand, I opened Project Explorer, Build Specifications. Under that is the name of my app. I right-clicked on that to see it's properties. Under the "Destination" category I see a long list of around 100 subdirectories where the built app will be stored. 

4. After the app is built, I go to where the "Destination" category said my built app would be stored. I only see only five subdirectories. 

5. This seems strange, but I can't be sure that  this is a problem. Some data files that I would expect to be missing on this basis seem to be installed successfully on second machine.

6. The Scopes directory is not one that I created. LabVIEW decides where to put the files in a built app. I seem to have no control. But the missing VI did originally live in a directory named "Scopes". 

Thanks very much for your help.

[MoReese · Accepted solution]

You might find this thread helpful.

http://forums.ni.com/t5/LabVIEW/Can-t-find-my-dynamically-loaded-VI-path/m-p/1124341/highlight/true#...

Have you tried searching the forum for you issue?  There are others.

[efarr]

Thanks very much for that tip. I had searched, but I had not found that thread. 

The suggestion at the bottom of the thread worked. That was, "Use Labview 8.X file Structure". I don't understand exactly what this does (apparently a flat structure instead of hierarchical), but it works on my app, because I'm updating an old LV6.1 app. 

[MoReese]

Glad to hear it.  Good luck!