Compilation Error

[cirrusio]

Hello all,

I have an unfortunate situation that appears to be due to the LV compiler.  My VI compiles fine until I add more code to the current VI - there seems to be no direct relation to whether the code compiles and what the code that is added.  Here is a screenshot of the error. Does anyone have any thoughts?  (the compile error comes up on save and I usually get like 3 errors).

Cheers, Matt

[SteveChandler]

Create a new blank VI. Go to the messed up VI block diagram and press CTRL-A to select everything. Press CTRL-C to copy it to the clipboard. Close the messed up VI and then go to the new VI and press CTRL-V to paste it. Make sure the messed up VI is closed before doing the paste.

I'm not claiming this will work but it is the first thing I would try. Sometimes VIs just get corrupt.

[cirrusio]

Thanks, Steve.  This could result in a lot of work - this is a user interface that has been somewhat carefully thought out.  I will give that a try though just to rule this out.  Unfortunately, I fear this may have something to do with the compiler.

m

[SteveChandler]

Doing the copy and paste should preserve the locations of the controls and indicators on the front panel. But like you say this will at least rule something out.

[MoReese]

Can you post the code that is "causing" the error?  What does it do?  What functions are you trying to implement?

[cirrusio]

Steve - no dice on the moving to a new VI.

Reese - swing away.  The UI CRDS_PAS Host in the UI Distribution works.  Try adding the VI Start Asynchronous Error Msg VI in the second zip file to the main user interface and saving (CRDS_PAS Host in the UI Distribution distribution).  I apologize for the messy diagrams - I am in the process of trying to fix this d*** problem.

m

[MoReese]

I understand the messiness of debugging.  I will have a look in a bit when I have time unless someone beats me to it.

[TheGeeze]

Hi All,

I took some time to look into this.  From previous service requests, the only recommendation, (and solution to every other case I saw), was to do the copy and paste technique.  (Did you ensure you closed the old VI before copying the data into the new one?)

Unfortunately, Your VI is very broken when I open it on my computer.  There are a lot of missing items.  When I add the code I do not get the same error (or any error).  I suspect its because there are lots of other broken items.  

Does this error happen any time you add anything new to this VI, or randomly?  

Have you tried copy/paste technique on the VI that works, and then tried adding code to the new VI?

Cheers,

Ryan

[MoReese]

I had a similar issue related to .net objects.  Mine was a build error however.  The copy/paste technique did work for me and cleaned it up.

[cirrusio]

Sorry about the delay in getting back to all who have been generous enough to look over this. But, I have a new development to report - I opened the VI and after a couple of weeks of getting this error, it seemed to compile fine when I dropped in the offending VI.  Don't know what has changed as I haven't been editing the code except to add and remove things to determine what breaks the thing (i.e. it would always end in the original, unbroken state).  Given that I did nothing to fix it, I am not convinced that this error will not pop up again when I add more code, so I will keep you updated.

But, in the interest in closing the loop on some of the issues that Ryan asks about:

• I had tried cutting and pasting into a new VI (with this one closed) and had the same results.
• This error was being thrown when I added more code - there was no clear relation to what code or what the code did.

And, I am not sure I would characterize the package as very broken - just a little .  What was missing was from the user.lib and it was Jonathan Green's Error Logger.  Unfortunately, this was not pulled into the distribution.

Anyway, I will keep you updated if this pops up again.  And, given that I did nothing specific to fix this, I am going to leave this open and am not going to click the 'Accept as Solution' button, so I apologize to all who want/need this resolution.

Cheers, Matt