Results 1 to 1 of 1
  1. #1
    Join Date
    Aug 2003

    Thumbs up Unanswered: MSDASQL and VB6 error 2147217887

    Hi there

    Brief overview:
    Using COM+ created in VB6, that executes stored procs (SQL 2K) via the command object (cmd.commandtype = adCmdStoredProc), with appended parameters.

    Whenever doing cmd.execute, the error "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done." is returned. The active connection errors collection contains only this error, nothing else.

    The stored proc works from sql query analyzer, and vb is happy when the stored proc is called like cmd.execute "exec spProc @Param1 = 5" etc.

    Strange thing is that it has always worked as described in first senario.

    When te component is recompiled, existing methods work fine when called with ASP, new methods fail. When running the component's code with a test project, all methods (old and new) that use the first scenario fail.

    We are trying to pinpoint the issue, but are getting nowhere. No changes were implemented on the servers between it working and stopping working, and project backups from a period we know everything worked fine exhibit the same symptoms.

    Tried MDAC 2.6 and 2.7 with no success. Any ideas?


    --update Aug 9 2003
    Found the culprit: working with uniqueidentifers, and it seems passing them as parameters to VB methods require that the curly braces be INCLUDED eg. GetPricelistProperties("{1234-........5678}") . SQL query analayzer and stored procs work either way, with or without the braces.
    Last edited by simpleton; 08-08-03 at 03:59.

Posting Permissions

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