Denis

As Rick & Roger point out, autonumbers are designed to serve as unique row
identifiers. If this matches your definition of "record number", fine. You
can find some folks who are willing to expose autonumbers to their users,
but I find them (the autonumbers, not the users or the folks) unfit for
human consumption.

I make extensive use of tables of lookup values, and, where suitable, use
autonumbers IDs on those tables.

JOPO (just one person's opinion)

Jeff Boyce
Access MVP

"Denis" wrote in message
...
Access allows a table to have an autonumber field which could be
considered a
record number.

In an application I am involved in developing there are a number of code
tables which are using the autonumber field as the code. This is
autonumber
code is then used in the tables holding the data.

I am seeking opinions on this approach. Is this a reasonable practice?
What
are the dangers of doing this?

I come from a mainframe environment where this sort of approach is avoided
by generating a unique code value which is not an effective record number
as
a record is added.
--
Denis