exe can't find simple vi's

[Dennis_Knutson]

I used the 34401 driver that comes with 2009 and built the project. Ran the exe and did not get prompted for anything. Do you have your driver installed in the instr.lib folder?

Edit - I'm also running sp1.

Message Edited by Dennis Knutson on 03-08-2010 03:10 PM

[GovBob]

Dennis, I also used SP1 for this. The 34401driver is the one that ships with LabVIEW and is located in the instrument library folder. I double checked this on my top level vi by opening those subvi's and looking at their individual properties. (Ctrl + I).

 The reason I upgraded to SP1 was to fix a dependency conflict warning I kept getting everytime I opened the top level vi from the project.

 I am so perplexed by what is causing this. The vi runs fine but the exe won't on the development computer.

Note: I do have a service call into NI and am also working with them.

Attached are 2 screenshots. One of what I got originally without SP1 and the other is what I see when I try to run the executable. Note that the second is a very simple version of my original project.

[Dennis_Knutson]

No idea, really. Does selecting 'Use LabVIEW 8.x file layout' on the Advanced category page make any difference?

[GovBob]

I haven't tried the 8.x layout yet but I will. Question: since you used my project do you think I can rule out a mistake I might have missed in my Build Specifications properties pages? I'm not sure what gets ported over when you use someone elses project e.g. source file settings.

To me this seems like a search directories problem. I'm not sure how the .exe search directories gets configured. In my overall options for the LabVIEW environment I left the Paths selection at the checkmarked "Use Default".

There's my tail, there's my tail, there's my tail

thanks again for your time.

[GovBob · Accepted solution]

Well I found out the cause of this problem and figured I would share and hopefully someone can confirm this behavior (bug?).

What it came down to was my selection of destination directory for the build.

Where I had been putting it was C:\Program Files\National Instruments\LabVIEW 2009\user.lib\builds...  When run from that location the exe could not find any of its subvis.

When I changed my destination directory to C:\Documents and Settings\Administrator\My Documents\LabVIEW Data\builds.... it worked like a charm.

I confirmed this behavior on 2 different systems using a simple vi/project consisting of GPIB calls to a Agilent DMM 34401A.

Is this known behavior?