Microsoft KB Archive/275115

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:26, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 275115

Article Last Modified on 11/5/2003



APPLIES TO

  • Microsoft Access 2002 Standard Edition



This article was previously published under Q275115

Moderate: Requires basic macro, coding, and interoperability skills.

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


SYMPTOMS

When you create a TOP X or TOP X PERCENT view or function in a Microsoft Access project, the view cannot be updated as expected. The object can be updated only when you specify TOP 100 PERCENT.

CAUSE

This behavior occurs as a result of a unique rows limitation, caused by the ADO UniqueRows property for the recordset being set to False. As a result, Microsoft SQL Server does not return the unique row information required to enable updating.

RESOLUTION

To work around this issue, specify TOP 100 PERCENT instead of TOP X or TOP X PERCENT.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce the Problem

  1. Open the sample project NorthwindCS.adp.
  2. In the Database window, click Queries, and then click New.
  3. Select Design View and click OK.
  4. Close the Add Table window; on the View menu, point to Show Panes, and then click SQL.
  5. In the SQL pane, type the following code:

    SELECT TOP 10 dbo.Products.*
    FROM dbo.Products;
                        
  6. Save the view as TestView, and then run the view. Note that the view is read-only.


REFERENCES

For more information about Microsoft Access projects, click Microsoft Access Help on the Help menu, type access project in the Office Assistant or the Answer Wizard, and then click Search to view the topics returned.



Additional query words: pra

Keywords: kbbug kbpending KB275115