Exe works on my computer, but not on others..

[JDlabview]

It is in my project file, isn't it ?

I really don't understand what's happening...

EDIT : ok, I have to add them as if they were mains VIs .. will be pretty long as there is a loooooot of VI 🙂

Message Edité par JDlabview le 06-11-2010 05:04 PM

[Dennis_Knutson]

The only VIs that you will have to add are those VIs that you call dynamically. If your entire hierarchy is listed in the dependencies, there is nothing to add since they will be included in the exe.

[Mark_Yedinak]

---

Dennis Knutson wrote:
The only VIs that you will have to add are those VIs that you call dynamically. If your entire hierarchy is listed in the dependencies, there is nothing to add since they will be included in the exe.

---

He will have to manually specify what the installer should include though. It generally does not pick up all the dependencies automatically.

[Dennis_Knutson]

Agree. I should have made that a bit clearer that the developer needs to be aware of what drivers the program is using and make sure those are included in the installer. So, with the SVI functions, that runtime should be selected as an additional install.

See this all the time with novice users who think a simple copy of the exe is sufficient.

[JDlabview]

Of course it is included in the exe at it works well on my computer.

And as the signal (plot of the signal) pass thru these sub VI, it should work well for the others plots too (Failures & Limit).

What do you call "dynamically" ? And yes all my sub VI are in the dependancies.

I'm done for today, it's 6pm.

Hope it will works well on Monday...

[Dennis_Knutson]

Did you really read my previous post? Did you install the SVI runtime? Did you go back and create an installer like you should have done in the first place?

[Mark_Yedinak]

---

JDlabview wrote:

Of course it is included in the exe at it works well on my computer.

And as the signal (plot of the signal) pass thru these sub VI, it should work well for the others plots too (Failures & Limit).

What do you call "dynamically" ? And yes all my sub VI are in the dependancies.

I'm done for today, it's 6pm.

Hope it will works well on Monday...

---

When builing the application there can be lots of external dependencies such as drivers. These are NOT built into the exe. The reason it works fine on your computer is that those things are installed there. When you simply copy the application to a different computer you are not guaranteed that those other dependencies are there. This would result in the application not working correctly.

[JDlabview]

The only VIs that you will have to add are those VIs that you call dynamically. If your entire hierarchy is listed in the dependencies, there is nothing to add since they will be included in the exe.

The point is that all these VI are included in the dependencies, but what do you mean by “those Vis that you call dynamically” ?

Agree. I should have made that a bit clearer that the developer needs to be aware of what drivers the program is using and make sure those are included in the installer. So, with
the SVI functions, that runtime should be selected as an additional install.

I did install labview 2009 runtime on the others computers, but I think you are talking about a sub VI runtime ? (the polymorphic SVI that doesn’t work: limit testing.vi). What is it and how can I add it in the installer ?

Did you really read my previous post? Did you install the SVI runtime? Did you go back and create an installer like you should have done in the first place?

Of course I did read your post, but I didn’t have the time to try this, and didn’t really understand everything as you can see. I'm a beginner in Labview (1 month experience)

Mark Yedinak: I understand well this, but how can I know what dependencies/drivers are needed? The only thing that doesn’t works is (I think) the polymorphic VIs about limit  specifications and testing and I didn’t install anything to make them work on my computer.

Thanks
to both of you for your advices, going to try this tomorrow at work.
JD

Message Edité par JDlabview le 06-13-2010 03:35 PM

[Dennis_Knutson]

You are usung the sound and vibration toolkit. That requires it's own runtime engine. The option to include that is shown when you do a Build Specificatios>New>Installer and go to the Additional Installers option.

[JDlabview]

No I don't use the sound and vibration toolkit, but I created an installer with NI-VISA Runtime and NI-488.2.

I will try this afternoon, but I'm not really confident as VISA & 488 are used for instrument communication, and it wasn't the problem I met.

I'll give you feedback.

Thanks for your help