V Rickert wrote:Is there an APEX dimension to this? If so, tell us the full APEX and DB versions, and provide full details of what the APEX app is doing (a debug trace of page accept processing is the obvious place to start).
What would cause Oracle to insert duplicate rows into a table? Could a join of two tables in the initial query assigned to an application page cause ORacle to insert an extra row into a table when an update to data value occurs? I have no insert triggers and no foreign keys assigned to the table. I am not sure what would cause Oracle to assume that an insert of a row must occur. I want to prevent that insert.
What would cause Oracle to insert duplicate rows into a table?Nothing. It's is the programmer that created bad code (if duplicate rows are not supposed to be inserted). If there is no table trigger, than some other code must be responsible for the insert.
If the user, however, needs to change the work order, then APEX creates another row instead of updating the current row.What kind of page did you create in Apex? Is it a form with report based on the INVOICE table?
a unique composite key/index was created on Invoice, Vendor, and Work OrderIs Invoice the sequence generated invoice number (the PK)? In that case creating a unique index on these 3 columns is not very useful, since Invoice is already always unique. Not that this would explain your duplicate record, though.
where you 'Add a Row'So, you are adding a row? Before you had a problem with updating a row.
I think I need a unique index on Invoice_number to prevent the 'duplicates'?You could do that, but it will just give you an error message. However, it could point to the process that is trying to insert a record when you are only updating a record.
a form with report based upon a sql query of the Invoice TableSo, you are not using the INVOICE table directly as a source? What is the query you are using? It's not a view by any chance, with INSTEAD OF triggers?