So I have an sql table that is shared with ArcMap and a 3rd party application. Both applications need to edit/insert rows. The 3rd party application uses the auto sql Identity = ON to use the sql server's method of generating new ID's on insert. ArcGIS on the other hand uses some internal counter method to generate the next id.
What happens is, when the 3rd party app inserts a row, a new ID gets generated, lets say 1000 and the row is inserted. But ArcMap's counter isn't updated, so when ArcMap tries to insert a row using its internal counter, it tries to insert with id=1000 also, and receives a duplicate key error.
A) Can I reset arcmap's counter to the new value?
B) Is there a better method I should use instead?