[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.