How To Build exe for Previous Versions

[Matthew_Kelton]

Coq,

While the LV Runtime won't overwrite his drivers, his program will need the drivers installed to run.  If he is using the same HW driver as the 8.5 programs, he'll probably need to install a leter version of the driver, which may not support 8.5.

For example, the latest version of DAQmx (9.4) does not support 8.5.  In this case, he could use 9.3 which should support 2010 and 8.5.  But it will require installing new device drivers on the machine and then verifying that the odl programs still work.  Depending on the procedures, the whole system may need to be revalidated, which is not a trivial task.

[Coq_Rouge]

---

@Matthew Kelton wrote:

Coq,

While the LV Runtime won't overwrite his drivers, his program will need the drivers installed to run.  If he is using the same HW driver as the 8.5 programs, he'll probably need to install a leter version of the driver, which may not support 8.5.

For example, the latest version of DAQmx (9.4) does not support 8.5.  In this case, he could use 9.3 which should support 2010 and 8.5.  But it will require installing new device drivers on the machine and then verifying that the odl programs still work.  Depending on the procedures, the whole system may need to be revalidated, which is not a trivial task.

---

No need to crisis maximization. You can find Compatibility chart for VISA and DAQ here

http://digital.ni.com/public.nsf/allkb/E7C93038169B6E7686257847004B8B9C

http://digital.ni.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248

And if validation is important. The simplest thing is to stay on a known version and validated version. Also for development.

No need to crisis maximization.

[marc1uk]

Right, thanks for the info. While it seems this could potentially cause problems, it sounds like i'll have fair warning if I'm prompted to update any drivers, and I'll know what to look for and where - thanks to you both.

So far I've tried a couple of new programs made in LV2010 and everything still seems to be working, no driver complaints yet. I suppose until then I'll keep working and make restore points before trying any new programs, in case it does prompt a driver update.

[marc1uk]

..

[Matthew_Kelton]

You probably won't get a message that you need ot update a driver.  You will get a crash, or invalid data, or general program errors.

[JÞB]

---

@marc1uk wrote:

@ Coq Rouge; I'm not sure which drivers are currently in use, but we have quite a few different bits of hardware, so probably a few of each?

---

It's probably safer to use a development envionment with the same version of LabVIEW and device drivers that are installed on the target machine.  Many bugs get fixed in the device drivers (And the IDE) and you may wind up with your deployment not working as expected. 

[marc1uk]

H'mm, I suppose it would never be that simple would it? OK, I'll keep it in mind. I suppose this'll mean re-checking backwards compatibility every time an unexplained error leads me to try a driver update... Hopefully not too often..

[ErnieH]

Kind of makes you want to stick with one version, doesn't it.

[marc1uk]

---

Jeff Bohrer wrote:

It's probably safer to use a development envionment with the same version of LabVIEW and device drivers that are installed on the target machine.  Many bugs get fixed in the device drivers (And the IDE) and you may wind up with your deployment not working as expected.

---

The difficulty there is that there are a lot of current programs developed on an older version, and using an older runtime. I'd rather not have to update all of them with the latest drivers. The only other way would be to rollback to LabView 8.5 for development.

[JÞB]

---

@marc1uk wrote:

---

Jeff Bohrer wrote:

It's probably safer to use a development envionment with the same version of LabVIEW and device drivers that are installed on the target machine.  Many bugs get fixed in the device drivers (And the IDE) and you may wind up with your deployment not working as expected.

---

The difficulty there is that there are a lot of current programs developed on an older version, and using an older runtime. I'd rather not have to update all of them with the latest drivers. The only other way would be to rollback to LabView 8.5 for development.

---

Yes, and rollback the drivers too!  (Because of compaatability and validation requirements some customers are still stuck in LabVIEW 6i.  Kinda makes you want to thing about planning for system upgrade and having a sheduled maintenence plan at the outset of the program! with resources dedicated to continous process improvement