DFGray

I have seen this type of thing many times before, but only when I was writing Express VIs, and I don't think any got out the door (I did not write this one). I filed a CAR on the issue. Details in your NI Forums post. Converting the Express VI to a normal VI (showing the front panel) is reversible. Use your favorite form of undo. Converting to a normal VI and fixing the issue is also your best workaround at this point. If you can figure out how you caused the error, please post it on the NI forums to help us debug the root cause. Express VIs are actually a special form of SubVI. This SubVI has a flag which signals the calling VI to save the called VI inside the calling VI rather than in another place on disk. But the called VI is a separate VI and you can get to it by showing the front panel, as you found out. When you close the configuration dialog of the Express VI, the contents of the called VI are scripted to match the configuration. In this case, something in that scripting went wrong.

I will agree with Aristos Queue on this one. FP terms inside a structure will prevent inlining. For a list of other things which will cause inlining to fail, check out my post on the NI forums for doing it programatically. It includes a VI which checks for a lot of them.

Add a page is a method on the Tab control, not on the Page. As has been mentioned before, you can't add a page to a tab control on a running VI. There is an extreme hack that I actually implemented once. Create a main VI with a subpanel. Dynamically create a tab control with a subpanel on each tab. Load the code for each tab dynamically into the subpanels. When you need a new tab, create a new tab control with the correct number of tabs and subpanels. Without stopping them, load the code into the new tab control and populate the new tab. Then exchange the new tab for the old in the top level subpanel. If done correctly, it is seamless to the user. I do not recommend doing this. It is far easier to create the maximum number of tabs you will need and hide them when you don't need them. I ended up using an entirely different GUI for the above system, and it worked much better (it was a simple subpanel with a tree control selector).