What does the message “No primary key defined on table name; you are unable to update records after migration.” mean?
This error message occurs because the specified table does not have a primary key defined on it. Jet requires a primary key on tables in Oracle databases in order to support dynasets against those tables. If the Oracle database table does not have a primary key, Jet only opens a non-editable snapshot on the table. It is possible to define a table in Microsoft Access that you can update yet does not have a primary key. When you migrate the table to an Oracle database, it does not have a primary key; therefore, the Jet engine is unable to update it. If you want to update the contents of the table through the Jet engine, do one of the following: Ensure that the original Microsoft Access table has a primary key defined on it. You then must re-capture the Microsoft Access database. Define a primary key on the migrated Oracle database table before you use the Migration Workbench to modify the Microsoft Access database. See Also: For more information on Microsoft Jet error messages, see the M
Related Questions
- What does the message "No primary key defined on table name; you are unable to update records after migration." mean?
- What does the message Insufficient Encryption: This document requires a larger secret key size mean?
- When adding a member, why do I receive the error message Primary or foreign key is not unique?
