Prev: SQLServer 2005 + VO2Ado + Deadlock
Next: RegisterHotKey(
From: Alessandro Antonangeli on 12 Jan 2010 10:29

> LOCDatum := Today() - 14
> odbGPerson:Visitlast(12.01.10) >= LOCDatum -> always .F.
>
What VisitLast(..) dose? I would check for an EOF or other unwanted
things in this Method


--
Ciao, Alessandro
From: cwb on 12 Jan 2010 11:09
I just checked with all new dates in 2010 :

12.01.2010
12.01.2010
12.01.2010
12.01.1910
12.01.2010

Don´t ask me why one entrie is 1910.
Hopefully all new entries are 2010.

Thank´s for help.

Christian

From: Willie Moore on 12 Jan 2010 15:39
Christian,

If you saved the record sometime before SetEpoch, then the date would have
been saved at 1910.

Regards,
Willie

"cwb" <cwbusse(a)web.de> wrote in message
news:10e628f3-471c-46df-81de-6db6dea64b34(a)j5g2000yqm.googlegroups.com...
> I just checked with all new dates in 2010 :
>
> 12.01.2010
> 12.01.2010
> 12.01.2010
> 12.01.1910
> 12.01.2010
>
> Don´t ask me why one entrie is 1910.
> Hopefully all new entries are 2010.
>
> Thank´s for help.
>
> Christian
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4765 (20100112) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4765 (20100112) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



From: Rene J. Pajaron on 12 Jan 2010 23:38
Johan,

> SetEpoch(Year(Today()) - 50)

I like this one. However, I always show century no matter what.

Rene


On Jan 12, 8:34 pm, Johan Nel <johan....(a)xsinet.co.za> wrote:
> Christian,
>
> As Willie indicated will do the trick, however to keep it in rolling
> form:
>
> SetEpoch(Year(Today()) - 50)
>
> Regards,
>
> Johan Nel
> Pretoria, South Africa.
>
> On Jan 12, 2:16 pm, "Willie Moore" <will...(a)wmconsulting.com> wrote:
>
> > Christian,
>
> > Put the SetEpouch in your start method and you shouldn't have any problems.
> > This is mine: SetEpoch(1960)
>
> > Regards,
> > Willie
>
> > "cwb" <cwbu...(a)web.de> wrote in message
>
> >news:c2212623-430b-4a80-8247-71a4467b2215(a)e37g2000yqn.googlegroups.com....
>
> > > Good morning,
>
> > > I have a problem since 2010 comparing dates.
>
> > > Getting a date from a database ( e.g.  12.01.10 ) is the century 1910
> > > and not 2010.
> > > I tried setting the SetEpoch() function to 2000, 2005,... without any
> > > changes - I always get 1910 !
>
> > > Does someone have any ideas ?
>
> > > Thanks Christian
>
> > > __________ Information from ESET NOD32 Antivirus, version of virus
> > > signature database 4763 (20100112) __________
>
> > > The message was checked by ESET NOD32 Antivirus.
>
> > >http://www.eset.com
>
> > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4763 (20100112) __________
>
> > The message was checked by ESET NOD32 Antivirus.
>
> >http://www.eset.com
>
>

From: Johan Nel on 12 Jan 2010 23:59
Hi Rene,

>> SetEpoch(Year(Today()) - 50)
>
> I like this one. However, I always show century no matter what.

I agree, SET CENTURY ON is the way I also go, however if you have
cluttered screens and can't fit the century in, maybe due to legacy
systems (can still remember the Y2K) issue, it is a good approach to
overcome the issue by having a rolling EPOCH.

Regards,

Johan
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: SQLServer 2005 + VO2Ado + Deadlock
Next: RegisterHotKey(