Error in labview 8.0 for MKS 146 device

[blue_sky]

Hi,

We have a Labview program written for a MKS 146 device. Howver, there were a couple of errors shown when the progam started up. Like, "Subvi 146trans.vi: subvi is not executable"
"Subvi MKStrans.vi: subvi is not executable" and "Subvi 146INIT.vi: subvi is not executable". Why is this happening? How can we get rid of this problem?

Thank you,
L

[mikeporter]

It sounds like this is happening with an executable. Yes?

The problem is that these functions can't find something they need to run. Typically when I have seen this sort of error in a runtime application is when DLLs that the subVIs need aren't where they are supposed to be.

Mike...

PS: Oh yes, has this application ever worked, or did it just stop working?

[blue_sky]

That is very possible. I copied these DLLs over and just put in a MKS folder under the NI folder. I will try to see if it will work  with these files moved to other place.  Thanks for the help.

L 

[mikeporter]

Remember that a reference to the DLL is saved in the call function. If the DLL is located in the Windows system directory this reference is simply the name of the DLL - the path to the system directory is a system constant stored in the registry. If the DLL is located anywhere else, the reference is the complete path to the DLL. At the end of the day, however, all you realy need to remember is that the DLL needs to be in the same place on the execution machine as it was on the development machine. In other words, if the DLL on the development machine was in, for example, "c:/Program Files/MKS Stuff/bin" you have to create that entire directory structure on the execution machine.

Mike...