My data entry clerk says she did not delete a record, but if I look at the 'Autonumber' field, a number is missing from the sequence of entries. And apparently Access will not allow me to edit the numbers to rectify the issue since it is an Autonumber field. Any solutions? I need the Autonumbers to be in order, and without missing numbers.
ARGH Data Entry Person!
- Thread starter blueBeard
- Start date
- Local time
- Today, 03:16
- Joined
- Aug 30, 2003
- Messages
- 36,157
Your data entry clerk is probably correct. It's not unusual for autonumbers to skip numbers. For instance, if you start a record and decide not to save it, the autonumber that had been "reserved" for that record will be skipped. Also, as you've discovered, you can't edit the number.
It sounds like you're going to need to create your own number rather than use autonumber, given the restrictions you've described. Here's one way:
http://support.microsoft.com/default.aspx?scid=kb;en-us;210194&Product=acc2000
It sounds like you're going to need to create your own number rather than use autonumber, given the restrictions you've described. Here's one way:
http://support.microsoft.com/default.aspx?scid=kb;en-us;210194&Product=acc2000
R
Rich
Guest
If you want guaranteed sequential numbers you'll have to create your own. Search here for solutions.
- Local time
- Today, 05:16
- Joined
- Feb 28, 2001
- Messages
- 30,563
Concur. Using the autonumber field as data (other than strictly for linking to other tables) is probably not the best idea.
You are guaranteed that an autonumber field is unique. You are NOT guaranteed that it is contiguous.
You are guaranteed that an autonumber field is unique. You are NOT guaranteed that it is contiguous.
I don't worry about autonumber fields incrementing regularly, my users never see them.
Further more, in some applications I use random increments, the numbers are really wild (very,very positive and very, very negative), so that the FE and BE are easily ported to a laptop for a user to take home and then new records added back to the BE the next day. If they add data a little data, with random indicies, I've never had a duplicate. This isn't the best practice, but it works well with my applications.
Further more, in some applications I use random increments, the numbers are really wild (very,very positive and very, very negative), so that the FE and BE are easily ported to a laptop for a user to take home and then new records added back to the BE the next day. If they add data a little data, with random indicies, I've never had a duplicate. This isn't the best practice, but it works well with my applications.
Similar threads
