> Thanks, Alan. I had read something about the testing server, but it was not
> clear exactly how all the pieces fit together.

Yes- if you declare a testing server in the site definition, dreamweaver
changes the way it does F12 Preview in Browser.

Instead of sending the code to the browser, dw using the info entered about
the Testing server to send the relevant files to the proper location

(either a locally installed testing server folder or even a remote ftp
location, you can use your remote host or a subdomain of the site as the
testing server. There's a lag while the files get transferred though)

then opens the browser with the "http prefix" of where the testing server
site can be seen.

Usually we get asked this question in the other direction; people who don't
need a testing server for their Site definition fill in information for it
mistakenly. Then can't understand why they get a 404 error message when they
hit F12 to preview their plain html pages.

Install the server and PHP and MySQL, get that part working.
Then define the site in dw, and fill in the Testing Server information.

Tip: If you know what most of the terms mean, the Advanced tab in the New
Site Dialog box is easier to fill out than the "wizard" step by step
version.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/