> You have it backwards. This can all be done in a
> single script with this
> 1. Check to see if there is any incoming data. If
> there is incoming data,
> validate it, and insert into your database.
> 2. Display data from your database.
> 3. Present an empty form.
frank, i didn't mention it, but i do validate the data
expressions, too, but that's down the road a bit.
i then insert the data.
i could display the data, but then we are talking two
clicks for each data set entered - or at least some
period of time between form display. admittedly, i'm
probably being hyper technical here, but one click is
more efficient from the user pov.
enter data -> click -> quickly review data if desired
-> enter more data -> click... etc.
as opposed to
enter data -> click -> quickly review data -> click ->
enter more data -> click... etc.
that's 100% increase in required clicks.
i can see the programming logic in the method you
outlined, though. all those session variables get
rather difficult to manage when lots of data is involved.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
In response to
pgsql-novice by date
|Next:||From: George Weaver||Date: 2005-03-02 02:39:58|
|Subject: Re: difference between varchar and varchar in pgadmin3 (and|
|Previous:||From: operationsengineer1||Date: 2005-03-02 01:43:50|
|Subject: Re: Form Design Advice|