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 can create the Excel file, using the template, and have it pass the macro to set up for printing through MRE. It runs when opened. But when I try to run it through Report Caster it does not pass the macro, Auto_Open, to the spreadsheet. The template is in baseapp
ON TABLE PCHOLD FORMAT EXL2K TEMPLATE 'TIMESHEET_PRINT_FORMAT_MACRO' SHEETNUMBER 1
The template was created using Excel 2003 (That's another issue. grrr)
Any thoughts on how to get Report Caster to pass the macro in the spreadsheet would be appreciatedThis message has been edited. Last edited by: Kerry,
Reporting Server 7.6.10 Dev. Studio 7.6.8 Windows NT Excel, HTML, PDF
Yes the template contains the macro. I think RC is overridding the ON TABLE PCHOLD statement in the Report Distribution Information section because I can set that to PDF and it will come out as PDF regardless of what the ON TABLE PCHOLD command says. I was hoping to get confirmation of that and maybe a workaround. Looks like the workaround is to send out a separate worksheet with the macro and then teach the users how to run it. Boo hiss.
Reporting Server 7.6.10 Dev. Studio 7.6.8 Windows NT Excel, HTML, PDF