Multiuser apps cannot use auitonumber w/o some corruption - at least where new records are added by more than one user. The more generic soloution is to change the Autonumber to a different 'type'. See {F1} topic "Autonumber" for some info on this. Search these fora (Tek-Tips) for a number of discussions re the concept. See faq700-184 for an alternative soloution to retain SOME semblance of order in a promary key field.
Autonumnber -in ALL its' incarnations (types) does not lock the source of the value, so it is ALWAYS possible for two (or more) users entering data (new records) to have a 'collision' in the retrieval / incrementing of the value. When this occurs, the more common 'failuure' is a simple error message 'duplicate key value ...) which may be bypassed with a re-try (programmatically). On occassion, the error appears to not actually get traped and some record corruption occurs.
MichaelRed
m.red@att.net
Searching for employment in all the wrong places