If you require it to always increment by 1, and have no gaps in the data, then autonumber is not the choice for you. The general rule is that if the field is to have any significance whatsoever, other than simply being a record identifier, then autonumber is not the best choice.
When a user goes to create a record with autonumber, the next number in the sequence is chosen. However, if the record is cancelled before it is created, the autonumber doesn't add the value back into the sequence.
For instance, if you have records 1, 2, and 3, and then you go to add record 4, but cancel before adding it. The next record you add will be 5. You will now have 1, 2, 3, and 5. Such is the nature of autonumber.
An alternative would be to use something such as
DMax("[FieldName]", "tablename"

+ 1
to find the next highest value.
However, if you're set on using autonumber, this link may help you do what you want. Use it at your own risk. I haven't tried it, or even actually read much of it, so I'm unable to comment on how well it works (or doesn't).
Good luck.
![[morning] [morning] [morning]](/data/assets/smilies/morning.gif)
Sleep is for people with no caffeine.