compiler error: Invalid size in _instSize = 23

[samynonsense]

Dear sir,

I have installed LabView 2011 in Windows 7  (64 bit). When I open a project which is worked before. A error message has been coming out as 

[Chris_1890]

I'm sorry to hear about that error.  I would like to get some more information on your application.  Is there any way you can either post a screen shot of your project, or attach the file so I can take a look.  Thanks.

[samynonsense]

Thank you for your response! After disccussion, due to the time limit, we desire to run this project in LabView 2009 only.

[Michael.Proctor]

hi,

I also encounter this problem.

Windows 7 (32 )

Moving from LV2010 to LV2011

Out of 400 vis only one failed to compile.  Not the most complex , but reasonbly large vi.

I believe I compiled this succesfully in lv2011 beta.

Michael

[guibook]

I've had the same error at compilation when migrating from LV2010 to LV2011.

in my case (after hours of debug!) the reason was a tab control (U32) connected to a "In Range and Coerce" function.

converting the Tab control input to I32 resolved the problem.

[Michael.Proctor]

NIce clue.

I have not had time yet to try it.

However when one clicks "Show Error" the front panel does pop to the front.

In this case I have many tabs on this interface and I do manipulate them so the chances are I have a

type conversion.  

Did you get one error message or many.

 I have the "Invalid size in _InstSize: 23" message come up 8 - 9 times per save/compile.

So it seems I have might have 8-9 places that have the error.

Michael

[guibook]

In my case, there was only one place in code where the conversion was needed but, yes, the message comes up about 8 times!

[Michael.Proctor]

Indeed it is the Coerce vi that causes the problem.

No matter how much care I took to remove any type conversions in my wiring - so long as I had an "In Range and Coerce"

in the wiring

my vi was cursed.  

Fortunately easy enough in my case to replace with case statements.

Thank you so much for replying as the vi I had problems with ( just 1 out of 400 ) was a large and multi layered GUI

vi.

Problem solved.

michael

[Ammouri]

Thank you for this. I had the same inrange and coerce problem that was fixed by inserting an I32 conversion

[Sanshiro]

Thanks for everybody. I encountered the same inrange and coerce problem that was fixed by correcting the same type inputs from 8.6 to 2012.