Re: yyyymmdd date format import
- From: d-42 <db.porsche@xxxxxxxxx>
- Date: Mon, 12 May 2008 14:22:41 -0700 (PDT)
On May 12, 9:57 am, d.kinn...@xxxxxxxxxxxxx wrote:
I am in the process of moving a database from Access to Filemaker. One
field is giving me some problems working out the best way to handle
it. The date fields have the format of yyyymmdd with "99999999"
representing "forever" or "does not expire".
I can import the dates into the new data base with a calculation to
change to the fm date format BUT how can I handle the "forever" dates?
OR would it be best to define all of these as numbers with some kind
of calculation for input validation?
'Forever' is not a valid date, and 'magic numbers' that mean something
special are generally bad design. The 'correct' way to handle it is
with 2 fields. An number field acting like a boolean (true/false) for
'does not expire'.
Alternatively you can define a text field, and have it store 'forever'
or a date as text, but it doesn't really get you anywhere useful,
because you will have to apply conversions to work with the date; e.g.
to perform finds, etc.
If you want 'forever' or a date to appear in a single 'place' on
layouts, you just define an unstored text calc... if(doesnotexpire =
1,"forever", expirydatefield)
-cheers,
Dave
.
- Follow-Ups:
- Re: yyyymmdd date format import
- From: Kevin Audleman
- Re: yyyymmdd date format import
- References:
- yyyymmdd date format import
- From: d . kinnard
- yyyymmdd date format import
- Prev by Date: Select folder/path
- Next by Date: Re: Select folder/path
- Previous by thread: yyyymmdd date format import
- Next by thread: Re: yyyymmdd date format import
- Index(es):
Relevant Pages
|