I don't see an attached VI.
However, I can give you some insight into the difference between run-time engine (rte) and development engine (dev). Generally VIs have a lot of subVIs and hierarchy that are linked internally inside the VI. Meaning that the VI knows how to find the subVIs based on relative paths or search directories that the LabVIEW dev environment knows where to look. When you switch it to rte the search directories are no longer used and in a lot of cases the relative paths become messed up, especially if you copy or move the VI to a different location.
You need to "deploy" the VI so that it brings all of its dependencies along with it. There are several options. You can use the TestStand deployment utility to deploy the VI. This will bring all of the dependencies and relink the VI to the new relative locations. You need to make sure that you move the VI and all of its dependencies to the proper location on the deployment machine. If you use the TestStand deployment utility creating an installer will take care of this for you.
Another option is to create a source distribution from LabVIEW. I've had success with that but it is not a great option.
Even another option is to put the VI into a packed project library and call it from there. PPLs will bring all of the dependencies along and put them in a single application space. This is how I do all of my TestStand deployments nowadays. You can run with both rte and dev in this scenario.
Another thing to consider is that if you are moving the VI to another machine sometimes it relys on drivers. Those drivers need to be installed on the new machine as well. Even if it is VISA or DAQmx they need to be installed on the new machine. Those don't just get installed with LabVIEW.
Hope this helps,
