Error 1003 At Open VI Reference

[nnnne]

I'm calling a VI from a library using the Open VI Reference. The main program in an executable file. If I make a change to the *.llb and try to call it using the main program I get an error 1003 Open VI Reference is not executable. Now I've made changes to the *.llb in the past and never got this error before, but this time I can't run the *.llb anymore. What is my issue?

[Joe_Guo]

Can you run the vi successfully in the llb separately? If you used activeX controls in both the main application and the subvi in the llb, make sure you are using the same version. You might need to relink the property node or methods if the activeX control has been changed.

Hope this helps,

-Joe

[nnnne]

Yes the *.llb can run all by itself. Infact if I run the main program in code format I can call the *.llb with no errors. But the executable of the main program can not after I make changes to the *.llb.

[Robert M]

Are you able to call the VI in the .llb correctly right after you build the executable? In other words, do you get the error only after making changes to the VI?

As long as you don't change the name of the VI in your .llb, you should be able to make changes to it and still run it from your executable.

How are you referencing the VI from the code in the executable? Are you using the absolute or relative path? Is all of this happening on your development machine, or are you moving the executable and .llb to a different machine?

[nnnne]

Thats correct, I only get the Error 1003 when I make changes to the vi within the .llb and then try calling it again with the executable. It is the absolute address that I'm using and I'm trying to call it using the Open VI Reference.vi in the executable. I haven't changed the name of the vi. And I get the error if I try it on my development computer or if I move to another computer.

[Robert M]

I created a couple of dummy VI's to simulate you situation, and was able to change the VI in the .llb and still open it from the executable. Would you do the same thing and see if it works on your machine? I would be willing to try running your VI's on my machine to see if I get the same error. Is your application of such a nature that I could do this (i.e. not too large, no necessary hardware)? If it is, try to scale it down to a version I can run that still exhibits the faulty behavior.