DP and Mart offer some great advice!
Bottom line to me is, since you are a self proclaimed novice, why not go directly to the technology that you will end up in anyway? What I mean is, I can see no reason to learn Access if you are eventually going to dive into SQL anyway.
You are at the right place to learn the difference. Bruce has coded the WWforum for both SQL and Access, a quick look at the code can really tell you some of the differences.
Can you download the trial version again? Not likely. There are a few registry entries you'd have to find and remove. But from the MS website, you can register your trial as a developer for $50usd.
DP offered a great suggestion. The upsizing wizard in access works great and it will reveal any table structure issues. (because some query's or inserts will stop working.)
Also, re: MSDE - I have gone down that road but when MS came out with the dev price for full SQL, I stopped "playing" with it. It is a viable option.
(SideNote: You said you were developing a DOT NET / C# application. A great place to look is
http://lab.msdn.microsoft.com/express/vwd/ because it will install a free version of SQL express. (grin) ---
Caveat! The ASP.NET v2 is still in beta and most hosting companies won't support it. I've installed it locally, but won't even think of using v2 until it's been out for 6+ months. That gives the dev community enough time to poke holes in the release and find all the security and other bugs.)
Like DP said... true/false (Yes/No) is a big issue as are dates. I've had to wrestle with a few null issues in conversions as well.
If it were me... if the access backend is working for you then use it. Try the upsizing wizard in a development environment and then use it as an object lesson. While you're fixing the SQL statements and fields, you should also consider investing time into stored procedures. The whole process of upsizing is a great way of learning the difference. (Well, I'm speaking from experience with Access 2000, I have no idea about 2003... sorry.)