I've seen this a couple of times on other sites and I've always wondered 

how it works.



Say we have reg.htm.  reg.htm contains a form that takes user 

registration information.  Now, that form  POSTS to details.htm.  The 

user fills out the registration form, and hits submit.  Now, according 

to the form tag, this information is then sent to details.htm.  The user 

is presented with the details screen with his information on it.  While 

he's sitting there reading it he receives a message in his inbox saying 

he has been registered with xyz.com  and his username and password is 

blah, blah. 



Now, I went through this one time, and filled it out, hit submit, and 

after a few seconds I received an odbc error on a primary key constraint 

from a page other then what the form was submitting to.  Every page that 

is called or submitted to has an html extension on it, but I see that 

there is a SQL Server back end and some asp processing going on.  I just 

don't see how the asp pages are getting called for the processing and 

how the html pages are loading them selves dynamically.  If anyone can 

clue me in, I would appreciate it.  At a guess, this is one of those 

things I should of picked up over the years but never had to, now 

curiosity is getting the better of me.



Thanks,



Jerry

I think on IIS - Application Configuration is set to process html pages

using asp.dll.  Since you can add any file extensions and select what dll

file to process it.  Why not html.



hope this helps,



Khanh



-----Original Message-----

From: Jerry Diegel [mailto:diegelj@g...]

Sent: Wednesday, February 27, 2002 11:16 AM

To: ASP Web HowTo

Subject: [asp_web_howto] What's processing what?





I've seen this a couple of times on other sites and I've always wondered how

it works.



Say we have reg.htm.  reg.htm contains a form that takes user registration

information.  Now, that form  POSTS to details.htm.  The user fills out the

registration form, and hits submit.  Now, according to the form tag, this

information is then sent to details.htm.  The user is presented with the

details screen with his information on it.  While he's sitting there reading

it he receives a message in his inbox saying he has been registered with

xyz.com  and his username and password is blah, blah.  



Now, I went through this one time, and filled it out, hit submit, and after

a few seconds I received an odbc error on a primary key constraint from a

page other then what the form was submitting to.  Every page that is called

or submitted to has an html extension on it, but I see that there is a SQL

Server back end and some asp processing going on.  I just don't see how the

asp pages are getting called for the processing and how the html pages are

loading them selves dynamically.  If anyone can clue me in, I would

appreciate it.  At a guess, this is one of those things I should of picked

up over the years but never had to, now curiosity is getting the better of

me.



Thanks,



Jerry






$subst('Email.Unsub').