IMHO, ODBC connection is the easiest & quickest way to go. I've been doing nothing but Access front-ends to SQL for the last 15 years, and it can make for some quick development turn around. I've got functions out the wazoo for dealing with linked tables & connectivity, converting access queries to SQL views, user information, etc.
One thing to keep in mind is whether or not any other applications will be using the SQL data at the same time, specifically updating with record locking. Since Access keeps a static connection open, if another app is trying to lock a table, it will hang if Access has it open. If you have the time to create views on all of the tables that will reduce the problem.
Also, if you're using integrated security you can utilize user information on the Sql side to track usage. If you're doing more than just report development, move as much business logic as you can to sql. My rule of thumb is to do it in SQL if it can be done.
I'm going to stop rambling now. If you have any specific questions just holler.