Microsoft KB Archive/97005

{|
 * width="100%"|

PRA: Descending Sort Query Returns Wrong Number of Rows
'Article ID: Q97005

Creation Date: 04-APR-1993

Revision Date: 19-SEP-1996' The information in this article applies to:


 * Microsoft Access version 1.0

SYMPTOMS

When sorting data in descending order on an indexed column containing over 506 duplicate entries, Microsoft Access may return the wrong number of rows to the user.

CAUSE

This occurs when the Index property for a column is set to &quot;Yes (No Duplicates)&quot; or &quot;Yes (Duplicates OK),&quot; but not when there is a primary key on the column. Nonprimary-key indexes can have multiple null entries.

RESOLUTION

Remove the index from the column being sorted. This causes the query to execute more slowly but gives you correct results.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access version 1.0. This problem was corrected in Microsoft Access version 1.1.
 * }

-

"THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY." '' ©1997 Microsoft Corporation. All rights reserved. Legal Notices.

''

Additional reference words: 1.00

KBCategory: kbusage

KBSubcategory: QryOthr