Cannot get installed application to work

[DB_IQ]

Yes, I broke the VI down to it's basic components. Those are pretty basic parts, not sub-vi's.

At the smalllest level of this particualr crash, I have some control inputs, some simple case statements, and some simple indicators. There are no sub-vi's in this function, only labview code. I would expect this sort of function to work correctly. Yet if this function is enabled, my VI fails to run. This is just one example, there are other parts of my code with similar issues I have disabled as well.

Yes, I CAN remove the VI from my code. BUT, this is but one VI in my project that is called. There are other VI's that I have to call and run that have yet to be executed.

I cannot remove every single subvi. I need to identify the cause so my entire project doesn't become a patchwork of disabled VI's.

AGAIN it works perfectly fine as an labview project. As an executable, on the SAME PC, the code does not execute.

I will work with tech support to resolve this. Maybe they will be less sarcastic.

[mikeporter]

The problem is not that we are sarcastic. The problem is that we aren't psychic. Vague descriptions and incomplete information doesn't allow for a good answer. So go ahead and call tech support -- though my experience is that they don't do any better in the 6th sense department than we do, and they know a lot less about LabVIEW.

Mike...

[CoastalMaineBird]

Maybe they will be less sarcastic.

Maybe, but they still require information from you, that you don't seem willing to give.

Put yourself in my shoes: You said that "it didn't work" and you tried something and that "also didn't work".

You didn't say exactly how it "doesn't work".  Does it give an error message?  Does it hang?  Does it give wrong answers?

You said that it "successfully works" if you comment out parts. 

Well, What else could that mean except that you have unnecessary parts?

[CoastalMaineBird]

At the smalllest level of this particualr crash,

So, it's three days after you initially reported this, and this is the first mention of a "crash".  

Did you not think that would be important to anyone to know?

[Bob_Schor]

Thanks, Mike!  They are cute ...

BS

[Jordan_M]

Hi,

I understand that you cannot share your entire code base.  Can you create and share a very small, very simple test case that exhibits the problem you face?  This might help us, or the NI tech support team, to understand and fix your issue.

Cheers,

    Jordan.

[DB_IQ]

---

@Jordan_M wrote:

Hi,

I understand that you cannot share your entire code base.  Can you create and share a very small, very simple test case that exhibits the problem you face?  This might help us, or the NI tech support team, to understand and fix your issue.

Cheers,

    Jordan.

---

I have been able to demonstrate my issues it to tech support.

Once we identify a solution, I will be sure to post it.

Thanks for the advice, no further help is needed at this time.

[DB_IQ]

I was able to address the issue by eliminating the need for the referential VI's.

It's a fix that will work in this case, for what I need it to do.

I would still be interested in knowing the reason why everything failed, but for now everything is good.

Thanks anyways.