Re: Lengthy recordset question

Dwayne:

Be aware that my opinions may well be addlepated, as they usually are. At
any rate, you're welcome!

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.DreamweaverFAQ.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Dwayne Epps" <dwayneepps (AT) centurytel (DOT) net> wrote

Thanks Murray. I appreciate the input! I haven't been working with
databases and ASP pages for that long and was looking for assurance on
whether my thought process was going in the right direction. Thanks again
for the help and suggestion!
-D-


"Murray *TMM*" <forums (AT) HAHAgreat-web-sights (DOT) com> wrote in message
news:beh8mb$ish$1 (AT) forums (DOT) macromedia.com...
Dwayne:

whether having a recordset that is 16 columns is too lengthy

I guess it totally depends on the kind of data, and how you want to use
it.
But in a non-relational sense, 16 columns is not too many (in my
opinion).

Is there a way to get the database to
set back to 1 when the RS's have been deleted out?

Why even worry about this? It really makes no difference. Only the
database and the calling page will ever see that data anyhow.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO
GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.DreamweaverFAQ.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Dwayne Epps" <dwayneepps (AT) centurytel (DOT) net> wrote in message
news:beh8au$i1t$1 (AT) forums (DOT) macromedia.com...
I've built a simple ASP application that writes information submitted
through a HTML form to an Access database. Each recordset consists of
16
fields. It all works fine, but I was interested in getting opinions
on
whether having a recordset that is 16 columns is too lengthy, and if
so,
what is the downside? I know that there are benefits to using
multiple
tables in a database, but wasn't sure if in this type of situation, it
would
really matter? My next step is to create a page that will retrieve
the
information from the database, display it on a page and enable the
administrator to print out the records and or delete them.
Also, I noticed when I was testing the app that the primary key (set
to
auto
increment) will still increment to the next numerical value even when
I
delete the RS. So, for example I submit information and the database
sets
to 1 (primary key) for the first recordset. I'll delete the recordset
in
the database and then test again and the primary key is set to 2 even
though
there is only one RS in the table. Is there a way to get the database
to
set back to 1 when the RS's have been deleted out?
Any input is appreciated. Thanks.
-D-