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.
Also looks as though you have broken your post as well
First obvious mistake is your use statement, totally incorrect, suggest a glance in the manual on the use of USE.
Second thing is that you have SET COMPOUND = OPEN and also ON TABLE PCHOLD FORMAT EXL2K OPEN - these are not normally used together. Again it might be a suggestion to visit the old manual.
I think the main thing to be said on this is that 7.6.5 didn't break your report, you did it yourself in an earlier version
Sort out your code and let us know where you get to then.
T
btw, RickW also pointed out these problems but, due to you not using the code tags to surround your second posting, you can't see it.
RickW's comments were (all that I could recover anyway) -
You have SET COMPOUND = CLOSE and PCHOLD FORMAT EXL2K OPEN - that doesn't look right.
SET COMPOUND = CLOSE
TABLE FILE HOLDDATA_NULL
PRINT
NULL NOPRINT
ON TABLE PCHOLD FORMAT EXL2K OPEN
ON TABLE SET STYLE *<BR>ORIENTATION=LANDSCAPE,
TITLETEXT='.',
This message has been edited. Last edited by: Tony A,
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
7.6.5 did break my report. I have two VMs running. I just recopied it and upgraded to 7.6.5 again, it works on the old but not the new. I know the set compounds does not look right but it works. I have had to use this crazy logic several times to put several reports on one tab, then place several tabs in one excel document.
What happens is called a "tighting of code" and when strange things for some reason worked in a previous release...may not in a newer one. The syntax you are using would cause strange results.
In Focus since 1993. WebFOCUS 7.7.03 Win 2003
Posts: 1903 | Location: San Antonio | Registered: February 28, 2005
Just because it worked on a previous release with incorrect code doesn't mean that it will work on a new release when various syntactical loop holes have been tightened.
If you were to raise this as an info response case the first thing you would need to do would be correct the syntax of your code and try again.
I can see why you resorted to this type of code to produce your multi worksheet workbook, but now that you are using 7.6.5, it might be a time to try out the new compounding tool with your Excel output?
Good luck
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
At least they didn't remove the undocumented quick exit feature. (DevStudio Crash)
this at least is definitely a pain- in fact im boiling with rage at the moment because the code i spent all day amending was just lost when dev studio did its famous
'shut down for no reason with no save prompt' - trick and ive lost hours of work....
and before someone says 'save regularly' there are some instances (ie testing and fixing a multistatement procedure) where you don't want to save every few minutes - i usually save all the time due to my mistrust of dev studios stability but for this report i couldn't due to its complex nature
sorry im ranting but im so annoyed ive had to stop coding for the day- can't face starting all over again today...
Developer Studio 7.64 Win XP Output: mostly HTML, also Excel and PDF
"Never attribute to malice that which can be adequately explained by stupidity." - Heinlein's Razor
Posts: 285 | Location: UK | Registered: October 26, 2007
Alan, when it happens to me its seems to be for no rhyme or reason- yesterday for example i had dev, outlook and an IE window open and when i went from dev to the IE window it just completely shutdown - no warning, it just dissapeared- im waiting to see if anyone else experiences these crashes with 7.6.5 and if so i probably won't upgrade either (and may even go back to 7.6.1 if it doesn't have this problem)...
Developer Studio 7.64 Win XP Output: mostly HTML, also Excel and PDF
"Never attribute to malice that which can be adequately explained by stupidity." - Heinlein's Razor
Posts: 285 | Location: UK | Registered: October 26, 2007