- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi @alik98709228,
This can happen when your sequence (xtkNewId) has gone to its maximum value and started over at 0. Whenever that sequence catches up to the lowest ID present in your table, you will receive this error. This will be the case for ALL native tables though (with the excpetion of delivery logs), so it's a big issue.
If you're working in v6, that sequence is a 32bit integer, so it's capped at +- 2.100.000.000. I solved this issue myself by adapting the sequence and the primary key of my table to a 64bit int. A quick fix can also be to reset the sequence to 0 and let it go into negative numbers, although this is not recommended.