HP TRIM 7.3.3 5645 , Win 7, MS Office 2010 Win 2008-R2.
After the recent upgrade from 7.1 it has been noticed the increased number of those primary key violation errors . E.g. certain field in a table cannot be updated as it is the PK
What would be the major cause for this happening?
For 2 years we did not have any of these errors.
As the results, TRIM crashes and also, the record (File or a document) is made without the information about the CREATOR?
Did the schema upgrade successfully?
This one might be easier to address in a support case.
I am back, very busy. Apologies for not replaying.
In short, We submited the case to HP. Log files will show the error.