Project

General

Profile

Bug #10868

Date FILL-IN: INPUT-VALUE attribute is not sensitive to current SESSION:DATE-FORMAT order

Added by Vladimir Tsichevski 8 months ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
16264
version_resolved:
reviewer:
Hynek Cihlar
production:
No
env_name:
topics:

Related issues

Related to User Interface - Bug #7642: Assigning SESSION:DATE-FORMAT has no effect on existing date instances WIP
Related to User Interface - Bug #7515: FILL-IN: editing dates issues WIP

History

#1 Updated by Vladimir Tsichevski 8 months ago

Run the following example:

DEFINE VARIABLE dateField AS DATE VIEW-AS FILL-IN NO-UNDO FORMAT '99/99/99'.
DEFINE FRAME f dateField NO-LABEL.
ENABLE ALL WITH FRAME f.
dateField:SCREEN-VALUE IN FRAME f = '1/2/3'.

SESSION:DATE-FORMAT = 'mdy'.
MESSAGE "mdy" YEAR(dateField:INPUT-VALUE IN FRAME f).

SESSION:DATE-FORMAT = 'ymd'.
MESSAGE "ymd" YEAR(dateField:INPUT-VALUE IN FRAME f).

WAIT-FOR WINDOW-CLOSE OF FRAME f.

In this example, a date-type FILL-IN widget is created and enabled with the format 99/99/99. The screen value is set to a valid date specification (01/02/03). When the INPUT-VALUE attribute is tested for different date component orders:

In OE: The values 2003 and 2001 are printed: the INPUT-VALUE is sensitive to the current date component order.

In FWD: The value 2003 is printed twice: the INPUT-VALUE is not sensitive to the current date component order change.

#2 Updated by Vladimir Tsichevski 8 months ago

  • Related to Bug #7642: Assigning SESSION:DATE-FORMAT has no effect on existing date instances added

#3 Updated by Vladimir Tsichevski 8 months ago

  • Related to Bug #7515: FILL-IN: editing dates issues added

Also available in: Atom PDF