Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Autonumber Field Incremented by 300+ when DB was Secured

1 view
Skip to first unread message

Dave Frazell

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to
After running security wizard to create a secure version of an existing
database, the autonumber index field incremented by 300+ causing a gap in
the sequence. I use this field as a project # assignment. Why did this
happen and how can I prevent it from happening when I secure the database
for real?

Thanks
Dave Frazell
IS Manager

Joan Wild

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to
An autonumber is not meant to be used as anything with meaning to the user.
If a user starts to enter a project, but doesn't complete the record (hits
escape for eg.), that autonumber will not be re-used. If you delete records
in the middle of a sequence, that autonumber will never be reclaimed. If
you want a project # field with no gaps, then you should create a custom
counter.

Joan

"Dave Frazell" <dfra...@carefreeofcolorado.com> wrote in message
news:01c05bcd$a7603fa0$0300000a@frazell...

Dave Frazell

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to
With that said, if I can live with gaps in my project numbers, is there any
other reason(s) to not use the autonumber feature for assigning project
numbers? I probably got this idea from the sample Northwind DB because it
uses autonumber to assign order numbers.

Thanks - Dave

Joan Wild <jw...@nospamtyenet.com> wrote in article
<90945...@enews3.newsguy.com>...

Joan Wild

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to
As long as you are aware of how an autonumber acts, and it doesn't or won't
affect you, I say go ahead and use it.
Other than gaps:
1. The autonumber will/can generate negative numbers. This happens once
the autonumber reaches 2,147,483,647, the next number will be –2,147,483,648
and it will increment up to 0. Unless you plan to have 2 billion projects,
this likely won't matter to you...

2. If you ever implement replication, the autonumber will become random
(some will be negative, some positive). Again, if you don't plan on
replicating, this won't be an issue.

3. Other than that, I wouldn't hesitate to use it.
Joan

"Dave Frazell" <dfra...@carefreeofcolorado.com> wrote in message

news:01c05be7$3c406500$0300000a@frazell...

MShe...@compuserve.com

unread,
Dec 2, 2000, 3:00:00 AM12/2/00
to
On 1 Dec 2000 15:41:35 -0700, "Dave Frazell"
<dfra...@carefreeofcolorado.com> wrote:

>With that said, if I can live with gaps in my project numbers, is there any
>other reason(s) to not use the autonumber feature for assigning project
>numbers?

Maybe. There's a problem with autonumbers in Access 2000 (Jet 4).
Sometimes, after compacting a database, the autonumber generates a
number that already exists. The bug was said to be fixed in Jet 4
SP4, but at least one admin reports that the problem persists after
installing SP5.

--
Mike Sherrill
Information Management Systems

0 new messages