Throwback Thursday: September 11, 2025
In this epoch edition of Throwback Thursday, we explore several key compatibility considerations between Access and SQL Server.
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
Linking to SQL Server Date Fields from Microsoft Access
I always avoided SQL Server’s DATE type in favor of the DATETIME type’s better compatibility with MS Access. A newer ODBC driver has me changing my mind.
Mike Wolfe
Yes/No Fields in SQL Server
The SQL Server equivalent of an Access Yes/No field is the “bit” data type. Or is it?
Mike Wolfe
Floating Point Arithmetic in VBA vs. SQL Server
VBA and SQL Server do not perform floating-point operations the same way. Being aware of this difference could save you hours of frustration someday.
Mike Wolfe
Epoch Differences Between VBA and SQL Server
Do you have unexplained dates of December 30, 1899 in your SQL Server database? VBA’s epoch (i.e., zero date) could be the culprit.
Mike Wolfe
Wisdom from Around the Web
My First BillG Review
In the olden days, Excel had a very awkward programming language without a name. “Excel Macros,” we called it. It was a severely dysfunctional programming language without variables (yo…
Joel Spolsky
Developer Humor
Bug
Cover image generated by Ideogram
