BUG: ADO Parameters Refresh May Cause Failure (183008)

MORE INFORMATION

Steps to Reproduce Behavior

1. Create a Visual Basic Project.
2. From the Projects menu, click References and select the ADO Type Library.
3. Place the following code in the form's load event. This example assumes that the backend database is SQL Server. You will have to change the data source name (DSN) to one available on your computer:
   
   Note You must change Username=<username> and PWD=<strong password> to the correct values before you run this code. Make sure that Username has the appropriate permissions to perform this operation on the database.

          Dim con As New Connection
            Dim cmd As New Command
   
            con.Open "DSN=YourDSN;database=YourDatabase;Username=<username>;PWD=<strong password>;"
   
            ' Drop stored procedure, but ignore error if it doesn't exist.
            On Error Resume Next
            con.Execute "drop procedure proctest"
   
            ' Restore error handling.
            On Error GoTo 0
   
            ' Create stored procedure that has return and input parameter.
            con.Execute "create procedure proctest(@in text) as return 1"
            Set cmd.ActiveConnection = con
            cmd.CommandText = "{? = call proctest(?)}"
   
            cmd.Parameters.Refresh
   
            ' At this point parameter 0's direction is indicated to be Output (adParamOutput, 2),
            ' when in fact it is return (adParamReturnValue, 4).
            ' Parameter 1's direction is correctly
            ' set to be an input parameter (1).  Even so, this code executes
            ' as is at this point.
            Msgbox "Cmd(0).Direction: " & cmd(0).Direction
            Msgbox "Cmd(1).Direction: " & cmd(1).Direction
   
            ' Uncommenting this line will make the test work fine.
            ' cmd(0).Direction = adParamReturnValue
            cmd(1).Type = adLongVarChar     ' Bug only occurs with this line
            cmd(1).Value = "Some String"
            cmd.Execute    '<<error here
     
   					

4. Run the code and note that the error is generated. If you uncomment the code specifying the direction, the code executes correctly.