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 firstname.lastname@example.org for further assistance. Reference the community FAQ to learn more about the community.
Jason, which method are you using? There were 2 presented -- one of them was mine and another one had a slightly different twist to it.
Mine was basically using JS functions in the CSS and relative positioning -- the session was called "Freeze Panes". If that rings a bell, you're probably using my method. You could definitely get slower performance if you have relatively large result sets -- and that is especially true if you have a very wide report or if you are using the "column locking" that I demonstrated. Reason being, on column locking, it has to recalc the position of every cell of every column of every row that you have locked -- every time you scroll.
We, without doubt, see slower performance when the rows get higher and higher. However, if all you're doing is locking the titles and headers, typically that performs pretty well for us -- because it's only being calc'ed when you scroll up/down and it usually only a handful of calculations taking place, not one for every row.
On the other hand, there was another method presented by someone from IBI that basically moved the headers outside of the result set -- same basic effect, but a slightly different way to accomplish it. You might want to explore both methods.
I'd be curious to know which method you're using and I'd like to see a glimpse of your CSS if you're using one.
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