Archives of the TeradataForum
Message Posted: Wed, 28 Oct 2015 @ 14:18:06 GMT
The problem is occurring in the third party spreadsheet component we use. SQLA 220.127.116.11 uses version 6.0 of Spread while SQLA 13.0 uses version 4.0. There were many new features added to the spreadsheet between 4.0 and 6.0 so it is quite possible the vendor introduced a bug that they may not even be aware of.
There was a known issue in Spread that occurs only when there are a large number of columns involved. (282 in the original case that was reported) This was originally reported when attempting to save the Answerset to an Excel file but it may be that the vendor has an issue with large numbers of columns in general.
(I'm not sure if this issue has been fixed even in Spread 7.0; which is what we use in SQLA 15.x.)
I will try to generate some test data to duplicate the problem.
However the problem may be specific to the actual data types used in the table, so if you could send me the DDL for the table I would have a better chance of recreating the issue.
If you are using test data, or other non-sensitive data, could you maybe send me an export file containing the test data that would cause the error. (Since the issue is in the spreadsheet Export should work OK.)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|