There is a ton you can do. Research normalization. When you build stuff, take an overly simplified approach until you feel comfortable. Focus on understanding tables, queries, forms, and reports. That's the easy part. Once you got that, read about modules, subs, and functions (just the basics). The code is what lets us do generally whatever we want, but it has a steep learning curve.
edit- I've got some time to kill, so I'll explain a little more.
Tables
Tables store the data. Understand that a table is not exactly like a spreadsheet in excel.
Normalization
There are online resources that explain this better than I ever could, but I'll try in a simplistic way. The idea is that alike data is stored in it's own table. So if a customer can have multiple phone numbers, then perhaps you would have tblCustomers, and tblCustomerPhoneNumbers. The customer table has an ID, and other fields relevant to customers, with NOTHING about phone numbers. The phone number table also has an ID, a foreign key, and the actual data. The foreign key provides the link to the customer's table.
Queries
This is how you ask questions about your data. Suppose you want a list of all customer phone numbers. In a query, you can use both the customer's table and the phone number's table to bring related sets of data together. These sets are related between the customer ID and the foreign key in the phone number's table. When you run the query, you can now see phone number's with corresponding customer name's.
Forms
These are the method of entering data.
Reports
This is how we print an analysis of our data.
Modules
These store code that can be used in any form.
Subs
A sub routine carries out a set of instructions.
Functions
A function can also carry out a set of instructions, but more importantly, it returns a value. You can ask what a function equals, and you should get something returned. If you asked what a sub equals, you'll get an error.
