Re: COMP: Record keeping databases
- To: "i*@onelist.com"
- Subject: Re: COMP: Record keeping databases
- From: S* I*
- Date: Thu, 09 Mar 2000 20:04:04 -0500
From: Sandy Ives <rives@home.com>
This is not too long, but boring nonetheless.
I have started a MS-Access iris database in the last month or so. I'm using it
for a memory aid more than anything else; I'll have more ammunition in my
arguments with Maureen plus we'll be able to make better informed votes when
filling out the judges' ballot.
The database will have a minimum of four separate tables when all is said and
done. All have dedicated forms to simplify data entry.
a) Source Table - a 'who's who' with the name, address, phone#, e-mail, and
web-site. This is a full description of where iris come from that happen to get
planted in my garden.
b) Cultivar Table - a 'what's what' with cultivar name, hybridizer, source,
intro year, purchase year, a series of indicator fields, a note field for the
description, and, most important, how and when I get rid of the cultivar in
question. I have added to this table all 1999, 98, and most of 97 purchases and
hope to get back to 1989 (when we received 'Pink Horizon' as our first iris. It
never bloomed).
c) Performance Table - a 'what have you done for me lately' table. This will
describe the garden performance of a particular cultivar by year. I will have a
separate table for the current year, then append that table to the master
performance table at the end of the growing season.
Note that this final table can get very large. I plan to remove all records
concerning a particular cultivar from the performance table when I dispose it.
I will summarize the results in the note field of the cultivar table at that
time. I will be maintaining a backup for each year, but the active database
will only contain summary information of disposed iris.
The database has several query reports mainly driven by the cultivar table. I
expect to create several more
I plan to bring this particular database to Dallas, but only because I intend to
bring the laptop it resides on. Anyone who wants to see what can fit on an
80'x50' lot with a bungalow in the middle might be interested. Anyone who wants
to review it for ideas can get a copy, but don't clutter up the list with
requests - PRIVATE svp. Advice would be welcome; my relational database skills
are 15 years old and somewhat weakened by the ages. ;-)
The database does not deal with garden visits as it stands. If I am impressed
with a cultivar, but do not grow it, I should still take note of it for the
future and for potential voting. Therefore, I should have a Visitor table as
well. Any ideas on what fields should be used for such a table?
I have about five books describing our garden's performance over the last
decade, especially the iris. Finding information in them is a trial. This will
not replace the books, but it will be a valuable adjunct to them (and vis
versa).
Regards,
Sandy Ives in Ottawa (z4ish, but it went up to 19.5C at noon today before
dropping to -3C at six. Wild)
------------------------------------------------------------------------
GET A NEXTCARD VISA, in 30 seconds! Get rates as low as 0.0%
Intro or 9.9% Fixed APR and no hidden fees. Apply NOW!
http://click.egroups.com/1/937/0/_/486170/_/952649842/
------------------------------------------------------------------------
