Changing Primary Key troubles

PaLPiTaTioN

Hi,

I changed the primary key of an empty table and now I want to save the table definition. I receive the message "The change in the primary key definition has resulted in two records with the same primary key value". This cannot be true, because there are no records in the table. Does anybody know how I should solve this problem?

PaLPiTaTioN

Stupid me! If I would have read the whole error message, I would have seen the solution, because the table is not shared and another company has data in the table that's not unique anymore. Solved :-).

Savatage

If there is one thing I got from reading everyone's post it's that Primary Keys are not something to mess with O:)

PaLPiTaTioN

Savatage wrote:

If there is one thing I got from reading everyone's post it's that Primary Keys are not something to mess with O:)

That doesn't surprise me . But this table was designed by me a few years ago and was used only by one user en for one goal. Now, the goal is changed and so should be the table. Because I created the stuff myself en there are only two tables related, it shouldn't be a big problem here. I wouldn't just change the primary key for the Jobs table, for instance