The information in this article applies to:
SYMPTOMSModerate: Requires basic macro, coding, and interoperability skills.
CAUSEExporting a linked table or an object based on a linked table to ASP may result in problems with permissions. When you open the ASP file in a browser, access to the data is granted to the World Wide Web service instead of to you as a user. The account used by the service is IUSR_<servername>, which is created by Microsoft Internet Information Server. For more information, see the following article in the Microsoft Knowledge Base: Q161333 ACC97: Check NT Permissions When Using IDC/ASP Files with AccessIn addition, when you export a database object to ASP, Microsoft Access automatically generates the script in the ASP file. This script contains not only the connection string that points to the data source, but also the SQL statement used to create the recordset. Microsoft Access uses Microsoft Jet SQL to create this SQL statement. If the object that you are exporting to ASP is linked to an ODBC data source, that data source may not be able to process the Microsoft Jet SQL in the script. RESOLUTIONUse Microsoft Access to export only local objects to ASP. ASP files that work with data in a linked table should be written to communicate directly with that data. Consider using a tool such as Microsoft Visual Interdev to help you to create these ASP files. MORE INFORMATIONThe following diagram depicts how components are used when you export a Microsoft Access object based on a SQL Server data source to ASP:
However, if you write an ASP file that accesses the data source directly, the components are used as follows:
REFERENCESFor more information about Microsoft Visual Interdev, visit the Microsoft World Wide Web site at http://www.microsoft.com/catalog/default.asp?subid=22and select Visual Interdev. Additional query words:
Keywords : kberrmsg kbdta IntAsp |
Last Reviewed: June 21, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |