executable

[dg_lbe]

Executable doesn't run like the source file?  Not all the parts of the source file vi are running with the executable.  eg. - Test inspection of bad and good parts.  Indicator shows pass/fail when parts are examined.  This is seen with the source file vi.  When an executable is generated the test seems to not detect bad/good parts as the indicator doesn't show pass/fail.  My conclusion is there are some vi's that are missing in the compiling.  How do I proceed to fix this? 

Thanks for the time......

[altenbach]

You provide very little information, but one typical problem is with relative paths.

Have a look at e.g. this note.

[dg_lbe]

Developed a vision application with Builder 2010.  Migrated the application into LabVIEW 2010 using Builder's tool "migrate into LabVIEW".  A vi is generated which I then transfered into a project to create the executable.  The project tree file shows this vi along with the dependencies folder showing the vi's, ctl's..... ( see attachment).  I then generate the executable using the default settings.  The executable is checked on the application development pc and doesn't run like the source vi.  It appears as though there are missing vi's.  So I must not be configuring the application properties to include all the dependency vi's.. 

I am working with ni applications rep. Sam Kristoff.  Believe more eyes are better......