VI works in development, but not as executable--file reading issue.

[Dhouston]

The application is able to access the network.  The two controls "Print Screen" and "Save Current" access the Z drive with no problem.  In fact, "Save Current' accesses a file located on that same drive, and the file has much of the same path that we were using in the sequence frame. 

[ErikaB]

Not sure why that happened. Let's try this URL again.

https://forums.ni.com/t5/LabVIEW/Build-exe-and-file-path/td-p/984137

[RavensFan]

---

@altenbach wrote:

---

@Dhouston wrote:

Alas, ErikaB.  I got an error when clicking on that link.  The error is stated below

An invalid set of parameters has been specified in the url.

---

Why does it think it is an url?

The Z: drive seems like a network drive that has been locally mounted to a drive letter.

Does the built application have firewall permissions to access the network? (I assume you allowed LabVIEW to access the network when you installed, but that rule no longer applies once you built an executable).

---

Altenbach,

This message wasn't regarding the problem with the VI, but about Erica's hyperlink she posted.  She had the same problem I had were copying and pasting the link from another source caused a hidden %A0 to get tacked onto the end of the real link and thus broke it.

[Dhouston]

Thanks for the link EricaB.  It eventually led to the same link RavenFan mentioned.

Ok, so we put the Application Directory VI into the program to see path.  We made the executable and ran it.  The path appeared as C:\Users\testlab\Desktop

This would seem to indicate that the exe is not being included in the VI path.  Is this correct, or are we looking at things wrong?

[ErikaB]

---

---

@Dhouston wrote:

This would seem to indicate that the exe is not being included in the VI path.  Is this correct, or are we looking at things wrong?

---

It appears not that it is not included in the VI's folder; that Application Directory VI would return the directory for the executable. You can choose the path that your executable when building that application (right click on Build Specifications --> New --> Application (EXE); Information tab --> Destination Directory), so I would check the properties of your application and see where it was built.

Thanks,