The executible I build with the application builder does not function the same as my VI file.

[TMBurleson]

I am using a USB 6008 device with the newest DAQmx drivers and Labview 8.2 to make analog voltage readings.  Within my main VI I first create a data folder in the same location as the VI using a property node and then use case statements to call two sub VIs that create a data file within the data folder and then collects data.  When I use the application builder to create an executible the resulting file does not operate the same as the origional VI.  The program appears to be reacting to button presses on the GUI, but there is no indication that the data folder is being created or that any measurements are buing made.  Are there any known issues that may account for this anomily?

-Mike

Message Edited by TMBurleson on 10-16-2006 03:09 PM

[Dennis_Knutson]

It's a pretty common mistake for beginners with the app builder. See this.

[kehander]

Are you using the VI Path property, using a reference to the current VI?

I could be wrong, but if you're attempting to use a path relative to the current VI, I think that does indeed change in a built application. If your VI used to be C:\somewhere\foo.VI, then after building its path would actually be C:\somewhere\foo.EXE\foo.vi . Thus, if foo.VI used to try to make a folder like C:\somewhere\datafolder, the built application would be trying to make C:\somewhere\foo.EXE\datafolder , which wouldn't work.

This is sort of a shot in the dark, but does this sound like it might be the case?

EDIT: Dennis beat me to it.

Message Edited by kehander on 10-16-2006 03:26 PM

[TMBurleson]

Thanks, I will give this a try.

-Mike

[JeffBoettcher]

If it doesn't turn out to be a path issue, or to otherwise help with such issues in the future, I say, try debugging it!  🙂  LabVIEW 8.0 introduced debuggable executables, a very handy feature that a lot of people don't know is available.  If you build your EXE with debugging info, you can use the "remote debugging" feature to debug your EXE as it runs.  For more info, try searching the LabVIEW Help for "debugging applications", and you should find a topic within the top 10 matches called "Debugging Applications and Shared Libraries".