| commit issue [message #144322] |
Wed, 26 October 2005 00:20  |
code_scavenger
Messages: 21
Registered: June 2005
|
Junior Member |
|
|
FORMS 6i
I had this button and commits when get clicked, however, I didn't see any data in the database when I tried to update a block. It goes to the PRE-UPDATE trigger, but it does not go to POST-UPDATE trigger?
Can anybody explain what happened to this? please help!
|
|
|
|
|
|
|
|
|
|
| Re: commit issue [message #144524 is a reply to message #144322] |
Wed, 26 October 2005 21:08  |
code_scavenger
Messages: 21
Registered: June 2005
|
Junior Member |
|
|
Changes I've made are exclusive to the Database only (TOAD).
As to the primary key, It is populated already. It has been setup in the forms properties to No Insert and Delete because it is intended for Update only. Insertion is made via a trigger of other table.
As I have said it worked before, so I didn't change anything with regards to the form.
All I ever changed are data on the database, and it is not even the table I changed! I only changed the user accounts table, user roles table. and that's it. Maybe the problem is the database, that is what I strongly believe, maybe it has something to do with the database direct updates i have made.
|
|
|
|
| Re: commit issue [message #144525 is a reply to message #144524] |
Wed, 26 October 2005 21:27 |
 |
djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia
|
Senior Member
Account Moderator |
|
|
Is the primary key NORMALLY populated by a number derived from a sequence? What were the primary key values you added yesterday? What is the nextval for the sequence? Did you inadvertently 'use' a number that the sequence is trying to give you thereby causing a duplicate key exception?
David
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
