[thelist] webapp logic

[David McCreath]

I just downloaded a sample application this morning that lets you add,
delete, or update records in an Access database using one ASP page, and
changes appearance according to the action in the form using an IF statement
for the value of the Request.StringQuery.

http://haneng.com/lessons/21.asp

Dave

----- Original Message -----
From: "Czechowski, Aaron" <aczechowski at towson.edu>
To: "Thelist (E-mail)" <thelist at lists.evolt.org>
Sent: Thursday, July 06, 2000 11:25 AM
Subject: [thelist] webapp logic


> A guy I used to work with prided himself on the fact that he could
> write a many-featured webapp in one page - he would obviously brag about
the
> lines of code, but also about how many physical files he needed to take
care
> of all the features.  The initial page would have a form (or something)
> which would submit to ITSELF, which would process the data and output it.
> All internal to one page or so.
> What do ya'll think about that?  Is there an advantage (process
> speed, less connections, etc.) in having just one or two pages for
> something, rather than having a multitude of pages, one for the initial
> page, one for processing featureX, another for featureY, etc.?
> Obviously I'd save myself some trouble (maybe?) in having multiple
> pages - the nested If-Else logic of a one-pager can be mind-boggling.