Error after changing values in a table

More
8 years 2 weeks ago #13724 by julian.wallasch
Hi,

I'm using Version 5.3.1.16 of ATE.
I get an error after changing values in a table.
I detected that it is an issue with the primary keys.
In the SQL statement of the table I selected two substrings and defined both of them as primary key. If only one of the primary keys is a substring the error disappears.
This is the error:


It says: "The key column information is insufficient or incorrect. The update affects too many records."

In Version 5.2.3.6 the usage of substrings as primary keys worked without the error.

Best Regards

Julian
Attachments:

Please Log in or Create an account to join the conversation.

More
8 years 2 weeks ago #13725 by Peter.Jonson
What is the database you are updating data in?

Peter Jonson
ETL Developer

Please Log in or Create an account to join the conversation.

More
8 years 2 weeks ago #13726 by julian.wallasch
It is SQL Server 2005.

Please Log in or Create an account to join the conversation.

More
8 years 2 weeks ago #13727 by Peter.Jonson
Ever week people tell us "But it was working with previous version" . B)
and the answer it s always the same "your data is now different".

The message you are getting is from Ole DB provider.
There is nothing our programmers can do to to resolve it.

You have to check and correct your data.

I assume that you defined the primary key within Active Table Editor.

Have you checked your data for duplication?
select primary-key,count(*) from table primary-key group by having count(*)>1.

Do you have primary key defined in the database?
If not eventually you will have problems

Are you pulling your data from multiple tables?
Although it looks like it is working quite often OleDB fails to update the data, so you have to be very careful with it

Peter Jonson
ETL Developer
The following user(s) said Thank You: julian.wallasch

Please Log in or Create an account to join the conversation.

More
8 years 2 weeks ago #13728 by julian.wallasch
Thank you for your quick reply.
As you said, I did not have a primary key defined in the database.
After I defined a primary key in the database, everything works fine.

Best Regards

Julian

Please Log in or Create an account to join the conversation.