As stated in the MS Kb article give by answer#1, a true record number doesn't exist.
You can, however, create an auto-number field in the table. The problem with this is that when a record is deleted, the records are not re-numbered - you would need to do this in a recordset loop and would not be recommended on a table with tens of thousands of records, unless the renumbering can wait until a maintenance period, (end-of-day), is done.
Then there is the possibility of deleting the number field and re-creating it on each deletion - blaa!
The question I have is what is the purpose of your record number? To show a record number in a datagrid or DbGrid? If so, then you only need to create a dummy number field in your sql statement thatis used for the grid, and then after the sql is ran, loop through and update the dummy field in the recordset, or loop through that column on the grid and update the grid column value. Both have the disadvantage of not being static - except if you were to always use the same sort order whenever you query this table.
But maybe it doesn't have to be static - ie. the only purpose of the record number is for ease of reading.
Please post a comment and tell what the purpose of the record numberis and if it has to be static, re-numbered on each deletion/addition, or can be different each time the records are shown meaning that it's only purpose in life is to show the order number of each record for the one time snapshot. Then maybe a solution can be given to help you more.