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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
We are currently running WF7.6 and are planning an upgrade to WF8.1. I am primarily concerned about any needed changes within the fexes. Should I expect any behaivioral changes from the report execution/results? All of our reports were developed on the 7.6 version.
On a side note, this forum has been extremely helpful and a great resource to this developer that is new to WF! Thanks!
steveThis message has been edited. Last edited by: Kerry,
WebFOCUS 7.6.x FOCUS 7.6.x Windows 2003
Posts: 3 | Location: Richmond, VA | Registered: August 12, 2011
When I upgraded from 7.6.11 to 7.7.02 I had problems with any DECODE that was missing an ELSE. We had a few IF statements without ELSE which is unacceptable code anyway, but it seemed to work on the 7.6.11 system. TEMPDIR was known to cause problems with 7.6 but the code was ignored, in 7.7.02 it gives an error that caused the report caster job to fail. We had a BY statement that used the word LEVEL as a temporary fieldname which fails, I beleive it is now a reserved word. We had a MATCH that failed due to a missing ON TABLE HOLD OLD-OR-NEW, which is also unacceptable coding. I don't know how it was working previously. I am glad we found these issues.
Wow! Nice list Wbackstrom. We've faced a few situations of our own due to code tightening in WF 7.7+.
In addition to your list I can recall:
- Missing a semi-colon in the last line in a DEFINE FILE section was no biggie in previous releases but now fails. - Having a double semi-colon at the end of a DEFINE'd variable or COMPUTE line renders an error.
LP_Steve, look out for any changes related to the iWay adapter to whatever database you have as there could be differences in how CHAR/VARCHAR fields are handled which may give you nasty surprises when creating ALPHA HOLD files.