[AccessD] More Strange Autonumber Behavior - Access 2002 (aka Access XP)

Randall R Anthony RRANTHON at sentara.com
Fri Jan 6 06:25:31 CST 2006


You would force me to look it up.  Access2.0.  And in more than one
instance.  ee-eefff

>>> Lambert.Heenan at aig.com 01/05/06 4:37 PM >>>
In every version of Acces that I have used AutoNumber fields can be
either
Long Integers or Replication IDs. How could you have set one to an
Integer?

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Randall R
Anthony
Sent: Thursday, January 05, 2006 3:38 PM
To: accessd at databaseadvisors.com 
Subject: Re: [AccessD] More Strange Autonumber Behavior - Access 2002
(aka
Access XP)


I had a similar problem, however it was dumb developer related.  I had
the
autonumber set to integer, which ran out at 32 thousand whatever. 
Changing the field size to Long Integer fixed it.

>>> Lambert.Heenan at aig.com 01/05/06 3:18 PM >>>
I started to get error messages from one application telling me ...

"Error 3022 : The changes you requested to the table were not
successful
because they would create duplicate values in the index, primary key,
or
relationship.  Change the data in the field or fields that contain
duplicate
data, remove the index, or redefine the index to permit duplicate
entries
and try again."
<snip>
-- 
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