James I would still wait to hear what Richard's advice is, having said that I would move my backend to SQL Server now if I were you. First you save yourself having to deal with the additional 25%. Also you go through the learning curve before the system is complete.

That's a tough situation. I remember when I first started migrating my database up to SQL Server, I did it a little bit at a time. I started with the tables that weren't used as much, just to make sure they'd work properly, and then slowly started moving more and more objects over, building views and stored procedures as needed. It was a slow process. You don't have to do it all in one day.

I'm definitely going to be spending a lot of time on taking a local Access database and migrating it up. That's the main focus of this class. Just be patient, and I would recommend you wait until I've got the first two or three levels out and then decide.

Thank you Sami and Rick.  I think what I will do is sort of a tandem process.  The database I have in Access is a full featured Golf league database with financial, golfer stats and billing features.  I was going to pair it with PowerBI in the end but I need to get it up and running here within a few weeks.  I am going to start, as you suggested by creating my table in SQL and then as the lessons move forward, sort of recreate what I have built in Access in SQL if that makes sense....allows me to pound the learning into my 76 year old brain.  Thank you both for your input and I will be signing up for all classes as they come up.