02-09-2012 08:07 PM
I built a LabVIEW executable using the installer. Another program (the master) can control this executable by using the activeX Server. I have updated the LabVIEW executable several times since it was first used on a production unit. The master program has a defined VI path to call the LabVIEW. For example, the VI activeX path is
C:\Program Files\RUN\RUN.exe\RUN.vi
For some reason with my latest install (1.7), it added a folder, so the original hard coded master program cannot get the VI reference anymore to control the LabVIEW executable. The path is now
C:\Program Files\RUN\RUN.exe\RUN 1.7\RUN.vi
My development machine still had the original path (without the 1.7 folder). I wondered if it had something to do with where I installed it from. Previously I always installed on my development machine from my development machine. So I uninstalled it and installed the same program from a copy on my network (the installer program is the same but it is in a differnt folder structure). Now my development machine has the same extra 1.7 folder and I tried to uninstall it and re install it frmo the develpmet machine itself. No luck. The VI path now is stuck with the extar folder. How do I get rid of it.
The master Program was bought from another company and was completed so it cannot be changed..unless I call up the company, have them change the code...to allow a variable VI path, and then install this new master program.
Why did LabVIEW put an extra folder in the VI path for the installed executable? Is there a way to fix it?
02-10-2012 04:57 PM
Hi javiucsd,
Have you made any changes to LabVIEW on your development machine (ie, upgrade)? Are there any other changes you've made between deploying 1.6 and 1.7?
Best,
02-10-2012 05:29 PM
No changes have been made to the LabVIEW Develpoment system. It has always been LabVIEW 2010 SP1. I made a backup copy of the project and then deleted the original project. I revreated the project with the built executable and the installer. The project matches the old one exactly but now the VI path is back to the way it was (without the extra folder in the VI path).
I spoke to another LabVIEW programmer and he had a similar problem. One day the VI path changed when he built a new executable so it made it unusable for another program using the VI reference through activeX. He has no idea how it happened.
I do backup my code from my local PC to the network (for backup purposes) and sometimes I have to recall it. When I finish a new revision of software I rename the folder (1.1, 1.2, 1.3, etc.) but that never caused problems until this most recent build. I always build the executable and installer on the same machine and in the same tree structure (just the parent folder name is different between verison numbers).
Perhaps, the problem has something to do with moving VIs (and all suport VIs) or renaming the parent folder (1.3, 1.4, etc.) but I have no idea why this would insert a folder in between the .exe and the .vi. I believe this is a bug in the applciation builder.
02-10-2012 06:11 PM