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.
This code is working fine in all reports in my Development environment, but when I move it to a test environment I get this error in one report only.
(FOC015) THE TEST VALUE IS LONGER THAN THE FIELD FORMAT LENGTH: 2010-09-01
0 ERROR AT OR NEAR LINE 46 IN PROCEDURE dm_crf_suppFOCEXEC
(FOC280) COMPARISON BETWEEN COMPUTATIONAL AND ALPHA VALUES IS NOT ALLOWED
If I update my code to
[CODE] WHERE SOME_DT GE DT(&NEWFROMDATE)
It works fine in my test environment for the one report but breaks the the other reports in test and breaks all reports in development environment.
In the database all of the date fields are Oracle DATE format fields.
Any help will be greatly appreciated. CodyThis message has been edited. Last edited by: Cody,
There has to be some difference in the Master files between the 2 environments. If there are multiple masters with the same name, one may be found before another in the APP PATH on one of the servers.
ABT, Thanks so much! I hadn't even considered that there could be another copy of the master files somewhere. It turns out someone else created them and they were getting picked up, which is where the error was. I am still a little confused why only the one report was having the error, but in the end as long as everything is working.