"Write Key.vi" wont work after build

[DBadowski]

I am having dificulty with the "Write Key.vi"  I am using it to save calibration values to an .ini file. This works fine when running in development mode but after I build it into a standalone exe it doesn't work. It will create the file in the correct folder but it is empty. I have no idea how to start figuing this one out. Any help would be greatly appreciated.

Here is the code that saves the configuration values into the .ini file. I am using LabVIEW 8.0

[smercurio_fc · Accepted solution]

Why Does My Executable Not Work When Using the Current VI's Path Constant? - KnowledgeBase - Support...

I will let someone else chime in here regarding all those local variables. They're out there, waiting in the bushes, ready to pounce when they see one of those little beasties. It's always hunting season for them.

[Gak]

Hi DBadowski,

Put Strip path between "Current Vi path" and "build Path" functions.

This might work. Try it and let me know.

Best of Luck

[smercurio_fc]

---

@Gak wrote:

Hi DBadowski,

Put Strip path between "Current Vi path" and "build Path" functions.

This might work. Try it and let me know.

---

That would work for the application, but won't when it's in the development environment. The KB article provides the proper approach.

[Hooovahh]

---

@smercurio_fc wrote:

Why Does My Executable Not Work When Using the Current VI's Path Constant? - KnowledgeBase - Support...

---

One other thing to mention is that KB is for LabVIEW 8.2.  In 2009 and 2010 a built EXE by default may have VIs referenced deeper than just one level.  You can keep stripping the path until a directory is found, or an easier solution is to check the box in the Advanced section that is "Use LabVIEW 8.x file layout" which then makes that KB valid again.

[DBadowski]

I had done a quick search for problems with file acces after a build but I guess I missed that article. Thanks.

[smercurio_fc]

---

@Hooovahh wrote:

---

@smercurio_fc wrote:

Why Does My Executable Not Work When Using the Current VI's Path Constant? - KnowledgeBase - Support...

---

One other thing to mention is that KB is for LabVIEW 8.2.  In 2009 and 2010 a built EXE by default may have VIs referenced deeper than just one level.  You can keep stripping the path until a directory is found, or an easier solution is to check the box in the Advanced section that is "Use LabVIEW 8.x file layout" which then makes that KB valid again.

---

Then you can use the alternate method which tst shows

.