jeff wrote: > 1) the server will need to be pointed > > at main_html, like thesite. > 2) the contents of public_html will need > > to be moved to a folder within main_html > > called browsers. > 3) there may be some other minor changes that > > i'll need to make with regard to template > > placement so that variables are available > > between the two sites. for example, i may > > need to move Application.cfm up a level to > > main_html. what are the advantages other than having logins on the browser archive site though i guess is what i'm asking. That is, does the functionality we'd get out of doing this outwiegh the fucking pain in the ass it would be to implement it? .djc.