Access 2003 - Me.Filter - not working?

[Sheree]

I have some Access 2003 VBA code that looks like this:

Private Sub SubName()
Me.FilterOn = True

Me.Filter = ""
' Me.FilterOn = False
' Me.Requery
x = msgbox("Filter Cleared. Number of Records: " & Me.Recordset.RecordCount)

Me.Filter = "Mother LIKE '%" & PT_Mother.Text & "%' OR Mother_AKA LIKE '%" & PT_Mother.Text & "%'"
' Me.FilterOn = True
' Me.Requery
x = msgbox("Filter Applied. Number of Records: " & Me.Recordset.RecordCount)
End Sub

What happens the FIRST time this sub is run is that the first msgbox shows an unfiltered total like it's supposed to. The second msgbox shows 0 records.
All subsequent runs yield what looks like random quantities of records, that don't have anything to do with the filter.

Attempting to toggle .FilterOn or .Requery doesn't seem to help.

I'm new to Access VBA, and there's probably something I'm missing, but what?

[puppydogbuddy]

This question duplicates your other post
http://www.thescripts.com/forum/thread745378.html
This causes confusion and is against site rules.

[Sheree]

This question duplicates your other post
http://www.thescripts.com/forum/thread745378.html
This causes confusion and is against site rules.

This code is different than the other code. This code uses the form's Me.Recordset property, and the other code uses an ADO recordset. Whichever works, but they do not use exactly the same properties and methods!

[MikeTheBike]

This code is different than the other code. This code uses the form's Me.Recordset property, and the other code uses an ADO recordset. Whichever works, but they do not use exactly the same properties and methods!

Hi

I could be wrong (what again!), but I believe that the form recordset is DAO, which uses * as the wild card characture, but ADO (and SQL ?) uses %.

Could that be the problem?

MTB

[Sheree]

Hi

I could be wrong (what again!), but I believe that the form recordset is DAO, which uses * as the wild card characture, but ADO (and SQL ?) uses %.

Could that be the problem?

MTB

I guess it could -- I've never used DAO before... just ADO scripting with vbscript, javascript, and now (grumble grumble *RABBLE RABBLE*) VBA. I've switched it back to ADO though, as I'm having better luck with it in general. (That would be that other thread referenced above.)