How to set up seperate pages with header/footer

Hi Joe,
     That's a route I would really really avoid.
Having TWO copies of the code in a single site makes maintenance more of a headache.
Customers expect any width detection to happen automatically & there's plenty of code on the web to help do that.  If you want them to be able to choose then  perhaps use the same/similar method as is used on :
http://demotemplates.joomlashack.com/lightfast/
(See the  ||  and <>  buttons on the right near the top ).

I would, off the top of my head, add code to header.asp to switch between the two versions.

I don't recall seeing any variable width ProductCart sites, and I haven't looked into it myself. - Actually, I've just done a small experiment & changed a site to a width of "90%" instead of a fixed 770px and, apart from the graphic in the header it looks fine.  

Why not try a flexible width version.
To try it out set the  main table in your  header file  to, say,  :- 
<table width="90%"  align="center"  class="yourClass">

Take a look and see what the impact is.  If you have a header image across the width of the page which then looks wrong either change it to "blend" into the background, or set it to auto resize.
If your site is live then either try it on a test copy or you can use a copy of header.asp and, say, viewprd.asp and add TST (or whatever) to the front of the file names & amend TSTviewprd.asp to use TSTheader.asp so you can experiment on the "live" site without impacting live customers.

If you want to go the route of the example Joomla site, then you will have to examine the source code and javascript etc on their sample site.
Is the client going to pay you extra for creating two versions, or is it already in your contract?  (None of my business - no need to answer that one - it's just a thought)
 

OK,
  Using their same pseudo-code I would keep ONE set of folders and create two versions of header & footer.
headerW, footerW   & headerF, footerF

Then header.asp and footer.asp become a small strub of code like :-

If "fullscreen mode" then
        "include fullscreen header"
else
    "include widescreen header"
endif

That way, as they say, you only have to maintain 1 set of code. The footer.asp would be the same except choosing between the two versions of footer.
You could either havr the customer choose before entering, or, nicer IMHO have a graphic button in each header to allow them to toggle between the two versions. If you store the value in the cookie then they will always keep the version they have selected, until they decide to change it.

Yes, 
   Create the four versions.
Then header.asp and footer.asp just become bits of code to select which version of each file is used  based on the variable from  the cookie, in this case the var is called headerw :

<% if headerw=1 then %>
<!--#include file="headerW.asp"-->            
<% else %>
<!--#include file="headerF.asp"-->            
<% end if %>

The downside to this approach is there will be a small performance hit as the includes are done at the server regardless, but only the required one will be sent to the browser.
An alternative approach would be to use that same if structure around the parts of header & footer that you wish to have different versions of, but to start I would go the route of separate header & footers as I suspect the impact would be minor and the maintenance much easier.   


The first version - That's in ASP/vbscript.
Effectively you are scrapping the existing header/footer and replacing them with code to select between the two alternate styles.
Don't forget you need to grab the variable headerw from the cookie - For an example of code doing that check pc/login.asp