Designing a database for a specific purpose is common. More experience with the database leads to "Could it do this".
Designing for a worst case scenario (Client with two addresses, or 3 email accounts or 5 phone numbers) is often time saving over time.
You have months, with incomes, from addresses.
You have renters, rent date, rent amount, amount received, date received, move out date, damage deposit, pet fee, etc.
Creating the necessary tables (three? four?) and relating them for the reports you need is the trick.
RENTAL, Renter, Monthly, etc
This list of FMP links (the first 5 especially) would be worth the read.
Ok, so I would need to create the following if I understand correctly:
- create a table for rent periods and connect that fk to the __pkPropertyID
- Create two fields in that table: start date and vacant (end) date
- add those fields to the layout of the rent period table.
- insert a portal in my property layout with the fields from the rent period table and allow creating records via property layout and such.
I can later add fields such as 'months rented' and 'rent revenu for this period' etc right?
please let me know if this it the right and best way to achieve this.