Yeah, it's been a pretty crazy couple of months, but it's definitely on my list to do.

I second Gary's motion.

It's going to be a lengthy series of courses, one that is surely to be as long as all the Access courses combined, if not longer.  So I understand it may take a while to put the courses together.  If you think I'm hyperbolating, I assure you I'm not.  For instance, SQL Server does not support VBA, and it has its own "coding language" called T-SQL that is just as daunting to learn.  Advanced Access users may be able to pick up SQL Server faster because there is some overlapping of material (but only some) between the two.  I'd be interested to know what prerequisites Richard would require his students to have for the SQL Server courses.

I think I'm going to approach it from the standpoint of someone who is currently running their small business with JUST an MS Access database and wants to upgrade the back-end to SQL Server for security and performance improvements. That represents a good portion of my existing client base. From there, I'll move into whatever topics people seem most interested in. And yes, I could spend YEARS covering SQL Server... I've got a few dozen books on my shelf covering it. But I think for my client base, the basics should be adequate for now. I'm not teaching Fortune 500 database analysts here. :)

Richard, this is exactly what I was wanting.   My database is about to outgrow Access, so all I need is to retain the Access frontend, and migrate the database backend to SQL Server.    Like you said, I'm sure this is sufficient for the vast majority of Access users who don't have the time or need to completely switch to SQL Server.

Well, there really isn't an option to "completely switch" to SQL Server. It lacks the front-end designer that Access has. That's why I personally believe the best solution for a small business is an Access front-end and SQL Server back-end.

I understand you can't cover every topic in your courses, but if anyone deploys SQL Server in their company, they will need someone with (near) complete mastery of it to manage it.  There is just no ifs, ands, or buts about it.  SQL Server is a server-class tool, not a semi-end user product like Access.  It needs a capable admin who knows (nearly) all its ins and outs.  And SQL Server's ins and outs are a lot more complex than those of Access.

But broadly speaking, as subject matters become more complex, they may also become "unteachable," because they may not be attainable to those without the necessary foundation, and those who have the foundation to attain them may not need to be taught.  The assumption (more like an expectation) is that as students gain more knowledge and foundation, they will be able to pick up stuff on their own more easily.

If you deploy SQL Server via an online hosting service such as Winhost, you may be able to avoid dealing with certain ins and outs of SQL Server.  But considerable knowledge is still needed.

Good points.