does anyone have a program to convert back to LabVIEW 7.1

[MattI]

LabVIEW 8 is just way too slow, too screwed up, too buggy, and crashes too often.  I need to conveniently roll back my entire development directory to LabVIEW 7.1.

The directory is composed of subfolders in a tree structure, also with non-LabVIEW files in it.

I want to have a program that can do a "save as previous" on every VI, LLB, CTL, etc. it finds in a recursive search.of the directory tree.

I've got several thousand VIs that need to be rolled back.

[Ray.R]

You should be able to do this.

Under the Files menu, select "Save with Options", then select "Save Previous".  It should save as 7.1.

...

EDIT

Humm...  I just saw (re-read your post) that you have 1000's of vi's to do.. Humm... So you probably tried the above already.

Let me check if you can create a library then save as previous version... 

Message Edited by JoeLabView on 06-28-2006 09:26 AM

[Bob_Y.]

I think it will not be easy.  Sure, you can use a recursive file listing (as seen here and on LAVA) to get all of the VIs and then open then through VI server and save them for previous (see the LAVA site's scripting section if it is not available without scripting) to a parallel location through VI server/scripting.  But it will create a directory for each with all of its subVIs and that means thousands turn into tens of thousands with many duplicates.  If you can deal with that, you can do it. 

I'd love to post some code, but I don't have the time.

Thanks,
Bob Young

[Ray.R]

---

@BOB Y. wrote:
I think it will not be easy. 

---

That is what I feared...  Unfortunately, you cannot save with options and backward save at the same time..  The only way is to have a script as you mentionned.

JLV

[GerdW]

Hi Mattl,

you just have to save back your backup...

Sorry, could not resist to post this one 🙂

[chrisger]

hi there

what about this:

search all top-level VIs and create a Master-VI that contains all top level VIs as sub-VIs. Then "Save with options" the Master-VI.

to find all Top-Level VIs you could

1. search the directory recursively for vi and ctl, handle LLBs like folders (like mentioned there are such VIs, search here or at LAVA)
2. open the vi with VI server (using the path) and don't close the references to keep them in memory
3. after all VIs and ctls are in memory create a vi and call the property node Application::"All VIs in Memory"
4. loop over the list of all names, open a reference to the vi/ctl using its name and call the property "Callers names"
5. if the array "Callers names" is empty, it is a top level VI (that will include all VIs called dynamically!), or simply use the VI hierachy viewer
6. create a new Master-vi that calls all top level VIs (has to be done manually)

i hope the number of Toplevel-VIs is much smaller than 1000!

[pincpanter]

I made something similar (in principle) from 7.1 to 7.0. I created a vi in the main dir where I dropped all conceivable top level vi's. Saving this big-main vi for previous, the directory structure was preserved. But I only had some tens vis, no LLBs, no extraneous files... and even with this simple scenario I didn't manage to have all needed vis at the first attempt.
Good luck!

Paolo

[daveTW]

Hi Mattl,
my suggestion is this:
in LV 8 click Tools>>Find VIs on Disk, when it is running, press Ctrl+. (dot), it will stop the VI. In the Diagram you insert the attached VI in the way shown below, then run, search for all VIs, then press "Close". This will start the inserted VI which uses the Find- list.


Greets, Dave

P.S. GertW, you are a real Kumpel, ey

Message Edited by daveTW on 06-28-2006 04:50 PM

[AnalogKid2DigitalMan]

Sometimes it escapes me as to why people do not have back-ups of their programming efforts.

[GerdW]

Hello Dave,

yes, sometimes I'm the nice guy...

Back to serious: I have often read in this forum things like: "Do a backup before installing a new LV version or doing a mass compile!" (Btw. doing a backup every week/month is not a bad idea.) And Mattl's question was crying for my answer.
And I have 4 different LV version on my development computer and I (atleast try to) want to have the same user.lib for all versions. It can be a real mess when you change a vi in LV8 and need it in LV6.1...