Hello,
A.) please do not question the origin of following problem
B.) When using "Export as ASCII Data" on a cube with 250 dimensions (each having 26 elements + 1topconsolidation) (please refer to statement A now!) the dialog-box opens as expected. Since I'm not crazy (A) I skip consolidations, rules and blanks. Out of the enormous number of possible cells (somewhere in 10^353 if I'm not mistaken) only the cells with the same index in each dimension have a value (as they follow the scheme DIM001A-DIM250Z they have the ASCII Value of the letter on the corresponding intersection - so on DIM001A-DIM250A is 65) - so it is a very, very sparse cube.
Anyways, after hitting the button for the export a buffer overrun will occur on client side and I need an answer - why does this happen (please refer to A), if you can prevent the overrun - how?
Since TM1 supports 256 dimensions this has to be
1 - some kind of bad setting on client side
2 - 1 but on server (like ignore stupid requests?)
3 - a bug
I'm sure everyone here tried to build a cube that big, right? ;D
thanks,
Lukas
ps.: I hate the "Save" button on this forum, I really, really do...
Export as ASCII Data --> Buffer overrun
- Steve Rowe
- Site Admin
- Posts: 2410
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Export as ASCII Data --> Buffer overrun
Sounds like an interesting problem.....
I doubt if anyone has ever tried this and it's very unlikely that Applix have tested it.
Suggest you try using ASCIIOutput in a TI process.
Oh and I hate the save button too, I'm constantly saving posts as drafts...
Cheers,
I doubt if anyone has ever tried this and it's very unlikely that Applix have tested it.
Suggest you try using ASCIIOutput in a TI process.
Oh and I hate the save button too, I'm constantly saving posts as drafts...
Cheers,
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- Regular Participant
- Posts: 152
- Joined: Fri May 23, 2008 12:08 am
- OLAP Product: TM1 CX
- Version: 9.5 9.4.1 9.1.4 9.0 8.4
- Excel Version: 2003 2007
- Location: Melbourne, Australia
- Contact:
Re: Export as ASCII Data --> Buffer overrun
I hate the save button too for what its worth ....
I agree with Steve, I think you would be unique in having encountered this problem. The structure you describe is not exactly typical for a TM1 model.
Yikes! I wouldn't be wanting to have to write the CellGetN or CellGetS statements for a 250 dim cube.Suggest you try using ASCIIOutput in a TI process.
I agree with Steve, I think you would be unique in having encountered this problem. The structure you describe is not exactly typical for a TM1 model.
- Eric
- MVP
- Posts: 373
- Joined: Wed May 14, 2008 1:21 pm
- OLAP Product: TM1
- Version: 9.4
- Excel Version: 2003
- Location: Chicago, IL USA
Re: Export as ASCII Data --> Buffer overrun
I briefly recall a post office in Europe having cubes of 250+ dims..... I will do some digging to see if I can find a name and see if they can offer any help.
Regards,
Eric
Blog: http://tm1-tipz.blogspot.com
Articles: http://www.google.com/reader/shared/use ... /label/TM1
Production: 32 bit 9.0 SP2, Windows 2000 Advanced Server. Web: 32 bit 9.0 SP2, Windows 2000 Server. Excel 2003
Eric
Blog: http://tm1-tipz.blogspot.com
Articles: http://www.google.com/reader/shared/use ... /label/TM1
Production: 32 bit 9.0 SP2, Windows 2000 Advanced Server. Web: 32 bit 9.0 SP2, Windows 2000 Server. Excel 2003
- Steve Rowe
- Site Admin
- Posts: 2410
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Export as ASCII Data --> Buffer overrun
Yeah I don't think it would be fun building up the statements in TI, but I think you could use text functions in Excel to write develop them.
Cheers
Cheers
Technical Director
www.infocat.co.uk
www.infocat.co.uk