SQL LIKE operator with parameters and wildcards

calendar_today Asked Dec 31, 2012
thumb_up 5 upvotes
history Updated April 14, 2026

Direct Answer

MS Access uses * as a wildcard not %, so your query will be trying to match literal '%' characters. Use * instead unless you are using ADO.…. This is an advisory response with reference links, ranked #60th of 67 by community upvote score, from 2012.


The Problem (Q-score 6, ranked #60th of 67 in the Access VBA archive)

The scenario as originally posted in 2012

I have a query where I want to return all Clients that have a certain string in the name with wildcards on either side. So the input could be “Smith” and i want to return all things like “The John Smith Company” or “Smith and Bros”. I want [Client] to be prompted so I set up the SQL like this:

PARAMETERS Client Text ( 255 );
SELECT *
WHERE (((tbl_IncomingChecks.Client) Like'%' + [Client] + '%') 
ORDER BY tbl_IncomingChecks.Client;

The query is not returning any results. Please help

Why community consensus is tight on this one

Across 67 Access VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — niche answer (below median) (+5)

Advisory answer — community consensus with reference links

Note: the verified answer below is a reference / advisory response rather than a copy-ready snippet.

MS Access uses * as a wildcard not %, so your query will be trying to match literal ‘%’ characters. Use * instead unless you are using ADO.

http://office.microsoft.com/en-us/access-help/like-operator-HP001032253.aspx


When to Use It — vintage (14+ years old, pre-2013)

Ranked #60th in its category — specialized fit

This pattern sits in the 84% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.

What changed between 2012 and 2026

The answer is 14 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

This is a below-median answer — when does it still fit?
expand_more

Answer score +5 vs the Access VBA archive median ~4; this entry is niche. The score plus 6 supporting upvotes on the question itself (+6) means the asker and 4 subsequent voters all validated the approach.

This answer links out — what are the reference links worth following?
expand_more

Read the first external link for the canonical reference, then search this archive for a top-10 entry in the same category — advisory answers are best paired with a ranked code snippet to close the loop.

This answer is 14 years old. Is it still relevant in 2026?
expand_more

Published 2012, which is 14 year(s) before today’s Office 2026 build. The Access VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Access VBA pattern ranks just above this one at #59?
expand_more

The pattern one rank above is “Creating a DSN-less connection for MS Access within Java”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 6, Answer-score 5, original post 2012, ranked #60th of 67 in the Access VBA archive. Last regenerated April 14, 2026.