- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Jan 22, 2025 12:02 PM
We use AT to manage rental properties. Here is a scenario and then what I am looking to accomplish.
We list each house as a record in a base. We have a filed for when a house goes vacant to track when the rental turn project start and another for when it ends. I don't want to lose historical data the next time this same house goes vacant and needs a turn project. I would like to keep track of each time these change and create a place where we notate the last time before update the new updates. This will allow us to have a history of how long vacancy lasted and over time and with multiple properties we can get a feel for how long they last on the whole portfolio.
Thank you in advance for your help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Jan 22, 2025 12:09 PM
Hey @brightler!
Given your description, I'm assuming you are currently entering all of your data in only one table?
I would suggest structuring your data in at least two different tables:
1. Properties
2. Rentals
Now if you link Rentals to Properties (through linked record field), you can keep historic track of all rentals (and vacancies) for each Property.
Your database architecture will fully depend on your needs, but given your description this is my smart guess!
Please feel free to schedule a brief call using this link, and I'd be happy to show you around some best practices.
Mike, Consultant @ Automatic Nation
![](/skins/images/DD0CD7D0ACF200EF4456420D87029A3D/responsive_peak/images/icon_anonymous_message.png)