08-24-2007 07:28 PM
08-24-2007 09:24 PM
How is this menu VI called in the main application? Whenever I hear that something stops working when an application is turned into an .exe, it makes me think of the issues with the reference paths to VI's being different in .exe files as compared to the development environment. There have been numerous message threads about this issue.
Here is one such thread. It is about a .dll not working. But the principle about the VI file path is there.
08-24-2007 09:42 PM
08-26-2007 08:34 AM
08-27-2007 09:51 AM
08-27-2007 09:32 PM - edited 08-27-2007 09:32 PM
Message Edited by slipstick on 08-27-2007 09:35 PM
08-27-2007 10:00 PM - edited 08-27-2007 10:00 PM
I know why it comes out okay in the end.
The for loop does autoindexing. Since the input array is empty, it runs 0 times. So the error coming into the loop never passes through the wire to the exit of the loop, because that wire doesn't execute. So the default value of the exit terminal runs, which is a "No error" value.
Now that doesn't explain the initial 1160 error occurring right at the delete menu items function. So the question is what is wrong with the menu reference coming in. Put a probe on the wire between the control and delete menu items function. Also put a probe in the main VI wherever the menu reference gets passed into the sub-VI. See if that sheds any light. When I ran a sample VI to see what the probe shows, I saw a 8 or 9 digit decimal number. And that number increased with each time I started the VI.
Also try a Get Menu Info right before deleting and look at an indicator of its output. See if that function generates an error since that function is just looking at data rather than taking the action of deleting it.
Message Edited by Ravens Fan on 08-27-2007 11:04 PM