Good article, as always, Andy!
Since Access 2000, I've been a big proponent of using Access Data Projects (adp's) when possible - there's less "plumbing" between the query designer/form/report and SQL Server, and as Steve Erbach rightly mentioned, you get to use T-SQL syntax instead of Access SQL.
Having said that, linking Access to SQL Server just the way you showed us is an excellent way for people to expand their SQL knowlege, if that's what they want to do.
I started life (at age 43) as an Access developer in Jan 1993. Steve Jones - you'll get a kick out of this - it was at Calvert Cliffs Nuclear Power Plant! A year later, our large IDMS mainframe-based maintenance & equipment database was converted to Oracle 7.3, and I found Access with ODBC to be a much more useful querying and reporting tool that what was then available from Oracle at less than 1/3 the cost per seat. Over the next few years, I easily taught hundreds of people on site how to get information out of that Oracle database - something that had been a black science using arcane JCL and FOCUS before '94.
When I became a VB developer in '98 and had to program against SQL Server databases, I started by first linking with Access and using its query designer to generate SQL, which I pasted into Query Analyzer. By trying to run that SQL and correcting the mis-translations, I quickly got used to T-SQL, and soon abandoned the "via Access" route. But Access turned out to be great SQL Server Training Wheels.
Access was revolutionary in '93, and now, even after 13 years, it's still a very productive environment. I rarely do any Access project any more, but I always enjoy them when I do.