LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I Can't copy the vi after build application

I copy the vi and make it run using vi server, it works great in the development environment. But when i build application,
 
it seems to can't copy. I know the path of application is different with development environment.  the VI is in a internal.llb of exe.
 
I try many ways of copy the vi, and place a indicator on the path of the copy vi, but every time I find it is "not a path"
 
Why?
 
 
 
0 Kudos
Message 1 of 4
(2,272 Views)

There are all kinds of differences between LV and the run-time engine, but I don't think they should affect copying of VIs (even built ones). I suggest you post your code so we can look at it.

By the way, if you what you want is multiple copies of your VI, all you need to do is rename its extension to vit and call it using VI server. A new copy will be created in memory each time you do this with each copy having its own memory space and FP. Search the example finder for VI templates and you will probably find some examples.

Addition - if you're trying to copy the VI into the exe, that is probably the reason for this as the exe would be write protected when it's running and you can't write into it. You shouldn't change an executable yourself anyway, as I think they're signed and changing them might cause the RTE not to run them.

Message Edited by tst on 07-20-2006 02:28 PM


___________________
Try to take over the world!
0 Kudos
Message 2 of 4
(2,264 Views)
This is the vi I used to copy other vi.    labview 7.1
 
 
0 Kudos
Message 3 of 4
(2,243 Views)
Continued here.

___________________
Try to take over the world!
0 Kudos
Message 4 of 4
(2,217 Views)