Help with proper set up of relationships for new database

[gafort]

I am going to set up a new database for my trade group. We host monthly meetings where members get their continuing education credits for their licenses as required by the State of Ohio. The goal is to issue membership badges with bar codes to swipe for time and attendance and print certificates.

Current setup:
Members register through Constant Contact for main meeting and early roundtable meeting if attending.
Once registration closes, I download csv file and convert into sign in forms which member initials upon sign in to the meeting. At conclusion of meeting, certificates are issued proving attendance. Registration rolls are then copied and forwarded to the State.

I’m thinking I will need separate tables for the following:

Members Information: Name, address, State ID, membership dues status (paid-not paid)
Monthly Classes: Instructor, date, class number, hours approved, certifications approved for


Monthly Registration: Who signed up for early class (choice of two) and main class
Walk in Registration: There are always some who forget to register online

For the membership badges there are two ways to go. One is to print on paper and include a bar code, then laminate. This would use the State ID number directly.
The other method would be to purchase logo printed cards that look like credit cards and are sequentially numbered. These look much better but the sequential number would have to be linked to the State ID number.

Am I on the right track for the tables or do they need to be broken down even further?
Which fields would I want to use for primary keys?
This will get me started. I will have many more questions as the database develops. Thanks in advance for your help.

[June7]

I don't know why the registration records have to be two tables. The method of registration could be another attribute field of one table.

Otherwise, looks like a good start.

Why do you need to export to CSV to produce sign-in forms? This could be a report in Access.

Either badge method would work. However, second method would mean more data entry to input the sequential ID associated with each State ID number. Or can't you have the State ID number printed on the card along with name? Couldn't it be part of the bar-coded info? You expect them to hold onto and present the badge every month? Method two might be worth the effort and expense.

[gafort]

One registration table makes sense. Attribute could be online or in person.
I do not export CSV. I import from Constant Contact. We use them instead of the website for PayPal transactions for certain events.
I thought of having state ID barcoded but thinking that might not be best for two reasons: cost and lost cards.
We can buy sequential cards under a dollar in minimum quantities. We will get new members and members will lose cards. If we have 200 extra, we can delete old cards and add new.
Thank you much for your input.

[June7]

And each time the card is replaced, have to edit the record to show the new sequence number. Would you care about maintaining history on replaced cards?