Hi All
We are using TM1 9.0 SP3 U7, and I am running some large reports in Excel 2007.
Whilst I know that both are not compatible with each other, I am hitting a #KEY_ERR when I reach row 65537 which is at the point of Excel 2003 (65536).
Does anyone know what I can do to allow the DBRW formulae to continue working beyond row 65536 ?
I hope that this didn't come across as a daft question !
Thanks
Ajay
Excel 2007 and rows calculated
- Michel Zijlema
- Site Admin
- Posts: 713
- Joined: Wed May 14, 2008 5:22 am
- OLAP Product: TM1, PALO
- Version: both 2.5 and higher
- Excel Version: 2003-2007-2010
- Location: Netherlands
- Contact:
Re: Excel 2007 and rows calculated
Hi Ajay,
I don't think more than 65536 lines are supported.
I'm always wondering what the use of a 'report' (I would call it a dump) with that much lines is, considering that you're connecting to a multi-dimensional database that helps you filtering and focussing on relevant portions of the data.
Michel
I don't think more than 65536 lines are supported.
I'm always wondering what the use of a 'report' (I would call it a dump) with that much lines is, considering that you're connecting to a multi-dimensional database that helps you filtering and focussing on relevant portions of the data.
Michel
-
- Site Admin
- Posts: 1458
- Joined: Wed May 28, 2008 9:09 am
Re: Excel 2007 and rows calculated
Your environment (TM1 9.0/Excel 2007) isn't supported. It's likely that if you moved to 9.4 the problem would go away, though I'm can't be definite, but I agree with Michel - it's probably not a good way to work.
Don't forget you can export a view to a CSV file and load that in.
Don't forget you can export a view to a CSV file and load that in.
-
- MVP
- Posts: 3706
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Excel 2007 and rows calculated
In 9.4 and XL 2007 the row limitation still exists. I'm not sure if it has been addressed in 9.5, I haven't tested it and quite frankly I have no interest in doing so. Other than "compliance" with Excel's new 10^6 row limit I can see no practical benefit whatsoever to upgrading the current limit. My opinion on this is pretty strong and probably much the same as Michel's and David's, namely if anyone specifies a need to pull a "report" with DBRWs over thousands of rows then something seriously wrong is afoot. There are much more efficient ways to dump or extract large volumes of data than by attempting a slice of this size.