called vi not running

[TCPlomp]

Where do you get what error?
I can see you have the name of the main VI wrong in the test 1.2.vi.

But for the rest the code functions as i would eexpect

Ton

[johnsold]

Did you change the path constants to reflect the modified names of the VIs? I had a similar problem when I started modifying your VIs. In the test1-1.2.vi which you posted the VI path is main menu.vi but the modified VI is Main Menu.2.vi.

I understand the NI will be including an option for LV to generate code which implements what the programmer really wanted to do rather than what he put on the diagram. But it won't be ready until at least LV version 53.

Lynn

[twayne]

Hah, of course, you guys are correct that I had the test.vi pointing at the wrong version of my Main Menu vi.  That fixed it quite well.  So I made sure everything looked right in my real software adn it all seems to be working very well.  The only issue I am running into now is an intermittant case where I select the button I want on the Main Menu and it seems to miss actually calling that .vi and just makes the Main Menu hidden without doing anything else.  Im totally at a loss about why this is happening but Im not sure what I can do about it at the moment.

Thank you all for all of your help.  you have saved my days of fooling around with this on my own.

LV 53    too funny.

[twayne]

Just out of curiosity, one quick follow up.  The path on the VI Open command, if the two vi's aren't in the same directory I know you have to put hte full path on there, how do you handle that for creating the exe?  right now my main menu and my vi's that the menu calls are not in the same directory so i have the full path in there, will labview account for this when i creat the full thing, so that i dont hav eot worry about changing that path in any way?

[Jennifer_R]

Hi twayne,

I did a basic test, and my executable loaded the other VI fine when given the full path.  Just make sure any VIs that are called are included as dynamic VIs when selecting the source files for your executable.