>From [EMAIL PROTECTED] Wed Nov 20 20:11:59 2002
Received: from imo-m03.mx.aol.com (imo-m03.mx.aol.com [64.12.136.6])
by sonet.rxcpi.net (8.9.3/8.9.3) with ESMTP id UAA23502
for <[EMAIL PROTECTED]>; Wed, 20 Nov 2002 20:11:59 -0500
Received: from [EMAIL PROTECTED]
by imo-m03.mx.aol.com (mail_out_v34.13.) id s.7.5e8a4f9 (22683)
for <[EMAIL PROTECTED]>; Wed, 20 Nov 2002 20:20:11 -0500 (EST)
Received: from netscape.net (mow-m23.webmail.aol.com [64.12.180.139]) by
air-in04.mx.aol.com (v89.21) with ESMTP id
MAILININ44-1120202011; Wed, 20 Nov 2002 20:20:11 1900
Date: Wed, 20 Nov 2002 20:13:38 -0500
From: [EMAIL PROTECTED] (Albert Berry)
To: [EMAIL PROTECTED]
Subject: RE: Auto Number
MIME-Version: 1.0
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: Atlas Mailer 2.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
There are two philosophies in use here, one to ensure no gaps, and the other, to which
I subscribe, is "who cares". The latter is
that as long as the number is unique, it has no real meaning, other than as a PK on a
row of data.
There are a number of methods of forcing sequential numbering without gaps, one being
to populate a table with a long list of
numbers and zap them as they are used, picking up only the lowest.
As I said in the first paragraph, I personally do not worry about numerical gaps. In
the case where pre-numbered forms are used,
it is simple to use the form number as a SECOND key entered by the user, and use it
for lookups. I prefer an autonumbered
primary key. Depending on one's coding systems, the number may be invisible to the
user in any event.
At the current level of the Canadian dollar, my 1 and 1/2 cents worth.
Steve Johnson <[EMAIL PROTECTED]> wrote:
>To All:
>
> I have created a simple application that stores permit data in one
>table. Other tables exist as look-up tables to fill in repetitive alpha
>data in the input form using numerical codes. The input form has an
>autonumber column that generates a sequential id number. On completion of
>the last field of the form, pressing the "enter" key obviously brings up a
>new blank form with a incremented id number. Works great, especially when
>one enters 50 to 100 forms in a single session. The only problem is that
>if you entered the form by mistake, the autonumber column increments. Even
>though you exit with "discard row" the autonumber remains incremented as
>expected. The work around is to remember to exit the last instance of
>completing the form with "esc" and "save". Not very elegant, but it works.
> Now I am going to guess that it is bad form to bring up a new form without
>asking if you want to enter another form each time. I am sure there is a
>better way to control autonumber more effectively. And I want to minimize
>the additional keystrokes needed on a repetitive basis to prevent instances
>of an unwanted incremented autonumber column. Suggestions?
>
>
>Steve
--
Albert Berry
Full Time Consultant to
PSD Solutions
350 West Hubbard, Suite 210
Chicago, IL 60610
312-828-9253 Ext. 32
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
