Row numbers in query result using Microsoft Access

calendar_today Asked Jun 24, 2013
thumb_up 8 upvotes
history Updated April 14, 2026

Direct Answer

Another way to assign a row number in a query is to use the DCount function. SELECT *, DCount("[ID]","[mytable]","[ID]<=" & [ID]) AS row_id FROM [mytable] WHERE row_id=15. This is a 4-line Access VBA snippet, ranked #41st of 67 by community upvote score, from 2013.


The Problem (Q-score 5, ranked #41st of 67 in the Access VBA archive)

The scenario as originally posted in 2013

I always use this query in sql server to get Row number in a table:

SELECT *
FROM   (SELECT *,
               Row_number()
                 OVER(
                   ORDER BY [myidentitycolumn]) RowID
        FROM   mytable) sub
WHERE  rowid = 15

Now I am working in Access 2010 and this seems to be not working. Is there any replacement for this query in Access?

Why community consensus is tight on this one

Across 67 Access VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — niche answer (below median) (+8)

4-line Access VBA pattern (copy-ready)

Another way to assign a row number in a query is to use the DCount function.

SELECT *, DCount("[ID]","[mytable]","[ID]<=" & [ID]) AS row_id
FROM [mytable]
WHERE row_id=15


When to Use It — classic (2013–2016)

Ranked #41st in its category — specialized fit

This pattern sits in the 74% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.

What changed between 2013 and 2026

The answer is 13 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

This is a below-median answer — when does it still fit?
expand_more

Answer score +8 vs the Access VBA archive median ~4; this entry is niche. The score plus 5 supporting upvotes on the question itself (+5) means the asker and 7 subsequent voters all validated the approach.

Does the 4-line snippet run as-is in Office 2026?
expand_more

Yes. The 4-line pattern compiles on Office 365, Office 2024, and Office LTSC 2026. Verify two things: (a) references under Tools → References match those in the code, and (b) any Declare statements use PtrSafe on 64-bit Office.

Published around 2013 — what’s changed since?
expand_more

Published 2013, which is 13 year(s) before today’s Office 2026 build. The Access VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Access VBA pattern ranks just above this one at #40?
expand_more

The pattern one rank above is “what is the alternative to NVL function in MS Access 2007”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 5, Answer-score 8, original post 2013, ranked #41st of 67 in the Access VBA archive. Last regenerated April 14, 2026.

ms-access