[AccessD] Autonumber Assigned Immediately

Charlotte Foust cfoust at infostatsystems.com
Thu Sep 8 11:04:14 CDT 2005


No, it is a row identifier and therefore always points to the same row,
period.  The data in that row are entirely independent from the
autonumber, which is what leads to all the intense discussions of
"primay key" vs "unique key" vs "surrogate key", etc.  The fact that you
have used it this way doesn't make it any more valid a usage.  After
all, you can drive nails with a screwdriver too. ;->

Charlotte Foust


-----Original Message-----
From: Reuben Cummings [mailto:reuben at gfconsultants.com] 
Sent: Thursday, September 08, 2005 8:46 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Autonumber Assigned Immediately


I don't know why everyone is so adamant about no showing an autonumber.
I agree technically they shouldn't be shown.

But sometimes a simple solution is the best.  For example, we currently
have some contracts to 'digitize' a state required form for several
local counties.  Our solution to digitize is merely enter the data into
a DB we created.  However, the paper copies have to remain available.
We number every form we put in so that the user can then search and find
a paper copy by using the number generated by the software.

Initially we did this using the autonumber and it worked perfectly (we
had to abandon it to allow multiple entry persons for one county.

It is a row identifier and therefore always points to the same set of
data. If he wants to use it as an identifier let him.  I have.

Reuben Cummings
GFC, LLC
812.523.1017


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte 
> Foust
> Sent: Thursday, September 08, 2005 10:31 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Autonumber Assigned Immediately
>
>
> That doesn't make sense.  If you have pull data in from other tables 
> and populated fields in a new record, the autonumber should have been 
> assigned, so there's something you aren't telling us.  And as someone 
> else pointed out, the user should NEVER see the autonumber.  It has no

> meaning, it merely identifies a row, not the data in the row, and it 
> should not be treated as meaningful.





-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list