VI does not work when coverted to Executable

[Javed_H]

Hello Everyone

I have prepared a VI(attached) which will give me the list of Dynamic files loaded in the Build Specfications. This VI works fine when I am running it normally. However when I am trying to build the VI into an executable, I get an Error with Error code 1.

It would be great if you could help me out in finding the reason for this behaviour.

I am using Labview 8 on Linux.

Regards

Javed Halani

[yenknip]

When you build an executable, all paths within the application are increased one step, this KB article addresses this.

essentially, "C:\Folder\myVI.vi"

becomes "C:\Folder\MyProgram.exe\myVI.vi"

[Javed_H]

Hello yenknip

Thank you for your input. However, I am not using any fixed path in my VI. If you look in the VI, it basically takes in a path to any laview project file.

You can either change this to constant and build this VI and try to see if you can get the list of Dynamic Files you specified for the corresponding project.

If I RUN this VI normally, it gives the list of Dynamic files specified in the build specs,  however after building when I run the build I get an error.

[yenknip]

I've created an exe with your VI, with debugging enabled.

I give the path control an address to a *.lvproj file, but I cannot create an error 1.

If you are running windows 7, might it be a permissions thing?

[Javed_H]

Which version of Labview are you using and how do you enable Debugging? Are you getting the list of Dynamic files in your build specs ?

I am working on Linux and using Labview 8

[yenknip]

Oh, sorry I completely missed that linux/LV8 line from your first post.

I'm using 2011. I haven't used 8.0 in some time and I don't have it installed here; but in the advanced tab of the executable builder, there is a checkbox to make the VI debuggable when run.

Then, in the project window, go to operate -> debug application. you can view the block diagram and highlight execution as normal.

I can't help much with linux. The most obvious problem would be how paths are handled, but as you are using the path datatype this would not cause any issue.