include vi file to the project

[TRanjith]

Hi.. I am using system busy.vi file to show the busy dialog in my application. When i build exe and run the application it prompts for the .vi path. Which i want to avoid. . Please see the attached file. it just put the system busy dialog on main vi(Its sample code).

Thank you

Ranjith

[TRanjith]

I am trying to implement the logic which is there in attached file. which i got it from NI forum.

Here the example takes the path manually. which is not going to help after making the exe.

Pls help me how to get the build system busy dialog without mensioning the path.

Ranjith

[TRanjith]

Any quick help would be great helpful.

Ranjith

[TRanjith]

I got the solution.... I am using the static reference...

[TRanjith]

Static Reference logic also failed for me. 😞

Please through some ideas without providing the vi path.

thank you,

Ranjith

[Ray.R]

I didn't look at the code so I'm not sure what you mean by static reference and why it is causing issues with a path after you build your application.

What you can do is to have an .ini file or .xml file that contains a static path (full path) to where you want to open your file.  If you use a relative path, please note that your path will change after building the application.  Look at the description of the path function within the context help.

R

[Sorooshster]

Hi TRanjith,

Does this happen on your development machine when you run the exe or when you distribute the exe to a different machine?  Thanks. 

[TRanjith]

As mensioned in example llb file. i would like to use the busy dialog without giving the vi path. How can i do this. this should work after creating exe also.

Otherwise if there is any better example to show busy dialog would be great helpful.

thank you all,

Ranjith

[Captain_Kirby]

Hi Ranjith,

You must have a VI reference to use the busy dialog, and you must have a path to the VI to get a reference. You can get a path in a number of ways. You can use the INI method described above, if you know the path to the VI on the deployment machine, and you can guarantee it will not change. You can also use relative paths to the VI and then deploy them together, guaranteeing that the relative location of the VI will not change. The last option might be the most fool proof in a deployed exectuable situation. You can build the subVI into your executable,and then use a relative path to the VI built into the executable to get a refrence. I have attached a KnowlegeBase article, that does a decent job of introducin the idea. Keep in mind that the article describes the new methods to access a VI inside of an executable since our methods changed in 8.x, but judging by your VIs submitted, you are using LabVIEW 6.0. In this case, you can still refrence this article because it accurately describes the methods being replaced. In essence, you can simply access the VI inside of the executable by refrencing the executable as a folder path.

Accessing VIs Inside of a LabVIEW Executable or DLL in LabVIEW 8.2 and Later