FindFirst error

[Bazsl]

The code below generates the error "Runtime error 3251. Operation is not supported for this object type" on the line
rst.FindFirst "[Costume Number] = '205-001'"

I am new to Access and must be doing something dumb but I cannot find what I am doing wrong. Help will be appreciated. Thanks.

Private Sub Show_Costume_Description()


Dim dbs As DAO.Database
Dim rst As DAO.Recordset

'Get the Costume table recordset.


Set dbs = CurrentDb
Set rst = dbs.OpenRecordset("Costume")


'Find the Costume record for the current Checkout
'table record.
rst.FindFirst "[Costume Number] = '205-001'"

[ranman256]

dont use FINDFIRST.
Just filter the records in the search in the form. Then there's nothing to find, they ALL match.

'me.filter = "[state]='NY'"
me.filter = "[state]='" & cboStates & "'"
me.filterOn = true

[Bulzie]

Costume Number in the table is a text field?

[Bazsl]

Found the problem. If I open the recordset as a dynaset FindFirst works. Costume Number is a text field and it is the primary key so I only need to call FindFirst to get the unique record. Thanks.

[Micron]

What's the syntax for your solution? I suspect Set rst = dbs.OpenRecordset("Costume",1) since (I think) the default is dynaset but of type 0, which requires the records to be based on a single table or tables with one to one relationships. BTW, there is no guarantee that when you open a recordset that you will start at what you think is the beginning. I would .MoveFirst before using FindFirst.

[orange]

If I recall correctly, a DAO recordset will point to the first record after openrecordset even without the rs.moveFirst--if there is a least 1 record in the recordset.

You can test for this condition using
if rs.recordcount =0 then......'empty recordset
and if some records exist, the .movefirst is redundant

However, many people use it (moveFirst), probably because of the following:

DAO loads some records on the Openrecordset, but not all records.

If you want a true recordcount for the recordset, you need to do a rs.MoveLast to get to the Last record and the real count;
then do a rs.moveFirst to get back to the beginning on the recordset for Loop or other processing.

I have not found an m$oft reference, but I seem to recall learning that way back when...

[Micron]

You are correct. From MS:
When you create a Recordset object, the current record is positioned to the first record if there are any records. If there are no records, the RecordCount property setting is 0, and the BOF and EOF property settings are True.
If you want the page, it is here https://msdn.microsoft.com/en-us/lib.../ff197799.aspx
Interesting info there about how undeclared rs types are handled. Seems you're taking your chances if you don't declare the type.
Thanks.