Problem building exe with dynamic vi

[ATMA]

Hi all, i'm using LV 8.2 evaluation version to build an executable file for my test platform. This platform calls for individual test vis dynamically.

I can export the platform vi into exe alright but it always fail to run the test vis dynamically when called by the platform. I know the platform is working alright as it's able to successfully traverse through all my operating states, but when it comes to the state which contains a subVI which calls these test vis dynamically, nothing happens and it just proceed with the next state. The even wierder thing is that the program then enters my default state (which isn't even on the list of states for that particular operating mode!)

Based on this result i can say that the platform is working fine as it was able to call various subvis and traverse through the defined states (except for the default state case). Thus i guess it must be something which i did wrongly during the build process which caused it not to run my dynamic test vis. I spent the whole day trying various build options but it still doesn't run my dynamic vis.

Any ideas?

PS: Does the build process automatically import the MAX settings?

[parthabe]

---

@ATMA wrote:
Hi all, i'm using LV 8.2 evaluation version to build an executable file for my test platform. This platform calls for individual test vis dynamically.

---

You CANNOT build an EXECUTABLE using an EVALUATION version of LabVIEW.

I m wondering how did you manage to do it!

[ATMA]

Funny, i was able to create the executable, only can't run the dynamic VI. Is it some bug or trick?

[parthabe]

See the attached pic. No Application Build option.

[parthabe]

Maybe your version is a cracked version of evaluation I think.

[Dennis_Knutson]

The build exe is not under the Tools menu in 8.5. It's only available in the project explorer.

ATMA,

you may have a path problem or failed to include the dynamic VI in the build. A common mistake that many users make is not accounting for the differences in paths when an exe is built. How are you defining the path to the dynamic VI?

[ATMA]

No, it's not a cracked version just to make myself clear.

Dennis, i don't think it's a problem with the path as the exe does not have any problem loading other text configuration files. Yes, i've included them under the dynamic vi and support files option.

[Dennis_Knutson]

That image doesn't tell me a thing. How exactly are you calling the dynamic VI? An image, or even better, the actual code, would help.

[parthabe]

Dennis,

That image if for me, I think...

[JeffBoettcher]

Just to clarify, there's nothing unexpected about ATMA's situation - as of LabVIEW 8.0 at least, the evaluation version should expose all the features of LabVIEW professional during the evaluation period.  And Dennis is correct, we removed the Tools menu shortcut to creating a project build specification in 8.5.  I agree that the problem is most likely path related.  It is possible to debug built executables (you would need to re-build the EXE with debugging enabled though).  I'd suggest looking up Remote Debugging in the LabVIEW help for more info.