TAB CANVAS PROBLEM

Question

hiiii
in one of the tabs in a TAB CANVAS ... am trying to insert some fields into a table .. a simple insert statement ... BUT in each time i got in the message bar(UNABLE TO INSERT RECORD)
and when i disply the error i got (ORA-00001: unique constraint (DIZZYLAND.ADMINS_PK) violated) ... the strange thing is that
am not trying to insert in this table (ADMINS) ...
AND the alert() appears ???!!!!!
here is the procedure that is called in WHEN_BUTTON_PRESSED trigger
PROCEDURE SEND_EMP_STD_COMM IS
std_f_name varchar2(50);
std_l_name varchar2(50);
std_id NUMBER(4,0);
ALERT_ID number;
BEGIN
select SID,F_NAME,LAST_NAME into std_id,std_f_name,std_l_name from student where user_name= :TEXT_ITEM777;
     insert into STUDENT_COMMENTS(
     SID,
     SENDER,
     SENT_DATE,
     COMMENT_TEXT,
     USER_TYPE
     values(
     3,
     :ADMIN_COMMENTS_BLOCK2.TEXT_ITEM776,
     TO_DATE(sysdate, 'DD-MON-YYYY HH24:MI:SS'),
     :ADMIN_COMMENTS_BLOCK2.TEXT_ITEM778,
     'A'
     commit;
     set_alert_property('CONFIRMATION_ALERT',alert_message_text,'Comment Has Been Sent Successfully To '||std_f_name||' '||std_f_name);
     alert_id:=SHOW_ALERT('CONFIRMATION_ALERT');
END;
*******************************************************************************************

Answer 1

Consider the usage of the commit statement.
It is possible that you are displaying the data in a form which is in insert mode.
When you issue commit, the program may be trying to insert the data twice. Once at the form level and again at sql level. You can determine this using debug with a breakpoint set at the button press.
My personal preference is to used forms_ddl( 'commit' ) to commit sql code and commit_form for forms. Generally, I avoid mixing the two when possible, for the reasons you describe.