Report generation tool, saving data

[Hulk1978]

I made now a complete fresh installation of LV.

Attached is my configuration.

Additional is a VI where i marked which part is working and not.

I´m really suprised that i´m alone with my problem 😞

Till now it´s a little bit waste of money.

[GerdW]

Hallo Hulk,

---

@Hulk1978 wrote:

Additional is a VI where i marked which part is working and not.

---

The "working" part is written to a file where you specify the filepath.

The "non working" part does not work, because the file isn't saved anywhere in your code. When you dig into the RGT functions you notice the "save changes" input is wired to the "Close" parameter of the Workbook.Close method…

[Hulk1978]

Dear Gerd,

thank you very much for your feedback.

Your explaining sounds logical....But i cannot practical follow.

I cannot understand how failure happen. To avoid individual failure i reinstall all new.(complete installation of Labview)

What can i do to change? How i´m getting a functionable version?

Again, it´s a fresh installation.

I suppose the problem is not only related to "excel"? 

[GerdW]

Hi Hulk,

where does the VI in this snippet comes from?

Is it taken from the RGT library/classes?

It is not allowed to unbundle the class' private data, most probably because it is not a member of the class…

[Hulk1978]

The snippet is from inside the save.vi.

I didn't Change anything before or later.

I tried to understand the post before from you. It was to cryptic for me.

Slowly i'm desperate....

Don't know reason for such huge trouble

[GerdW]

Hi Hulk,

which LabVIEW version? Which bitness?

Which MS Office version? Which bitness?

---

@Hulk1978 wrote:

The snippet is from inside the save.vi.

---

Which "save.vi"?

[Hulk1978]

Labview 2016

RGT 2016

Office 365 

Windows 10

Labview i fresh installed today morning.

---

I'm talking about the Protocoll  save.vi

This is the reason about failure.

Please Take a look to the complete Threads.

The identic vi is running by the other Guy.

Open Protocoll, add Data, save, Close....

Something is really wrong at me.

Additional the labview example with the template doesn't start with similar failure.

Best regards

[GerdW · Accepted solution]

Hi Hulk,

RGT2016 was NOT made for Office365, see here!

You could have discussed this with NI sales before ordering the toolkit…

(I will/could have the same problems in two weeks when my companies IT department rolls out the "upgrade" to Office365.)

---

@Hulk1978 wrote:

I'm talking about the Protocoll  save.vi

Please Take a look to the complete Threads. The identic vi is running by the other Guy.

---

Where does this "Protocoll  save.vi" comes from? NI doesn't provide a VI with two lowercase L and two spaces in its name…

I rushed through this complete thread and didn't find this "other Guy" nor this "Protocoll  save" VI you are talking about…

[Hulk1978]

Good morning Gerd,

my Office 365 was coming later then my labview. But till now i never used RTG. It will be helpfully to know if this is really the reason.

Opening and writing to excel is still functionable. (German "Excel Easy table.vi) to find at Protokolle/Excel Specific.

But the trouble VI i´m talking is called (GERMAN) "Prot. speichern), to find at "Protokolle"

Thank you

[Hulk1978]

Hey Guys,

I tested again with following solution:

Reason seems to be office365 and LV2016 with RGT2016...no friends.

When this Standard vi for saving ist started, it fails. Changing in same Session to HTML protocol type you will have the same issue. Restart of labview helps.

I deinstalled the Report Tool now. I don't like Excel anyway. For me CSV is enough and for charts and formulas i have labview too.

Thank you.