Deploying Exported XML File Sets to a Web Server

One advantage of exporting Access objects to static XML data documents is that their file sets are self-contained. Presentation of the data as a Web page isn't dependent on access to a Jet or SQL Server data source. Thus you can simply copy or move the .xml, .xsl, and .htm or .asp files for any exported Access object to the default \Inetpub\wwwroot of Internet Information Server (IIS) 5+ or a virtual directory you dedicate to delivering XML-based pages. Client computers must have IE 6+ installed to render the .htm files locally; specify server-side processing with ASP to support all browsers.

It's not necessary to copy static .xml/.xsl/.htm file sets to a Web server to make them accessible to others on a network. If you share the folder that holds the file set, others can open the .htm file by specifying the path and file name in IE 6+'s Open text box. Clients must have IE 6+ installed to process the .xsl file on the client. If you need interoperability with IE 5.5 or earlier, use the conventional HTML or ASP export process.