Error in updating records brought by LOV

Hi everybody
I am using Oracle 10 g
when fetching data from the database by choosing a specific record from LOV then trying to make "save" means "commit" I have this error
FRM-40509: Oracle error: unable to update record
I think there is a problem in mapping btw the record in the form and the cursor pointing to that record in the database because when i execute "next_recod" button after choosing one in LOV it go to the record next the one specified before choosing from LOV
knowing that updating process working correctly when choosing by ("first_record, previous_record, next_record or last_record)
so what is the solution
please help
thank you very much

yes please
I didn't know what do you mean by customized or default menu
I build LOV using the wizard and bind it by a query to a table then make Show_LOV from the form
so when I choose one of the rows and they brought to the text boxes assigend to them after that when I make "Commit" I got that error
thank you for help
and sorry for bieng late in reply, I don't have enternet after 2:00 pm

Similar Messages

  • MySQL error while Updating Record

    Hi
    I'm newbie so your help will be welcomed.
    While I'm trying to Update Record, the following error
    occurs:
    " You have an error in your SQL syntax; check the manual that
    corresponds to your MySQL server version for the right syntax to
    use near '' at line 1".
    This is the code that gives me headache:
    "<?php
    require_once('../../../../Inetpub/wwwroot/theHotel/Connections/connHTL.php');
    ?>
    <?php
    $colname_rsBooking = "-1";
    if (isset($_GET['ID'])) {
    $colname_rsBooking = (get_magic_quotes_gpc()) ? $_GET['ID']
    : addslashes($_GET['ID']);
    mysql_select_db($database_connHTL, $connHTL);
    $query_rsBooking = sprintf("SELECT * FROM bookings WHERE ID =
    %s", $colname_rsBooking);
    $rsBooking = mysql_query($query_rsBooking, $connHTL) or
    die('HERE IS THE ERROR, I GUESS' . mysql_error());
    $row_rsBooking = mysql_fetch_assoc($rsBooking);
    $totalRows_rsBooking = mysql_num_rows($rsBooking);
    $colname_rsClient = "-1";
    if (isset($_GET['clientID'])) {
    $colname_rsClient = (get_magic_quotes_gpc()) ?
    $_GET['clientID'] : addslashes($_GET['clientID']);
    mysql_select_db($database_connHTL, $connHTL);
    $query_rsClient = sprintf("SELECT * FROM clients WHERE ID =
    %s", $colname_rsClient);
    $rsClient = mysql_query($query_rsClient, $connHTL) or die('NE
    MOZAM' . mysql_error());
    $row_rsClient = mysql_fetch_assoc($rsClient);
    $totalRows_rsClient = mysql_num_rows($rsClient);
    ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
    Transitional//EN" "
    http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    etc......"
    I want to know if this is a syntax , MySQL or PHP error. I've
    tried things, but no results.
    PLS HELP!
    Thanks in advance!

    dedurus wrote:
    > " You have an error in your SQL syntax; check the manual
    that corresponds to
    > your MySQL server version for the right syntax to use
    near '' at line 1".
    The error message is clear in one respect - it's an error of
    MySQL
    syntax. What it doesn't tell you is what the error is. The
    way to find
    out is to use echo to display the SQL query onscreen. I
    suspect that
    what's happening is that either ID or clientID haven't been
    defined.
    > $query_rsBooking = sprintf("SELECT * FROM bookings WHERE
    ID = %s",
    > $colname_rsBooking);
    Display the value of the SQL query here
    echo $query_rsBooking.'<br />';
    > $rsBooking = mysql_query($query_rsBooking, $connHTL) or
    die('HERE IS THE
    > ERROR, I GUESS' . mysql_error());
    > $row_rsBooking = mysql_fetch_assoc($rsBooking);
    > $totalRows_rsBooking = mysql_num_rows($rsBooking);
    >
    > $colname_rsClient = "-1";
    > if (isset($_GET['clientID'])) {
    > $colname_rsClient = (get_magic_quotes_gpc()) ?
    $_GET['clientID'] :
    > addslashes($_GET['clientID']);
    > }
    > mysql_select_db($database_connHTL, $connHTL);
    > $query_rsClient = sprintf("SELECT * FROM clients WHERE
    ID = %s",
    > $colname_rsClient);
    And again, here:
    echo $query_rsClient;
    > $rsClient = mysql_query($query_rsClient, $connHTL) or
    die('NE MOZAM' .
    > mysql_error());
    Once you know what the SQL queries look like, you can begin
    troubleshooting.
    David Powers
    Adobe Community Expert
    Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
    http://foundationphp.com/

  • Stale data error while updating record

    Hi,
    While updating page getting below error.
    ++++++++++++++++++
    Error
    Unable to perform transaction on the record.
    Cause: The record contains stale data. The record has been modified by another user.
    Action: Cancel the transaction and re-query the record to get the new data.
    ++++++++++++++++++
    - In page navigation, the setForwardURL is done without retaining the AM
    - There is no other user trying to change the values that are just created.
    - Doing pageContext.releaseRootApplicationModule(); before commit.
    - ObjectVersionNumber attribute of entity object, check the Change Indicator checkbox for this attribute.
    Still it is NOT working getting same error.
    Any idea, why this error coming.
    Thanks,
    Srikanth

    OA Framework updates the ObjectVersionNumber attribute in the generic OAEntityImpl Java class. That is, the createObjectVersionNumber(), and updateObjectVersionNumber() methods perform automatic initialization and update of these values.
    Read more in Dev Guide
    Thanks
    --Anil                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Stale data error while updating record on extending standard OAF pages

    We are on Oracle R12. I have a standard oracle shipped page to enter attributes of an inventory item. This page has an APPLY and CANCEL buttons to post the changes to DB. There is one attribute called FORMULA. To create a formula , I created a new custom page.
    I added a custom controller and AM to the standard page and added a new button, "Create Formula" . When the user clicks this button, he can navigate to the new custom page and create a formula. When the user clicks APPLY on this new page, I am navigating him back to the original page , looping through the Entity Object of that page and setting the formula attribute using method
    EO.SetATTRIBUTE.
    This works fine the first time. Then I click the apply button on the original page, the change is saved on teh DB. Now if I click the formula button again and try to modify the formula, on returning to the original page, the formula is updated but I also get the following error :
    Unable to perform transaction on the record.
    Cause: The record contains stale data. The record has been modified by another user.
    Action: Cancel the transaction and re-query the record to get the new data.
    I tried getTransaction().setClearCacheOnCommit(true); after the setattribute but I still get this error . Not sure why this is happening, what I need to do.
    Please help . I did not modify any oracle shipped VOs or EOs.
    thanks
    Satya

    you can also release transaction by using
    pageContext.releaseRootApplicationModule();
    --Prasanna                                                                                                                                                                                                       

  • Error while updating the records through a DB link

    Hi ,
    I am getting the below error while updating around 15 thousands records, i suspect it to be timeout but not sure.Please can you let me know what solutions needs to be taken.
    Not Found
    The requested URL /pls/htmldb/wwv_flow.show was not found on this server.
    Not Found
    The requested URL /pls/htmldb/wwv_flow.show was not found on this server.
    Oracle-Application-Server-10g/10.1.2.0.0 Oracle-HTTP-Server Server at htmldb.oraclecorp.com Port 80
    Object Type TABLE Object GWB_GRN_GRP_COUNTRIES_LU
    Table Column Data Type Length Precision Scale Primary Key Nullable Default Comment
    GWB_GRN_GRP_COUNTRIES_LU NAME Varchar2 720 - - - - - -
    ALIAS Varchar2 720 - - - - - -
    ACTIVE Varchar2 3 - - - - - -
    REGION Varchar2 300 - - - - -
    1 - 4
    Thanks & Regards,
    Ramu

    Hi Sangu,
    See if the following notes help you:
    Error when calling API from SQL*Developer, eg. ORA-01403 in API OE_ORDER_PUB.PROCESS_ORDER (Doc ID 1054295.1)
    Cancellation Of Transfer Orders Is Not Possible - ORA-01403: no data found in Package OE_Order_PVT Procedure Process_Order (Doc ID 391307.1)
    Thanks &
    Best Regards,

  • Getting error " Incomplete update due to error in single records"

    Dear All,
    We are loading data from DSO to Cube using full load and the load is failing giving an error message Collection in the source system ended and when checked the error message button it is showing as  " Incomplete update due to error in single records" . and also one more message "Messages (type E) for data records with record number 0
    Message no. RSM2714". Can any one tell us the reason for the failure of this load ? and how to resolve it ?.
    When we click on the help button of the error message it is displaying the message as below
    Incomplete update due to errors in single records --> Long text
    Message no. RSM2712
    Diagnosis
    In the update rules, one InfoSource record was used to create several records in the data target. These records must be handled in the same way to enable tracking into the PSA and the treatment of errors in individual records.
    In the previous case, one record was updated in this kind of group generated by update rules, whereas other records in the same group were rejected. If you updated the PSA data record again, the records that were already updated would be updated again. Duplicate records would appear in the data target and the data target would thus be inconsistent.
    System Response
    The data record with errors was highlighted in the PSA. However, no error request was generated.
    Procedure
    Delete the request in the data target and, after removing the error, update all records for the request to the data target again.
    Regards,
    JayaKrishna

    hi,
    Can you please check out the PSA error record and check this out in Source DSO as this load is for DSO -> Cube....
    Please correct it in PSA if this is not correct as per DSO ....prior correcting data in PSA pls delete the request from Cube.....then it will allow to correct or delete record in PSA and then further push data from PSA to Target Cube...
    If its correct as per DSO then run load in DSO sometime few records wrongly updated by  end user and they correct it by evening for Submission....So u will get the corrected record and then run manually further load to Cube...
    Hope this will help....
    Regards,
    Mahesh

  • Getting the error "Error while trying to update record" when I try to force complete a plan in DAC

    Hello Everyone ,
    I am using OBIA 7.9.3.7 . One of my execution plan has finished executing all the tasks but it is still in running mode . When I try to force complete it , it gives the error " Error while trying to update record" . Upon checking the log file , I found the below errors :
    MESSAGE:::ORA-04092: cannot COMMIT in a trigger
    ORA-06512: at "DAC_CUSTSCM.ETL_FAIL_NOTOFICATION", line 9
    ORA-04088: error during execution of trigger 'DAC_CUSTSCM.ETL_FAIL_NOTOFICATION'
    EXCEPTION CLASS::: java.sql.SQLSyntaxErrorException
    The Plan is in running state for past couple of days . I tried to re-start the DAC services , but again it gave the same error . Kindly suggest .
    Regards
    Satyendra

    Just to correct , the version of obia is 7.9.6.3

  • Get error ORA-20505 and ORA-01403 when UPDATING record

    Hi,
    I'm running APEX 3.2.1, on Oracle XE 10.2.0.1, on Sun Ultra20 (Intel-based) running Windows Server 2003.
    I created a small, department database - to keep track of contacts, equipment, etc.
    Initially, I used a NUMBER as the PRIMARY KEY in both the CONTACTS table and EQUIPMENT tables. I created a CONTACTS interactive report and a CONTACT DETAILS form, where the EDIT button on a row in the CONTACTS report brings up the individual record to modify. Same thing for EQUIPMENT - interactive report page and form page.
    This all worked fine!
    Then, I decided to change the PRIMARY KEY for the CONTACTS table to a STRING - with CONTACT_FIRST_NAME and CONTACT_LAST_NAME as the primary key. I figured I this would prevent duplicate entries. After the change, inserts work. Updates work, IF a change is made to ANY field EXCEPT first name or last name.
    UPDATES fail - if user modifies EITHER the first name or last name - in APEX. But, update SUCCEEDS if done in SQL Developer. Obviously, I missing a subtle nuance in APEX, but I can't figure it out.
    I've included DEBUG trace and version information below.
    Thanks,
    Andy
    ORA-20505: Error in DML: p_rowid=Adam1, p_alt_rowid=CONTACT_FIRST_NAME, p_rowid2=Adam, p_alt_rowid2=CONTACT_LAST_NAME. ORA-01403: no data found
    0.02: A C C E P T: Request="SAVE"
    0.02: Metadata: Fetch application definition and shortcuts
    0.02: NLS: wwv_flow.g_flow_language_derived_from=FLOW_PRIMARY_LANGUAGE: wwv_flow.g_browser_language=en-us
    0.02: alter session set nls_language="AMERICAN"
    0.02: alter session set nls_territory="AMERICA"
    0.02: NLS: CSV charset=WE8MSWIN1252
    0.02: ...NLS: Set Decimal separator="."
    0.02: ...NLS: Set NLS Group separator=","
    0.02: ...NLS: Set date format="DD-MON-RR"
    0.02: ...Setting session time_zone to -06:00
    0.02: Setting NLS_DATE_FORMAT to application date format: DD-MON-YYYY
    0.02: ...NLS: Set date format="DD-MON-YYYY"
    0.03: Fetch session state from database
    0.03: ...Check session 1896858759858984 owner
    0.03: Setting NLS_DATE_FORMAT to application date format: DD-MON-YYYY
    0.03: ...NLS: Set date format="DD-MON-YYYY"
    0.03: ...Check for session expiration:
    0.03: ...Metadata: Fetch Page, Computation, Process, and Branch
    0.03: Session: Fetch session header information
    0.03: ...Metadata: Fetch page attributes for application 101, page 21
    0.05: ...Validate item page affinity.
    0.05: ...Validate hidden_protected items.
    0.05: ...Check authorization security schemes
    0.05: Session State: Save form items and p_arg_values
    0.05: ...Session State: Save "P21_CONTACT_FIRST_NAME" - saving same value: "Adam"
    0.06: ...Session State: Saved Item "P21_CONTACT_LAST_NAME" New Value="Adam Jr"
    0.06: ...Session State: Save "P21_CONTACT_COMPANY" - saving same value: "Atempo"
    0.06: ...Session State: Save "P21_CONTACT_JOB_TITLE" - saving same value: "Sr Sw Engr"
    0.06: ...Session State: Save "P21_CONTACT_JOB_ROLE" - saving same value: "Engineering"
    0.06: ...Session State: Save "P21_CONTACT_STATUS" - saving same value: "Active"
    0.06: ...Session State: Save "P21_CONTACT_PRODUCT" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_PHONE" - saving same value: "222-333-4444"
    0.06: ...Session State: Save "P21_CONTACT_MOBILE" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_FAX" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_EMAIL" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_STREET" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_CITY" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_STATE" - saving same value: "CO"
    0.06: ...Session State: Save "P21_CONTACT_ZIP" - saving same value: ""
    0.06: ...Session State: Save "P21_CONTACT_COUNTRY" - saving same value: "United States"
    0.06: ...Session State: Save "P21_CONTACT_NOTES" - saving same value: ""
    0.06: Processing point: ON_SUBMIT_BEFORE_COMPUTATION
    0.06: Branch point: BEFORE_COMPUTATION
    0.06: Computation point: AFTER_SUBMIT
    0.06: Tabs: Perform Branching for Tab Requests
    0.06: Branch point: BEFORE_VALIDATION
    0.06: Perform validations:
    0.08: ...Item in validation equals expression 2: P21_CONTACT_JOB_ROLE
    0.08: ...Item in validation equals expression 2: P21_CONTACT_STATUS
    0.08: ...Item Not Null Validation: P21_CONTACT_PHONE
    0.08: ...Item in validation equals expression 2: P21_CONTACT_STATE
    0.08: ...Item in validation equals expression 2: P21_CONTACT_COUNTRY
    0.08: Branch point: BEFORE_PROCESSING
    0.08: Processing point: AFTER_SUBMIT
    0.08: ...Process "Process Row of ISR_CONTACTS": DML_PROCESS_ROW (AFTER_SUBMIT) #OWNER#:ISR_CONTACTS:P21_CONTACT_FIRST_NAME:CONTACT_FIRST_NAME:P21_CONTACT_LAST_NAME:CONTACT_LAST_NAME|IU
    0.08: Show ERROR page...
    0.08: Performing rollback...
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    Database     
    NAME     XE
    CREATED     06/08/2010 05:22:50 PM
    RESETLOGS_TIME     07/09/2010 10:09:59 AM
    PRIOR_RESETLOGS_CHANGE#     193066
    PRIOR_RESETLOGS_TIME     06/08/2010 05:22:52 PM
    LOG_MODE     ARCHIVELOG
    CHECKPOINT_CHANGE#     4436025
    ARCHIVE_CHANGE#     4387159
    OPEN_RESETLOGS     NOT ALLOWED
    VERSION_TIME     07/09/2010 10:08:44 AM
    OPEN_MODE     READ WRITE
    PROTECTION_MODE     MAXIMUM PERFORMANCE
    PROTECTION_LEVEL     MAXIMUM PERFORMANCE
    REMOTE_ARCHIVE     ENABLED
    DATABASE_ROLE     PRIMARY
    ARCHIVELOG_CHANGE#     4458138
    SWITCHOVER_STATUS     SESSIONS ACTIVE
    DATAGUARD_BROKER     DISABLED
    GUARD_STATUS     NONE
    FORCE_LOGGING     NO
    CGI Environment     
    PLSQL_GATEWAY     WebDb
    GATEWAY_IVERSION     2
    SERVER_SOFTWARE     Oracle Embedded PL/SQL Gateway/10.2.0.1.0
    GATEWAY_INTERFACE     CGI/1.1
    SERVER_PORT     8080
    SERVER_NAME     XDB HTTP Server
    REQUEST_METHOD     GET
    QUERY_STRING     p=4500:36:1896858759858984:::::
    PATH_INFO     /f
    SCRIPT_NAME     /apex
    REMOTE_ADDR     10.135.65.180
    SERVER_PROTOCOL     HTTP/1.1
    REQUEST_PROTOCOL     tcp
    REMOTE_USER     ANONYMOUS
    HTTP_USER_AGENT     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.19) Gecko/2010031422 Firefox/3.0.19 (.NET CLR 3.5.30729)
    HTTP_HOST     isr-si-project:8080

    Maybe because you're changing primary key...and then updating record with primary key that doesn't exist.

  • SM13 - Error in Collect.Run - Yellow status update records.

    Hello,
    After some problems with update queues in R/3, we have some update records in yellow status "Error in collective run" in sm13 t-code.
    If we run collective run, new records are pushed into rsa7, but this yellow status records won't move, and we actually need them.
    Does anyone know how to process this errors?

    Hi,
    There is no problem with background process, the new update records are being processed with no problem.
    These update records remain in yellow status since yesterday, but new records are being processed.

  • FRM-40509: ORACLE error: unable to UPDATE record.

    FRM-40509: ORACLE error: unable to UPDATE record.
    what can i do?

    There will always be another error which tells you what the actual problem on the database is. Use the Display message key, or message out DBMS_ERROR_TEXT

  • Error -2028 Update No matching records found (ODBC -2028)

    An apology for my English, I'm trying to update a field but I get this error:
    No matching records found (ODBC -2028)
    This is part of the code that I use to add new ones and works fine, when I change the oItems.Add (); by oItems.Update () does not work.
    public static void addItem(DataRow itemObject)
       oItems = (SAPbobsCOM.Items)(oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oItems));
       oItems.ItemCode = itemObject["ItemCode"].ToString();
       oItems.ItemName = itemObject["ItemName"].ToString();
       lRetCode = oItems.Add();
       if (lRetCode != 0)
          oCompany.GetLastError(out lErrCode, out sErrMsg);
    I get the data from MySql, and I tried putting the data manually from an existing record and does not work
    Any ideas why?

    Hi,
    Before you can call Update on an item you need to call the GetByKey method to retrieve the item you want to update:
    public static void updateItem(DataRow itemObject)
       oItems = (SAPbobsCOM.Items)(oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oItems));
       if(oItems.GetByKey(itemObject["ItemCode"].ToString())
            oItems.ItemName = itemObject["ItemName"].ToString();
            lRetCode = oItems.Update();
            if (lRetCode != 0)
                    oCompany.GetLastError(out lErrCode, out sErrMsg);
    Kind Regards,
    Owen

  • Update Record Server Behavior blows error (its part of CS5.5 standard installation!)

    One wouldn't expect the code supplied by a MAJOR CORPORATION and WEB DEVELOPMENT TECHNOLOGY LEADER to blow an error on one of the server behaviors it supplies as part of its standard install. But then again, there is reality.  The UpdateRecord.js, to be found in your installation on Windows 7 at ..ProgramFiles(x86(/Adobe Dreamweaver CS5.5/configuration/ServerBehaviors/Php_MySQL/UpdateRecord.js  causes an error when it is selected from the SERVER BEHAVIORS menu.  This happens BEFORE you I enter anything into the fields.  The error states:  "While executing onLoad in  UpdateRecord.htm, the following JavaScript error(s) occured: At line 687 of file "........UpdateRecord.js":  name has no properties.  I've looked at the code and it is beyond my comprehension.  Something about the NAME of a value in the node list.... I just don't have the chops to go rewriting Adobe's code.  If I did, I'd be making the big bucks.  Does anybody know what to do about this? About my system:  Windows 7, 64bit,   CS5.5 (on a lease so it is up to date) using PHP and MySQL, on a remote dedicated server running Apache on Linux.   :<)McFrisco

    Ok, I deserved that spanking.  I was just frustrated.  Sorry for the rant. 
    I've managed to figure out a workaround on this.  There really is something wacky going on with Dreamweaver and the Update Record handler.  Here's what I did:   
    How to trick DREAMWEAVER into writing an UPDATE RECORD. 
    Dreamweaver's server behavior for Update Record doesn't work correctly sometimes.  The symptom of this is that when you try to fill in the popup form provided by the Server Behaviors/Update Record menu item, it doesn't allow you to choose form fields to update to the database if they are posted there by a previous page.  It only allows you to choose them if they are bound to the database.  This doesn't do any good, because you are updating a record with the information from the database you want to update, NOT with new information.  Kind of weird... But here's the way to get around it.  Its a bit tedious but it works.   
    1.  On a clean php page, set up a form with the input fields matching the database fields you want to update.  This page is to be used as the RESULT page of a form submitted on a previous page where the UPdate Record won't work due to conflicts, plugins, or some other unknown reason.   
    2.  Connect to the database table you want to update,  and set up a new RECORDSET on the page. 
    3.  Bind all the form fields to the appropriate database fields. 
    4.  Do an Update Record behavior based on this form.  This will actually do nothing but update the record with the stuff that is already in the record, as noted above.   
    5. Delete the php code that sets up the record set.  But, LEAVE THE Update Record code alone!  It is correct.   
    6.  Change the bindings of all the fields in the FORM to the $_POST[] variables passed from the form on the previous page. (Make sure the previous page form uses the POST, not the GET method.)
    Now, when you submit the form it will pick up the values in the form, which have been passed from the previous page's form.

  • Update record error message: Server behavior, updaterecord.js

    Hello,
    I'm developing a website using PHP and MySQL on Dreamweaver CS5, Snow Leopard.
    I'm having trouble with the updateRecord Server Behavior:
    Right after selecting "Update Record" in "Server Behavior" menu, I get the following error message in a popup window:
    while executing onLoad in UpdateRecord.htm, the following javascript error(s) occurred:
    At line 687 of file "Macintosh HD:Applications:Adobe Dreamweaver CS5:Configuration:ServerBehaviors:PHP_MySQL:UpdateRecord.js." name has no properties
    After selecting "ok" in the popup window, the "Update Record" window menu opens. However, when I tried to selected the desired table from the database in the dropdown menu, the same error message/popup window appears. I clicked "ok" once again, but the "column" textarea doesn't get populated at all. But, the "Value" dropdown menu does get populated with the correct data.
    I need help asap. Please contact me if you need more information.
    Thank you so much for taking your time to read my post, hopefully you'll be able to help me.
    Best,
    Alice Li

    I have this same problem. Was working fine then I removed the Recordset and added it again to change the name. After binding the dynamic info to my form fields I tryied to add an update record behavior and I got this error.
    I had already done this once I think with no problem. I tried restarting Dreamweaver and the computer but the issue still persists.
    Any help!?

  • Unable to update record in web Form

    Hi, i am unable to update record in a form. I am building a custom form using forms 6i and putting it on the web in oracle applications 11.5.9
    I used template.fmb as a starting point for my form. I have one datablock based on a table. Insert, update and delete properties are set to yes on the property pallete of data block. The table against which i am running the form has a primary key which is a combination of two fields. I am able to update a record with pure SQL running against the table.
    My form now brings back a record from the db like it should but whenever I try to update that record either by pressing Action Save or by clicking button that has update statement in it, instead of doing an update, it does an insert and tells me that this record already exists and that i entered value(s) that must be unique for each record. It thinks I want to insert but I want to update. What am i doing wrong???
    Update allowed value is set to Yes in all the items in the data block and at the data block level as well. Querly_only is set to no.
    What's even more frustratinng is that I've ran the form manually before starting with template.fmb and have been able to update the table but when I put it on the web and used template.fmb it stopped working!
    I am very new to forms, can anybody suggest anything? Please help!!!

    When you populate the 2nd block with a select into query, it's the same as just typing the data into the block. The record is treated as one needing to be inserted, not as one that is queried.
    To populate it using a true query, but with data from the LOV, you can do this:
    Programmatically set the default_where clause of the block based on the LOV. For example, if a name is chosen from the LOV in an item called LOV1, you could do:
    set_block_property('block2','default_where','name='''||:block1.lov1||'''');
    or if the LOV is a number, like a department number:
    set_block_property('block2','default_where','deptno='||:block1.lov1);
    The tricky part when you build your where clause is that you must surround strings with single quotes, and the way to do this is to use two single quotes to represent an actual single quote in the where clause. Otherwise a single quote is interpreted as part of the PL/SQL syntax.
    Then, just navigate to block 2 and execute a query:
    go_block('block2');
    do_key('execute_query');
    I hope this works for you. I didn't have time to test this, so I hope I didn't make any syntax errors when typing.

  • Error while updating data from PSA to ODS

    Hi Sap Gurus,
    I am facing the error while updating data from PSA to ODS in BI 7.0
    The exact error message is:
    The argument 'TBD' cannot be interpreted as a number
    The error was triggered at the following point in the program:
    GP44QSI5RV9ZA5X0NX0YMTP1FRJ 5212
    Please suggest how to proceed on this issue.
    Points will be awarded.

    Hi ,
    Try to simulate the process.That can give you exact error location.
    It seems like while updating few records may be no in the format of the field in which it is updated.
    Regards
    Rahul Bindroo

Maybe you are looking for