A family of Microsoft relational database management systems designed for ease of use.
Unfortunately, the people who volunteer their time here (and elsewhere) are NOT able to do research on your behalf regarding questions posted on other forums.
However, to address a couple of your comments.
Yes, Access is indeed a great choice for this kind of database application.
All of those tasks you describe are commonly handled in different applications.
If you want to look for sample databases and templates that can help you get started, that would be a good investment of your time. There might even be samples out there based on a very similar business model. It's a matter of using the search tools available to you.
You are not correct in thinking that Access does not use SQL logic. The foundation of Access and nearly all other relational database applications is the use of SQL, via queries, to manage your data. The data resides in tables. Getting the data into and out of tables, and manipulating it all involve SQL in one way or another, either directly through queries or indirectly through bound forms.
In conjunction with understanding that, it's probably also worthwhile to review the basic components of a relational database application.
There are three primary components:
The Data Layer:
All of your data is stored in tables in a database. Access has a built-in database called ACE. However, Access also has the ability to connect, or link, to many other databases such as MySQL, SQL Server, Postgres, Oracle, and others. The more complex applications tend to use of the larger database engines, but the ACE database engine built-in to Access will be fine for a small, simple application as you describe it.
The Interface:
You and your users interact with the data in the tables through a custom interface. It consists of forms and reports primarily. Forms are used to manage data interactively. Reports are used to summarize and display data.
The Logic Layer:
You need code that manages all of the other components. It will include VBA code and sometimes Macros. This code incorporates the logic that underlies your application.
The first, and most fundamentally important component is the table design. Start there.
Decide what data you need to track: Rental property, rental agreements, tenants, repairs and maintenance, and all of the other things that go into the process. Set up your tables accordingly. Then you can come back and ask people to review and suggest enhancements.
Get started by investing time in learning about the Rules of Database Normalization.