ANYBODY HAVE A REAL ESTATE RENTAL DATABASE?

[KGB003]

I'M TRYING TO SETUP A DATABASE FOR OUR REAL ESTATE RENTAL BUSINESS AND I AM
BRAND NEW TO ACCESS.

I NEED TO SHOW WHICH PARK THE UNITS ARE IN, THE ADDRESS, CURRENT RENTERS,
WHEN THEY MOVE IN, THEIR NAME, RENT AMOUNT, THE MONTHLY RENT DUE, THE DATE OF
PAYMENT, OVERDUE AMOUNTS. I ALSO NEED HELP SETTING UP THE REPORTS.

 

[BruceM]

Use of all capital letters in a newsgroup posting is regarded as shouting,
and is considered a breach of etiquette. Also, it tends to annoy people,
which is not the best way to get an answer.

 

[PC Datasheet]

I can help you with any part of this or the whole database. My fees are very
reasonable.

 

[KGB003]

Use of all capital letters in a newsgroup posting is regarded as shouting,
and is considered a breach of etiquette. Also, it tends to annoy people,
which is not the best way to get an answer.



Sorry for if I offended anyone with the capitol letters but in a way I was shouting for HELP. I have been trying to set up a data base on my own and I can't get it right.

 

[Duane Hookom]

Steve/PC Datasheet,

Some people just don't understand that it isn't polite to advertise.

This thread is barely 1/2 hour old and you are already posting your
advertisement.

Can you imagine how clogged and unruly these NGs would be if everyone had
the same attitude as you? What if every time someone posted a question, they
got 20-30 replies like yours? OPs expect to get free support, not ads.

Your ethics are incredibly corrupt!

 

[BruceM]

That would be quite a project if you are new to Access. For some purposes
it is simpler to buy software than to invest in the time needed to learn a
program and create a database. You could keep monitoring the thread in case
some suggestions come from it. In the meantime a Google search can yield
some helpful results if the search is worded properly. Here is one
possibility from entering "Real Estate Rental Program" (without the quotes):
http://www.google.com/search?hl=en&lr=&q=Real+Estate+Rental+Program&btnG=Search

 

[John Vinson]

I'M TRYING TO SETUP A DATABASE FOR OUR REAL ESTATE RENTAL BUSINESS AND I AM
BRAND NEW TO ACCESS.

I NEED TO SHOW WHICH PARK THE UNITS ARE IN, THE ADDRESS, CURRENT RENTERS,
WHEN THEY MOVE IN, THEIR NAME, RENT AMOUNT, THE MONTHLY RENT DUE, THE DATE OF
PAYMENT, OVERDUE AMOUNTS. I ALSO NEED HELP SETTING UP THE REPORTS.

Please... lay of the caps lock. It's hard to read, and considered
impolite - it looks like you're SHOUTING AT US.

I'm not aware of any templates to do this, but it should not be a very
complex database to set up. Identify the Entities - real-life persons,
things, or events of importance; each type of Entity should get its
own Table. I can see a table of Parks, one of Units (containing the
address), a table of Tenants, a table of Rentals (linked to both Units
and Tenants), and a table of Payments. Once you have the tables
constructed you can work on queries to link them and Reports to print
them out.

It's not going to be trivial, but it's very much something that Access
can do for you!

John W. Vinson[MVP]

 

[Vincent Johns]

Please... lay of the caps lock. It's hard to read, and considered
impolite - it looks like you're SHOUTING AT US.

I'm not aware of any templates to do this, but it should not be a very
complex database to set up. Identify the Entities - real-life persons,
things, or events of importance; each type of Entity should get its
own Table. I can see a table of Parks, one of Units (containing the
address), a table of Tenants, a table of Rentals (linked to both Units
and Tenants), and a table of Payments. Once you have the tables
constructed you can work on queries to link them and Reports to print
them out.

You might want to try using the "New Table Table Wizard", in which some
of the sample Tables contain fields that are relevant to your needs.
These are suggestions, and you can include fields from several of these
samples. For example, for your [Tenants] Table, you could use some
fields from the "Mailing List" sample.

It's not going to be trivial, but it's very much something that Access
can do for you!

John W. Vinson[MVP]

For each of the Tables you set up, let Access create a "primary key",
which will give you an easy way to link Tables together (for example,
linking records in [Units] to the [Parks] record in which they are located).

-- Vincent Johns <[email protected]>
Please feel free to quote anything I say here.

 

[Sprinks]

I fully agree with Vincent on using an AutoNumber primary key for each table,
but a more meaningful name, such as RentalID, or PaymentID, is more useful
than the generic "ID" name that Access will assign.

Sprinks

Please... lay of the caps lock. It's hard to read, and considered
impolite - it looks like you're SHOUTING AT US.

I'm not aware of any templates to do this, but it should not be a very
complex database to set up. Identify the Entities - real-life persons,
things, or events of importance; each type of Entity should get its
own Table. I can see a table of Parks, one of Units (containing the
address), a table of Tenants, a table of Rentals (linked to both Units
and Tenants), and a table of Payments. Once you have the tables
constructed you can work on queries to link them and Reports to print
them out.

You might want to try using the "New Table Table Wizard", in which some
of the sample Tables contain fields that are relevant to your needs.
These are suggestions, and you can include fields from several of these
samples. For example, for your [Tenants] Table, you could use some
fields from the "Mailing List" sample.

It's not going to be trivial, but it's very much something that Access
can do for you!

John W. Vinson[MVP]

For each of the Tables you set up, let Access create a "primary key",
which will give you an easy way to link Tables together (for example,
linking records in [Units] to the [Parks] record in which they are located).

-- Vincent Johns <[email protected]>
Please feel free to quote anything I say here.

 

[Vincent Johns]

I fully agree with Vincent on using an AutoNumber primary key for each table,
but a more meaningful name, such as RentalID, or PaymentID, is more useful
than the generic "ID" name that Access will assign.

Sprinks

Thanks for mentioning that! Yes, you'll find life in Access a lot
easier if you use a different name for each one. I usually give the
Autonumber field a name formed from the name of the Table, followed by
"ID". For example, in the [Rental] Table, my primary key would be
[RentalID]. Also, any key in another Table that refers to that key
would also have the name [RentalID]. Access doesn't care what you call
them as long as they're unique and obey the naming rules, but if the
names match, Access will suggest that the same-named fields be the
links, and it may even set up the links for you, saving you a fair
amount of work.

-- Vincent Johns <[email protected]>
Plase feel free to quote anything I say here.
\

 

[Sprinks]

Right on, Vincent.

And interesting you're from Cal Tech, home of one of my mentors, Richard
Feynman.

Sprinks

I fully agree with Vincent on using an AutoNumber primary key for each table,
but a more meaningful name, such as RentalID, or PaymentID, is more useful
than the generic "ID" name that Access will assign.

Sprinks

Thanks for mentioning that! Yes, you'll find life in Access a lot
easier if you use a different name for each one. I usually give the
Autonumber field a name formed from the name of the Table, followed by
"ID". For example, in the [Rental] Table, my primary key would be
[RentalID]. Also, any key in another Table that refers to that key
would also have the name [RentalID]. Access doesn't care what you call
them as long as they're unique and obey the naming rules, but if the
names match, Access will suggest that the same-named fields be the
links, and it may even set up the links for you, saving you a fair
amount of work.

-- Vincent Johns <[email protected]>
Plase feel free to quote anything I say here.
\

 

[Vincent Johns]

Right on, Vincent.

And interesting you're from Cal Tech, home of one of my mentors, Richard
Feynman.

Sprinks

Cool! Yes, I knew Feynman, visited with him a few times, though I
never took a class from him. He was wildly popular among the students.
When it was announced that he'd won the Nobel Prize (for his work in
QED), one of the student houses posted a banner inviting him to drop in
for a beer, and he accepted. His 1963 physics textbook is still (lo
these many years later) in print, including in audio editions, as
interesting philosophical reading.

-- Vincent Johns <[email protected]>
Please feel free to quote anything I say here.

 

[PC Datasheet]

And to make life even more easy, name your tables starting with Tbl and name
your queries starting with Qry. When you are looking at recordsources for
forms and reports, rowsources for comboboxes and listboxes, code and queries
pulling data from multiple sources, you'll always know whether the data is
coming from a table or query and you'll be able to find that data source in
the database window quicker.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
(e-mail address removed)
www.pcdatasheet.com

I fully agree with Vincent on using an AutoNumber primary key for each
table, but a more meaningful name, such as RentalID, or PaymentID, is
more useful than the generic "ID" name that Access will assign.

Sprinks

Thanks for mentioning that! Yes, you'll find life in Access a lot easier
if you use a different name for each one. I usually give the Autonumber
field a name formed from the name of the Table, followed by "ID". For
example, in the [Rental] Table, my primary key would be [RentalID]. Also,
any key in another Table that refers to that key would also have the name
[RentalID]. Access doesn't care what you call them as long as they're
unique and obey the naming rules, but if the names match, Access will
suggest that the same-named fields be the links, and it may even set up
the links for you, saving you a fair amount of work.

-- Vincent Johns <[email protected]>
Plase feel free to quote anything I say here.
\

 

[roccogrand]

KGB,

Assuming that you want to learn Access yourself, I suggest that you do a few
things to get up to speed faster.

One good way to get started is to take an existing database and change it to
suit your purposes. Do this a little at a time. Your Access CD should have
the Northwind database on it, if not you can download it from the MS website.
The developer(s) of Northwind cut some corners with it (i.e., purists would
find fault) but it is still an excellent place to start learning how to use
Access and it has some really neat functionality.

There are other starter and more advanced databases on the MS website at:
http://office.microsoft.com/en-us/templates/CT011366681033.aspx

Run all of them and select the one that is closest to what you need. Then
add attribute fields, forms and reports that you need. Take your time unless
your agency needed a database yesterday, in which case go out and buy one.

The second suggestion is to get your hands on one of the Acess books for
beginners. These include Access Step by Step and How to Do Everything with
Access 2002(3?). More intermediate and larger texts include the Access Bible
and Access Inside and Out. Check your local library or your local Access
Users group may have a library for members.

Third, if you have a local Access Users Group where you live and they have a
Access lab, attend it for one-on-one help.

Fourth, consider an Access class at your local college or university. These
can force you to learn Access faster than you would by flipping through
books. If no college class is offered in your area, check the phonebook for
professional trainers.

Again if your agency needed a database last week, buy one or hire a
consultant. And don't be afraid to start using Excel or InforPath to store
your information. You can import the data into Access later.

I have used all of these ways to learn Access and there isn't a day that
goes by without me learning something new. Good luck.

LDN