Here is the parts of my code that I think are causing the problems. If you need more info, please let me know.

Private Sub cmdRun_Click()

Dim strMonth As String
Dim strYear As String
Dim strBeginDate As String
Dim strEndDate As String
Dim lngTotal As Long 'Running total of pages
Dim strNum As String
Dim validYear As Boolean
Dim result As String


    validYear = Year_Validate 'Validates that month textbox has four digit year

    If validYear = True Then
        'lblError = ""
         strMonth = lstMonth.ListIndex

        If strMonth = -1 Then
            lblError = "Please select a month"
            Exit Sub
        ElseIf Len(strMonth) = 1 Then
            strMonth = "0" & lstMonth.ListIndex
            lblError = ""
            strYear = txtYear.Text
        Else
            strMonth = lstMonth.ListIndex
            lblError = ""
            strYear = txtYear.Text
        End If

        strBeginDate = strYear & "-" & strMonth & "-01"
        strEndDate = strYear & "-" & strMonth & "-31"


        result = runQuery(strBeginDate, strEndDate)
        lngTotal = CLng(result)
        txtResults.Text = "Scanned & Imported Count: " & Format(lngTotal, "###,###,###") & " pages"
    Else
        Exit Sub
    End If

    StatusBar1.Panels(1).Text = "Finished wirh page count!"

Exit Sub

End Sub

-----------------------------------------

Public Function runQuery(strBeginDate As String, strEndDate As String) As String
   On Error GoTo QueryError

    runQuery = ""

    If cnServer.State = adStateClosed Then
        Set cnServer = New ADODB.Connection
            With cnServer
                    .ConnectionString = "Provider=SQLOLEDB;" & _
                                                 "INITIAL CATALOG=ESWM41;" & _
                                                 "USER ID=EISROBOT;" & _
                                                 "PASSWORD=ROBOT;" & _
                                                 "DATA SOURCE=SQLSERV"
                    .ConnectionTimeout = 1500
                    .CursorLocation = adUseClient
                    .CommandTimeout = 2000
                    .Open
            End With
    End If

    Set rsServer = New ADODB.Recordset

    With rsServer
            .ActiveConnection = cnServer
            .CursorType = adOpenStatic
    End With

    createParams

    cmdPageCount.CommandText = "select sum (cast(right(object_name,3)as int)) " _
               & "From Attributes " _
               & "Where ix_receive_date >= ? " _
               & "And ix_receive_date <= ? " _
               & "and object_class <> 'images' " _
               & "and fv_scan_data not in " _
                    & "(select fv_scan_data " _
                     & "From Attributes " _
                     & "Where object_class = 'images' " _
                     & "and ix_receive_date >= ? " _
                     & "and ix_receive_date <= ? )"

    cmdPageCount(0) = strBeginDate
    cmdPageCount(1) = strEndDate
    cmdPageCount(2) = strBeginDate
    cmdPageCount(3) = strEndDate

    StatusBar1.Panels(1).Text = "Processing Query"
    Set rsServer = cmdPageCount.Execute

    runQuery = rsServer.GetString

    If rsServer.State = adStateOpen Then
        rsServer.Close
    End If

    If cnServer.State = adStateOpen Then
        cnServer.Close
    End If

    Set rsServer = Nothing
    Set cnServer = Nothing

QueryError:
    MsgBox Err.Description & Err.Source
    Exit Function

End Function


Private Sub createParams()
    Set cmdPageCount.ActiveConnection = cnServer
    cmdPageCount.CommandType = adCmdText
    cmdPageCount.Prepared = True

    Set prmOuterBeginDate = cmdPageCount.CreateParameter(, adChar, adParamInput, 10)
    cmdPageCount.Parameters.Append prmOuterBeginDate

    Set prmOuterEndDate = cmdPageCount.CreateParameter(, adChar, adParamInput, 10)
    cmdPageCount.Parameters.Append prmOuterEndDate

    Set prmInnerBeginDate = cmdPageCount.CreateParameter(, adChar, adParamInput, 10)
    cmdPageCount.Parameters.Append prmInnerBeginDate

    Set prmInnerEndDate = cmdPageCount.CreateParameter(, adChar, adParamInput, 10)
    cmdPageCount.Parameters.Append prmInnerEndDate

    paramsCreated = True
End Sub

What happens if you execute the query as a stored procedure?

--Stole this from a moderator

I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

We are not to use stored procedures. We are supposed to keep everything in prepared statements, as it is now. Do you think that the prepared statements could have something to do with it?

To be 100% honest with you, I do not use prepared statements like you do above since that is only good to execute one certain query; I use a wrapper class that I can send any sql command to and have a result returned to my applications (if the query is to return a resultset obviously).

In any case it has been a long time since I have looked at VB code prior to .NET so I may be a little rusty, but, your params you setup as input params, length of 10 but I don't see where you supply a variable to the parameter itself.

In .NET a parameterized query looks something like this:
SELECT * From table Where valuea = @value1 AND valueB = @valueB

our command object would then look like this:

objCommand.Parameters.Add("@value1", txtValueA.text) 'You can also supply the DBType, length, etc as an overload
objCommand.Parameters.Add("@value2", txtValueB.text)

I see where you have added your parameters, their types and such, but I don't see where you point it to a physical value?

--Stole this from a moderator

I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.

Thanks everybody. I figured it out. I had to add above the 'cmdPageCount.CommandText', cmdPageCount.CommandTimeout = 0. I appreciate the help and knowledge on this problem.

Yeah, after looking at your code (sorry, was just getting around to looking at it), you were setting the timeout on the connection itself and not on the command object.

Glad you got it working.

Scott Klein
Author - Professional SQL Server 2005 XML
http://www.wrox.com/WileyCDA/WroxTit...764597922.html

Bob,

You might want to run a security analyzer program against all that embedded SQL... looks like an SQL INJECTION attack just waiting to happen... that's the reason why most folks use stored procs... they're one of the first lines of defense against SQL INJECTION...

--Jeff Moden

First of all, thanks ScottSQL for the comment. Next, Mr.Moden, I'm not quite picking up on the SQL Injection. Can you explain that a little further? Since it was only one query in my application, I saw no reason for prepared statements, but I guess you do what you are told in the workplace for the most part. Anyway, if you will, could you please give me some info on SQL Injection? It would be much appreciated!!

Hi Bob,

In Books Online, look up SQL injection. there is a great explanation on what that is.

Scott Klein
Author - Professional SQL Server 2005 XML
http://www.wrox.com/WileyCDA/WroxTit...764597922.html