Okay, got a good one for you
I'm allowing Users to log in and update their details. One field is Date of Birth
(DOB). This is stored as one date field in Filemaker, but to try and enforce some kind
of input scheme, I'm planning to use 3 input fields:
DOB_dd / DOB_mm / DOB_yy (note UK dd/mm/yy scheme)
This works fine - on first registration I take the ARGs and load a Variable (DOB) like
this:
value=<@ARG DOB_dd>/<@ARG DOB_mm>/<@ARG DOB_yy>
The variable is then punched into the database and all's well
Here's where it gets tricky: when I reload User Variables to edit the data, I get a
date like dd/mm/yyyy out of Filemaker - it defaults all 2-digit date inputs to
dd/mm/19yy
This date loads OK into a variable DOB, and I load a formatted version of this
variable into three input fields:
<INPUT NAME="DOB_dd" SIZE="4" MAXLENGTH="2" VALUE='<@FORMAT STR="<@VAR NAME='DOB'
SCOPE='User'>" FORMAT="datetime:%d">'> /
<INPUT NAME="DOB_mm" SIZE="4" MAXLENGTH="2" VALUE='<@FORMAT STR="<@VAR NAME='DOB'
SCOPE='User'>" FORMAT="datetime:%m">'> /
<INPUT NAME="DOB_yy" SIZE="4" MAXLENGTH="2" VALUE='<@FORMAT STR="<@VAR NAME='DOB'
SCOPE='User'>" FORMAT="datetime:%y">'>
These input fields are preloaded correctly with the right date in dd/mm/yy
configuration, but when I try to update the date things go screwy - I tend to get a
year value of -42 when the correct date is 1958
This sounds like a classic Y2K vs 2-digit year problem. As this approach isn't written
in stone, before it goes live can anyone help me solve the problem or suggest a
better/simpler solution?
tango 3.63.002, Webstar 4.4, Mac OS 9.1, Filemaker 4.1v3 on server
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
