Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

ACC2000: A Microsoft Access Project Disconnects After You Open SQL Server Objects


View products that this article applies to.

This article was previously published under Q313253
Advanced: Requires expert coding, interoperability, and multiuser skills.

This article applies only to a Microsoft Access project (.adp).

↑ Back to the top


Symptoms

After you open an ADP file that appears to connect successfully, the ADP file disconnects after you open a table or a view. Additionally, you may receive one of the following error messages.

  • When you create a new table
    You do not have exclusive access to the database at this time. Your design changes will not be saved.
    followed by:
    ADO Error: SELECT permission denied on object 'sysobjects', database '<DatabaseName>', owner '<OwnerName>'.
  • When you create a new view:
    You do not have exclusive access to the database at this time. Your design changes will not be saved.
  • When you create a new stored procedure:
    '<StoreProcedureName>' cannot be opened due to a dropped server connection.
  • When you create a new database diagram:
    Cannot create objects of type 'Diagram' against current SQL backend. Please check your permissions and server setup.
  • When you open an existing report:
    The record source '<RecordsourceName>' specified on this form or report does not exist.

    You misspelled the name, or it was deleted or renamed in the current database, or it exists in a different database.

    In the Form or Report's Design view, display the property sheet by clicking the Properties button, and then set the RecordSource property to an existing table or query.
After you get one of these error messages, the Database window may display (Disconnected) in the title bar. However, forms may continue to work as usual.

↑ Back to the top


Cause

You do not have SELECT permissions on the SysObjects system table in the database. Access relies on the SysObjects table when it performs various tasks, such as opening reports or determining which stored procedures to display in the Database window.

↑ Back to the top


Resolution

Grant the user (or the Public database role) SELECT permission on the SysObjects system table in the database.

↑ Back to the top


More information

For more information about handling SQL Server security, please see to the SQL Server security articles on the following Microsoft Web site:

↑ Back to the top


Keywords: KB313253, kbprb

↑ Back to the top

Article Info
Article ID : 313253
Revision : 3
Created on : 7/13/2004
Published on : 7/13/2004
Exists online : False
Views : 263