Old Report Generation Toolkit VIs

[GregFreeman]

I have some old VIs I'm modifying and they, themselves, use VIs that used to be in the report generation toolkit but no longer are (Generate Report Get Data to Modify.vi, Generate Report Get Data.vi, show table lines.vi, etc...there are many more). I can grab an old library that I have on another PC that includes these VIs, but then that causes all sorts of conflicts. I have seen lots of things posted that are somewhat like this but no viable solution. Does anyone have one, so that I can load the VIs and not have to redo any code?

[Joel Khan]

Hi,

You should be able to add old VIs as dependencies in a LV project, is this what you have already tried to accomplish? Now if these VIs still are available or a VI in the new version has the same name you will run into issues. Instead of adding the entire library you should try to add specific functions/ VIs. Try saving these VIs individually and creating a library for these specific VIs; after this you can try adding this library to your project.

I am not aware of any other workarounds.

<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE> 

[Ben]

---

@for(imstuck) wrote:

I have some old VIs I'm modifying and they, themselves, use VIs that used to be in the report generation toolkit but no longer are (Generate Report Get Data to Modify.vi, Generate Report Get Data.vi, show table lines.vi, etc...there are many more). I can grab an old library that I have on another PC that includes these VIs, but then that causes all sorts of conflicts. I have seen lots of things posted that are somewhat like this but no viable solution. Does anyone have one, so that I can load the VIs and not have to redo any code?

---

I believe that is yet anothe manifestation of the issue I posted about in this thread where using VI's that are not on the palettes, can sneak up and bite you when LV gets updated.

In the case of the DB and report gen tool kit, the first version re-written in LVOOP did not expose any methods to get at any of the classes agregated by the class (how is that for OOP speach?).

Latter version of those tool kits exposed the ref to the more advanced functions so first make sure you have the lateset and greaset version of the tool kits.

Ben