A
Afzal
Hi.
I am surprised by different result of a simple INNER JOIN query based on
SORTING the result.
Situation: There is Customers and Inventory table. CustomerID, a text
field, is in both of the tables. I was trying to find records that match
and those don’t match in the Inventory table based on CustomerIDs. Here is
the query find the matched records:
SELECT Inventory.customerID, Inventory.CutomerName
FROM Inventory INNER JOIN CustomerList ON Inventory.customerID =
CustomerList.customerID;
The result returned 2052 records. But, as soon as I sort on any column,
result changes to 1968. I know that 1968 is the correct answer because
another query “Inventory Without Matching CustomerList†returns 96 records
(doesn’t mater how I sort it; out of 2064 total records).
To find out what was going on, I printed some screen shots of two different
results. It seems like Access is printing some of the records twice in the
result pane; as soon as I sort, the duplicate records go away.
Is there a bug in Access 2003 (11.6355.6408) SP1 ?
(I can duplicate this problem easily)
I am surprised by different result of a simple INNER JOIN query based on
SORTING the result.
Situation: There is Customers and Inventory table. CustomerID, a text
field, is in both of the tables. I was trying to find records that match
and those don’t match in the Inventory table based on CustomerIDs. Here is
the query find the matched records:
SELECT Inventory.customerID, Inventory.CutomerName
FROM Inventory INNER JOIN CustomerList ON Inventory.customerID =
CustomerList.customerID;
The result returned 2052 records. But, as soon as I sort on any column,
result changes to 1968. I know that 1968 is the correct answer because
another query “Inventory Without Matching CustomerList†returns 96 records
(doesn’t mater how I sort it; out of 2064 total records).
To find out what was going on, I printed some screen shots of two different
results. It seems like Access is printing some of the records twice in the
result pane; as soon as I sort, the duplicate records go away.
Is there a bug in Access 2003 (11.6355.6408) SP1 ?
(I can duplicate this problem easily)