LabVIEW Built Application still requires LabVIEW to be installed on target computer

[Marshall GaTech]

I have built an application for use on another computer, and an installer to go with the application using the LabVIEW app builder. The problem is that after I install the application along with the LV runtime engine on the target computer, and then try to run the application, it starts up with several error messages saying it cannot locate several of the subVI's in my program. All of the VI's in question are part of the Digital IO section of the labview functions pallet. After all of these messages appear I get another message appearing which says that the previous errors can be fixed by installing the LabVIEW full development system on the computer. Sure enough, when I install th
e FDS it works perfectly.

I was under the impression that when you created a labVIEW application using the App Builder, it create a real stand alone application which did not require an installation of labVIEW to run (aside from the Run Time Engine). Could someone please explain to me what I may have been doing wrong when I created the application?

The code was created using the labview 6.1 FDS, and the same was used on the target computer.

[mikeporter]

Your assumptions on how the app builder should work are correct.

Do you have NIDAQ installed on the target computer? The LV installer doesn't automatically include it in the build. Also when you say you are getting "error messages" that subVIs couldn't be found, is LV presenting a file dialog box to find the missing VIs? If you are gettring a file dialog, can you find the VIs (they shuld be in the .exe)--or a seperate library if you select the "small executable" builder option.

Finally, is your application using any dynamically called VIs?

Mike...

[Marshall GaTech]

I am not positive whether or not NI Daq was installed on the computer. The error messages were dialog boxes that said a simple message along the lines of "could not locate Read from Digital Port.vi" for each of the DIO vi's that I had used. There was an Ok button and that was all. These were probably generated using the One button dialouge function that you can find on the functions pallet or something similar. So, no there was no way to browse to the vi.

Also, no dynamically called vi's are being used.

Thank You

[mikeporter]

Well, first off if your application is using DAQ VIs, NI-DAQ needs to be installed on the target system. That could be your problem. If LV runtime can't find a VI it presents a dialog box just like the development version for you to go find it.

Mike...