Standard report vi problems going from LabVIEW 6 to 2009

[DanRen_IQA]

I have a large application developed in LabVIEW 6 that I am converting to 2009. I have encountered multiple errors and conflicts with the standard report generation vis (not the Report Generation Toolkit for Office). The image below shows the conflict screen, and indicates the nature of the conflicts, but I am not sure how to resolve the problem. 

If I click on one of the selections for NI_Report.lvclass, I get the "File not found" error, shown above. If I highlight the other selection in the conflict, I get a "Needs Update" notice in the lower "Referencing Items" listbox. In both cases, the window indicates that the Item cannot currently be used to resolve the conflict. I also do not know what needs to be done to "Update" the item, as there is no instruction associated with this notice.

As the project is loading, there are also notices that a couple of report vis cannot be found. The "Generate Report Get Data to Modify.vi" and "Generate Report Set Modified Data.vi", which are present in the LabVIEW 6 NIReports.llb library, are not present in the _NIReports.llb folder loaded by LabVIEW 2009. I have seen other forum entries where these two vis are listed as redundant, yet I have no idea what to do to replace them in my project. I have not explicitly called these two vis in any of my project vis. Their calling is coming from other vis in the report vis.

How do I resolve these conflicts when neither item can be used?

Why is the NI_Report.lvclass not found, when it obviously exists in the folder?

How do I update the items showing :Needs Update"?

Why are these two report vis no longer used, and with what do I replace them?

Should I just copy the NIReport.llb from my version 6 install and replace the folder installed by LabVIEW 2009?

What is needed to successfully go from LabVIEW 6 to 2009 with the standard report vis?

Any help with these items would be appreciated.

Dan

[0utlaw]

Hello FreedomDan,

It appears that you have copied at least some of the contents of VI lib along with the source for your project (this is just based on Set Report Orientation visible in your screen capture)- these are conflicting with the VIs shipped with 2009 and are probably the root of your linking issues.  If you've modified these functions, you'll want to resave them with new names.  Otherwise, remove them from the project and mass compile the rest of the project to ensure they're pointing to the report generation VIs shipped with LabVIEW.  This might not take care of everything, but it's a start. 

Regards,

[Philosophe]

Hey Dan,

I have read over your issue and have a few ideas to relay back to you.

Firstly, conversion from LabVIEW 6 to LabVIEW 2009 is not always an easy an process. For some people and their applications, it is an easy conversion and everything transfers nicely. For others, (like what you are experiencing) it can cause a difficult transition. The VIs should convert properly between these two versions, but if any toolkits are being used in the code, then that's where there can be some complications. 

Inbetween LabVIEW 6 and LabVIEW 2009, there were some pretty big changes regarding those VIs. Unfortunately, you may end up having to change a lot of your code because the underlying code for the toolkit was changed during the LabVIEW 8.6 upgrade. One option would be to convert your code from 6 to LabVIEW 8.6, and then upconvert to 2009 after that. I wouldn't rely on this method though becuase the same error may occur, but it is an option.

Another step involves mass comiling the files in LabVIEW 2009. To do this open LabVIEW 2009 and under the main menu, go to Tools»Advanced»Mass Compile and select the directory to compile to and follow the steps for adding the necessary files of the project.

The third option would be to add your code to the Version Conversion forum for an upcoversion @ http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion

Here is some more literature that may be of help as well...

http://digital.ni.com/public.nsf/allkb/986243270824BD188625722C0070CC4B

http://digital.ni.com/public.nsf/allkb/0C7100D6E9E4783B862575070055A499

However, through all the research on this subject, asking colleagues, etc., the truth may be that solution you are looking for may not be there. Meaning, it may be more beneficial to change the code yourself to solve the issue. There have been other customers who have logged an issue on this matter and they mainly ended up re-working some code in the long run. Sorry for the potential bad news.