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.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
For those of you that are seeing performance issues, can you give me an idea of how big of results you're talking?
I think most of us at my org run 1gb of memory or less -- but I've got result sets that are around 20-25 columns wide and approx 250 rows depending on how the users run the report. I definitely see degradation when I get a lot more rows than that, but it does still flow pretty nicely.
Just curious at what threshold you all are seeing the degradation occur.
Production: 7.6.6 WF Server  <=>  7.6.6 WF Client  <=>  7.6.6 Dev Studio Testing: <none> Using MRE & BID.  Connected to MS SQL Server 2005 Output Types: HTML, Excel, PDF
i saw that...i'm clueless but interested,as well. Trav, my lockup happens when i have more than 1 BY field, and i want to lock, say, column 2 or higher. First time out, i locked at column 6, with fixed headers. Very amusing results... A cool, but so-far-unneeded feature, you can lock JUST column 6, and everything else slides underneath it... Silly, but might come in handy someday
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
I should have said too that I am locking ALL headers in my report and column 1 only. I am also locking all report headings and I have 2 BYs I think.
As far as locking a column in the middle of the report -- it does sound fun. Maybe if you wanted to create some sort of "dual pane" effect or something? Can't think of a good application/example at the moment...
Production: 7.6.6 WF Server  <=>  7.6.6 WF Client  <=>  7.6.6 Dev Studio Testing: <none> Using MRE & BID.  Connected to MS SQL Server 2005 Output Types: HTML, Excel, PDF
Well, Frank, I'm the WF admin and every time there is a new release, I take the time to read the SoNF to see if we want to move forward to that release. I'm like a kid in a candy store when it comes to that stuff.
I also support quite a number of business developers who ask me many questions that force me to do research.
Also I've been in the business 40 years and I've just always read manuals. I find it saves you time in the long run.
I just took a look at HFREEZE and I like it. Makes it very easy to implement header/footer/title freezing.
For what it's worth though, the method I use has the ability to freeze entire columns as well -- sort of like what you can do in Excel with freeze panes. Not trying to bash HFREEZE because it's definitely MUCH easier to implement than my CSS stuff!! But if you need to freeze more than just headers, footers, and column titles, you might not be able to use HFREEZE... I like the ability of HFREEZE to set a specific size to scroll, but in some cases you may not know that or may not want a fixed size.
Overall though, it's a great start and I hope they expand it's functionality because it would really make some of my stuff much easier to deal with...
Production: 7.6.6 WF Server  <=>  7.6.6 WF Client  <=>  7.6.6 Dev Studio Testing: <none> Using MRE & BID.  Connected to MS SQL Server 2005 Output Types: HTML, Excel, PDF
Frank, Active Reports has a "VFREEZE" type thing.. but its a bit buggy. it works fine on the car file, but get very fancy in your code, and it starts whacking out...especially if there are subtotal lines..
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
Any obvious way to set the scroll size in HFREEZE? That feature would be VERY useful if so...
Production: 7.6.6 WF Server  <=>  7.6.6 WF Client  <=>  7.6.6 Dev Studio Testing: <none> Using MRE & BID.  Connected to MS SQL Server 2005 Output Types: HTML, Excel, PDF
Trav, yes, the hfreeze sets the size of the scroll window. 4 or 5 is the default, but you can set it to whatever you want. SCROLLHEIGHT i believe is the argument name. Syntax: How to Scroll Report Output Using StyleSheet attributes, you can set aside a scrollable area for HTML report output:
HFREEZE doesn't work with multiple lines of Grand total. Any one has ideal why? Thanks.
TABLE FILE CAR
SUM
SALES OVER
DCOST OVER
COMPUTE NET/D12 = SALES - DCOST;
BY CAR AS ''
ACROSS SEATS AS ''
ON TABLE COLUMN-TOTAL AS 'GRAND TOTAL'
ON TABLE PCHOLD FORMAT HTML
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
UNITS=IN,
SQUEEZE=ON,
ORIENTATION=PORTRAIT,
$
TYPE=REPORT,
GRID=ON,
FONT='ARIAL',
HFREEZE=ON,
SIZE=8,
$
ENDSTYLE
END
This message has been edited. Last edited by: Hua,
Developer Studio 7.6.11 AS400 - V5R4 HTML,PDF,XLS
Posts: 305 | Location: Winnipeg,MB | Registered: May 12, 2008
It's not the multiple grand total lines that cause hfreeze not to work,it's the OVER that prevents the HFREEZE feature from being activated. If you have OVER in place, your column headings are not on top any more, but are located to the left of the column value.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
OVER was the requirement and the totals were aligned properly until I added the HFREEZE. You could be right about the confusion of freezing titles when it goes side by side.
HuaThis message has been edited. Last edited by: Hua,
Developer Studio 7.6.11 AS400 - V5R4 HTML,PDF,XLS
Posts: 305 | Location: Winnipeg,MB | Registered: May 12, 2008