Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 5 of 5 total

Thu, Nov 15 2007 9:02 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Tim Running a migrate from DBISAM4, a good way through and past the tables with a lot of data I get ElevateDB Error #1004 The primary key constraint PrimaryKey has been viollated (NULL values are not allowed in a primary key) It would be really nice if I knew which table Roy Lambert ps I did figure it out eventually
Thu, Nov 15 2007 9:07 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Tim Just a comment - these sort of things are where it would be nice to import a singe table rather than the database. Roy Lambert
Thu, Nov 15 2007 5:06 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Roy, << Running a migrate from DBISAM4, a good way through and past the tables with a lot of data I get ElevateDB Error #1004 The primary key constraint PrimaryKey has been viollated (NULL values are not allowed in a primary key) It would be really nice if I knew which table >> It should be the last table in the list of tables that are in the database. -- Tim Young Elevate Software www.elevatesoft.com
Fri, Nov 16 2007 2:48 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Tim >It should be the last table in the list of tables that are in the database. It was, but I sill think we should be told in the error message. Roy Lambert
Fri, Nov 16 2007 6:08 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Roy, << It was, but I sill think we should be told in the error message. >> Well, normally you shouldn't get a constraint error message during a migration. The one situation you came across is the only one I can think of apart from having a corrupted source table. However, I'll see what I can do. -- Tim Young Elevate Software www.elevatesoft.com