True. For general or public use, this would be a big issue. However,
we use this for an intranet/extranet application, and strictly control
who (and what and where also) can access the http servers. Eventually
the whole mess gets put into Oracle on the back end via a package
procedure (in a datetime field), and if bad data did get past the web
app the update process would bomb as there are checks within the
package for this also.
As with everything, YMMV.
Brgds,
Mike
.
On Tue, 02 Nov 1999 18:36:25 -0800, Jeffrey Baker wrote:
>"Michael J. Miller" wrote:
>>
>> I did this using a JavaScript function that runs before the form is
>> submitted to validate the date locally (in the client, using JavaScript
>> Date objects) before submission. Has the side benefit of giving the
>> user real time feed back as well without a send back to the server ....
>>
>> Brgds,
>>
>> Mike.
>
>You still have to check it on the server side, unless you are willing to
>let bad data slip into your database or wherever.
>
>(Think user with JS turned off or simply submitting via LWP)
>
>-jwb
>--
>Jeffrey W. Baker * [EMAIL PROTECTED]
>Critical Path, Inc. * we handle the world's email * www.cp.net
>415.808.8807
>
