hockeyfan21
Registered User.
- Local time
- Today, 02:38
- Joined
- Aug 31, 2011
- Messages
- 38
I have a temp table with an Autonumber PK field "EntryID" set to "no duplicates". The database is split with users having their own copy of the frontend on their desktops and the temp table is stored in a single backend.
Can anyone tell me why it is jumping numbers so drastically when users are uploading new records to the temp table?
For example - A group of records created on 10/14 started with an autonumber of 3149154 and, after about 30 additional records, the 31'st was assigned autonumber 8043206 and today it is assigning #'s like 12,742,724. I've never seen this before. Does it have something to do with multiple users hitting the same backend tables??
I am wondering what the potential downfalls of this could be - will it hit a certain # of integers and start erroring out. From the inception of the database, we only have a total of around 30000 records ever entered.
Thanks,
Toni
Can anyone tell me why it is jumping numbers so drastically when users are uploading new records to the temp table?
For example - A group of records created on 10/14 started with an autonumber of 3149154 and, after about 30 additional records, the 31'st was assigned autonumber 8043206 and today it is assigning #'s like 12,742,724. I've never seen this before. Does it have something to do with multiple users hitting the same backend tables??
I am wondering what the potential downfalls of this could be - will it hit a certain # of integers and start erroring out. From the inception of the database, we only have a total of around 30000 records ever entered.
Thanks,
Toni