Report Generation Toolkit Error (undefined erro)

[Neil.Pate]

Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.

I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).

Any ideas? 

[muks]

My guess is it might be related to file permission error. Check your permissions

[Neil.Pate]

Muks,

This was the same file that had been written to correctly for two weeks periodically already, so that has me really stumped!

[muks]

Check whether this discussion will help

[Neil.Pate]

Thanks for the link Muks. It is not really the same issue as my app falls over after some time behaving normally. I use the same report generation function multiple times, with very similar inputs, on the same excel file, with no problems whatsoever.

[muks]

---

Thanks for the link Muks. It is not really the same issue as my app falls over after some time behaving normally. I use the same report generation function multiple times, with very similar inputs, on the same excel file, with no problems whatsoever.

---

Do you suspect a corruption?

[muks]

sorted it out?

[parthabe]

---

nrp wrote:

I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.

---

Was it the first time you attempted to write the table to that spreadsheet?

Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.

What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...

[Neil.Pate]

Thanks for the tips!

I haven't exactly sorted it out, but did see a similar error this morning. When I spoke to the operator I asked them about it and they calmly said yes they had closed the spreadsheet that was open! D'oh! So my app was more than likely trying to write to a spreadsheet which it assumed was open (as it had opened it), but in fact was no longer there...

I thought this could be the cause when I first saw the error, and so tried to simulate this kind of failure, but didn't get the same error (or any error actually!). A bit odd really.

Holding thumbs that this error is due to the spreadsheet being closed!!!