Error Updating Oracle Table from Access Form

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • time2hike
    New Member
    • Mar 2012
    • 68

    Error Updating Oracle Table from Access Form

    Hi, I have an Access 2010 Front End database linking to Oracle 11g tables. I have a form where the user sets a date value in an unbound text box and a 5 character text value in an unbound combo box field. The user clicks on a command button and a query runs to update the appropriate fields for the selected records with the values set on the form. The fields being updated in the oracle table have properties of Date/Time and Text(10).

    I am receiving the following error:
    ODBC--update on a linked table failed.
    [Oracle][ODBC][Ora]ORA-01461: can bind a LONG value only for insert into a LONG column (#1461)

    I have tried playing with cDate(Form!Fiel d1) and cStr(Form!Field 2) to resolve this but I keep getting the same error. I have also tried hard coding my values in a query and loading them that way and I get the same error. This is the sql for my query where I am hard coding the values:

    Code:
    UPDATE TBL SET TBL.APCESOURCE = "TCISP", TBL.APCEDATEAPPROVED = #4/30/2013#
    WHERE (((TBL.CACMNTH)=9) AND ((TBL.CACYR)=2013) AND ((TBL.PROJECTID)="TC365500") AND ((TBL.SUBPROJECTID)="TC36550002"));
    I am confused as none of my fields are LONG.

    I am able to manually enter a date and text in these fields in the Oracle table so I don't think this is a premissions issue. Do you know how to resolve this?
  • zmbd
    Recognized Expert Moderator Expert
    • Mar 2012
    • 5501

    #2
    Double check the date format in the [TBL.APCEDATEAPP ROVED] field. You have #m/dd/yyyy# as the data and your field could be expecting #mm/dd/yyyy# or some other date format.

    Comment

    • time2hike
      New Member
      • Mar 2012
      • 68

      #3
      Circling back on this conversation. My IT shop looked into this issue and found that if we use the Microsoft ODBC for Oracle Connection instead of the Oracle Client 11G Connection the issue seems to go away. We are continuing to test this but preliminarily changing the connection is solving the issue and I have not found any problems that are created by changing the connection to the Microsoft ODBC for Oracle Connection.

      Comment

      Working...