As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
It is difficult to imagine a situation where displaying 100,000+ records would be useful. Is it possible to group the records in some way to produce a summary report? Then you could provide drill-down links to the detail records for each group.
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
For Excel, you can define a field that the program uses to break to a new worksheet in the workbook after every specified number of rows:
DEFINE FILE GGORDER
CTR1/P6 WITH ORDER_NUMBER = IF CTR1 EQ 100 THEN 1 ELSE CTR1 + 1;
CTR2/P6 WITH ORDER_NUMBER = IF CTR1 LT 100 THEN CTR2 ELSE CTR2 + 1;
TABLE FILE GGORDER
BY CTR2 NOPRINT
ON CTR2 PAGE-BREAK
ON TABLE PCHOLD FORMAT EXL2K BYTOC
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
I'm with Dan on this one. If you're displaying that many records, you should be using a specific tool as well. Using any old tool is NOT the correct approach. The reason that the browser hangs is because of available memory. You'll have the same problem with Notepad. It's not the application's fault, but limited to available memory. The OLD versions of Excel had the 64K limit on file size. I believe that the Office 2000 or possibly 2003 versions gave you a limit around 2 million. IMHO, if you're wanting to "display" more than that you should be using a database, not a viewer.
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
User want the report containing in One go it self, So, Drill down approach fails.
Not putting too fine a point on this but, your users don't understand the problems they are demanding and it should be you who explains to them why their request is flawed. Report design and development should be a two way effort - the users demands and the developers knowledge of how those demands would be handled by the equipment to be used.
As you have found out, HTML output is difficult because of the number of records. This will have different effects on different machines depending upon the actual memory they have installed and available. Many end user Windows based machines will have around 1 Gb of memory and will struggle badly with 100,000 records (for those that haven't Googled it, Lakh is the Indian term for 100,000).
As you say, Excel (pre 2007) will only handle 64K records, and Excel 2003 also has a memory limit of around 2Gb anyway.
To me the solution is clear, educate your users so that their demands take account of the equipment to which they are restricted. Also ensure that you know what their equipment can handle and guide them accordingly.
There are few things worse than a demanding end user whose demands outweigh their equipments abilities.
p.s. don't forget to take into account the width of the report as well. IE might handle 100,00 records of only 8 chars width but will struglle with 100,000 of 800 chars wide.
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004