This is truly a difficult concept - the thing to think about is this - an html (static) page is simply opened by a client's browser and read as-is. It's not 'that' simple, but that's essentially what happens - a client's browser tells the web server to deliver this page to me, and that html page is sent.

Asp, Asp.net, etc are rendered by the server - that is - the server gets a request from a browser for a file, it loads the file and interprets things in the file (like code, etc). Then it sends the resulting html to the client.

No matter what you use - eventually, straight simple html is sent to the browser. The browsers have no idea of how it was rendered, where it came from, etc. It just has html to display.

If you are not using Asp, you can use server side includes - that is very similar to the way asp is rendered - essentially, you would have a single file (perhaps with buttons, etc defined in it). This file would be raw html. In your html page, you would have a code to tell the web server to insert that chunk of text here. The result sent to the browser is all of it together.

>Ok, it finally came up for me. Not sure what the problem was before. Likely user error...
>
>Still not real clear on how all this works. I thought it would be a simple thing, but it seems that it's more involved than just referencing the html you want to include. Have to make changes to IIS and all that to test locally.
>
>>Me either... if you can get the link to come up, scroll down - the answers are there for me.