Mysterious Recordset Changes

[Guest]

Recently I ran a query, the query had a join between two table. One of the
joined tables was set up to restrict the result set of the query. This
joined table only contained one row of data. When I ran the query it had
1066 rows of data. This looked like way too many records. I resorted the
data by one of the unique keys to look for duplicate rows and the recordset
went from 1066 rows to 360. This happend in the datasheet view, I did not do
a requery. How is this possible and why would the query results change just
because I resorted the datasheet view of the data.

 

[Allen Browne]

Did you alter the criteria of the query? If so, see the discussion about
joins and nulls in this article:
The Query Lost My Records!
at:
http://members.iinet.net.au/~allenbrowne/casu-02.html

If that is not the issue, it sounds like a corrupt index.
See the 2nd symptom in this article:
Number of records varies, depending how the data is sorted
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html