Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 235267 - Last Review: June 30, 2004 - Revision: 2.0
ACC2000: Table in a Microsoft Access Project Cannot Be Updated
This article was previously published under Q235267
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access project (.adp).
You find that you cannot delete, update, or insert new records in a table in an Access project.
The table does not have a unique index.
To work around this behavior, check that the table has a unique
index. If the table does not have a unique index, create a unique index by using a stored procedure such as the one in the "How to Correct the Behavior" section that follows step 4 of the "Steps to Reproduce Behavior" section later in this article.
CAUTION: If you follow the steps in this example, you modify the sample Access project NorthwindCS.adp. You may want to back up the NorthwindCS.adp file and follow these steps on a copy of the project.
Steps to Reproduce Behavior
- Open the sample Access project, NorthwindCS.adp.
- In NorthwindCS.adp, create the following stored procedure, and then run it:
Create Procedure "MakeTestTable"
As
SELECT * INTO tblTest FROM customers
CREATE INDEX tblTest_Index ON tblTest (customerid)
return
- In the Database window, click Tables, and then press F5 to refresh the Tables list.
- Open the tblTest table in Datasheet view. Note that when you open the table in Datasheet view, you cannot edit or add records.
How to Correct the Behavior
You can correct this behavior by running the following stored procedure:
Create Procedure "FixTestTable"
As
DROP INDEX tblTest.tblTest_Index
CREATE UNIQUE INDEX tblTest_Index ON tblTest (customerid)
return
APPLIES TO
- Microsoft Access 2000 Standard Edition
| kbprb kbclientserver kbusage KB235267 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
Wolfgang Steuer
- wac NOSPAM-AT-NOSPAM steuer.demon.co.uk
|
Report As Irrelevant
|
| Written:
7/20/2005 6:14 AM |
|
|