Microsoft KB Archive/97528

{|
 * width="100%"|

PRA: Fast Search on Indexed Paradox Column Fails
'Article ID: Q97528

Creation Date: 13-APR-1993

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


 * Microsoft Access version 1.0

SYMPTOMS

A Fast Search on an indexed Paradox column fails, even when there is data to match the search criteria.

CAUSE

This problem occurs when a Paradox column (field) name has the same name as the Paradox table it is contained in.

In Paradox, the primary index is always stored in a table named .PX, and secondary indexes are stored in tables named .NXX. For example, with a table named &quot;Authors&quot; that contains fields named &quot;Authors&quot;, &quot;Books&quot;, and &quot;Publisher&quot;, the primary index file is named AUTHORS.PX, and the secondary indexes are named BOOKS.N01, PUBLISHER.N02, AUTHORS.N03.

When Microsoft Access performs a Fast Search, it ignores the file extensions for these indexes. As a result, if a column name is the same as a table name, Microsoft Access sees two indexes with the same name and assumes it to be a single multicolumn index instead of two separate single- column indexes. This results in strange behavior, such as not getting the results you would expect from a search or query.

RESOLUTION

Be sure that the field names in the Paradox table differ from the table name.

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: kb3rdparty

KBSubcategory: IsmPdox