Find Missing Items - export list to spreadsheet?

[cycleguy]

I inherited a LabVIEW project that has a whole lot of missing items (vis, controls, lvlibs, etc...).  From the project I can display a list of the missing items, but I cannot figure out how to export the list to something useful for sorting and sharing.  Right clicking or trying to select multiple items in the list doesn't work.  Is there a way to do this?  I have attached a printscreen of the missing items window in case it helps...

Thanks.

[cycleguy]

Okay, I figured out how to get the name and the path of the missing items programmatically.  I didn't see where to access the property to display the location in the project, but at least I have a good start now.  See the attached vi for what I ended up doing.  I could have saved the array to file in the vi, but I chose to just export to Excel from the front panel. 

[Hooovahh]

I see a bunch of User.lib stuff.  I'm guessing someone had a reuse library installed.  Do you have access to the development machine?  You can probably get many of the files from there.

You can also potentially extract the VIs from the EXE, but this will be a VI with no block diagram, and likely no front panel.  It will also be a VI that can only be ran on the version of LabVIEW that EXE was made for.  My advice is to get in contact with the original developer if you can't find what you need.

[cycleguy]

Yes, I am in contact with the original developer.  I am hoping to get all of the libraries since I am updating the application to LV2014 and making some modifications for our customer.  I was just frustrated with the native LabVIEW project tool for viewing the missing and/or conflicting items since it doesn't seem to be able to sort or export to a shareable format.  Now that I was able to programmatically get the name and path of the missing items, I can send him a spreadsheet to help me resolve things.

I didn't know you could potentially extract the VIs from an EXE - I'll have to check that out sometime.

Cheers!

[Hooovahh]

---

cycleguy wrote: 

I didn't know you could potentially extract the VIs from an EXE - I'll have to check that out sometime.

---

Yes you generally can do this, but the technique changes with some versions of LabVIEW because it can be seen as a security risk.  But realistically it is more like extracting part of a binary application.  After extraction the VI has no documentation, no icon, and just works like a DLL with some inputs and you get some outputs with no way of seeing the code that goes on inside it.  It also cannot be recompiled for other versions of LabVIEW so again it isn't all that useful.