Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Another AddNew returns multi-step OLE DB operation generated errors

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Another AddNew returns multi-step OLE DB operation generated errors

    tgmayes wrote: > I am having the same problem, with a twist. I am able to add a new > record if I only populate the first 4 fields of my file. If I try to > populate past those fields, I receive the multistep ole error. It is > driving me nuts. The fifth field is signed. I thought it might have > been a problem, so I took it out of the flds and vals arrays that do > the add. Still the same error message. I am checking each of the > character fields to make sure they are the proper length. It is the > same code as can be found in the client access programmers toolkit. I > guess my question are "Do you have to include all the fields in order > when you try to add a record?" and "If so, has anyone updated a > signed field using the IBMDA400 connection?" I can't see the message to which you are referring to. Why not start somewhat anew and show your statements? Bill

  • #2
    Another AddNew returns multi-step OLE DB operation generated errors

    My code is attached below
    Code

    Comment


    • #3
      Another AddNew returns multi-step OLE DB operation generated errors

      I actually have all the fields updating now, except the signed data field and the packed fields. Any suggestions?

      Comment


      • #4
        Another AddNew returns multi-step OLE DB operation generated errors

        It looks like the code loads the values with Nulls under certain conditions. If you haven't defined the Data Base fields as null capable than maybe that's your problem. See below: Mike
        Code

        Comment


        • #5
          Another AddNew returns multi-step OLE DB operation generated errors

          I'll try that and will let you know. Thanks Again Tammy

          Comment


          • #6
            Another AddNew returns multi-step OLE DB operation generated errors

            I tried it and it didn't work. I took out the loop with the null and enabled the database to accept null. Still no Luck. Tammy

            Comment


            • #7
              Another AddNew returns multi-step OLE DB operation generated errors

              I don't have VB on this machine, so I hope I get the syntax right... Does it work if you do the AddNew, assign the fields individually and then to Update ? If nothing else, maybe you'll get a different error that you can debug. And you're absolutely sure that the field names are correct? You may want to double-check in debug. In the debug window do: ? rs(0).Name and increment the index to work through all the field names in the collection. Then try rs.AddNew rs(0).Value = strTSuite rs(1).Value = strTItem . . . rs(20).Value = "newgens" rs.Update And see if the results are the same.

              Comment


              • #8
                Another AddNew returns multi-step OLE DB operation generated errors

                I am having the same problem, with a twist. I am able to add a new record if I only populate the first 4 fields of my file. If I try to populate past those fields, I receive the multistep ole error. It is driving me nuts. The fifth field is signed. I thought it might have been a problem, so I took it out of the flds and vals arrays that do the add. Still the same error message. I am checking each of the character fields to make sure they are the proper length. It is the same code as can be found in the client access programmers toolkit. I guess my question are "Do you have to include all the fields in order when you try to add a record?" and "If so, has anyone updated a signed field using the IBMDA400 connection?"

                Comment


                • #9
                  Another AddNew returns multi-step OLE DB operation generated errors

                  Nope this didn't work either, The IBM driver requires the other format - passing the array. Thanks anyway, Tammy

                  Comment

                  Working...
                  X