Static VI reference only available in Development Environment (2011)?

[Bob_Schor]

When I build an EXE that has a Main (the Top-Level VI that "starts" the system) and assorted VIs that get called as Clones with Start Async Call, "Main" is in Startup VIs and nothing is in Always Included.  The use of the Static VI Reference forces the referenced VI to be included in the Build.

Bob Schor

[Ben]

Dumb question...

Was "main" back-saved to 2011 as well?

Ben

[Gregory]

Hi Ben, yes, everything works fine in LV 2011 development environment, it's only when I make an executable that it doesn't like the static vi ref. 

[aputman]

What do you mean "it doesn't like the static VI ref"?  Does the EXE not build or it doesn't run?

My splash screen is setup to call Main like this but I use the VI name, as mentioned.  However I just tried it with "VI Path", in both 2012 and 2011 (IDE and EXE) and it works fine.  I have the splash screen as the startup VI in the build specifications with nothing in the Always Included box.

Try deleting the reference and recreating it.  I'm not sure what is going on.  If you can share the project, I can try it on my system and see what happens.

[Gregory]

Thank you, I'll try that when I get to the office in an hour or two. 

When I build the executable it pops up saying the VI can't run and the arrow is broken. If I put a disable structure around the static vi ref (after much trial and error), the executable is fine, but of course runs with errors since the Main VI doesn't launch. Maybe the problem is with Main VI and not the reference...

[aputman]

Yes, it would seem so.  That is why Ben asked the question.  Maybe, when you back saved the VI, everything was back saved properly but the reference is still pointing to the 2012 version.  Just a guess but it sounds plausible to me. 

[Ben · Accepted solution]

You may also want to dig into "main" and see what part of it is not liking the 2011 environment.

There where some changes from 2011 to 2012 see release notes and perhaps LV is running into problems converting back to 2011.

Ben

[aputman]

---

@Ben wrote:

You may also want to dig into "main" and see what part of it is not liking the 2011 environment.

There where some changes from 2011 to 2012 see release notes and perhaps LV is running into problems converting back to 2011.

Ben

---

You would think that might be the case but he says that it runs fine in the IDE.  I definitely think that something was messed up in the conversion, just not sure what.

[Ben]

---

@aputman wrote:

---

@Ben wrote:

You may also want to dig into "main" and see what part of it is not liking the 2011 environment.

There where some changes from 2011 to 2012 see release notes and perhaps LV is running into problems converting back to 2011.

Ben

---

You would think that might be the case but he says that it runs fine in the IDE.  I definitely think that something was messed up in the conversion, just not sure what.

---

Yes good point.

But code developed in 2012 back-saved to 2011 and then built may be a corner case that has a problem.

I think it is time to start lopping out big chunks of "Main" to see what parts are introducing the problem.

Ben

[Gregory]

Thank you all for your help. I think I've narrowed it down to the openg "Write Section Cluster", which I only used for development purposes so I got rid of it. Oddly, the "Read Section Cluster" was not an issue.