RAISE FORM_TRIGGER_FAILURE is not working

I am customizing a medical form with two blocks: cov_med_prem_header and cov_med_prem_lines. When user select emp_group from header, the list of medical program with end_date = '31-DEC-4712' will show at the detail block. Once a year at the open enrollment, HR will end date the previous year's program and enter the same programs but with different premium, also set the end_date = '31-DEC-4712'. In order to prevent user from enter to the wrong record, I added when-validate-record trigger for the detail block:
declare
max_effective_end_date DATE;
begin
select effective_end_date
into max_effective_end_date
from cov.cov_medical_premiums
where emp_group = :cov_med_prem_header.emp_group
and coverage_type = :cov_med_prem_lines.coverage_type
and part_time = :cov_med_prem_lines.part_time
and med_provider = :cov_med_prem_lines.med_provider
and sysdate between effective_start_date and effective_end_date;
if (:system.record_status = 'INSERT') and (max_effective_end_date = '31-DEC-4712') then
MESSAGE ('YOU HAVE ENDTERED THE WRONG RECORD. PLEASE CHECK AND TRY AGAIN!');
RAISE FORM_TRIGGER_FAILURE;
end if;
exception
when others then null;
end;
But the RAISE FORM_TRIGGER_FAILURE is not working because the exception, but if I take out the exception part, I am not able to insert into the form, message like unhandled exception.
Can anyone help with this? Thanks.

Hi,
There should not be an Exception part if you are using Form_Trigger_failure. So first find out what exception you are getting with the code, commenting out the raise form_trigger_failure. And first handle that, and then remove the exception part and use form_trigger _failure                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

Similar Messages

  • Raise form_trigger_failure is not working in multi-record block?

    raise form_trigger_failure is not working in multi-record block.
    Why?
    I am using Form 9i.
    Thanks and regards,
    Vikas

    Here is my code. Workorder_master is single block, workorder_dtls is multi-block.
    This code is written in KEY-NEXT-ITEM of labour_code in workorder_dtls.
    If suspended labour, invalid labour etc. is selected then it should not leave labour_code, but does not happen as I like. What will be the solution?
    DECLARE
    v_count                         NUMBER;
    v_status                    CHAR(1);
    v_workorder_no     VARCHAR2(15);
    v_pass_no                    VARCHAR2(15);
    v_rec_pos                    NUMBER;
    BEGIN
         IF :workorder_dtls.labour_code IS NOT NULL THEN
              v_rec_pos := :SYSTEM.CURSOR_RECORD;
              SELECT COUNT(*) INTO v_count FROM labour_master
                                  WHERE labour_code = :workorder_dtls.labour_code;
              IF v_count > 0 THEN --if labour exist.
                   SELECT status INTO v_status FROM labour_master
                                  WHERE labour_code = :workorder_dtls.labour_code;
                   IF v_status = 'I' THEN--'I' stands for busy.
                        --check if labour is for extension i.e. if labour is working for same workorder
                        SELECT COUNT(*) INTO v_count FROM workorder_dtls
                                            WHERE labour_code = :workorder_dtls.labour_code
                                            AND workorder_no = :workorder_dtls.workorder_no
                                            AND to_dt <= SYSDATE;
                        IF v_count > 0 THEN
                             --if working in same workorder then for extension, then give from_dt, to_dt
                             SELECT MAX(TO_DT)+1 INTO :workorder_dtls.from_dt FROM workorder_dtls
                                                 WHERE labour_code = :workorder_dtls.labour_code
                                                 AND workorder_no = :workorder_dtls.workorder_no
                                                 AND to_dt <= SYSDATE;
                        ELSE
                             --if not working in same workorder then give message.
                             SELECT workorder_no, pass_no INTO v_workorder_no, v_pass_no FROM workorder_dtls
                                                 WHERE labour_code = :workorder_dtls.labour_code
                                                 AND to_dt <= SYSDATE;
                             MESSAGE('This labour is already working through workorder no. '||v_workorder_no||' using pass '||v_pass_no);
                             MESSAGE('This labour is already working through workorder no. '||v_workorder_no||' using pass '||v_pass_no);
                             RAISE FORM_TRIGGER_FAILURE;
                        END IF;
                   ELSIF v_status = 'A' THEN--'A' stands for available.
                        :workorder_dtls.from_dt := SYSDATE;
                   ELSIF v_status = 'H' THEN--'H' stands for help-up.
                             SELECT workorder_no, pass_no INTO v_workorder_no, v_pass_no FROM workorder_dtls
                                                 WHERE labour_code = :workorder_dtls.labour_code
                                                 AND to_dt <= SYSDATE;
                        MESSAGE('This labour has been held-up for not submitting gatepass.');
                        MESSAGE('This labour has been held-up for not submitting gatepass.');
                        RAISE FORM_TRIGGER_FAILURE;
                   ELSIF v_status = 'S' THEN--'S' stands for suspend.
                             SELECT workorder_no, pass_no INTO v_workorder_no, v_pass_no FROM workorder_dtls
                                                 WHERE labour_code = :workorder_dtls.labour_code
                                                 AND to_dt <= SYSDATE;
                        MESSAGE('This labour has been suspended through workorder no. '||v_workorder_no||' using pass '||v_pass_no);
                        MESSAGE('This labour has been suspended through workorder no. '||v_workorder_no||' using pass '||v_pass_no);
                        RAISE FORM_TRIGGER_FAILURE;
                   END IF;
                   IF v_status IN ('A', 'I') THEN
                        :BLK_TEMP_WORKORDER.LABOUR_CODE := :WORKORDER_DTLS.LABOUR_CODE;     
                        GO_BLOCK('WORKORDER_DTLS_IMG');
                        EXECUTE_QUERY(NO_VALIDATE);      
                        GO_RECORD(v_rec_pos);
                        GO_ITEM('WORKORDER_DTLS.FROM_DT');
                        IF :workorder_dtls.from_dt + 180 <= :workorder_master.to_dt THEN
                             :workorder_dtls.to_dt := :workorder_dtls.from_dt + 180;
                        ELSE
                             :workorder_dtls.to_dt := :workorder_master.to_dt;
                        END IF;
                   END IF;
              ELSE --if labour does not exist.
                   MESSAGE('Invalid labour code');
                   RAISE FORM_TRIGGER_FAILURE;
              END IF;
         END IF;
    END;

  • Raise form_trigger_failure does not work in when-timer-expired trigger

    hi everbody,
    i create timer (no repeat) in when-validate-item trigger for an item then in timer i use raise form_trigger_failure for not posting related item.but raise form_trigger_failure not work in timer and cursor go next item ? do you say anything for that ? thanks..

    when your validation runs ok, then and only then you should create the timer and in the WTE you navigate to the other item.
    Think about: The WTE-trigger runs after the when-validate-item. It runs not within the WVI. That's the reason why you cannot cancel the WVI with the WTE.
    Only the WTE can be stopped with the Form_Trigger_Failure.

  • Raise form_trigger_failure do not work

    Hi,
    I catch an error in on-error trigger and raise form_trigger_failure, this should be triggered when user clic <ok> button, that works, but in this screen user can go to menu and use another option that opens another screen, when user do that, the error message is displayed but form_trigger_failure do not raise and this another screen can be opened, does someone has any idea on how to fix it? Thanks.

    RAISED_FORM_TRIGGER_FAILURE will trigger only for the form whish has that command. So it will not failed when user navigate to anotyher form.
    What you want to do is if you get this message then poup a modal window and show the error. So at that time user unable to goto any other form because they can not navigate to any other window other than the modal window with the error
    Thanks
    * if this is correct/helpful then please mark it

  • Raise FORM_TRIGGER_FAILURE don't work well.

    Dear All,
    I'm facing a problem that I can't understand well.
    I have a screen that contain two fields: Field1 and Field2.
    The control I had to add: is to avoid saving duplicate records, and also do not save a record if one of these fields is empty.
    I wrote the trigger KEY_COMMIT, where I did:
    Line: -----
    declare
         x number;
         ret number;
    begin
    if ( (:Field1 is null ) and (:Field2 is null ) ) then
         ret:=msgbox('Please choos a Field1 and Field2');
                   RAISE FORM_TRIGGER_FAILURE;      
    else if ( (:Field1 is null ) or (:Field2 is null ) ) then
         ret:=msgbox('Please Enter Field1 and Field2');
                   RAISE FORM_TRIGGER_FAILURE;
                   else
                        begin
                        select count(*) into x from TABLE1 where xxxxxxxx=:Field1;
                        exception when others then
                             x:=0;
                        end;
                        if x>0 then
                             ret:=msgbox('Field1 Already Registred');
                             :Field2:='';
                                                 RAISE FORM_TRIGGER_FAILURE;
                        else
                             commit;
                        end if;
    end if;
    end if;
    end;
    Line: -----
    The problem in that is when I click on EXIT button, I get this message: " Do you want to save all modifications you made? "
    If I click YES => I find in te table TABLE1 that, also the records having one of the above fields empty, are saved.
    How Come?
    As I know, Raise FORM_TRIGGER_FAILURE must stop the trigger and then, no commit. It's not the case !
    Can someone help me in that? Did I wrote the wrong trigger ?
    Many Thanks for your help.
    Imad QANDOUCI

    you wrote an KEY-COMMIT Trigger. But you press KEY-EXIT. Why should KEY-COMMIT Trigger fire on KEY-EXIT?
    Put your checks to PRE-INSERT and PRE-UPDATE triggers (to both!). Best, avoid duplicate code by writing a procedure consisting the checks and coll the procedure in the triggers.

  • Siri - Raise to speak not working

    I recently upgraded to iOS 7.0.3 after which raise to speak in Siri is not working. Please help

    Hi satish12,
    Welcome to the Support Communities!
    Here are a couple of things to try to address this issue:
    iOS: Turning off and on (restarting) and resetting
    http://support.apple.com/kb/HT1430
    If that does not resolve the issue, refer to page 146 in the iPhone User Guide to Reset All Settings:
    iPhone User Guide for iOS 7
    manuals.info.apple.com/MANUALS/1000/MA1565/en_US/iphone_user_guide.pdf
    iOS: Troubleshooting Siri
    http://support.apple.com/kb/TS4079
    Cheers,
    - Judy

  • "Raise to Speak" not working on iPhone 4s

    I got my Iphone 4s today. Everything works fine except for the "Raise to Speak" feature. I have it turned on in the Siri settings but there is nothing that I can do to get Siri to start when I raise the phone to my ear. Really frustrating. I have been on the phone with Apple's support and so far nothing that they proposed worked. We tried rebooting the phone, turning the phoe off and on again, and turning the raise to speak setting on and off.  Anybody having the same problem?

    I think I got it to work fine now. Everything depends on the kind of moviment you do to raise your phone to your ear. If you have your arm straight down and move the phone to your ear it does not work. It works with shorter moviments. I hold the phone in front of me as if I am reading the screen with my arm bended in 90 degrees. I bring the phone to the ear and it works like a sharm every time.
    How did I founf that out? I went to the Apple store and I was able to see that everybody was having dificulty with using the feature. We tried several phones and it seemed to work randomly. After spending a lot of time behaving like an idiot moving the phone up and down thousands of times  I sat down and it started to work much better. That was when I realized that it was working better because I was not moving the phone from all the way down but from much closer to my chest.
    Now some important information. First, the raise to speak feature works from any screen that is on, even from active application screens. For example, when reading a message, I raised the phone to my ear and it worked fine.  At the apple store, some of the apple advisors thought that it would only work if you were already in the Siri screen, which is not true.
    Second, I have to say that I actually got my phone replaced just in case it was a hardware issue. However, I tried the new phone still using the long moviments and the raise to speak feature would not work. I changed to the short moviment I described before and everything worked fine. I am convinced that it is not a hardware problem.
    I hope this helps. Enjoy your new Iphone 4s.

  • BPM-Raise Exception does not work

    I have designed the BPM in following way.
    1. Receive step - Receive Asynchronous message
    2. Defined the Block - DB
    3. Send step 'A'  to JDBC - inside the Block-'DB' - Acknowledgement-Transport, Exceptions System Error-DB, Receiver from-Send context.
    4. Created an exception handler and Selected 'DB' as exception handler for the property of the exception handler branch.
    5. Inserted the Send step-'B' to send mail inside the exception handler branch by using the MAIL receiver adapter.
    We want send the message to update database by using JDBC adapter but if it fails to update database then we want send an e-mail to outlook.
    But it looks like it is not working when it fails to update database.
    Can someone please help me?
    Thanks in advance!

    Hi,
    According to the SAP online help documentation for the receiver JDBC adapter:
    <i>The receiver JDBC adapter supports system acknowledgments but not application acknowledgments.</i>
    What you will need to do is either get a system error triggerred by the adapter (which basically throws up the red flag and tells XI that the message could ot be delivered successfully) , or get the application to trigger a fault message back to the adapter. I have not worked with the JDBC adapter, so I cant tell you in more detail.
    Here are some links that I have been able to find that might help you...
    Statuses in the monitor :
    http://help.sap.com/saphelp_nw04/helpdata/en/ea/2f053d39177608e10000000a114084/frameset.htm
    Dealing with Exceptions in BPM
    http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm
    Cheers
    Manish

  • Siri 'Raise to Speak' not working with iPhone 5S

    Didn't work, did a restore, still doesn't work. The basic 'raise to face' function is working since my phone goes dark when I'm talking with it.
    Guess the first question would be 'Is it working for anyone with a 5S'.
    If it is I guess a trip to the Genius Bar is in order.

    Apple has not made any statements about why they removed that feature. Speculation is prohibited. However, the fact that there is a new feature that allows you to raise the phone to make a recording in iMessages may be related.
    Submit your feedback requesting the return of the feature directly to Apple using the appropriate link on the Feedback page:
    http://www.apple.com/feedback

  • "raise to speak" not working on iPhone 6

    My son was very upset when he discovered that the "raise to speak" feature no long works on iPhone 6 or if you updated your iOS to 8. The issue seems to be that Siri comes through only on speaker and not the phone so there is no privacy when using Siri.
    Can you tell me whether you know or have information that Apple will restore the "raise to speak" functionality in an iOS update? It really doesn't make sense that they took it out.

    Apple has not made any statements about why they removed that feature. Speculation is prohibited. However, the fact that there is a new feature that allows you to raise the phone to make a recording in iMessages may be related.
    Submit your feedback requesting the return of the feature directly to Apple using the appropriate link on the Feedback page:
    http://www.apple.com/feedback

  • Raise Trigger form failure not working

    Hi everybody,
    I'm working with form builder 10g. And in my form, I have a button for save.
    The issue is that I have a validation in the pre-insert trigger of a block where I am validating a particular record and in my preinsert trigger on a given condition, I'm raising a Form_trigger_failure.
    Even when the condition is encountered in my pre-insert the flow of the program in not stopping.
    But when I'm clicking on the default save button on the toolbar.. the flow of the program is stopped.
    Here is the code on my save button:
    :system.message_level:=5;
    commit_form;
    :system.message_level:=0;
    IF Form_Success THEN
    message('saved succesfully');
    else
    RAISE form_trigger_failure;
    END IF;
    Edited by: Amlesh on May 14, 2010 4:42 PM

    Hi,
    I have same issue, have you got any solution,
    I have in my pre-insert trigger
    if NVL (:COUNT_HEADER, 0) <= 0 THEN
         Msg_Alert ('Enter Call Details !','I',FALSE);
         RAISE Form_Trigger_Failure;
    else
         select nvl(max(HCH_CALL_ID),0)+1 into :HCH_CALL_ID
                   from HLP_CALL_HEADER;
         Msg_Alert ('The generated Call ID:'||:HCH_CALL_ID,'I',FALSE);
                   :HCH_ORGN := :Global.orgn;
                   :HCH_CRT_ON := sysdate;
                   :HCH_UPD_ON := sysdate;
                   :HCH_CRT_BY := :Global.usr;
                   :HCH_UPD_BY := :Global.usr;
    end if;Even though the alert, 'Enter Call Details', is shown, the flow of the form is not getting stopped.
    it seems Raise Form_trigger_Failure is not working
    I have in key-comit trigger
    commit_form;
      IF FORM_SUCCESS THEN
           msg_alert('form success','I',FALSE);
         CLEAR_FORM(NO_VALIDATE);
         EXECUTE_TRIGGER('PRE-FORM');
      END IF;and it shows form success
    Any help will be appreciated
    Thanks

  • Buitin RAISE FORM_TRIGGER_FAILURE not working in forms Personalization

    Hi,
    I create a SIT where i dn't want user to create more than 1 record. I successfully able to set the condition and popup error message in action tab when more than 1 record is entered by the user. Now I want to stop further processing and for that purpose I use built-in RAISE FORM_TRIGGER_FAILURE. But it won't work and user can able to process further easily.
    Can any one guide me how I acheive this using forms personalization?

    Pl see ML Doc 420518.1 on why this does not work
    HTH
    Srini

  • Raise Form_Trigger_Failure Not Working

    On my form I have a button. This button updates 3 base table items from it's when-button-pressed trigger.
    My problem is that when another user comes along and clicks the button for the same record before a previous user has committed their changes the following messages are displayed 3 times (once for each item that the button attempts to update fields?):
    1. Could not reserve record (2 tries). Keep trying?
    2. FRM-40501: ORACLE error: unable to reserve record for update or delete
    My desired result would be that these messages only appear once regardless of how many items the button attempts to update and that the form processing would be stopped after the first messages are displayed. This isn't happening.
    To try to accomplish this I am using an On-Error trigger to capture the FRM-40501 error message and instead display my own custom message followed by "Raise Form_Trigger_Failure".
    Despite the On-Error trigger displaying my custom message successfully, the "Raise Form_Trigger_Failure" doesn't seem to stop the form from processing the remaining code in the when-button-pressed trigger. These messages still appear multiple times in a row and the remainder of the when-button-pressed trigger code continues to run.
    So my question is why isn't my "Raise Form_Trigger_Failure" working to suppress subsequent messages? Is there a way I can address this?
    Any help would be greatly appreciated. Thanks.
    Edited by: sharpe on Jul 13, 2012 9:39 AM

    The FORM_TRIGGER_FAILURE in the ON-ERROR-trigger will not stop the code in your WHEN-BUTTON-PRESSED-trigger. Could you post the code from your trigger?

  • RAISE form_trigger_failure not working in purchase order form

    Hi,
    I am working on a customization in Purchase Order Form (poxpoepo)
    This is what I tried to do.
    CURSOR 1_cur IS
    SELECT pol.LINE_NUM v_line
    ,gcc.segment1 v_seg
    FROM gl_code_combinations gcc
    ,PO_DISTRIBUTIONS_ALL pod
    ,po_lines_all pol
    WHERE SUBSTR(gcc.SEGMENT1,1,1) = 'X'
    AND gcc.code_combination_id = pod.code_combination_id
    AND pod.PO_LINE_ID = pol.PO_LINE_ID
    AND pol.po_line_id = v_po_line
    AND pol.PO_HEADER_ID = v_po_header;
    CURSOR 2_cur IS
    SELECT pol.LINE_NUM v_line
    ,gcc.segment1 v_seg
    FROM gl_code_combinations gcc
    ,PO_DISTRIBUTIONS_ALL pod
    ,po_lines_all pol
    WHERE SUBSTR(gcc.SEGMENT1,1,1) = 'X'
    AND gcc.code_combination_id = pod.code_combination_id
    AND pod.PO_LINE_ID = pol.PO_LINE_ID
    AND pol.PO_HEADER_ID = v_po_header;
    BEGIN
    v_error_found := false ;
    IF (form_name = 'POXPOEPO' AND
    (block_name IN ('PO_LINES' ,
    'PO_SHIPMENTS',
    'PO_DISTRIBUTIONS') AND
    event_name = 'WHEN-NEW-ITEM-INSTANCE') OR
    (block_name = 'PO_HEADERS' AND
    event_name = 'WHEN-NEW-RECORD-INSTANCE' AND
    name_in('SYSTEM.BLOCK_STATUS') = 'QUERY' ) OR
    (block_name = 'PO_APPROVE' AND
    event_name = 'WHEN-NEW-BLOCK-INSTANCE' )
    ) AND
    NAME_IN('PO_LINES.PO_HEADER_ID') IS NOT NULL AND
    NAME_IN('PO_LINES.PO_LINE_ID') IS NOT NULL AND
    name_in('PO_LINES.LINE_NUM') >= 1 ) THEN
    v_po_header_id := NAME_IN('PO_LINES.PO_HEADER_ID');
    v_po_line_id := NAME_IN('PO_LINES.PO_LINE_ID');
    v_line_num := NAME_IN('PO_LINES.LINE_NUM');
    IF block_name in ('PO_LINES' , 'PO_SHIPMENTS', 'PO_DISTRIBUTIONS') THEN
    v_seg := null;
    FOR cursor1 in 1_cur
    LOOP
    if cursor1.v_seg = 'X' THEN
    v_seg := 'X';
    v_line_num := cursor1.v_line;
    EXIT;
    end if;
    END LOOP;
    ELSIF block_name in ('PO_HEADERS','PO_APPROVE') THEN
    FOR cursor2 in 2_cur
    LOOP
    if cursor2.v_seg = 'X' THEN
    v_seg := 'X';
    v_line_num := cursor2.v_line;
    EXIT;
    end if;
    END LOOP;
    END IF;
    IF v_seg = 'X' then
    fnd_message.set_string('custom message to be displayed.');
    FND_MESSAGE.ERROR;
    IF block_name = 'PO_APPROVE' THEN
    go_block('PO_HEADERS');
    raise form_trigger_failure;
    END IF;
    END IF;
    END IF;
    END;
    I actually want to achieve somewhat like this. When ever the charge account field start with 'X' or in other words if segment1 is 'X' and if changes are made to that line like note to supplier is changed and saved then the user should not be allowed to approve/reapprove the order and it shall pop up the message and ONLY restrict from going further if the user hits the APPROVE button. Highlighted in bold should have actually taken care of the requirement from proceeding to the next level of approval but it is not. I have had several debug messages and I am pretty sure that it is satisfying the condition of going to the PO_APPROVE block and still not raising form trigger failure. Could you please help me handle this scenario?

    Your Raise works -- it will terminate your procedure, Change_Detail_Block_Status.
    But, how are you calling the procedure? It is in THAT place that you should look for your problem.
    If you call the procedure, and then have coded EXCEPTION WHEN OTHERS THEN.... or something similar, you might be ignoring the "Raise FTF".
    In addition, you probably need to add these lines in your form where navigation or a commit or similar code causes a trigger to call your procedure:
    If not Form_Success then
    Raise Form_Trigger_Failure;
    End if;

  • Raise form_trigger_failure not wokring on validate records

    hi,
    I wrotea block level trigger WHEN-VALIDATE-RECORD, which do some screen level validation and
    in case of failure i use RAISE FORM_TRIGGER_FAILURE. working fine if i move records
    another trigger is KEY-COMMIT on form level.
    which calling a program unit where a command is FIRST_RECORD
    now when i save the records using the save button
    its call FIRST_RECORD, because of this command its executing WHEN-VALIDATE-ITEM
    and execute RAISE FORM-TRIGGER-FAILURE
    but system continue the executaion and jump back to key-commit triiger
    why WHEN-VALIDATE-RECORDS 's raise is not working...
    thanks

    hi
    its call FIRST_RECORD, because of this command its executing WHEN-VALIDATE-ITEM
    another trigger is KEY-COMMIT on form level.
    and execute RAISE FORM-TRIGGER-FAILURE
    If when-validate-item trigger is not set at item-level plz set it at item-level and check.
    set key-commit-trigger at block level.
    may it helps u.
    sarah

Maybe you are looking for

  • Itunes shuts down on optimizing photos during sync

    Hello So when I connect my iPad it begins to sync and it goes through steps 1-5 with no problem.  when it gets to step 6 it says it is optimizing photos 1-17 and every time it gets to number 13 or 14 windows dialog shows up and says itunes has to clo

  • R6034 and Auto-Analyzer problems in Photoshop Elements 9.0

    When I start the organizer of Photoshop Elements 9.0 I get an error that says: Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\Program File... R6034 An application has made an attempt to load the C runtime library incorrectly. Please

  • Design view not showing actual layout

    I have a test page where I have a navigation div element created and it floats to the left. When I preview the page in IE, this navigation div element shows up as it should on the left part of the page but in the Design view of Dreamweaver CS3, the n

  • LSMW, to upload material sales long text , MM02

    Hi I have not been able to upload long the long text of the material master record related to view Sales text (see tcode MM02). The upload should use the tcode LSMW, below is the steps that I used to create my LSMW codes: Step 1: Maintain Object attr

  • Elements 6.0- Suddenly can't open a file

    This is a sudden development, as Photoshop Elements 6.0 has been working fine for years. I am able to open the program, but as soon as I try to open any sort of file, even a new one, it no longer responds. Any suggestions? I have no idea what is caus