I tried by checking:
Debug.Print MyCommand.CommandText
and after setting the parameter, I see the same query with '?' sign.
So no parameter setting happened.
Boaz

Hi,

No, commandtext will be the same. You should check if you have any result in recordset after executing of your command. Something like

If MyRecordset.EOF then
'no result
else
'there is a result
endif

--
Val Mazur
Microsoft MVP

  I tried by checking:
  Debug.Print MyCommand.CommandText
  and after setting the parameter, I see the same query with '?' sign.
  So no parameter setting happened.
  Boaz

Since I'm working also on IBM DB2,
Is there a way to see the SQL statement?
I get [IBM][CLI Driver] CLI0112E  Error in assignment. SQLSTATE=22005"
Boaz

  Hi,

  No, commandtext will be the same. You should check if you have any result in recordset after executing of your command. Something like

  If MyRecordset.EOF then
  'no result
  else
  'there is a result
  endif

  --
  Val Mazur
  Microsoft MVP

    I tried by checking:
    Debug.Print MyCommand.CommandText
    and after setting the parameter, I see the same query with '?' sign.
    So no parameter setting happened.
    Boaz

But you build it yourself and you should know what it looks like. Try to do simle test. Do not use any Variant variables and assign value to your parameter using just simple code like

MyParameter.Value="TestValue"

--
Val Mazur
Microsoft MVP

  Since I'm working also on IBM DB2,
  Is there a way to see the SQL statement?
  I get [IBM][CLI Driver] CLI0112E  Error in assignment. SQLSTATE=22005"
  Boaz

    Hi,

    No, commandtext will be the same. You should check if you have any result in recordset after executing of your command. Something like

    If MyRecordset.EOF then
    'no result
    else
    'there is a result
    endif

    --
    Val Mazur
    Microsoft MVP

      I tried by checking:
      Debug.Print MyCommand.CommandText
      and after setting the parameter, I see the same query with '?' sign.
      So no parameter setting happened.
      Boaz

You are right but I have 30 parameters, If i can see the Statement its much easier,..

  But you build it yourself and you should know what it looks like. Try to do simle test. Do not use any Variant variables and assign value to your parameter using just simple code like

  MyParameter.Value="TestValue"

  --
  Val Mazur
  Microsoft MVP

    Since I'm working also on IBM DB2,
    Is there a way to see the SQL statement?
    I get [IBM][CLI Driver] CLI0112E  Error in assignment. SQLSTATE=22005"
    Boaz

      Hi,

      No, commandtext will be the same. You should check if you have any result in recordset after executing of your command. Something like

      If MyRecordset.EOF then
      'no result
      else
      'there is a result
      endif

      --
      Val Mazur
      Microsoft MVP

        I tried by checking:
        Debug.Print MyCommand.CommandText
        and after setting the parameter, I see the same query with '?' sign.
        So no parameter setting happened.
        Boaz

Hi,

Maybe DB2 has some tracing tools, but I am not sure. What you need to do is to declare all parameters with proper data type and avoid using Variand variables when you assign values to those parameters

--
Val Mazur
Microsoft MVP

  You are right but I have 30 parameters, If i can see the Statement its much easier,..

    But you build it yourself and you should know what it looks like. Try to do simle test. Do not use any Variant variables and assign value to your parameter using just simple code like

    MyParameter.Value="TestValue"

    --
    Val Mazur
    Microsoft MVP

      Since I'm working also on IBM DB2,
      Is there a way to see the SQL statement?
      I get [IBM][CLI Driver] CLI0112E  Error in assignment. SQLSTATE=22005"
      Boaz

        Hi,

        No, commandtext will be the same. You should check if you have any result in recordset after executing of your command. Something like

        If MyRecordset.EOF then
        'no result
        else
        'there is a result
        endif

        --
        Val Mazur
        Microsoft MVP

          I tried by checking:
          Debug.Print MyCommand.CommandText
          and after setting the parameter, I see the same query with '?' sign.
          So no parameter setting happened.
          Boaz