DAO Recordset FindFirst

[GraeagleBill]

I must not be using FindFirst correctly, see snippet of code below.

With rsRegEMAs

bolrsRegEMAs = True

lngEMACount = 0
intEMAPartCnt = 1

.FindFirst Not IsNull(!EMA)

If Not .NoMatch Then
    lngEMACount = 1
    blah
    blah
    blah
Else
    Msgbox "no EMAs found blah blah............
end if

The current DAO Recordset has many records containing non-Null EMA expressions but "NoMatch" must be true because the Else path is taken. I assume I've used the FindFirst incorrectly?

I tried putting the option in quotes like .FindFirst "Not IsNull(!EMA)" but runtime then does not recognize the field reference to !EMA.

[Micron]

AFAIK, You find first from the underlying domain, not the recordset itself. Check out
https://docs.microsoft.com/en-us/off...rst-method-dao

...the criteria should be in either the form "field = value" where field is an indexed field in the underlying base table,...

Bold format is by me.

[GraeagleBill]

Using the statement:

.FindFirst "!EMA <> Null"

while satisfying the FindFirst syntax fails because !EMA is not recognized as a field. In the underlying query, EMA is coded as a substitute for "eMail_Address", i.e., EMA:. Further, eMail_Address is not an indexed field.

Because of other considerations I think I'll just step through the recordset one record at a time and examine the EMA as I go.

[John_G]

I tried putting the option in quotes like .FindFirst "Not IsNull(!EMA)" but runtime then does not recognize the field reference to !EMA.

Try putting the criteria in quotes, but without the "!" :
.FindFirst "Not IsNull(EMA)"

[GraeagleBill]

Thanks John. After digging a little deeper into the very old app, basic human intelligence prevailed and I just tweaked whatever filter might have been in affect and processed as needed with a clone.

(Whatever possessed me years ago to name a table field that includes a dash character totally alludes me. Same can be said of "blanks". Including "EMA As e-MailAddr" in a query is okay most of the time, but not everywhere. At the moment, I can't remember the exact context where the EMA reference failed at Runtime.)

Private Sub cmdEMAToCB_Click()
'*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
' Unless invoked via the "Selected" UI, the current recordset may or may not have any
' EMA's.  With that, we append additional criteria to the existing RecordSource to
' exclude records that do not include EMAs.
'*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
If Me.FilterOn Then      'Applies to both QRegistry AND QGroupings
    Me.Filter = Me.Filter & " AND not isnull(Registry.[e-MailAddr])"
Else
    Me.Filter = "not isnull(Registry.[e-MailAddr])"
    Me.FilterOn = True
End If
Me.Requery

EMAtoCB ("Clone")      'Get full or filtered set (EMAtoCB will now have a clean DOA Recordset to process)

End Sub

Thanks again,
Bill