application builder vi does nothing

[krwlz101]

OK.  Found the error...  That said, not sure how to fix it.

(attached also if this is too small)

So it looks like VI reference error, although I am not sure on the how or why?

[JÞB]

yes you do----- relative paths  Nice work!

[krwlz101]

I guess I am feeling a little bit dense today.  I see where the default data directory function may cause an error here, so I can fix that to save into the data file in the directory for this application in program files...

But why am I getting an invalid reference from the VI Property node for the name?

[smercurio_fc]

The path where the config file is saved has nothing to do with the error here. I don't know why you're getting that error, as it works just find on my computer. I built the app based on your build spec (see below for additional comments) and even the installer, and the app worked just fine. So, something else is going on. Not sure what yet.

• You do have a problem with paths, though. You have a big NO-NO, especially in what appears to be an application that's intended to be distributed to what I assume is a customer. You have hard-coded paths pointing to the login of the laptop. BIG PROBLEM.
• You do not need all to put all those files in the "always include" list in the build spec. That's intended for dynamic VI, which you have none. As long as you have the top-level VI then all statically linked VIs and controls are automatically added. This is explicitly explained in the LabVIEW Help.

[krwlz101]

Thanks smercurio. 

I definitely will be distributing this, technically the distribution is to fellow co-workers, but they are customers too.

I will definitely review the paths and the build spec items.  I did read the help, but the first read was a little overwhelming, so I clearly missed a few items.

I wonder if maybe one of those other hard coded paths is causing my issues.  Like I said, the app loads fine, but as you update fields, the queue output is always null from what I can see.

Thanks for all the help!

[smercurio_fc]

---

@krwlz101 wrote:

I wonder if maybe one of those other hard coded paths is causing my issues.  Like I said, the app loads fine, but as you update fields, the queue output is always null from what I can see.

---

I thought your issue was with the error from the property node. I just checked to make sure the colors would load when you quit and restarted the app. Are you having other issues?

[krwlz101]

Well,

The problem is that nothing executes.  When I found that error I thought that maybe it was causing my issues.  as I change the values in any tab, it should be recalcuating, but my QSM just stays at "Null" all the time.

[smercurio_fc]

The most likely issue is that the error that's being generated out of the VI that's reading the configuration information. That error is being passed into your loops and into your queue VIs. Since they see an error in, they don't execute.

As I indicated, I have no idea why that VI is generating an error, and unfortunately right now I'm really bust on trying to get something done at work, so I don't think I'm going to have time to look at this. Maybe someone else may be able to take a crack at it.

[krwlz101]

I thank you very much for the time you've put in.  I have no problem at all with troubleshooting the issue, but I am very glad to hear that the source of the problem is likely pin pointed.

[krwlz101]

Finally got some time to play with this today, and I must say that this is getting frustrating.

I changed my path to be relative, as above, although I am not sure this works once the VI gets built?

Also, when debugging the app, the read from speadsheet file vis show up as not found.  I am thoroughly confused.