Why does my main VI open some subVIs and not another?

[JeffOverton]

If you call a broken VI with VI server and attempt to put it in a subpanel, it will demonstrate the behavior you describe.  What I would do is go through the VIs you call by reference, make sure they're not broken, not throwing errors, that kind of thing.

[guy1]

I'm srry, I can't send you the VIs like I said I would yesterday. Company policy. But I will describe it to the best of my knowledge.

Gerd: crash is not a good term. I am unable to stop the main program from my "quit" (= stop) button or enable any of my other buttons and I am unable to interact with the subVI that I am trying to call. The only way I am to stop it (besides ctrl + alt + delete) is by x-ing out of it (top right) and then it exits me out of the main program all together. 

"Is there a reason to call those vis using vi server instead of putting them as subvi in the main vi? You only set some properties which can be set in the vi too...". I'm not sure what you mean. I thought I am calling it as a subVI in the main VI. VI server? Which properties do I need to set and where do I find them?

Jeff: It is not the VI itself. It is not broken or throwing any kind of errors. I am able to open and run it if I call it in a blank VI the same way am I calling it in the main VI or if I run it by itself. But when I call it from the main VI it does what I described before. The subVI pops up however, the main menu is still showing and is the VI LabView still wants me to interact with. Plus I am unable to interact with the showing (but grayed out) subVI. I've unlocked the FP in the event structure property and the same thing happens.

Since I am able to run it on its own or through a blank VI, I have to believe that the problem lies somewhere in the main VI code. I just dont know how or where.

[JeffOverton]

Is your call by reference node set to Wait Until Done false?  Is your main VI set modal?