You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear All, I will appreciate Your suggestions on how to come out from the problem reported below.
Using the following method when filling fields and creating records across two different tables, where each table has a TIMESTAMP (NOT NULL) field, the MONTH is swapped with the DAY.
So far, when creating a record for table 1 having the following date "2004-marzo-12 08.48.39" set into aString and another record for table 2 with the same date, then table 1 has the MONTH that's swapped with the DAY if compared with the records in table2.When browsing through the records...table 1 shows its records with the timestamp field having a value of December the 3rd, 2004, while table 2 shows its records with a timestamp set (correctly) to March the 12, 2004.
By the way, I've tryed with all of the possible timestamp formats, as for MM-dd-yyyy, dd-MM-yyyy, ecc. (such formats have been applied across all the table insert functions, but the problem it's still there).
Thanks
The text was updated successfully, but these errors were encountered:
Submitted by: luigi (ricercar)
Assigned to: @carlosga
Attachments:
Bug Firebird.pdf
Dear All, I will appreciate Your suggestions on how to come out from the problem reported below.
Using the following method when filling fields and creating records across two different tables, where each table has a TIMESTAMP (NOT NULL) field, the MONTH is swapped with the DAY.
aString=New System.DateTime(CInt(sYEAR), CInt(sMONTH), CInt(sDAY), CInt(sHOUR), CInt(sMINUTE), CInt(sSECOND)).ToString("yyyy-MMMM-dd hh:mm:ss")
So far, when creating a record for table 1 having the following date "2004-marzo-12 08.48.39" set into aString and another record for table 2 with the same date, then table 1 has the MONTH that's swapped with the DAY if compared with the records in table2.When browsing through the records...table 1 shows its records with the timestamp field having a value of December the 3rd, 2004, while table 2 shows its records with a timestamp set (correctly) to March the 12, 2004.
By the way, I've tryed with all of the possible timestamp formats, as for MM-dd-yyyy, dd-MM-yyyy, ecc. (such formats have been applied across all the table insert functions, but the problem it's still there).
Thanks
The text was updated successfully, but these errors were encountered: