I need to deploy an executable to a customer's computer and for the first time I have the need to use an asynchronous call in my program I am not sure how i am going to keep the file path to the "Open VI Reference" valid after I build and deploy the application. The Obvious manner would be to use a configuration file to allow me to set the path independently of the LabVIEW Application. However, when you include A VI in the "Always include" it is not An EXE thus not include as a file in the build folder, making it had to reference on the host computer. Some educational tips on how to do this would be very help full for learning how to deploy this application Attached is a code snippet of how i am currently stating an asynchronous call Thanks Mark R.

@JÞB wrote: Thanks James! Digging up old posts for the fun of it? I actually consolidated a little bit because I realized I didn't need two static VI refs when the strict one can do all the work.

This is how I always call a VI by reference. Having the static VI ref causes LabVIEW to load that VI in to memory and be able to find it by name when opened.

LabVIEW

asynchronous call deployment

Solved!

I joined this forum when I first started using LabVIEW in 2012 just to post a few times when I had issues. I went the next 3 years without really tapping this resource because I had a decent network around me. A few months ago I moved to a new city where I don't know anyone, don't have an alliance partner membership, and don't have a LabVIEW support network whatsoever, so I became active on here. Now I'm addicted!

So much can be learned from the massive number of posts and code that show up on this forum each day.

Cheers

--------, Unofficial Forum Rules and Guidelines ,--------

'--- >The shortest distance between two nodes is a straight wire> ---'