Excel Report tool driver in LABWINDOWS/CVI

[Dhemaius]

I want to report another bug in the Excel Report tool driver. This time it is in the function

"ExcelRpt_WriteDataFromTableControl"

which I found that it doesn't take care of the unsigned int data type. What happen is the function leaves the cell blank and pass to the next cell.

My questions are, are there many reported bugs concerning Excel Report, and if so, will NI consider doing any documentation on this?

[Chris Matthews]

We have seen a couple of issues with it that were concerning resource management (releasing ActiveX handles). I'm not sure if this particular issue has been addressed yet, so I will pass it on to our developers.

Best Regards,

Chris Matthews
National Instruments

[Eric Meyer]

I have confirmed this issue in an example project which I have passed to Research and Development requesting a fix. There have been other issues reported with the Excel Report instrument driver, which will be addressed in the next release of LabWindows/CVI. Unfortunately, the release date is not set yet.

It seems that unsigned short int's also fail.

If you would like further information, or would like your contact information to be added to the Corrective Action Request (ID: 2IQ9RRHX) for this issue, please go to www.ni.com/ask and create a service request. An applications engineer can then further assist you.

regards,
Eric

Applications Engineering
National Instruments

[Chris Matthews]

In thinking more about this, I have some more info for you. Obviously, we are using ActiveX to talk to Excel with the Excel Report tool. unsigned int is NOT an ActiveX data type, therefore it is impossible to send an unsigned int to Excel. Our report tool should be reporting this as an error to you and trying to convert it to an int (if the uint is not out of int range) which we will fix. Even after the fix though, you won't really be passing unsigned int values to Excel since it isn't a supported data type in ActiveX.

I would just convert your values to int before sending them to Excel, since that is the only option anyway and is what we would be doing in the Excel Report tool.

Good luck,

Chris Matthews
National Instruments

[aperez]

Dhemaius,

I see what you mean. I was able to see the part of the code that's missing the constants VAL_UNSIGNED_SHORT_INTEGER, VAL_UNSIGNED_INTEGER and VAL_UNSIGNED_CHAR.
To tell you the truth, there are only a few reported bugs with the Excel Report driver. All of them have minor workarounds (such as this one) and have been documented and fixed. I will report this to our developers.
Thanks for the feedback!

Azucena
NI