Search on date not working?

• In Private Sub CommandButton1_Click() there is a loop.
• For Each Ctrl In Me.Controls
• which calls GetStatistics m_id & "-" & TextBox1.Text, "admin", "Database.ACCDB"
• which writes the data to ws.Range("A2").CopyFromRecordset DBrs

Obviously, that same range is used on every loop. Therefore you will only ever get to see the last set of data unless the last set is shorter than any of the previous. In that case you will see some data that don't belong at the bottom.

Therefore you should do two things.

1. Clear the space of any previous data
2. Make the destination cell dynamic, perhaps using code as shown below
   which would define the cell below the last used cell in collumn A.

    If Not DBrs.EOF Then
        ' Data search return into sheet4
        Ws.Cells(Ws.RowsCount, "A").End(xlUp).Offset(1).CopyFromRecordset DBrs
    End If
    DBrs.Close
    DBcon.Close
    Set DBrs = Nothing
    Set DBcon = Nothing

By the way, the following snippet of your code is inviting me to comment. If you like, please read my commentsd below it.

On Error GoTo procerr
    If Not DBrs.EOF Then
    ws.Range("A2").CopyFromRecordset DBrs
    End If
    DBrs.Close
    DBcon.Close
    Set DBrs = Nothing
    Set DBcon = Nothing

    GetStatistics = True

procerr:
'MsgBox (Err.Number)
 Exit Function

End Function

1. GoTo commands are considered disruptive of the flow of code. Best practice is to avoid them.
   1. An exception would be a true error handler that identifies and corrects the error and ends on Resume, which returns code execution to the point where the error occurred. An example would be a missing worksheet which the error handler creates.
2. Your "error handler" ends on Exit Function which, to be frank, doesn't make a lot of sense coming, as it does here, just before End Function. Omitting the line would proviode the same result with less code.
3. In order to maintain the flow of execution it's better to use On Error Resume Next just before the line you expect to cause the error and then
   

   If Err.Number Then         ' if Err is any number other than 0
       MsgBox Err.Number & vbCR &  Err.Description
       Exit Function
   End If

4. Of course, Exit Function is also a disruption of the flow but it is acceptable here because this is a fishing exhibition. You just want to know the name of the error and the final version of the code won't include those 4 lines. Where this isn't the case a construction like the one shown next may be preferrable. It just continues execution after the message.
   

   If Not DBrs.EOF Then
       On Error Resume Next
       ws.Range("A2").CopyFromRecordset DBrs
       if Err.Number Then MsgBox "Couldn't read the recordset."
   End If