Post reply

Problem with disconnected recordsets

  • October 20, 2005 at 3:57 am

    #169375

    We have a VB6 application using ADO 2.8 connecting to SQL Server.

    We use disconnected recordset to load data to client-side. The client does updates in the recordset and then sends it back to server-side component that converts the recordset into SQL to update the database. No problems in SQL 2000 but on Yukon we get error when trying to update the disconnected recordset on the client.

     

    Error: -2147217887 Multiple-step operation generated errors. Check each status value.

     

    Error only occurs on recordsets which obviously won't work it was a connected recordset; for example a UNION sql.

     

    Is this the way Yukon is supposed to work? Is there anyway to disable this new functionality to really get a disconnected recordset?

     

    One thing that would work is to create a recordset from scratch based on the loaded recordset and copy all data into this new recordset. But it seems like a lot of work doing this each time.

  • October 24, 2005 at 8:00 am

    This was removed by the editor as SPAM

  • June 15, 2015 at 2:57 pm

    #1805585

    hi everyone, I am having a very similar issue. Was there ever a resolution?

    I get the same error number -2147217887 but with this error message "ODBC--call failed.". I get this when I try to execute an rst.Update. I have an MS Access 2013 application using an ODBC connection to SQL Server 2008 r2. I am using a query to update a table. It is a simple Select query with no joins. I have checked to make sure the table can be updated.

    Can anyone help me here?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply