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.
I'm wondering. I know this is not really a WF issue, but it is because of WF that I have this problem. And I can not be the only one. One of you might have a clue...
I have a fex with this output: 1 excel worksheet with 150 lines of data ( approx 25 columns ) 1 excel worksheet with 10000 lines of data ( approx 25 columns ) Together in one file.
It is an xls, but internally it's .xht The file is 8 MB.
When opening this document excel takes 100% CPU for about 5-10 min. on a decent PC. But we've also got end-users using a NC ( like Citrix ). On those tiny machines it takes ages...
When then saved as a real xls or xlsx it's only 2 MB. When reopening in excel again it takes just seconds.
I know "this is the way WF works", but to me it's a bit odd. Finally we've got a fast native tool and a good datawarehouse to deliver the data fast... ...and then you have to wait 15 min before your workstation can open the data.
Anybody else experiencing this? Any help, clues?
Greets, DaveThis message has been edited. Last edited by: Kerry,
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
If so are you programmatically changing any page settings within the excel worksheets?
In case you are, excel opens the printer properties dialog internally for every single page setting that is made. If you have 50 odd setting changes then that can be an awful amount of time if you have one of these latest fancy "does everything but the washing up" printers with their humongous drivers.
If this is your situation then change your default printer to something innocuous like the XPS writer in Windows and see how much difference it makes.
T
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
But it's not an iSeries issue. When prompted I can choose to save the file directly. When I do this to my windows workstation C-drive. It works fine ( and fast ).
When I try to open that local file it also takes very long to open. ( and consume local CPU% ). iSeries is not involved in this proces.
I know there might be work-arounds, but I still feel this is not the way it should work. It's way to slow... ...and if I'm really the only one, I wonder what wrong with my workstation. ( and those of my co-workers ).
WF 7701 might be a solution if EXL07 is really binary.
Lucky me
Plans are we move to 7702 the day after tomorrow
Greets,Dave
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010