Personally I would stick with the SQL server, I hear of far more issues with sharepoint (which will require the same if not more front-end setup). Especially if you are currently not using SharePoint for something else. You could ask questions here if there's only a few things that are confusing you, or if the learning curve is too much you could have someone set it up for you in the DevNet.

Hi Julian,
Watch https://www.youtube.com/watch?v=Uw6JBJfcjCo.
"Albert Kallal, former Microsoft MVP, will share his experience using Access Front End accdbs with SharePoint Lists. Albert will tell us "what is great, what to watch out for, and how this solution is easy, and great option for Access users." Albert's knowledge of SharePoint is unmatched in our community. This is good".
He explains you don't have to change anything on the front-end if you build it right.

I personally recommend SQL Server. The only reason why I did my SharePoint seminar in the first place was because I had a bunch of customers who said they already have SharePoint set up in their offices, and that's what their company requires them to use. They wanted to see how to connect their Access database to their SharePoint lists, so I only recommend using Access if you already have SharePoint set up and that's what your company is demanding. Otherwise, setting up SQL Server online is not that difficult once you get your tables up and you connect your Access database to it. The rest of it's pretty much just like you're running a normal Access database. If you didn't get it the first time through, watch the seminar a second time, follow along with the steps, try setting up a sample database first; don't try to set up your own work database the first time. Set up a play database, maybe something for a hobby that you have, and then, after you get it, and you will get it, move on to your regular database. It's a much better solution than SharePoint and much more secure, too.