Index
2014-04-15 06:00Joerg Arand : Gomonth() Bug?
2014-04-15 06:26Allen : RE: Gomonth() Bug?
2014-04-15 06:29Allen : RE: Gomonth() Bug?
2014-04-15 06:43Ted Roche : Re: Gomonth() Bug?
2014-04-15 07:05Allen : RE: Gomonth() Bug?
2014-04-15 07:53Ted Roche : Re: Gomonth() Bug?
2014-04-15 08:54Laurie Alvey : Re: Gomonth() Bug?
2014-04-15 09:07Ted Roche : Re: Gomonth() Bug?
2014-04-15 09:31AndyHC : Re: Gomonth() Bug?
2014-04-15 09:35Allen : RE: Gomonth() Bug?
Back to top
Gomonth() Bug?

Author: Joerg Arand

Posted: 2014-04-15 06:00:24   Link

Hi all,

on my System (VFP 9.SP2 / Win 7) gomonth() returns for Values <

1753/01/01 an empty date?

Verry strange.

Dr. Joerg Arand

Consultant Neonatologist

Neonatology

Children's Hospital

University Tuebingen

Calwer Str. 7

D-72076 Tuebingen

Tel.+49-(0)7071-2982211

Tel.+49-(0)7071-2980895 (office)

E-mail:Joerg.Arand(AT)med.uni-tuebingen.de

--- StripMime Report -- processed MIME parts ---

multipart/mixed

multipart/alternative

text/plain (text body -- kept)

text/html

---

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/534D2D680200002D00055672@gwia1.zit.med.uni-tuebingen.de

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Joerg Arand
Back to top
RE: Gomonth() Bug?

Author: Allen

Posted: 2014-04-15 06:26:28   Link

I seem to remember mention of when the calendars changed which could have

been about then.

Al

-----Original Message-----

From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Joerg

Arand

Sent: 15 April 2014 13:00

To: profoxtech@leafe.com

Subject: Gomonth() Bug?

Hi all,

on my System (VFP 9.SP2 / Win 7) gomonth() returns for Values <

1753/01/01 an empty date?

Verry strange.

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/008601cf589d$8b62a000$a227e000$@com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Allen
Back to top
RE: Gomonth() Bug?

Author: Allen

Posted: 2014-04-15 06:29:19   Link

http://www.timeanddate.com/calendar/julian-gregorian-switch.html

Note 1752 was change date for UK USA and Canada.

Al

-----Original Message-----

I seem to remember mention of when the calendars changed which could have

been about then.

Al

-----Original Message-----

on my System (VFP 9.SP2 / Win 7) gomonth() returns for Values <

1753/01/01 an empty date?

Verry strange.

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/008701cf589d$f1c2a9d0$d547fd70$@com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Allen
Back to top
Re: Gomonth() Bug?

Author: Ted Roche

Posted: 2014-04-15 06:43:04   Link

Page 23 of the Hacker's Guide to Visual FoxPro 7.0:

[For example, GOMONTH() won't go back farther than the year 1753, the

year after England took on the "Gregorian shift" of the calendar,

jumping 11 days overnight and adding the bizarre leap-year rules of

"every four, except in years ending in 00's, except those divisible by

400."]

Great book, highly recommended. :)

On 04/15/2014 07:29 AM, Allen wrote:

> http://www.timeanddate.com/calendar/julian-gregorian-switch.html

> Note 1752 was change date for UK USA and Canada.

> Al

>

> -----Original Message-----

>

> I seem to remember mention of when the calendars changed which could have

> been about then.

> Al

>

> -----Original Message-----

>

> on my System (VFP 9.SP2 / Win 7) gomonth() returns for Values <

> 1753/01/01 an empty date?

> Verry strange.

>

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/534D1B48.4030603@gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Ted Roche
Back to top
RE: Gomonth() Bug?

Author: Allen

Posted: 2014-04-15 07:05:46   Link

The site I sent says USA and Canada also went at the same year. I would

think the USA going would have more influence on Microsoft than the UK.

Al

-----Original Message-----

Page 23 of the Hacker's Guide to Visual FoxPro 7.0:

[For example, GOMONTH() won't go back farther than the year 1753, the year

after England took on the "Gregorian shift" of the calendar, jumping 11 days

overnight and adding the bizarre leap-year rules of "every four, except in

years ending in 00's, except those divisible by 400."]

Great book, highly recommended. :)

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/008e01cf58a3$09548000$1bfd8000$@com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Allen
Back to top
Re: Gomonth() Bug?

Author: Ted Roche

Posted: 2014-04-15 07:53:12   Link

The USA didn't have that much of an effect in 1753 :)

And I'm pretty sure this call was made in Perrysberg, OH, and not by

Microsoft.

I said "England" in the original article. My apologies to my English

friends, as I'm pretty sure the term should have been "Great Britain."

On 04/15/2014 08:05 AM, Allen wrote:

> The site I sent says USA and Canada also went at the same year. I would

> think the USA going would have more influence on Microsoft than the UK.

> Al

>

> -----Original Message-----

>

> Page 23 of the Hacker's Guide to Visual FoxPro 7.0:

>

> [For example, GOMONTH() won't go back farther than the year 1753, the year

> after England took on the "Gregorian shift" of the calendar, jumping 11 days

> overnight and adding the bizarre leap-year rules of "every four, except in

> years ending in 00's, except those divisible by 400."]

>

> Great book, highly recommended. :)

>

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/534D2BB8.3070801@gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Ted Roche
Back to top
Re: Gomonth() Bug?

Author: Laurie Alvey

Posted: 2014-04-15 08:54:50   Link

Strange goings on. If you issue this in the command window:

d = {^0001/01/01}

? d && correctly displays 01/01/0001

? DATE(1,1,1) && Error!

Laurie

On 15 April 2014 13:53, Ted Roche <tedroche@gmail.com> wrote:

> The USA didn't have that much of an effect in 1753 :)

>

> And I'm pretty sure this call was made in Perrysberg, OH, and not by

> Microsoft.

>

> I said "England" in the original article. My apologies to my English

> friends, as I'm pretty sure the term should have been "Great Britain."

>

>

> On 04/15/2014 08:05 AM, Allen wrote:

> > The site I sent says USA and Canada also went at the same year. I would

> > think the USA going would have more influence on Microsoft than the UK.

> > Al

> >

> > -----Original Message-----

> >

> > Page 23 of the Hacker's Guide to Visual FoxPro 7.0:

> >

> > [For example, GOMONTH() won't go back farther than the year 1753, the

> year

> > after England took on the "Gregorian shift" of the calendar, jumping 11

> days

> > overnight and adding the bizarre leap-year rules of "every four, except

> in

> > years ending in 00's, except those divisible by 400."]

> >

> > Great book, highly recommended. :)

> >

> >

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/CAMvTR9dHTZdAcBjEodezM-WvKdtCZLCWoRyY=PMRV9HJ8XSWfg@mail.gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Laurie Alvey
Back to top
Re: Gomonth() Bug?

Author: Ted Roche

Posted: 2014-04-15 09:07:19   Link

On 04/15/2014 09:54 AM, Laurie Alvey wrote:

> Strange goings on. If you issue this in the command window:

> d = {^0001/01/01}

> ? d && correctly displays 01/01/0001

> ? DATE(1,1,1) && Error!

> Laurie

Laurie:

It's a great idea that dates have some concrete meaning, but the

Christian numbering system has some huge flaws in it, and a lot of

disagreement on what dates mean what. The Gregorian correction of the

1752 brought most of Europe into agreement, but Russian dates didn't

catch up until the Russian Revolution.

Year One is pretty meaningless. Several of our current months (July and

August) didn't even exist until some time later.

FoxPro date math is useful only for the date range of 1753 forward.

--

Ted Roche & Associates, LLC http://www.tedroche.com/

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/534D3D17.7040907@gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Ted Roche
Back to top
Re: Gomonth() Bug?

Author: AndyHC

Posted: 2014-04-15 09:31:01   Link

Not in 1753 <BG>

On 15/04/2014 17:35, Allen wrote:

> The site I sent says USA and Canada also went at the same year. I would

> think the USA going would have more influence on Microsoft than the UK.

> Al

>

> -----Original Message-----

>

> Page 23 of the Hacker's Guide to Visual FoxPro 7.0:

>

> [For example, GOMONTH() won't go back farther than the year 1753, the year

> after England took on the "Gregorian shift" of the calendar, jumping 11 days

> overnight and adding the bizarre leap-year rules of "every four, except in

> years ending in 00's, except those divisible by 400."]

>

> Great book, highly recommended. :)

>

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/534D42A5.7060208@hawthorncottage.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 AndyHC
Back to top
RE: Gomonth() Bug?

Author: Allen

Posted: 2014-04-15 09:35:47   Link

I think it was called Ye old Microsoft telegraph then

Al

-----Original Message-----

From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of AndyHC

Sent: 15 April 2014 16:31

To: profoxtech@leafe.com

Subject: Re: Gomonth() Bug?

Not in 1753 <BG>

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/00b301cf58b7$fddc0cb0$f9942610$@com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2014 Allen