Project Dependency Conflicts NI_ReportGeneration toolkit

[NateG901]

I have gotten a new computer at work that required a reinstall of LabVIEW. After installation of LabVIEW on the new computer, there appears to be a dependency issue with the NI_ReportGeneration toolkit in my project.

The project/VI operates fine otherwise and the path of that error looks like total junk (I dont even have a D:\). But this is blocking me from being able to build a standalone application or anything as well.

Is it possible for me to remove this dependency somehow?

I'm using LabVIEW 2021 SP1 if it matters.

[Bob_Schor]

Well, you didn't share the Error Message, you almost didn't share the LabVIEW Version you are using (but failed to share the "Bitness"), you didn't mention what version of Microsoft Office you are using (or even if you have Office).  

Some other questions:

• If you run a simple program (such as my favorite, the "Revised Report Generation Example" that you can find by doing a Search on this Forum) that tests the RGT's ability to generate an Excel report, does it work?
• Can you build an Executable with that simple Example program?  Does it still work?  If it gives you an Error, what is the Error?

I just realized I should probably run the same two tests myself on the Laptop I'm using right now.  I'm mostly running LabVIEW 2019 SP1 (32-bit), but I also have LabVIEW 2021 SP1 (32-bit) installed, so I'll try that first.

Bob Schor

[Bob_Schor]

Oops, I got the name of the Post wrong (but you should still probably find it).  Try "Revised Generate Excel Report Example", or just type "Revised" and wait 3 seconds.

Bob Schor

[NateG901]

I had thought I attached a photo of the error but it appears its gone. Sorry about that, trying again.

-64bit

-Office 365, with this particular verison I am unsure how to get more information on it, its a locked down corporate version. I was not sure that this would matter as the issue seems related to the dependency and not office itself (it works fine, the excel report prints out as expected, but it just has this dependency error).

[Bob_Schor]

Aha!  You probably have a problem with your Build Spec.

But first, I just ran the test that I recommended to you (and I still recommend it, as it will tell you if the difference is something different between our basic PCs (I'm running Microsoft Office 365, not my choice, but Corporate and LabVIEW 32-bit) or our different builds (mine is dirt simple -- I only specify the Top Level VI, nothing under "Always Included", and the RGT is mentioned nowhere in the Build Spec).

The Good News -- it ran just fine.  The Bad News -- the idiot who created the Demo "cleverly" built the name for the Report by stripping the Path from "Current VI's Path" when building the name of the Excel File.  Replacing this with "Default Data Directory" fixed that problem, and it also generated an excellent Report.  Grrrr.

If you want advice on your Build Spec, take a Snip of your Source Files page in your Build Spec and show it to us.  Here's mine ...

Bob Schor

[DerekZhang]

Hi, I got the same problem with you, the conflict path is even not exist in my computer.

Close the dependency warning window, the program can run through well, but it will fail when build up a exe application.(I have tried to rebuild the program in a new project, but the warning still arise...)

My LabVIEW version is 2021Sp 64bit.