does anyone have a program to convert back to LabVIEW 7.1

[daveTW]

Hello Gerd,
I think you are right, I see myself often despaired colleagues, crying because of lost work of weeks. But then it's good to have some fireman, saving the lost data.
Greets, Dave

[unclebump]

If you need a program to execute the keystrokes for saving as previous, take a look at this program. You could have it create a list of all vi's in a directory and then open them and do the keystrokes. or you could give it a text file with a list of all vi's

http://www.macroexpress.com/

[MattI]

I did do a backup, but I also did a lot of valuable development in LV8 since the backup.

I didn't want to just try LV8 for 1 day & see how it went.  I gave it a good couple weeks of development before throwing in the towel.

[Anthony_Wong]

I agree with unclebump, using a key macro program would be another method that could potentially save you from hours of tedious manual clicking and re-saving.  

[MattI]

How do I handle the fact that the "Save for Previous" actually creates a folder of the VI & all its subVIs?

That means that, at the very least, in order not to create many copies of the same VI, I have to programmatically delete all the subVIs.

Programmatically I can get the "top-level VIs" for the entire library.

But since more than one top-level VI might reference a subVI (very likely -- unless I have zero code re-use!), then there will be many instances of the subVI created -- bad!

And there's no way by key-clicks & mouse-moves I can delete all the subVIs but not the LV7 VI that I intended to save!

[chrisger]

hi there

Mattl, you have to create a Master VI containing ALL top level VIs of your project (including the dynamic ones). when you save this Master VI for previous NO copies of multiple referenced Sub-VIs will be created. And each VI will only be touched ONCE during the concersion process. The "save for previous" of this Master VI will create a directory structure reflecting your current 8.0 structure with no extra copies or directories.

if you use the method of recursivly scanning the directories and llbs to get all Top-Level VIs as described in my previous post you even will convert these VIs that are NOT called by your code (dead code), in contradiction to the conversion of each Top-Level VI manually one by one.

[daveTW]

Hi Mattl,
have a closer look at my previous post, it works on directory- level and makes a copy of your directory- structure. It doesn't care for VI- dependencies. It is inspired by the post of Bob Young to use VI-Server. The problem was to quickly find a way to get a listing of all VIs, especially inside llb's. And this solution doesn't create duplicates of the sub-VIs, so you get a one-by-one copy of the directory-structure.

Try it, it works.
Greets, Dave

Message Edited by daveTW on 06-29-2006 10:46 AM

[MattI]

Dave, this looks pretty incredible.  Unfortunately, the stuff in Diagram.png are LabVIEW VIs that I don't normally use & am totally unfamiliar with. I kind of know where to look for the builtins (somewhere around the "Synchronization VIs" subpalette, I think), but I can't tell what magic you've got on Frames 0 or 2, either.

 Can you attach that VI as well so I can just copy it? 

[daveTW]

Hi Matt,
in LabView click in the menu (you know, like File, Edit, Project ...) of some front panel or diagram-window Tools>>Find VIs on Disk...
This will start this Tool delivered with LV. Then you have to stop its execution by pressing Ctrl+.    (dot)
Now you can access the diagram.
Greets, Dave

[MattI]

Well, here's a program that I came up with instead, based (very) loosely on yours.  It also handles LLBs, which were tricky cuz you gotta use List Directory on them to break them out to VIs which then can be reverted.  And other stuff, such as NOT converting VIs that are pre-8.

The program itself really isn't THAT user-friendly, but maybe somebody else could make use of it.