Re: OB Get on Time Field
the same question was posted on the forums a couple of days ago. time values are represented in milliseconds, so a date string, the first part of which is the year 2017, approximates to 2 seconds past midnight. > 2017/05/25 8:32、Tom Dillon via 4D_Tech <4d_tech@lists.4d.com> のメール: > > OB Get($OBGenInfo;"created";Is date) with > But, time always returns ?00:00:02? using: > OB Get($OBGenInfo;"created";Is time) > Or is the time a count down 'till an IPA or maybe steamer lager? ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
OB Get on Time Field
I suppose I'm missing something obvious... Within an object "created":"2014-02-01T09:28:56" OB Get is returning the correct date with: OB Get($OBGenInfo;"created";Is date) with But, time always returns ?00:00:02? using: OB Get($OBGenInfo;"created";Is time) Or is the time a count down 'till an IPA or maybe steamer lager? -- -- Tom Dillon 825 N. 500 W. DataCraft Moab, UT 84532 tomdil...@datacraft-inc.com 720/209-6502 -- Life is a great big canvas; throw all the paint you can at it. --- Danny Kaye -- ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: v13 - Warning Compiler misses syntax error
> Le 24 mai 2017 à 22:14, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > seems like a bug to me > :) v17 feature. non-disclosure agreement. -- Arnaud de Montard ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: v13 - Warning Compiler misses syntax error
seems like a bug to me :) On Wed, 24 May 2017 14:16:32 -0500, Keith Culotta via 4D_Tech wrote: > In v16 interpreted > > C_TEXT($t) > C_POINTER($p1;$p2) > > $t:="A" > $p1:=(->$t) > $p2:=(->$p1) > > ALERT($p2->->) // Error > ALERT(($p2->)->) // A > ALERT(String(Type($p2->->))) // 2 > ALERT(String(Type(($p2->)->))) // 2 > > Type and Alert have different tolerances? > > Keith - CDI > > >> On May 24, 2017, at 1:50 PM, Chip Scheide via 4D_Tech >> <4d_tech@lists.4d.com> wrote: >> >> I accidentally typed the following line of code: >> $0:=(Type($To_Validate->->)=Is Pointer) >> >> Notice anything wrong? >> At least the compiler did not... >> >> Error is : >> ->-> >> >> I haven't checked newer versions >> Chip >> >> >> --- >> Gas is for washing parts >> Alcohol is for drinkin' >> Nitromethane is for racing >> ** >> 4D Internet Users Group (4D iNUG) >> FAQ: http://lists.4d.com/faqnug.html >> Archive: http://lists.4d.com/archives.html >> Options: http://lists.4d.com/mailman/options/4d_tech >> Unsub: mailto:4d_tech-unsubscr...@lists.4d.com >> ** > > ** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ** --- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
RE: What would cause PROCESS 4D TAGS to "not work" - SOLVED
Thanks to all who responded. Tim Penner and Charles Miller - It was the compatibility setting "Use 4DVAR Comments instead of Brackets" This explains why a new database worked correctly. You can not even access the option there. Since the structure has been through multiple versions of 4D this option was turned off. I thought that I had been through that check and obviously I had not. Edgar Hammond ehamm...@questinformation.com Quest Information Systems ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: v13 - Warning Compiler misses syntax error
In v16 interpreted C_TEXT($t) C_POINTER($p1;$p2) $t:="A" $p1:=(->$t) $p2:=(->$p1) ALERT($p2->->) // Error ALERT(($p2->)->) // A ALERT(String(Type($p2->->))) // 2 ALERT(String(Type(($p2->)->))) // 2 Type and Alert have different tolerances? Keith - CDI > On May 24, 2017, at 1:50 PM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I accidentally typed the following line of code: > $0:=(Type($To_Validate->->)=Is Pointer) > > Notice anything wrong? > At least the compiler did not... > > Error is : > ->-> > > I haven't checked newer versions > Chip > > > --- > Gas is for washing parts > Alcohol is for drinkin' > Nitromethane is for racing > ** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ** ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **