SYMPTOMS

An ordered query (a query in which one or more fields are sorted using the SQL ORDER BY clause) on an attached Paradox table with secondary indexes does not consistently select all the records that meet the designated criteria.

RESOLUTION

In Microsoft Access version 1.0, run the query as a make-table query, without specifying a sort on secondary indexed fields. Then, create and run an ordered select query on the new table.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access version 1.0. This problem no longer occurs in Microsoft Access version 1.1.

MORE INFORMATION

This problem occurs only when the query is ordered by a secondary index field.

A Paradox secondary index is a field, other than the primary key, that is indexed. This is analogous to Microsoft Access tables that are indexed on fields other than the primary key.

How to Check for Secondary Indexes

1. Attach a Paradox table in Microsoft Access.
2. Select the attached table in the Database window and choose Design. An error message will appear, stating that some properties cannot be modified.
3. Choose Yes to open the table.
4. Select each row in the table and note its indexed property. The indexed property for secondary indexes is Yes.

1. Check for secondary indexes. If you find any secondary indexes, complete the following steps.
2. Open the query in Design view.
3. Remove all sort specifications based on secondary indexes.
4. Run the query and note the number of rows returned.
5. Enter the sort specifications for the secondary index fields.
6. Rerun the query.

Paradox is manufactured by Borland International, Inc., a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.