Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 2 of 2 total |
Key violation but there is not key |
Fri, Dec 7 2007 10:55 AM | Permanent Link |
revort | Occasionally I'm getting the following error. There is no contraint or primary key on this table, what is causing this and how can I avoid this problem.
thanks randy ElevateDB Error #1004 The primary key constraint __PrimaryKey has been violated (Duplicate key 6317 found) |
Fri, Dec 7 2007 3:33 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Randy,
<< Occasionally I'm getting the following error. There is no contraint or primary key on this table, what is causing this and how can I avoid this problem. >> Repair the table - most likely it is corrupted. There is an internal primary key on the RowID when you don't explicitly define one, and you should never run into duplicate RowID values unless the table/indexes have been corrupted. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |