Every n-th record in a selection

[termitebe]

WINDOWS XP, Access 2003
I have a query that lists certain amounts as follows

Select a,b,c, amount
from table
ordered by amount.

Now i've been asked to produce a list of every n-th record in that list (preferably in such a way as to be able to reproduce the selection identically to previous selections, also n should be entered manually).

Any suggestions as how to do this ?

[JConsulting]

WINDOWS XP, Access 2003
I have a query that lists certain amounts as follows

Select a,b,c, amount
from table
ordered by amount.

Now i've been asked to produce a list of every n-th record in that list (preferably in such a way as to be able to reproduce the selection identically to previous selections, also n should be entered manually).

Any suggestions as how to do this ?

SELECT a,b,c, amount
FROM Table
WHERE ((([myindex]-1) Mod [enter Nth]=0));
 

[termitebe]

SELECT a,b,c, amount
FROM Table
WHERE ((([myindex]-1) Mod [enter Nth]=0));
 

Thank you for this solution.
My problem being that there is not really an index since the fields need to be ordered by a series of other fields (i failed to mention this in the initial question, a,b and c).

I gues I'll just have to create an index unless someone has another solution.

[NeoPa]

The only solution I can think of is to process through the recordset in code. Unfortunately, this cannot be used as the Record Source for objects like forms or reports.
Essentially, an RDBMS is designed to treat each record as a unique item and so the idea of ordinal numbers (1st; 2nd; 3rd; 4th; etc), or anything that is positionally relative is anathema (It doesn't make sense within that scenario).
Sometimes, tricks can be used to imitate what's required, but I can't see a useful one here.

[JConsulting]

The only solution I can think of is to process through the recordset in code. Unfortunately, this cannot be used as the Record Source for objects like forms or reports.
Essentially, an RDBMS is designed to treat each record as a unique item and so the idea of ordinal numbers (1st; 2nd; 3rd; 4th; etc), or anything that is positionally relative is anathema (It doesn't make sense within that scenario).
Sometimes, tricks can be used to imitate what's required, but I can't see a useful one here.

>>The only solution I can think of is to process through the recordset in code

If a temp table was used to store every nth record while cycling through a recordset, then that could be used as the source for a form or report.

J