06-09-2009 09:44 AM
Solved! Go to Solution.
06-09-2009 10:05 AM
Do you see the run arrow? or is it a broken arrow?
If it is a run arrow, you will not see a list of errors.
However, if you click run and it exits, then there is something strange.
Do you use a Quit LabVIEW vi anywhere in your code?
R
06-09-2009 10:55 AM
The arrow is broken.
Clicking on this opens a blank errors window before promptly crashing.
There is no code to quit labview in the code as the application will ultimately be compiled as stand alone.
This behaviour is something that I have not seen as a repeatable problem before even after a computer reset.
06-09-2009 08:10 PM
06-10-2009 04:52 AM
Earlier versions do work correctly with deliberate errors inserted, the error is then listed rather than crashing.
This is the first time that this is happening. The main vi is gettingto a fair size now with new events, some complex, being added and ties into the front panel closely making use of many many property nodes. I am hoping I do not have to resort to earlier saved versions as it would require significant work to again reach this point with no understanding as to why.
06-10-2009 05:39 AM
06-10-2009 09:07 AM
06-10-2009 11:32 AM - edited 06-10-2009 11:33 AM
06-10-2009 12:46 PM
06-10-2009 01:23 PM
E for English?
Where did you find that .exe on the NI website? I searched and couldn't find it.
The link you gave is to the temporary directory on your hard drive.