Running the query five times, it failed to produce a complete output twice (9997 records instead of the original 9998).
On the last time it did not show the row containing "478" in the "NUM" column.
Attached is a screenshot of 'TableX' and the select query.
Can you either upload the updated Access file or a screenshot of the changes you make to the select query?
I ask because I am unclear what you mean by setting "the sort order."
The table I am querying from is already in ascending order.
Are you saying I should sort the column again in the query, because the "NUM" column is set to sort ascending?
Attached is an updated Access file to illustrate the changes I made. The "TableX" is now 10,000 rows instead of the...
Update on the issue:
I think I solved the issue:
When I was running the query it was in "Select-Query" mode. If instead I create a table to append to using "Append-Query" the query works every time.
It seems as though the "Select-Query" mode may have some memory issues.
Note: I am using...
Attached is an example of what I am trying to accomplish.
It is a list of numbers increasing in value, 1 to 10,000. The actual list is the same as what is provided except they are floating point numbers (Field Size = Double), both numeric types produce the undesired results.
The query...
Banana:
I opened a new .mdb file, imported a different dataset, and just copied the logic from the Microsoft support example. The problem still occurs.
gemma-the-husky:
Do you have any examples of the possible solutions you are posing or sites where I can find them? My Access experience...
Referencing this example from Microsoft Support:
ACC2000: How to Compare a Field to a Field in a Prior Record
(If the link does not work because I am a new member it is from support.microsoft.com/?id=208953)
This example works with the limited dataset provided but if a new dataset is...