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 built a date/time field and I am trying to compare it to a date defined in FOCUS. I am getting errors!?!?
-*
-SET &BEG1 = '20081201';
-SET &END1 = '20081231';
-*
-SET &BEGDT = EDIT(20081201,'9999/99/99') |''| '00:00:00';
-SET &ENDDT = EDIT(20081231,'9999/99/99') |''| '23:59:59';
-*
-TYPE 2008/12/01 00:00:00 . . . . . . 2008/12/31 23:59:59
2008/12/01 00:00:00 . . . . . . 2008/12/31 23:59:59
-*
-*
JOIN CLEAR *
-* Here, I have a WHOLE BUNCH of JOINs
-RUN
-*
TABLE FILE WHATEVER
BY RESULT_DATE
WHERE RESULT_DATE GE '2008/12/01 00:00:00' LE '2008/12/31 23:59:59';
IF RECORDLIMIT EQ 15
END
-RUN
-EXIT
0 ERROR AT OR NEAR LINE 33 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC015) THE TEST VALUE IS LONGER THAN THE FIELD FORMAT LENGTH: 2008/12/01
00:00:00
0 ERROR AT OR NEAR LINE 33 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC280) COMPARISON BETWEEN COMPUTATIONAL AND ALPHA VALUES IS NOT ALLOWED
(FOC009) INCOMPLETE REQUEST STATEMENT
BYPASSING TO END OF COMMAND
-*
-SET &BEG1 = '20081201';
-SET &END1 = '20081231';
-*
-SET &BEGDT = EDIT(20081201,'9999/99/99') |''| '00:00:00';
-SET &ENDDT = EDIT(20081231,'9999/99/99') |''| '23:59:59';
-*
-TYPE 2008/12/01 00:00:00 . . . . . . 2008/12/31 23:59:59
2008/12/01 00:00:00 . . . . . . 2008/12/31 23:59:59
-*
-*
JOIN CLEAR *
-* Here, I have a WHOLE BUNCH of JOINs
-RUN
-*
TABLE FILE WHATEVER
BY RESULT_DATE
WHERE RESULT_DATE GE '2008/12/01 00:00:00' LE '2008/12/31 23:59:59';
IF RECORDLIMIT EQ 15
END
-RUN
-EXIT
0 ERROR AT OR NEAR LINE 33 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC015) THE TEST VALUE IS LONGER THAN THE FIELD FORMAT LENGTH: 2008/12/01
00:00:00
0 ERROR AT OR NEAR LINE 33 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC280) COMPARISON BETWEEN COMPUTATIONAL AND ALPHA VALUES IS NOT ALLOWED
(FOC009) INCOMPLETE REQUEST STATEMENT
BYPASSING TO END OF COMMAND
Below is what just a report of the RESULT_DATE field.
-*
TABLE FILE WHATEVER
BY RESULT_DATE
IF RECORDLIMIT EQ 3
END
-RUN
....
Here is a little report:
RESULT_DATE
2000/03/28 00:00:00
2000/03/29 00:00:00
2000/03/30 00:00:00
In the WHATEVER Master File, RESULT_DATE is defined: FIELDNAME=RESULT_DATE, ALIAS=RESULT_DATE, USAGE=HYYMDS, ACTUAL=HYYMDS, MISSING=ON, $
Any Ideas??? This message has been edited. Last edited by: Kerry,
WHERE RESULT_DATE GE DT('2008/12/01 00:00:00') AND RESULT_DATE LE DT('2008/12/31 23:59:59');
Thank you both for your suggestions. They are both workable, but I liked using the true date/time field, and I have always LOVED coding in Dialogue Manager!