8.2.1 save for previous version

[Gaslight]

It is 8.2.1.  Very interesting that the 2010 which we are ordering will be able to save to 8.0.  However, what can one use it for if the saved VI doesn't look enough like an 8.0 VI?  I suppose it could just be used to verify that no newer functons above 8.0 were used.  You can open it, no broken arrow and run it.  However, it is going to ask you to save.

I would be very interested if someone could save a simple VI with Labview 2009 or 2010 and save it for 8.0 to see if my 8.0 asks me to save it again.  Maybe I'll ask our local rep. to do that for me.

[Dennis_Knutson]

It really does not matter what version you have. What is the exact version the remote location has? Is that 8.0.1?

[smercurio_fc]

I don't think the 8.0/8.0.1 has any effect. I have LabVIEW 8.2 and 8.0 (not 8.0.1), though the latter is on a virtual machine. If I create a simple VI (say an add function with controls and indicator) and back-save it to 8.0, when I open the VI in 8.0 it still asks me to save it. It seems that the way the 8.2 back-compiler works (if that's what's going on) is a little different than the stock compiler in 8.0, so there is no alternative other than opening the VI is "pure" 8.0 and re-saving. Reality sucks sometimes.

[dan_u]

---

@Gaslight wrote:

3-Save for Previous Version will not save only the one VI specified, it saves a bunch of VIs.  I have to pick out only the changed VIs and place them with the unchanged 8.0 VIs.  Is there a way to just save a single changed file as 8.0?

---

You can backsave a single VI programmatically. See my post here.

Hope this helps.

[Gaslight]

I now realize the reason the History never goes to zero is because the VI wants to be saved by Labview 8.0 (the previous version).  If they ever fix this function to really save as previous, the revision problem will go away.