Re: Form Design Advice

From: Sean Davis <sdavis2(at)mail(dot)nih(dot)gov>
To: <operationsengineer1(at)yahoo(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Form Design Advice
Date: 2005-03-01 20:52:54
Message-ID: e334221536fd5a61ed8f4156ddd5df50@mail.nih.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice


On Mar 1, 2005, at 3:39 PM, <operationsengineer1(at)yahoo(dot)com> wrote:

> 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.

In what framework are you doing this--CGI?

Sean

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message operationsengineer1 2005-03-01 21:24:51 Re: Form Design Advice
Previous Message operationsengineer1 2005-03-01 20:39:30 Form Design Advice