 | |
#1
 
| |||
| |||
|
date -
11-04-2006
, 06:58 AM
#2
| |||
| |||
|
|
In article <J703h.127405$lT5.28720 (AT) fe2 (DOT) news.blueyonder.co.uk>, Eileen eileen (AT) blyndr (DOT) co.uk> wrote: Does anyone have a clue why a field with dates entered, e.g. 13/12/2004, should all have changed to 100 years earlier, i.e., e.g. 13/12/1904? Because the date was entered as only 13/12/04 instead of the full year? Or because of the field format / validation options? I've had exactly the same thing happen, especially when importing data from an excel spreadsheet file. If the year is input as simply the last two digits (without the century), and then the field format is set to display the century, FileMaker has no way of knowing what century it should be in ang "guesses". If you were to suggest that it would make more sense to "guess" the current century, I'd agree with you, but I'm not one of FileMaker's programmers! I remember having to fix this in a database, and ended up splitting the date field into day, month, and year fields, then recalculating the year by adding 2000 to the 04 etc, values. |
#3
| |||
| |||
|
|
Filemaker (at least V 8) assumes that dates are in a window 70 years before to 30 years after the current date. That should not give any trouble with 04/2004/1904 When converting older versions to newer, all dates were assumed to be historical, so they would get converted to a lower year if they were in the future at all. i.e. converting today (Nov 4, 2006) 11/05/06 would be converted to 11/05/1906. Filemaker makes no prediction about what will happen during conversion if your date is stored in a non-date field such as text. Kent David C. Stone wrote: In article <J703h.127405$lT5.28720 (AT) fe2 (DOT) news.blueyonder.co.uk>, Eileen eileen (AT) blyndr (DOT) co.uk> wrote: Does anyone have a clue why a field with dates entered, e.g. 13/12/2004, should all have changed to 100 years earlier, i.e., e.g. 13/12/1904? Because the date was entered as only 13/12/04 instead of the full year? Or because of the field format / validation options? I've had exactly the same thing happen, especially when importing data from an excel spreadsheet file. If the year is input as simply the last two digits (without the century), and then the field format is set to display the century, FileMaker has no way of knowing what century it should be in ang "guesses". If you were to suggest that it would make more sense to "guess" the current century, I'd agree with you, but I'm not one of FileMaker's programmers! I remember having to fix this in a database, and ended up splitting the date field into day, month, and year fields, then recalculating the year by adding 2000 to the 04 etc, values. |
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.