VI gets corrupted and will not operate when moved to another system

[jonerbe]

I have a test program that I am needing to run on more than 1 system.  When I try to move it from the computer I developed it on, to the test system computer I get corrupted VI errors.  The number of corruptions and the VIs that get damaged seem to be random.  This is also the case if I build an executable and move that to a different system.  Every time I try it I get different sub-VI errors.  Any suggestions would be helpful.

Thanks

[Dennis_Knutson]

There's a difference between a corrupted VI, a VI with a broken arrow, and a VI that returns an error. Please explain with some details.

[Ben]

---

Dennis Knutson wrote:
There's a difference between a corrupted VI, a VI with a broken arrow, and a VI that returns an error. Please explain with some details.

---

Please add me to the "I'm baffled list".

Ben

[jonerbe]

Its not a broken arrow, an error window pops up and gives an error message, I'll try to catch the message again, but I think it is error 23.  It also mentions lack of memory to open and data corruption.  These VI's work before I try to move them.

[Dennis_Knutson]

Did you merely copy the exe or did you create an installer that includes the run time engine and all hardware drivers?

[Ben]

---

jonerbe wrote:
Its not a broken arrow, an error window pops up and gives an error message, I'll try to catch the message again, but I think it is error 23.  It also mentions lack of memory to open and data corruption.  These VI's work before I try to move them.

---

Well, i'm not as baffled as I was previously but I'd still like to see that error message before I speculate.

Ben

[Broken_Arrow]

---

Dennis Knutson wrote:
There's a difference between a corrupted VI, a VI with a broken arrow,...

---

And a VI with a broken arrow isn't nearly as dangerous as Broken Arrow with a VI.

But seriously, do you use Toolkits on the computer that works? Esp. Microsoft stuff?

[Ben]

---

Broken Arrow wrote:

---

Dennis Knutson wrote:
There's a difference between a corrupted VI, a VI with a broken arrow,...

---

And a VI with a broken arrow isn't nearly as dangerous as Broken Arrow with a VI.

But seriously, do you use Toolkits on the computer that works? Esp. Microsoft stuff?

---

THat is a great line Broken. Maybe its time for you to give yourself a signature?

Ben

[jonerbe]

This is the error, the only change is that it is not always the same VI that has the error loading.

[Ben]

Clarifications

1) You  have no problem with these VIs on the developmen machine? (T/F)

2) Every machine you try to move the VIs too show you this error? (T/F)

3) NO VIs including small quickies will move from your development machine and open on any other machine? (T/F)

4) VI developed on other machines (including small quickies) will open on your development machine without any error? (T/F)

Ben