10-17-2022 09:31 AM
What you are doing should, in principle, work. The tricky part lies in the "path" name, which is different if called from the Development side as opposed to from the Executable side.
There's a way, however, to get the (correct) path at Run Time (Development path if during Development, Run Time path if during Run Time). You open a Static VI Reference (Application Control palette), browse to the Path of your VI, and click "OK". If you are using Start Asychronous Call, you'll want to right-click the Static Reference and make sure it says "Strictly Typed" (a red Star will appear on the Icon). Wire this to a Property Node, choose Path, wire Path to an Open VI Reference, and wire this path to the Start Asynchronous call. Here's an example:
Bob Schor
10-18-2022 02:45 AM