Thanks for the thoughtful comments Steven,
On 25/2/2000 10:10 PM, Steven D'Aprano wrote (in part) regarding the
choice between using many separate fields for single-value inputs and a
single, multi-lined field:
>1. Less scripting. Standard behaviour is already built in without any
>extra scripting. Non-standard behaviour (eg down arrow jumps to the next
>field) can be accomplished with very little scripting.
>
>2. Data integrity. There is less chance the user can accidently corrupt
>the data if it is split into seperate fields. Eg there is no way they
>can accidently overtype all four sets of data in one action, which could
>happen in a single field.
>
>3. Easier maintainance of the program. Lets say that one of the fields
>is a person's name. Compare the following data retrievals:
>
>get field "Person Name"
>
>with:
>
>get line 3 of field "Data Entry"
>
>In twelve months time when you are maintaining this program, which one
>is easier to understand?
>
>If you decide to move the name field from line 3 to line 2, how many
>places will you have to edit the script to change 3 to 2? Are you sure
>you haven't missed one? What if you decide to add an extra field? Now
>you have to go through the scripts and edit them all again. It is *much*
>easier to refer to them by name.
>
>None of these issues are insurmountable with the single-field data entry
>method, but it takes extra work to implement it. I'm not sure why you
>think it is neccessary.
>
_________________________________________
Gregory Lypny
Associate Professor of Finance
Concordia University
_________________________________________
"Take chances, make mistakes!"
- Ms Frizzle, The Magic School Bus
This is the MetaCard mailing list.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
