I have to make a database to track university apartments in access. I am stuck trying to decide what type of tables and field names i should have.
would it make sense to have a table for students including first, last names, address, city, postal code, telephone number
table for apartments including number of bedrooms, rent cost, lease term, utilities, parking, address
and a final table for landlords including first, last names, address, telephone, city, state, postal code, telephone number
does this make sense or am i on the wrong track.. what would i use as the prmary key??
thanks!
Your approach seems to be on the right track. Creating separate tables for students, apartments, and landlords is a good way to organize your database for tracking university apartments in Microsoft Access. Let's go over the suggested tables and their potential field names:
1. Students table:
- Primary key: Student ID (a unique identifier for each student)
- Fields: First Name, Last Name, Address, City, Postal Code, Telephone Number
2. Apartments table:
- Primary key: Apartment ID (a unique identifier for each apartment)
- Fields: Number of Bedrooms, Rent Cost, Lease Term, Utilities Included, Parking Available, Address
3. Landlords table:
- Primary key: Landlord ID (a unique identifier for each landlord)
- Fields: First Name, Last Name, Address, City, State, Postal Code, Telephone Number
By including primary keys for each table, you ensure that each record in a table has a unique identifier. This helps maintain data integrity and allows you to establish relationships between the tables.
Regarding the field names, the ones you have suggested for each table seem appropriate. However, you may want to consider adding a few more fields to enhance the functionality of your database. For example, you might want to consider adding a field for Email Address in the Students and Landlords table to store contact information. Additionally, you could include fields for Apartment Availability and Property Type in the Apartments table to provide details about the apartment's status and type (e.g., studio, one-bedroom, etc.).
Remember, your table design should capture all the necessary information required for tracking university apartments, and the field names should accurately represent the data being stored.