I've also experienced problems with form fields named 'something_date',
they don't get properly passed as form fields. I think it has something
to do with CF's data input validation algorithm getting confused when it
doesn't find a 'something' field to do the validation on. I've learned
(the hard way) to never name a form field with a _date suffix, except
for validating a date field.
Regards,
Karl Simanonok
Original message:
===========
Date: Sun, 1 Oct 2000 11:13:17 -0400
From: Bud <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Date fields in SQL
Message-ID: <p0432040fb5fd043d4afa@[192.168.0.2]>
On 10/1/00, W Luke penned:
>Hi,
>
>Well it's another Query problem for Will today - the error message is
>telling me it can't find expiry_date field - in Access I've set the
>date/time format to a custom dd-mmm-yy - is this the problem? Here's
the
>code:
For some reason, every now and again I have problems if I name
something underscore date. Try naming expirydate and see if that
helps.
And it wouldn't hurt to refer to today as #createodbcdate(today)#.
But that's probably not the problem.
--
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
