Filemaker 4.0 v3 is not Y2K compatible 
Author Message
 Filemaker 4.0 v3 is not Y2K compatible

Folks,

I've upgraded to 4.0 to 4.0 v3 to solve some Y2K problems only to find
they were not solved. I don't know if later versions solved it or not and
I'd invite others to test.

1. In a data entry field defined as date, a date entered in the format
y/m/yy with "00" as the year, as in "1/5/00" will be converted by
Filemaker to 1/5/2000. Fine.

2. In the same field, entering "1/5/00" in find mode will find that
record, again interpreting the find string as 1/5/2000. This is as
expected. Searching on "1/5/2000" produces the same result.

3. Also in find mode, entering "<1/6/00" will result in a no records found
error, inconsistant with above. Entering "<1/6/2000" as the search string
will find the above record.

4. Furthermore, using m/d/00 for any search string involving a range of
dates will produce unexpected results (unless no records found was your
expected result). The results will differ from using 4 digit years.

Given all this, I find it very hard to believe that Filemaker cannot be
aware of the problem, and raises some questions about their QA for
shipping this supposed solution out the door.

My question: do the later versions of Filemaker produce more consistant
date treatment?

Thanks,

Steve Firebaugh



Wed, 01 May 2002 03:00:00 GMT
 Filemaker 4.0 v3 is not Y2K compatible

Hi. This is a non-judgmental response made simply to give information.

The FileMaker Y2K document on their website says to always use 4 digit
dates in a Find.

PB

Quote:

> Folks,

> I've upgraded to 4.0 to 4.0 v3 to solve some Y2K problems only to find
> they were not solved. I don't know if later versions solved it or not and
> I'd invite others to test.

> 1. In a data entry field defined as date, a date entered in the format
> y/m/yy with "00" as the year, as in "1/5/00" will be converted by
> Filemaker to 1/5/2000. Fine.

> 2. In the same field, entering "1/5/00" in find mode will find that
> record, again interpreting the find string as 1/5/2000. This is as
> expected. Searching on "1/5/2000" produces the same result.

> 3. Also in find mode, entering "<1/6/00" will result in a no records found
> error, inconsistant with above. Entering "<1/6/2000" as the search string
> will find the above record.

> 4. Furthermore, using m/d/00 for any search string involving a range of
> dates will produce unexpected results (unless no records found was your
> expected result). The results will differ from using 4 digit years.

> Given all this, I find it very hard to believe that Filemaker cannot be
> aware of the problem, and raises some questions about their QA for
> shipping this supposed solution out the door.

> My question: do the later versions of Filemaker produce more consistant
> date treatment?

> Thanks,

> Steve Firebaugh



Fri, 03 May 2002 03:00:00 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. Filemaker Pro V3.0bv5 (WIN95) - fmpro.exe not found

2. Filemaker Pro Server V3 and Filemaker Pro V5.5

3. PC Filemaker Pro v3 file to Mac Filemaker Pro 2.1

4. PC Filemaker Pro v3 file to Mac Filemaker Pro 2.1

5. Is NT 4.0 compatible with Interbase 4.0?

6. Y2K Compliance in VB v3

7. Paradox v3.5 for DOS Y2K compliance

8. Filemaker 4.0 "not enough memory" error

9. Filemaker Pro 4.0 Server or not??

10. Y2K compatible

11. Foxpro 2/2.5/2.6 (Dos) - Y2K compatible?

12. Filemaker V3.x DB connectivity via dialup, Win9x platform


 
Powered by phpBB® Forum Software