Can't Figure Out Why Code Doesn't Work

[nosmoke]

I have the following bit of test code which, in my attempts to learn something about Access 2010 VBA, is based mainly from examples found in "Access 2007 VBA Programming for Dummies".

Dim cnnX As ADODB.Connection
Set cnnX = CurrentProject.Connection
Dim myRecordSet As New ADODB.Recordset
myRecordSet.ActiveConnection = cnnX

myRecordSet.Open "Select [First Name], [Last Name] From [Admissions] WHERE ([Address] Like 'Box 1954')"

myRecordSet.MoveFirst
Debug.Print myRecordSet.Fields("First Name").Value

The above code works i.e the correct "First Name" is printed in the Immediate window.

However, again following an example in the Dummies manual, if the middle line of code is changed to:

myRecordSet.Open "Select [First Name], [Last Name] From [Admissions] WHERE ([Address] Like '*ox 1954')"

i.e. the "B" in "Box 1954" is changed to a wild card character, the code abends with a message indicating a record(s) was not found.

The relevant example code portion in the Dummies manual is:

..... WHERE ([Email] Like '*@aol.com*')" which appears to be the same syntax as my case.

Could anyone please tell me why my code doesn't work...

TIA for any assistance.

[June7]

What does 'abends' mean?

The * is a wildcard character. The constructed SQL must not be recognizing the wildcard. Review http://msdn.microsoft.com/en-us/libr...ffice.10).aspx

What that comes down to is try using % instead of *. It worked for me when I tested your code.

[nosmoke]

Many thanks June7! The % worked as advertised. I also see from the article that ? must be replaced by _.

Strange all that because the Dummies examples are ADOB so I wonder why it supposedly worked for them. Must be differences between VBA 2007 and Access VBA 2010. Actually I was wondering if I would eventually run into such problems (have to get a more appropriate manual I guess).

BTW, I guess I'm dating myself with the "abends" terminology. It was common back in the 60s and 70s as applied to mainframe computing IIRC and simply stood for
"abnormal ending" i.e. the failure of a program to run properly, usually indicated by program termination and an error message(s).

[June7]

Must be an oversight by the author. I get same behavior with Access 2007.