ACC2: Unexpected Query Results with Attached xBASE TableID: Q132012
|
Moderate: Requires basic macro, coding, and interoperability skills.
When you run a select query based on an attached Microsoft FoxPro or dBASE
table with the criteria applied to an indexed field designated as the
unique record identifier, the Microsoft Access version 2.0 Service Pack
produces unexpected query results. For example, the query returns only 1
record instead of all the records that match the criteria applied to the
unique record identifier field.
If the unique record identifier field contains duplicate values, the
Microsoft Jet database engine version 2.5 returns the first record that
matches the criteria in the query.
NOTE: This behavior differs from the Jet database engine version 2.0 that
was shipped with Microsoft Access version 2.0. The Jet database engine
version 2.0 returns all the records that match the specified criteria in
the unique record identifier field, not just the first matched record.
To work around this behavior, re-attach the table without a unique record
identifier, and then run the query again. To do so, follow these steps:
This behavior is by design.
USE ORD_DET
INDEX ON PRODUCT_ID TAG PRODUCT_ID
USE
QUIT
Query: Query1
------------------
Type: Select Query
Field: Order_Id
Table: ORD_DET
Field: Product_Id
Table: ORD_DET
Criteria: 24
For more information about attaching tables, search for "Attach Table," and then "Attach Table Command (File Menu)" using the Microsoft Access Help menu.
Keywords : kb3rdparty IsmXbase
Version : 2.0
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: April 30, 1999