ni excel.lvclass

[Yakup1971]

I create a ni_report and run it for Excel or Word it is always search the ni_excel. lvclass  it does not give an error and it is working I can not find manually the file on my computer. but it was not made before Just I installed the Labview 2024 community edition. How can I solve this?

[Bob_Schor]

You are not expected to directly use the Class wire -- it serves as a "Connector" that encapsulate the "object" you are creating as an Excel Report.  Here is a picture of the RGT main Palette:

The function "Create Report" creates this Object, which is then passed into (top left) and out of (top right) most of the other RGT functions until you end the chain with "Dispose Report" (which closes Excel -- if you want to save a WorkBook, you, of course, need to "Save Report to File" first).

If you are just getting started with using the RGT, a decade ago I posted on the Forum a "Revised "Generate Excel Report" Demo" whichyou can find it by searching the Forum for "Revised Generate Excel Report" and it should pop up before you finish typing "Excel").  It shows how you can generate a report, and illustrates some of the features of the RGT.

Bob Schor

[Yakup1971]

There are two NI examples and Your File screenshot just starts the ranging. But it is the same.I also send my ni_report directory. I think there are missing files I am not sure

[Darren]

This issue has been reported to LabVIEW R&D as Bug 2754118. The search dialog appears when your code runs in the LabVIEW 2024 Q1 editor... you shouldn't see any issues when running the code as a built EXE.

[Bob_Schor]

---

@Darren wrote:

This issue has been reported to LabVIEW R&D as Bug 2754118. The search dialog appears when your code runs in the LabVIEW 2024 Q1 editor... you shouldn't see any issues when running the code as a built EXE.

---

Oops -- if NI updates the RGT (which has run pretty well for at least 15 years) and introduces a bug, then my suggestions won't fix it!  The example code I attached just worked fine on my LabVIEW 2021 installation, and has worked since I published it in the Forum in 2014.

Do you have access to an older version of LabVIEW to try out your code (and my example)?

Bob Schor

[Darren]

Yes, this bug was introduced as a result of some file reorganizations made to the Report Gen Toolkit in LabVIEW 2024 Q1.

[Yakup1971]

I have tried by 21 (32-bit) and it works normally. Is there any way to use this 2021 version of report add-ons in 2024? For example is it possible to copy this file into the 2024.

[Bob_Schor]

The simple answer to "can I open a working VI in LabVIEW 2021 in a newer version of LabVIEW, say LabVIEW 2024 Q1" is "Yes, you can, but when you do that, LabVIEW 2024 Q1 will "change it internally" so it becomes as though it was written in LabVIEW 2024 Q1, so any internal flaws/bugs in LabVIEW 2024 Q1 will still be preventing the code from working in that faulty environment.

[I just reread this post, and realized I forgot to say "So the real answer to your question is "No, it won't work for you"", and edited it to insert this paragraph.]

The "reasonably good news" is this is a known (and serious!) bug that NI knows about.  Did you enable the NI Update Service when you installed LabVIEW?  You might try running that and see if NI has released an update that "fixes the problem".  Otherwise, temporarily downgrade your development environment to LabVIEW 2021 for projects involving the Report Generation Toolkit, and when LabVIEW 2024 Q1 gets fixed, you can migrate it back.

Bob Schor

[Darren · Accepted solution]

You can manually fix the issue in your LabVIEW 2024 Q1 install by replacing the following VI with the one attached to this reply:

[LabVIEW 2024]\vi.lib\Utility\NIReport.llb\Calculate Dynamic Item Absolute Path.vi

Make sure to back up the original file before making this change. This updated VI is the one that will ship with LabVIEW 2024 Q3.

[Bob_Schor]

Hello, @Yakup1971.

     Please try the patch that @Darren posted on the previous reply.  If it fixes the problem (which I hope it does), please mark Darren's response as the "Solution".  There will undoubtedly be other Forum users who find this bug, and having the "answer" tested and verified (by you) will be a big help to them!

Bob Schor