Don't worry - not offended!
Man, if you could learn relational databases then you would be well on the way to a significant improvement on your design. If you go down the MySQL route, then I can provide support, but be warned: relational database design is an entirely new discipline to learn, and is not the same as programming. I've never looked for tutorials, but you might find something useful out there. If so, try and find something that provides MySQL examples.
SQL is not simpler than Access. I think it is probably easier to get up and running with Access databases, because of all the hand-holding tools. In fact when I started doing some serious programming, I used Access's query builders to help me construct SQL commands. So it has its uses. But SQL is faster by several orders of magnitude (in my non-rigourous impression...) and much more robust, and perfectly suited to large databases and multi-user environments.
In your final comment you refer to two users overwriting each others inventories. No. You have a table of users, and a table of inventories. You use the user's ID to link to the corresponding entries in the inventory table.
If you install MySQL, also get hold of phpMySQLAdmin; excellent for adminstering MySQL databases in a php environment.
Addendum: if you get the MySQL ODBC connector, you can actually use Access as a frontend to MySQL tables. i.e. get the power and speed on MySQL queries on the tables that are stored on your MySQL server, coupled with the ease of interface design of Access. A veteran DB programmer told me many years ago that you should always keep your data separate from your interface. He was right.