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 have an Excel template that contains many tabs, and most of the tabs include a chart. A focexec pulls data and sends it to the Excel template, which is then saved out to a client's file server.
There is a macro in the Excel spreadsheet to re-save it to real Excel format instead of wfservlet when it is first opened.
Te problem is that the scale on the x axis of the chart on ***some*** of the tabs is being changed to 2/1/1900. I'm not sure why...This message has been edited. Last edited by: Kerry,
Posts: 64 | Location: Denver | Registered: July 20, 2005
OK, I figured out this one on my own. Turned out that the formatting on the x axis of the charts that changed did not have the "Maximum" box checked on the "Scale" tab, "Time (X) axis scale" "Auto" items.
When I went back and checked the formatting on the x axis on the graph on each tab and corrected this to having the "Maximum" box checked, the problem was solved.
Posts: 64 | Location: Denver | Registered: July 20, 2005