Creating new records in Microsoft Access

[ulillillia]

I'm trying to make plans for my 2D RPG game. I originally used Excel, but it's hard to get a glance at how something is, especially since the field count measures in the dozens, mostly as simple numbers. I thought of using Word and making use of tabs, but adding and rearranging fields is time-consuming since I have to do the same thing each time dozens of times over. So, the solution I have is using Microsoft Access. I made the form, table, and query that is supposedly needed, now I just want to fill out the form for each aspect of a group, such as the list of the game's spells. I don't care for searching, filters, or any of that stuff, I just want an easy-to-see interface where I can look at the specs of spells at a quick glance, done by looking through the records. Trouble is, the "new record" button is grayed out. What do I need to do to make new records? I took a screenshot, removing confidential parts, to show you what I mean.

View 1920x1440 screenshot

Any ideas what I may be missing?

[whiteflags]

It looks like you are trying to modify a table from a form which is not a very smart idea. If your forms are not read only then you can do it, but it shouldn't matter: Edit the table you should have created. It's the safest, especially if any of your tables have a relationship. I've never heard a compelling reason to edit a database from a form.

The form should be updated automagically when you save the table.

Queries will need to be ran again, though.

You can also edit from queries, (delete records, etc.) but this may actually corrupt the database depending on the tables you reference and their relationships, so make sure you read your help file (it's been a long time since my last database course; you can probably tell).

[ulillillia]

Filling out the form updates the database based on the input. The table is just for what types of content goes into the field (such as text or numbers). I found the problem now and it's working. I've got 2 records so far - fewer than expected due to a problem I spotted in my main plans. That's the nice thing about planning before you make it - you can spot potential problems before making it, otherwise it's a lot more work having to redo sizable chunks of code from one small mistake in a detail.