Results 1 to 7 of 7
  1. #1
    Join Date
    Mar 2004
    Location
    Grenada, MS
    Posts
    7

    Question Unanswered: Multiple Step OLE DB error from VB

    One of our users is getting this error message.

    Microsoft OLE DB Provider for ODBC Drivers (0x80040E21) Multiple-step OLE DB operation
    generated errors. Check each OLE DB status value, if available. No work was done.

    This is the only user that is currently getting the message. Last week another user got this one day and then it stopped.


    Inside VB6 code, we're sending some filters to an ASP that in turn sends a SELECT based on those parameters the SQL database and we get data back to the program.


    Stepped through the code and found the error returns after this line

    oSqlServConn.Open "Provider=MSDAOSP;Data Source=MSXML2.DSOControl.2.6"



    Any thoughts out in ForumLand? Please take it easy on me since I didn't write most of this code. Just trying to solve the problem.

  2. #2
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Check if this pertains to your situation.

  3. #3
    Join Date
    Mar 2004
    Location
    Grenada, MS
    Posts
    7
    Nope. Unfortunately not. Only sending a handful of filters and the user has Service Pack 4 already. Wouldn't be as concerned (since this is a user that rarely needs the data and can get it via other means) except this person has the newest computer on the block.

  4. #4
    Join Date
    Mar 2004
    Location
    Grenada, MS
    Posts
    7
    Still having this problem. Any thoughts out there?

  5. #5
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Check tables names and columns names in SQL. I think there may be issue in deploying columns referred by the page.

    Check the following :
    Use client-side cursors (by setting the ADO recordset Cursor Location property to adUseClient).
    Remove the insert trigger from the source table.
    Put SET NOCOUNT ON line at the beginning of the trigger code.
    After calling Update the first time to insert the new row in the table, scroll the recordset using methods like MoveNext and MovePrevious before calling Update again.

    HTH
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  6. #6
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Setting cursor location may affect the situation, but the rest simply does not apply, - the error occurs at the time of initializing the connection, not at the time of execution of an action query that fires a trigger.

  7. #7
    Join Date
    Mar 2004
    Location
    Grenada, MS
    Posts
    7
    Tried setting cursor location on either side of the equation and still no go. I can recreate the problem on my computer now as long as I'm pointing to a test SQL server. When I switch over and point to our Production SQL server, I get no error.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •