Many times when I create a new database and I click to have Access set a
primary key for me, it then starts at the number 22 for the auto number
instead of 1. Can anyone tell me why this is or what I'm doing wrong.

Thanks

Nothing. Just remember that autonumbers are only guaranteed to be unique if
used as a primary key. You can not depend on them be sequential or even
starting at a certain number. If the numbers must be sequetial and start at
1, an autonumber is not the right choice.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

"chicagoteacher" wrote:

> Many times when I create a new database and I click to have Access set a
> primary key for me, it then starts at the number 22 for the auto number
> instead of 1. Can anyone tell me why this is or what I'm doing wrong.
>
> Thanks

In news:A7F45E55-5A86-4442-B61F-(E-Mail Removed),
Jerry Whittle <(E-Mail Removed)> wrote:
> Nothing. Just remember that autonumbers are only guaranteed to be
> unique if used as a primary key. You can not depend on them be
> sequential or even starting at a certain number. If the numbers must
> be sequetial and start at 1, an autonumber is not the right choice.

On the other hand, if autonumbers are starting at 22 for most tables,
something a bit odd is going on. While the value of the autonumber
itself means nothing, an autonumber would normally start at 1 when you
begin to enter the first record for a brand new table. Maybe
chicagoteacher is always performing some series of steps that repeatedly
dirties and then clears a new record.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Good point. I was going to suggest deleting all records in that table. Then
doing a compact and repair to see if it resets the initial autonumber back to
1.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

"Dirk Goldgar" wrote:

> In news:A7F45E55-5A86-4442-B61F-(E-Mail Removed),
> Jerry Whittle <(E-Mail Removed)> wrote:
> > Nothing. Just remember that autonumbers are only guaranteed to be
> > unique if used as a primary key. You can not depend on them be
> > sequential or even starting at a certain number. If the numbers must
> > be sequetial and start at 1, an autonumber is not the right choice.
>
> On the other hand, if autonumbers are starting at 22 for most tables,
> something a bit odd is going on. While the value of the autonumber
> itself means nothing, an autonumber would normally start at 1 when you
> begin to enter the first record for a brand new table. Maybe
> chicagoteacher is always performing some series of steps that repeatedly
> dirties and then clears a new record.
>
> --
> Dirk Goldgar, MS Access MVP
> www.datagnostics.com
>
> (please reply to the newsgroup)
>
>
>