is performed), the filename in which the error appears, the line number in code on which the error appears, and a description of the actual error. Figure 4.41. Site Report results are displayed in the Site Reports tab in the Results window. [View full size image] 6. Similar to the Link Checker, you can double-click the error in the Results window. Dreamweaver automatically opens the document in Code view and focuses your cursor on the exact line that contains the error. 7. You can also save the report for later use. To do this, click the Save icon on the left side of the Results window. Dreamweaver saves the file in an XML format, allowing you to later format the report into a web page, a spreadsheet, or a database table. After you've fixed errors, you can run the report again by selecting the Play icon to re-open the Site Reports dialog.           Using Advanced Site Management Options Although it seems we've run the gamut in terms of site management functionality, Dreamweaver actually includes a few more features that can only be categorized as advanced site management options. Available from the Advanced submenu in the Site menu, these advanced features include the following: FTP Log: While transferring files using the built-in FTP client, Dreamweaver records all activity. If an error occurs when you are transferring a file using FTP, the FTP log can help you determine the problem. Simply select this option to present the text-based log in the FTP Log tab in the Results window similar to Figure 4.42. Figure 4.42. The FTP log can help you troubleshoot FTP errors. [View full size image]   Recreate Site Cache: At the beginning of the chapter, we discussed the cache. I mentioned that Dreamweaver takes a snapshot of your folder and file structure and caches it. In most cases, this cache is automatically generated and in some cases, when changes are made in Dreamweaver, the cache is regenerated. If, for some reason, you make changes to the folder and file structure outside of Dreamweaver (not recommended), run this handy utility to re-create Dreamweaver's cache for the selected site. Remove Connection Scripts: When connecting to databases, Dreamweaver relies on a connection script built into a file and placed within a Connections folder in your site. If you've begun working with databases, this file is automatically created for you. Unfortunately, Dreamweaver doesn't know when you're no longer working with databases. You can minimize the risk of someone accessing your database remotely by removing these connection scripts manually. Because compromise is possible only while the scripts are actually present on the server, removing the scripts removes the risk of database access in the future. Deploy Supporting Files: When working with dynamic web applications, Dreamweaver relies on pre-built files and scripts (like connection scripts) to create the functionality with which you'll ultimately interact. In most cases, Dreamweaver automatically creates a folder within your site for these files. If,