Problem reading a vi's description property in an executable

[becktho]

Hi guys

I run into a very strange problem. I have a vi (attached) which reads the description property of a vi. The vi is inside a llb. I use the function "current vi's path", strip it and then build a new path with the name of a vi which is in the same llb. When I run my program in the IDE it works without any problem, but if I build the executable it doesn't work anymore. I logged all the paths - all of them are correct, but I don't get the description property of the necessary vi.

Basically I have the toplevel-vi in llb 1, the attached vi in llb 2 and it is used in another vi which is called in the toplevel-vi and located in llb3.

Is there anyone who could help me out?

Many thanks in advance.

Thomas

[MikeS81]

Hi Thomas,

in your application all vi´s lie side by side. So the path you get from "currentvispath" is:

directory\yourapplication.exe\actual.vi

To see it better you can simply add an indicator to the currentvispathvi and show it in your application.

Mike

Message Edited by MikeS81 on 01-29-2008 10:15 AM

[becktho]

Hi Mike

Yes, I know. As I wrote all the paths are correct, otherwise I would get an error when opening the vi-reference (Err 7 - file not found). I am wondering why I can read the description property but don't get any text.

As mentioned in my first post all works correctly if I let the program run in development mode. If I run the exe I don't get anything.

Thomas

[BillMe]

Are you using the "default save settings" in the build properties (under the Source File Settings page)? This removes the front panel and block diagram which I suspect may remove the VI description text. I haven't tried a test case so I'm guessing here.

[parthabe]

Hi Thomas,

I know that this is just the opposite side of your problem, but you can ve a look over here for more details, I think...

http://forums.ni.com/ni/board/message?board.id=170&message.id=180194&requireLogin=False

Sorry, if it is totally out of context.

[becktho]

That's exactly what I've been looking for..

As usual - if you don't use something for a long time, you forget it.

Anyway - thanks Bill. You helped me a lot.