Throwback Thursday: March 26, 2026
In today's edition of Throwback Thursday, we review some common gotchas of the SQL BETWEEN statement and how to avoid falling victim to these potential logic errors.
With over a million words scattered across more than 1,500 articles on this blog, you've probably missed a few things here.
That’s why each week in "Throwback Thursday," we’ll revisit some standout posts. Expect a blend of my personal favorites, insightful articles from other great minds, and a touch of coding humor to keep things light.
Highlights from NoLongerSet.com
Beware the BETWEEN
Using the BETWEEN clause with date-time fields may lead to unexpected results. There’s a safer alternative.
Mike Wolfe
3 Gotchas of the SQL BETWEEN Statement
The SQL BETWEEN statement produces very readable condition expressions. But developers of all skill levels can still get into trouble with it.
Mike Wolfe
A Safer Alternative to BETWEEN When Filtering Dates
This convenient function generates defensive SQL statements to help you avoid the subtle dangers of the BETWEEN statement when filtering dates.
Mike Wolfe
Wisdom from Around the Web
Microsoft Access tips: International Dates in Access
How to ensure dates are interpreted correctly in a Microsoft Access database, even when the user’s regional settings are different from the US format.
Examples of using dates as criteria in Access queries - Microsoft Support
When entering dates as query criteria, enclose them in pound signs (#) to help Access understand what they are.
Cover image generated by Ideogram
