... fine :-) (not exactly correct, but the explanation seems fine) Yes, it looks like the timestamp you provided is in milliseconds since the Unix epoch. To convert a Harbour date variable into a Unix timestamp expressed in milliseconds, you need to follow these steps: Get the date value from the ...
... "Testing " // pad("Testing Gets",40) LOCAL nNum := 0 LOCAL dDat := Date() inicio := 0 Set Century on Set Date To British Set Epoch to 1960 Set Multiple On Set Deleted On DEFINE DIALOG oDlg TITLE "TGet from " + FWDESCRIPTION @ 1, 2 SAY "Text..:" OF oDlg ...
... "Testing " // pad("Testing Gets",40) LOCAL nNum := 0 LOCAL dDat := Date() inicio := 0 Set Century on Set Date To British Set Epoch to 1960 Set Multiple On Set Deleted On DEFINE DIALOG oDlg TITLE "TGet from " + FWDESCRIPTION @ 1, 2 SAY "Text..:" OF oDlg ...
... LOCAL cCad := "Testing " // pad("Testing Gets",40) LOCAL nNum := 0 LOCAL dDat := Date() Set Century on Set Date To British Set Epoch to 1960 Set Multiple On Set Deleted On DEFINE DIALOG oDlg TITLE "TGet from " + FWDESCRIPTION @ 1, 2 SAY "Text..:" OF oDlg ...
Once we know that 1970-01-01 is the epoch date in Unix, it is very easy to write the conversion: function UnixToDateTime( nUnixDate )return HB_STOT( "19700101000000" ) + ( nUnixDate / 24.0 / 3600.0 ) This ...
Once we know that 1970-01-01 is the epoch date in Unix, it is very easy to write the conversion: function UnixToDateTime( nUnixDate )return HB_STOT( "19700101000000" ) + ( nUnixDate / 24.0 / 3600.0 ) This returns ...
... Dear Dutch Please try with ( not with Fw_SetUnicode( .T. ) ), and tell me HB_SETCODEPAGE( "UTF8" ) MYSQL_TinyIntAsLogical( .T. ) SET EPOCH TO year(date())-90 SET DATE FORMAT TO 'DD/MM/YY' SET DATE BRITISH
... filter to SetDeskWallPaper( "Fivewin.bmp" ) SetHandleCount(75) // to open until 75 files at a time set century on set date british set epoch to 1950 set deleted on if MsgGet( ctitle, cText, @cgroep, cBmpfile) cnaam=LEFT(cgroep,10) cchar=SUBSTR(cgroep,12,1) clenght=SUBSTR(cgroep,14,2) ...
Hola al final localicé el fallo del efecto 2020, resulta que está definido dos veces y la segunda vez lo han definido como SET EPCOH TO 1920, y con lo cual este ultimo es el que perdura en todo el programa y ahora como los cojo solamente dos cifras interpreta que es el primer año del siglo, o sea 19...
Tengo definido el set epoch a 1950 con set(5, 1950) , y hasta la fecha siempre me ha funcionado bien. Pero ahora que empezamos a dar fecha de alta del 2020 me hace una cosa rara por ejemplo en un mismo registro introduzco una fecha de ...