06-08-2010 03:19 AM
Sorry muks, but could it be, that you accidentally attached the original version?
06-08-2010 04:13 AM
06-08-2010 05:46 AM
06-08-2010 06:42 AM
06-08-2010 06:49 AM
Perfect, many thanks,
\Ulli.
06-08-2010 09:19 AM - edited 06-08-2010 09:20 AM
Ulli27 wrote:Sorry muks, but could it be, that you accidentally attached the original version?
muks wrote:
I mass compiled using 8.0.
The problem is that the files inside the zip are set to read-only. When mass-compiling LabVIEW will not save the VIs if the file is set to read-only. It will also not tell you that it can't save the files because they're read-only. The files you posted before had the same problem. I rad into the same issue when I couldn't understand why the files wouldn't open in LV 9 after compiling in 8.2, and then I looked and saw that the files were read-only, so I had to change that attribute.
06-08-2010 09:25 AM
smercurio_fc wrote:
Ulli27 wrote:Sorry muks, but could it be, that you accidentally attached the original version?
muks wrote:
I mass compiled using 8.0.
The problem is that the files inside the zip are set to read-only. When mass-compiling LabVIEW will not save the VIs if the file is set to read-only. It will also not tell you that it can't save the files because they're read-only. The files you posted before had the same problem. I rad into the same issue when I couldn't understand why the files wouldn't open in LV 9 after compiling in 8.2, and then I looked and saw that the files were read-only, so I had to change that attribute.
Message Edited by smercurio_fc on 06-08-2010 09:20 AM
Didnt know that. ![]()
06-10-2010 08:50 AM
Looking for an upconvert from v5.0 to anything v6.0 or higher (running v9.0.1).
Thanks in advance!
- Joe
06-10-2010 09:17 AM
06-10-2010 09:22 AM
MrSomeone wrote:Looking for an upconvert from v5.0 to anything v6.0 or higher (running v9.0.1).
Thanks in advance!
- Joe
I had upconverted, but I saw that muks posted it. HOWEVER, the problem you're going to have with this is that the VIs use a CIN (which in and of itself is outdated technology), so you will need to reload the code resource. If you don't have that (it wasn't in the zip file), then the code won't work. You should go back to the manufacturer/distributor to find out if they have a new version.