Error using findfirst

[moepusu]

I try to use findfirst command and I got error.
Could someone please help me to find the solution:?
My code is as follow

Dim db As Database
Dim rs As Recordset
Dim strCriteria As string


mdate=date-10


Set db = CurrentDb()
MsgBox strCriteria

Set rs = db.OpenRecordset("Calendar")
strcriteria=mdate


rst.FindFirst(strCriteria)' error shown as run-time error 424 object required'
If rst.NoMatch Then
MsgBox "No entry found"
Else
mrdate = hrdproc
End If
Msgbox mrdate


Thank you in advance

[Mariostg]

You Dim and Set rs, but use rst...

You should also take the habbit of declaring whether you use DAO or ADODB when you declare recordset.

[moepusu]

Thank you for your advice

I just changed and re-run the program with new criteria since my old criteria doesn't work. Another error shows. please see below


Dim db As DAO.Database
Dim rst As DAO.Recordset
Dim strCriteria As string

mdate=date-10

Set db = CurrentDb()
strCriteria = "[rdate] = " & mdate
'strCriteria = mdate

MsgBox strCriteria

Set rst = db.OpenRecordset("Calendar")

With rst
.FindFirst (strCriteria)' error show - runtime error 3251, operation is not supported for this type of object
If rst.NoMatch Then
MsgBox "No entry found"
Else
mrdate = hrdproc
End If
End With

[Mariostg]

I don't use the findFirst featur too often, but it appears you must specify a recordset type dbOpenSnapshot for it to work:
Set rst = db.OpenRecordset("PayList", dbOpenSnapshot)


[moepusu]

Hi
Thank you again, no more error
but, still problem

msgbox strCriteria show as 4/16/2011, since I use mdate=date-10. That is correct.

But when I write the code: msgbox mrdate nothing in there. keep showing "no entry found", Actually supposed to show 4/29/2011 according to my data.
rdate is date structure with index .
Do you have any idea?

Thank you so much

[TheSmileyCoder]

The thing is when you later try to use the string strCriteria with the findfirst function, it will get evaluated by the JET engine. Thus instead of a date, JET will see it as 4 divided by 16 divided by 2011.

I suggest you look at this insights article here on Bytes, it will tell you all you need to know about the issue.
Literal DateTimes and Their Delimiters (#)