Casey, in Excel, a database is just a list of records -- data in rows, with a column header at the top that describes each column. So for a car database, it might be Make, Model, Year, VIN, color, upholstery, ... whatever you want to store.

What data is in the database will determine how to lay out the form -- does that make sense?

Do you have to implement the search functions from the form, or just design a form for data entry?

As a future naval architect, you will base ship designs on requirements -- cargo ships, 12m yachts, and attack submarines diverge early, even to the point of always remaining buoyant. What are yours? Even if you were given none (as an exercise in strategic problem solving), you have to define some on your own before you can start coding.