Article ID: 167294 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Advanced: Requires expert coding, interoperability, and multiuser skills.
When you export Microsoft Access 97 objects to ASP format, you provide the name of a System DSN on your Web server, which Microsoft Access uses in the ConnectionString property of the ASP script that it generates.
You can modify the ASP script so that it uses either a File DSN or a DSN-less ConnectionString (by providing detailed connection information). This capability has the following advantages:
The following example shows you how to create an ASP file with Microsoft Access 97, and then modify it so that a System DSN is not required. This section is divided into these parts:
Important NotesFor the sake of simplicity, the example in this article instructs you to copy all files to the same folder on your Web server. This is not a requirement, as long as the ConnectionString information in the ASP file contains the correct path to the files. For example, the database and the File DSN (if you use one) can be located on a network share, and you can use universal naming convention (UNC) paths in your ConnectionString.
All files that you want to access require appropriate permissions on the Web server computer. This includes IIS permissions, NTFS permissions, and network share permissions. If IIS is configured to use Anonymous Access with an Internet Guest Account, then that account must have Read and Write access to the folder in which the database resides. If you use a File DSN, then the Internet Guest Account must have Read access to the File DSN. And if network shares and UNC paths are used in the File DSN or in the ConnectionString, then the Internet Guest Account must have appropriate network share permissions. For a detailed description of permissions issues when using ASP files, please see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/161333/EN-US/ )Check NT Permissions When Using IDC/ASP Files with Access
Copying Northwind and Your File DSN to the Web ServerYou must have a folder on your Web server where you can copy files. The folder should be an IIS virtual directory with Execute permissions. Copy the Northwind sample database, Northwind.mdb, to this folder. Write down the complete path to this file; you will need that information when you create the ConnectionString later. The path can use either a drive letter or a UNC name.
If you plan to use a File DSN in the ConnectionString instead of detailed connection information, make sure the appropriate argument in your File DSN contains the complete path to your database on the Web server (drive letter or UNC path). Copy your File DSN to the same folder on your Web server where you place Northwind.mdb. Then, when you modify the ConnectionString in the ASP file, you only need to provide a path to the File DSN.
For more information about creating File DSNs and DSN-less connections, please see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/165866/EN-US/ )How to Use File DSNs and DSN-less Connections
Creating and Modifying the ASP FileIf you are using a File DSN, please skip to the next section.
Testing the ASP File
For more information about exporting ASP files, search the Help Index for "ASP files," or ask the Microsoft Access 97 Office Assistant.
For more information on how to create and modify ASP files, please refer to your Microsoft ASP online documentation.