[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Validation of data within widgits
From: |
Jim Busser |
Subject: |
Re: [Gnumed-devel] Validation of data within widgits |
Date: |
Mon, 19 Jul 2004 20:55:26 -0700 |
On Jul 19, 2004, at 8:17 PM, Richard Terry wrote:
Only allowing back-end validation is a huge time-waster...
where for example valid postal codes vary by country, if the validation
were to be done only from the back end, would this mean every country
would need its own version of the table field constraints? Is that in
fact the easiest way to accommodate such differences?
Each and every text box needs to be allocated the
character types allowed to be entered there.
or at least, to be *able* to have allocated to them the character
types...
Presumably a "smart date" function, which would interpret a single
integer as the date of the current month etc, would operate in a client
widget rather than via the back end? The back end would only care that
it is a valid date and, for example in the case of a date of birth,
must not be a date in the future?
Back in my old FoxBASE application -- which I still use for billing --
field formatting support included
! to make all alpha characters upper case
9 to specify a character that must be an integer
A to specify a character that must be a-z, A-Z
X to specify a character that must be a-z, A-Z or an integer
(others...)
is this something for which there is built-in support in
wxpython/wxwidgits?
Re: [Gnumed-devel] Validation of data within widgits, Karsten Hilbert, 2004/07/20