Bug #9956
Client crashes in DATE function
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
100%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
15876
version_resolved:
Related issues
History
#1 Updated by Vladimir Tsichevski about 1 year ago
Run the following program:
DEFINE VARIABLE d AS DATE NO-UNDO.
d = DATE("---1131") NO-ERROR.
MESSAGE "After".
In OpenEdge:
- The
DATEfunction fails to parse---1131, raising error 80 ("The month of a date must be from 1 to 12"). - The
NO-ERRORmodifier suppresses the error. - The program continues, displaying the message "After".
In FWD:
- The
DATEfunction attempts to parse---1131, leading to aNumberFormatExceptioninInteger.parseInt(). - The exception is not suppressed, causing the FWD client to abend, and the "After" message is not displayed.
#2 Updated by Vladimir Tsichevski about 1 year ago
- Related to Bug #9906: Incorrect date parsing in FWD DATE(CHARACTER) implementation added
#3 Updated by Vladimir Tsichevski about 1 year ago
The 9906a fixed this issue as well.
#4 Updated by Vladimir Tsichevski about 1 year ago
The same problem occurs is you use SCREEN-VALUE attribute to set FILL-IN value.
#5 Updated by Vladimir Tsichevski 8 months ago
- Status changed from New to Internal Test
Vladimir Tsichevski wrote:
The same problem occurs is you use
SCREEN-VALUEattribute to setFILL-INvalue.
The updated example:
DEFINE VARIABLE d AS DATE NO-UNDO.
d = DATE("---1131") NO-ERROR.
DEFINE FRAME f d.
ENABLE ALL WITH FRAME f.
d:SCREEN-VALUE = "---1131" NO-ERROR.
MESSAGE "After".
Issue resolved after merging branch 9906a. Close this issue.
#6 Updated by Hynek Cihlar 8 months ago
- Status changed from Internal Test to Closed
#7 Updated by Hynek Cihlar 8 months ago
- % Done changed from 0 to 100