Solved

How to include stored procedure input parameters when using ado data control; VB 6.0, SQL Server 2000

Posted on 2007-04-06
8
398 Views
Last Modified: 2013-12-25
I have been unable to find instructions regarding this question in help files, at microsoft, or via google.
I am using VB 6.0 sp6 w/ WinXP Pro sp2, and SQL Server 2000.
I am trying to use an ado data control to fill a dbgrid.
I am trying to call a stored procedure with 2 input parameters.
I need to know how to include the parameters in the subprocedure that calls the stored procedure.

The error I receive is, "Adodc1  - Procedure'WHTSP_FetechReporderDetails' expects parameter '@emp_id' which was not supplied."

I know this isn't correct - can someone provide an example?  My thanks in advance for any helpful responses.

Here is the code for the subprocedure:
   Dim cmd As New ADODB.Command
    With cmd
        .CommandType = adCmdStoredProc
        .CommandText = "WHTSP_FetchReporderDetails"
        .ActiveConnection = conn
        .Parameters.Append .CreateParameter("@emp_id", adVarChar, adParamInput, 5, strEMP_ID)
        .Parameters.Append .CreateParameter("@date_scanned", adsmalldatetime, adParamInput, , dtmTodaysDate)
    End With
   
    With Adodc1
        .ConnectionString = CommonConnString
        .CursorLocation = adUseServer
        .CursorType = adOpenStatic
        .LockType = adLockOptimistic
        .CommandType = adCmdStoredProc
        .RecordSource = WHTSP_FetchReporderDetails
       
        .Refresh
    End With
0
Comment
Question by:michael801
  • 3
  • 3
  • 2
8 Comments
 
LVL 142

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 18864924
please try the following change:
        .RecordSource = cmd


    Dim cmd As New ADODB.Command
    With cmd
        .CommandType = adCmdStoredProc
        .CommandText = "WHTSP_FetchReporderDetails"
        .ActiveConnection = conn
        .Parameters.Append .CreateParameter("@emp_id", adVarChar, adParamInput, 5, strEMP_ID)
        .Parameters.Append .CreateParameter("@date_scanned", adsmalldatetime, adParamInput, , dtmTodaysDate)
    End With
   
    With Adodc1
        .ConnectionString = CommonConnString
        .CursorLocation = adUseServer
        .CursorType = adOpenStatic
        .LockType = adLockOptimistic
        .CommandType = adCmdStoredProc
        .RecordSource = cmd
       
        .Refresh
    End With
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 18865264
Best advice would be lose the Data Control and bind the data grid directly to a resultset that supports bookmarks.
0
 
LVL 1

Author Comment

by:michael801
ID: 18865409
Hi angelIII:, thanks for the FAST response - I tried your suggestion, but I received a compile eror: 'Type mismatch'.  Here is the code with the suggested change:
    Dim conn As New ADODB.Connection
    conn.Open CommonConnString
    Dim cmd As New ADODB.Command
    With cmd
        .CommandType = adCmdStoredProc
        .CommandText = "WHTSP_FetchReporderDetails"
        .ActiveConnection = conn
        .Parameters.Append .CreateParameter("@emp_id", adVarChar, adParamInput, 5, strEMP_ID)
        .Parameters.Append .CreateParameter("@date_scanned", adDBTime, adParamInput, , dtmTodaysDate)
    End With
   With Adodc1
        .ConnectionString = CommonConnString
        .CursorLocation = adUseServer
        .CursorType = adOpenStatic
        .LockType = adLockOptimistic
        .CommandType = adCmdStoredProc
        .RecordSource = cmd     '<-- Compile error Type Mismatch
         .Refresh
    End With
0
Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

 
LVL 75

Assisted Solution

by:Anthony Perkins
Anthony Perkins earned 240 total points
ID: 18865451
You need to execute the Recordset open using the Command object as the Source and then assign the recordset to your data control.  Again, this is overkill.  You do not need a Data Control to do this.
0
 
LVL 142

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 260 total points
ID: 18865632
I see I submit before finishing to write...
.RecordSource = cmd.Execute

but as acperkins indicated, Data Controls are usually avoided, as they take too much control from the developer for a pro application.
they are fine to quickly prototype forms etc...
0
 
LVL 1

Author Comment

by:michael801
ID: 18865841
>angelIII:I see I submit before finishing to write...
.RecordSource = cmd.Execute<
Thanks.
The compile error still occurs, highlighting 'RecordSource = '

It may be that what I'm asking cannot be done; or in any event will take more time than coding without the control.
I agree with both angellll and acperkins, my attempt to shortcut by retaining the ado dc is most likely ill-advised.  I accept both solutions, I weight the percentage split in favor of angellll for the extra effort.  My thanks to both.

0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 18867790
>>It may be that what I'm asking cannot be done<<
Sure it can.

You cannot do this (as you have discovered, they are different animals):
 .RecordSource = cmd

And you cannot bind to a recordset that does not support bookmarks.  When you use the Command's Execute method you create a firehose (forward-only, read-only) cursor.  This resultset cannot be used to bind to a grid. So as I stated previously the workaround is to use the Recordset's Open method to create the appropriate resultset.  As in (plagiarizing AngelIII's code):

Dim conn As ADODB.Connection, cmd As ADODB.Command, rs as ADODB.Recordset

Set conn = New ADODB.Connection
conn.Open CommonConnString
Dim cmd As New ADODB.Command
With cmd
      .CommandType = adCmdStoredProc
      .CommandText = "WHTSP_FetchReporderDetails"
      .ActiveConnection = conn
      .Parameters.Append .CreateParameter("@emp_id", adVarChar, adParamInput, 5, strEMP_ID)
      .Parameters.Append .CreateParameter("@date_scanned", adDBTime, adParamInput, , dtmTodaysDate)
      Set rs = New ADODB.Recordset
      With rs
            .CursorType = adOpenDynamic
            .CursorLocation = adUseClient
            .LockType = adLockReadOnly
            .Open Cmd
      End With
End With
Set Cmd = Nothing

Rest of your code goes here.  If you insist on using the ADO Data Control than the rest of the code would look something like this:

Set  Adodc1.Recordset = rs
Adodc1.Refresh
0
 
LVL 1

Author Comment

by:michael801
ID: 18871369
Thank you very much - I had to put the first end with back where it came from and things seem to work ok.  I'm posting this for anyone in the future that may be interested.  Kind regards, m801.

Dim conn As ADODB.Connection, cmd As ADODB.Command, rs as ADODB.Recordset

Set conn = New ADODB.Connection
conn.Open CommonConnString
Dim cmd As New ADODB.Command
With cmd
      .CommandType = adCmdStoredProc
      .CommandText = "WHTSP_FetchReporderDetails"
      .ActiveConnection = conn
      .Parameters.Append .CreateParameter("@emp_id", adVarChar, adParamInput, 5, strEMP_ID)
      .Parameters.Append .CreateParameter("@date_scanned", adDBTime, adParamInput, , dtmTodaysDate)
End With
      Set rs = New ADODB.Recordset
      With rs
            .CursorType = adOpenDynamic
            .CursorLocation = adUseClient
            .LockType = adLockReadOnly
            .Open Cmd
      End With
Set Cmd = Nothing

Rest of your code goes here.  If you insist on using the ADO Data Control than the rest of the code would look something like this:

Set  Adodc1.Recordset = rs
Adodc1.Refresh
0

Featured Post

Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When designing a form there are several BorderStyles to choose from, all of which can be classified as either 'Fixed' or 'Sizable' and I'd guess that 'Fixed Single' or one of the other fixed types is the most popular choice. I assume it's the most p…
If you need to start windows update installation remotely or as a scheduled task you will find this very helpful.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…

815 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now