Abnormal Microsoft Office component popup calling Save Report to File VI

[michele.santucci]

When I execute this code:

After the call to Save Report to File VI this dialog pops up:

The Activity Manager shows it as "Microsoft Office Component".

I think the problem comes from the report manipulation made before saving it.. like these:

I will try to disable such calls to see if they are responsible of such behaviour.

Does anybody had similar issues and fixed them in some way?

Best regards,

 Mike

[michele.santucci]

Disabling the graph creation and the following labeling removes the popup but of course I need the graph... 

[Bob_Schor]

A decade agp. I posted a "Revised Generate Excel Report Example" here on the Forum that included putting a Graph in the Worksheet.  Here's (a part) of what it just generated when I ran it:

Granted, it's a minimal plot, but it's a demo, for goodness sake.

Why don't you post your VI (preferably in a version of LabVIEW 2021 or older (as I can't open LabVIEW 2025 (yet)), and enough "supporting VIs and data" that we could "try for ourselves" to make it work?  [Of course, if you are using LabVIEW 2025, and the RGT really is broken, all I can say is that it's been working fine for at least the last 12-or-so years ...

Bob Schor  

[michele.santucci]

---

@Bob_Schor  ha scritto:

Why don't you post your VI (preferably in a version of LabVIEW 2021 or older (as I can't open LabVIEW 2025 (yet)), and enough "supporting VIs and data" that we could "try for ourselves" to make it work?  [Of course, if you are using LabVIEW 2025, and the RGT really is broken, all I can say is that it's been working fine for at least the last 12-or-so years ...

---

You don't have to bother about LabView version since I'm still working on LabView 2013 🙂

The original (buggy version) VI could have some problem loading since it depends on many other external dependencies but here it's. I pointed the view on the inner case where the report is handled .. if it's not hope you can find it (the case is labeled UP CONVERTER...).

I fixed it removing the graph generation trough code and defined it (the graph) into the report template, I set it to be fed by a range of cells where I put some dummy data and then, at runtime, I filled such range with the real measured values;

this removed the chanche of bug and IMHO it is a much cleaner solution since the graph is visibile also into the template and can be modified in layout without the need of editing the code.