Stand-alone application generates error with function 'Ramp Pattern' (bug in application builder?)

[chelydra]

Hello,

in my program a main.vi links to a sub-VI via 'open VI reference' and 'invoke node'. In this sub-VI the function 'Ramp Pattern' is used. The program itself runs normally, but if I build a stand-alone application using application builder I get an error message 'error 1003 occurred ..'. I believe this error is directly related to the build specifications which are as follows: the main.vi is referenced in a main build specification, the sub-VI in its own specification where the target is a LLB.

I appended an example-program that exhibits the error (when executing 'Application.exe' and pressing 'calculate ramp'). The error does not occur when disabling the 'ramp pattern' function and rebuilding the application.

I would rate this to be a bug in the application builder and would appreciate any help on how to solve this problem. However, due to the structure of the whole program the sub-VI has to remain in its own LLB.

[mikeporter]

The error means that the subVI is not executable. There can be many reasons for this and (I believe) one bug related to it. Do a search in the forum for "error 1003" you will find lots of things to verify.

Mike...

[chelydra]

Hello,

right, it says that the sub-VI is not executable - but there is no obvious reason for it. If you open the VI from the LLB it says it IS executable. I searched the forums already and honestly believe this particular error has not been described before. The 'ramp pattern' function makes use of the file 'lvanlys.dll' and therefore I tried to include it in the build-specifications (although normally that should not be required), but that did not solve the problem.

[mikeporter]

There can be reasons why a VI might appear broken when loaded from an executable. For example, if you have different versions of the same VI or enum that differ in such a way as to break the calling VI, that can cause a broken arrow when loaded from the executable. If you have DLLs being called and the runtime engine can't find the DLL, that can cause a broken arrow that you might not see otherwise. Finally, there is a bug related to a VI appearing broken when its not.

Mike...

[chelydra]

Hello,

I slightly modified my example: in the new example the sub-VI appears with no broken arrow when opening it from the LLB. The error message upon execution of the main-VI is still the same. That means the sub-VI appears erroneous only when called from the main-VI during runtime. I can not see how to fix that.

[Sima]

What version of LV are you using?

Edit:

Nevermind, I see you're using 8.2. Here are a few things to try for error 1003 (from a previous post):

- Uncheck "Disconnect type definitions and remove unused polymorphic VI instances" in the Advanced section of the builder.

- Remove front panels from sub VIs that use shared variables

- Check "Enable debugging" in Advanced.

Of course, try one at a time and see which one works, if any.

Message Edited by Sima on 07-31-2007 03:53 PM

[chelydra]

Well, I have tried all of these recipies (and a few other things) before, but none of them worked 😞

[Sima]

Is the llb included as a support file?

Try a forced recompile? mass compile?

Have you tried deleting the build and starting from scratch?

Here's some more: Error 1003 Occurs When Trying to Create an Executable

[chelydra]

Hello,

yes, I also tried the recipes in this knowledge base entry. Although I should mention that in my case I do not receive the error message upon building the stand-alone version (which executes normally), and not upon running the applicaton but only when the main.vi actually runs the sub-VI.

Forced recompile/mass compile should not be required in the simple example I posted. And I did not include the llb as a support file, it is my understanding that the application builder should build and link the llb in parallel with building the whole project.

Thanks to all the support here but I still can not figure out how to fix it.

[Sima]

Hi chelydra, any news on your problem? Could you please clarify what you meant by "Although I should mention that in my case I do not receive the error message upon building the stand-alone version (which executes normally), and not upon running the applicaton but only when the main.vi actually runs the sub-VI."

I'm running 8.0.1 at this computer so I haven't been able to open your VI.