Form Design Advice - Mailing list pgsql-novice

From
Subject Form Design Advice
Date
Msg-id 20050301203930.92797.qmail@web52406.mail.yahoo.com
Whole thread Raw
In response to Please help  (Kumar S <ps_postgres@yahoo.com>)
Responses Re: Form Design Advice  (Sean Davis <sdavis2@mail.nih.gov>)
Re: Form Design Advice  (Frank Bax <fbax@sympatico.ca>)
Re: Form Design Advice  (Keith Worthington <KeithW@NarrowPathInc.com>)
Re: Form Design Advice  ("Ross Gohlke" <ross@grinz.com>)
List pgsql-novice
i'm developing a number of data entry forms.  thanks
to many on this board, i'm getting pretty close.  i
*really* do appreciate everyone's knowledge and
insight and their unselfish spirit.

i want my data enterer to be able to verify what they
entered and still minimize the clicks required to
enter data.

i ahve a form process that looks like this...

1. display blank form
2. perform insert after data is submitted (assuming no
errors which i check for)
3. perform select to get data entered
4. save data in global session array
5. redisplay the empty form (ready for new input) with
the printed session array components (representing
what was entered) above the form followed by "
successfully entered."

now that i've moved beyond filling in one column in
one table, this seems to be an overhead hog -
especially when multiple columns are entered into
multiple tables.

it's design decision time... am i being to picky by
wanting to display the data without adding any extra
button clicks?

does anybody have a "cool green" way of getting this
done?

i'm thinking i can just do the data entry (and avoid
the extra selects and session work) and include a
button to include a user input variable number of most
recent entries.

tia...



__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo

pgsql-novice by date:

Previous
From: Sean Davis
Date:
Subject: Re: Please help
Next
From: Sean Davis
Date:
Subject: Re: Form Design Advice