LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

We have an application with a very deep directory with 600 vi's on the windows machine and 600 vi's on the PXI. The directory is so complex that we sometimes cannot find vi's, any suggestions, besides, make it smaller.

The person who developed the application has left the company and we now need to maintain it.
0 Kudos
Message 1 of 5
(2,575 Views)
Create subdirectories under the main one. Call them something like A and B ... Then open a command prompt window. Change directory to the main one (cd \main or whatever). Then use the move command to move all files starting with "a" to the A subdirectory (move a*.* A). Do the same with all files starting with "b", moving to B subdirectory, and so on. After they are separated, you may find a way to group them better.
Another method that would take longer is to open a main vi and look at the VI Hierarchy to see which sub-vi's it uses. Create a subfolder and move these sub-vi's and the main into the new subfolder. Do this for all main vi's. This will take a long time but it will organize your vi's in a good manner. If some sub-vi's are used by more than on
e main vi, you might want to create a subfolder called Common or Support or Library or whatever, and move the commonly used sub-vi's there.
Good Luck, this will be tedious and time consuming.
- tbob

Inventor of the WORM Global
0 Kudos
Message 2 of 5
(2,575 Views)
With such large directories you may have a substantial number of unused VIs. If you open the main VI as tbob suggested and then File >> Save with Options... >> Development Distribution, you will get a new library with only the used subVIs. If the program calls VIs by reference, those VIs may not be included. Thsi can help sort out the good from the bad (unused). It does not help with the ugly however.

Lynn
0 Kudos
Message 3 of 5
(2,575 Views)
Bob recommended a very time consuming method of examining each main VI's hierarchy and storing the sub-VIs in common folders. I've attached two utilities to make that easier. DS Hierarchy to file will create a text file you can export to EXCEL to document the VI's calls.

Clean directory will move all files NOT in the VI hierarchy to any directory (folder) you specify. In other words, if you run it on MYMAIN.VI, with instructions to move unused files to folder UNUSED, then after it runs, the only *.VI files remaining in the same folder as MYMAIN will be the ones actually used by MYMAIN.

That should help.
Download All
Message 4 of 5
(2,575 Views)