Mendhak,

Thanks. I understand the idea of separating the code logic from the static HTML stuff. I gues what I'm trying to warp my head around is this:

In your example, how is this normally done? Do you place a standard webform submit button & then have that run the server side ASP stuff? Do you create the entire form in ASP.NET?

Then to take that a step further, let me descibe a project I just completed for a Web Design class. It was a small site for a "Dog Adoption" center. There were essentially 4 pages. A main home page that was relatively static, a logo accross the top, links along the left and a bit about the organization in the main content area. The logo and link areas a replicated accross the four pages. The second page was a series of "Pet Profile", now this page is somewhat static, but in a real site it might change on a monthly or weekly basis, in my mind the may or may not benefit from using ASP.NET to render it. The final two pages are a calendar/schedule and a registration for. These two pages seem to be obviously ripe for dynamic content and ASP.NET to do things like load the registration data into a database for later use. Now I used an external CSS style sheet to manage the appearance of the site.

So, I gues what I'd like to understand is how ASP.NET might fit into an environment like that. Obviously the ASP.NET code would run on the server, but how would the ASP.NET portion of the site be incorporated into the CSS Style, if I made the first two pages static HTML and the other two ASP.NET, would the last two simply be ASPX pages and be linked that way in the a tag, or would they be embedded objects in an HTML shell page?

I hope this clarifies what I'm trying to understand. I'm not necessarily looking for a definitive answer just a push in the right direction to find the info (unless some CAN give me a definitive answer).

Thanks again for your help,

Steve