And what in the world does the code in your post #7 have ANYTHING to do with the code in your post #1???
#7 is doing a SELECT query and getting a bunch of records to be displayed.
#1 is adding one record via an INSERT query.
I wonder if I can come up with an analogy...hmmm...
#7 is like driving to the post office to open your mailbox there and finding a bunch of letters that you can then list the contents or senders of.
#1 is like driving to the post office and then SENDING *one* letter yourself.
TWO DIFFERENT PURPOSES.
But you *COULD*, say, go to the post office to send a letter and then, after sending the letter, open your mail box to see what letters you have received.
And you *CAN* do the equivalent in ASP code.
You can add one record to your database table using an INSERT query. And then, on the same ASP page but *AS A SEPARATE OPERATION* you *can* do a SELECT query and get some records to display.
But the two operations *ARE SEPARATE*, even if they are on the same ASP page.
The *ONLY* thing they share are the already-open connection to the database. Kind of like you driving to the post office only once to both send a letter and open your mail box there. You save gas by only driving to the post office once, instead of making two trips. But the only thing the sending and receiving have in common is that they both needed a trip to the post office. Ditto the connection being used for both INSERT and SELECT.
But, and this is very important, you DO NOT HAVE TO do a SELECT after doing an INSERT. You only do that if it makes sense in the logic of your application/web page.
An optimist sees the glass as half full.
A pessimist sees the glass as half empty.
A realist drinks it no matter how much there is.