Hi,
The datetime field is showing the wrong information in dbForms...
In SQL it's 2014-12-02 12:14:56.313 on a standard dbform it shows as 02/12/2014 00:14:56
12 Hours out...
Hi,
The datetime field is showing the wrong information in dbForms...
In SQL it's 2014-12-02 12:14:56.313 on a standard dbform it shows as 02/12/2014 00:14:56
12 Hours out...
Martin Pincott
(Member of the SigCj project)
Martin,
New as in this is the first you've noticed it or new as in it didn't happen in the prior 18.0.20 release?
Best regards,
-SWM-
(New as in 18.0.20)
We have customer that reported the issue, we tested it in 17.0, 17.1 (no issue) and this latest version of 18.0.20.15, I believe the issue is also in 18.0.20.10.
Is there something we can do to solve this issue locally?
Thanks
Martin Pincott
(Member of the SigCj project)
In the help for Mask_DateTime_Window
It says hh hour 01-12 should it read 00-23
In the help for Mask_Time
It says h hour 0-9 should it read 0-23
and hh hour 00-09 should it read 00-23
Martin Pincott
(Member of the SigCj project)
I reported an issue with Datetime fields awhile ago. I have my own home-brew time keeping program and I cannot enter a 12 (noon) to 1:00pm time in my program.
So I just go to lunch during that time period
Chuck Atkinson
"No matter how confounding the case, Bob Worsley always finds the quaesitum."
Hi Martin,
I have tested DateTime fields in VDF 17.1 for Data Access Europe. Using datetime masks in VDF 17.1 works fine. In DF 18.0 datetime fields work fine, if you don't use a form_mask.
Using the Form_Mask "dd-mm-yyyy hh:mm" you will lose 12 hours.
The Form_Mask for time in DF 18.0 works better than in VDF 17.1. Using the Form_Mask "hh:mm" shows sometimes a second ":". In DF 18.0 it works really good.
Best regards,
Peter van Mil
Appvantage b.v.
Still not working for me. I removed the mask and I still cannot enter a time from 12:00 (noon) to 12:59
Chuck Atkinson
"No matter how confounding the case, Bob Worsley always finds the quaesitum."
Hi Chuck,
We have other regional settings (European, Dutch). This might make a difference. It works for me with Database Explorer and with a program without a Form_Mask.
Code:Object oCustomer_TestDateTime is a dbForm Entry_Item Customer.TestDateTime Set Location to 84 62 Set Size to 13 70 Set Label to "TestDateTime:" Set Label_Col_Offset to 2 Set Label_Justification_Mode to jMode_Right Set Form_Datatype to Mask_Datetime_Window // Set Form_Mask to "dd-mm-yyyy hh:mm" End_Object
Best regards,
Peter van Mil
Appvantage b.v.
I think I finally figured it out. In my case the date times are in a cjDBGridColumns. But the source of my own problem was wonky validation method I had written giving me false results. I fixed that and changed the psMask to "mm/dd/yyyy hh:mm"
Chuck Atkinson
"No matter how confounding the case, Bob Worsley always finds the quaesitum."
The issue looks to be with the Form_Mask of a dbForm (in my case with a SQL backend).
The above example dbform is bound the MYTABLE.Modified_Datetime column which is defined as a SQL datetime column. To get the issue to occur, the value of the column in the database is between 12:00 and 12:59 (for example 15/12/2014 12:10:00) the time will be displayed as 15/12/2014 00:10Code:Object oModifiedDt_dbForm is a dbForm Entry_Item MYTABLE.Modified_Datetime Set Label to "Modified On" Set Size to 13 85 Set Location to 58 61 Set Form_Datatype to Mask_Datetime_Window Set Form_Mask to "dd/mm/yyyy hh:mm" End_Object // oModifiedDt_dbForm
The above is using standard Dataflex 18.0 (18.0.20.10) code with the SQL connectivity kit version 6.0.0.32 (18.0.20.15 has the same issue)
(NOTE: With the above SAME code and database under Dataflex 17.0 (17.0.38.0) with the SQL connectivity kit version 5.1.0.94 generates the correct output)
I can also confirm that if you remove the Set Form_Mask from the object, the date displays correctly but includes the seconds (which I do not want to display to the user).
Last edited by Andy Roden; 15-Dec-2014 at 04:40 AM.
Andy Roden
Software Developer
That's not a bug, it's an exposed hidden feature. "You don't like it?", Here, let me remove that for you...