LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I can start my vi but executable asking for sub-vi when it starts

My vi starts right up but when I created an executable it ask for sub vi's when it starts. What's the progblem?

0 Kudos
Message 1 of 11
(3,043 Views)

We are not mind readers. What subVI is it asking for? Is this a VI that ships with LabVIEW? Is this a VI that you wrote? Is this a VI that you're calling dynamically? If so, did you include it in the "dynamically called VIs" list? What LabVIEW version are you using? What's in your project?

0 Kudos
Message 2 of 11
(3,032 Views)

Is it an executable you built from your VI?
Did you make an installer so that all dependencies (including necessary subVIs) are installed?

Cory K
0 Kudos
Message 3 of 11
(3,028 Views)

Maybe you are using VI's which are called dynamically? If so, you have to include them in the "Always Included" section of Source Files when making the Build Spec.

 

Also, path constants can get you into trouble with EXE's, like Default Directory path and Current VI's Path.

Richard






0 Kudos
Message 4 of 11
(3,012 Views)

I don't think they are called dynamically..

0 Kudos
Message 5 of 11
(3,007 Views)

How do you make installer? Doesn't it ha[[en automaticcaly when you create an executable? I'm using 2009.

0 Kudos
Message 6 of 11
(3,006 Views)

 


@mchips wrote:

I don't think they are called dynamically..


 

Don't you know? Didn't you write the code?

 

 


How do you make installer? Doesn't it ha[[en automaticcaly when you create an executable? I'm using 2009.

No. An application is separate from an installer. The installer ... installs the application. The process of creating an application and an installer are fully documented in the LabVIEW Help. Please read that first and then come back if you have specific questions.

 

0 Kudos
Message 7 of 11
(2,997 Views)

I didn't write that portion...

0 Kudos
Message 8 of 11
(2,995 Views)

 


@mchips wrote:

How do you make installer? Doesn't it ha[[en automaticcaly when you create an executable? I'm using 2009.


 

No, just because it makes an executable does not mean you have a complete installer.

An installer has:
- the executable

- the run-time enginer

- dependencies

 

If you do not create an installer, you will only have one of the three necessary components

Cory K
0 Kudos
Message 9 of 11
(2,988 Views)

 


@mchips wrote:

I didn't write that portion...


Well, we're still not mind readers, and you still haven't given us any more useful information, such as what VI(s) it's looking for. Unless you can look at the code yourself and determine whether the VIs are being called dynamically then post the code.

 

0 Kudos
Message 10 of 11
(2,981 Views)