![ms access runtime error 3251 split database index = ms access runtime error 3251 split database index =](https://www.stellarinfo.com/blog/wp-content/uploads/2017/04/Fix-MS-Access-Database-Error-3049.jpg)
The function returns the number of tables that were changed - zero if none had the problem.
#Ms access runtime error 3251 split database index = code#
In earlier versions, Tools | Database Utilities.Īlternatively, the code below checks all tables in your database, and offers to fix any where the Seed of the AutoNumber is less than zero or below the existing values. You may be able to solve the problem with a compact/repair. Open your table in design view, select the AutoNumber field, and ensure Field Size is "Long Integer", and New Values is "Increment." (Not possible in replicated databases.) Use the code below to fix the AutoNumber.ĪutoNumber defined as Random or Replication ID.
![ms access runtime error 3251 split database index = ms access runtime error 3251 split database index =](https://img.yumpu.com/36352749/1/500x640/cache-error-reference-intersystems-documentation.jpg)
Note that this issue is more generic than the kb article suggests: it occurs any time you specify the value for the AutoNumber when appending to a linked table, not just when appending from one linked table to another. Microsoft's workaround is discussed in knowledge base article 884185.
![ms access runtime error 3251 split database index = ms access runtime error 3251 split database index =](https://www.stellarinfo.com/blog/wp-content/uploads/2015/04/6.jpg)
Use the code below to fix your AutoNumbers. Several issues can trigger this problem: CauseĪpply JET 4 Service Pack (7 or later) to prevent the problem recurring. The attempt to assign a duplicate fails if the field is primary key, so it may not be possible to save new records in an affected table. In Access 2000 and later, an AutoNumber field may begin assigning extreme values, negatives, and even duplicates. Fixing AutoNumbers when Access assigns negatives or duplicates