populate subform

[jake]

I have a form with several comboboxes(minister, cemetery, organist,
etc).
I want the user to go through and make his choices and have those
choices populate the "todo" subform.

The "todo" subform consists of [id]; [todo item]; [notes]; and
[completed y/n]

I also want the user to manually add items to the "todo" subform as
they see fit.

First, is this possible?
Second, if so - what do I need to do get it done?
Thanks for helping,
Jake

 

[John Vinson]

I have a form with several comboboxes(minister, cemetery, organist,
etc).
I want the user to go through and make his choices and have those
choices populate the "todo" subform.

The "todo" subform consists of [id]; [todo item]; [notes]; and
[completed y/n]

I also want the user to manually add items to the "todo" subform as
they see fit.

First, is this possible?
Second, if so - what do I need to do get it done?
Thanks for helping,
Jake

One thing to consider: A Form is NOT a data repository. You cannot
store information into a form, or a subform.

You can use a Form or Subform *as a tool* to store data into a Table.
That Table must have fields already existing into which to store that
data. Your "todo" form - if it's bound to a todo table with those
fields - does not appear to have any place to store information about
ministers or organists, unless you want to "do" the minister or the
organist (which should only be done with that persons's informed
consent of course... <g, d & r>)

If you can explain what the relationship between the combo boxes and
the fields on the subform should be - and perhaps a bit more about the
structure of your tables - we'll be glad to help.

John W. Vinson[MVP]

 

[jake]

Thank you John for your help,
I'm creating my database for my business, a funeral home.
The main form (the one with the comboboxes) is based on the 'deathinfo'
table.
This table has a primary key called [Casenum].

This [Casenum] serves as a "foriegn key?" in the "todo" table.
The structure of the "todo" table is as follows:
1.id - key
2.Casenum
3. todo item
4. notes
5. completed (y/n)

So for example: So depending on what the family wants for a funeral
service, the record, or deathcall might have the following items
appear in the "todo" table.
cboCemetery - call john doe gravedigger at 339-3434,
cboCemetery - contact cemetery sexton at 339-2121
cboMonument - contact monument company for last date
cboMinister - call Rev. Corning at 339-2121
cboOrganist - call betty at 339-2121

Right now I update the ToDo Subform manually. It would greatly improve
my database to
automate this.
So if I enter Mt. Repose Cemtery - I know the program will
automatically enter the right
entrees in the Subform Todo List, in the above case
1. call john doe gravedigger at 339-3434
2. contact cemtery sexton at 339-2121

So basically, each case will make a custom "todo" list based upon what
the user enters in the computer.
This will be soooo sweet if I get this to work!
Thanks again,
Jake

 

[John Vinson]

Thank you John for your help,
I'm creating my database for my business, a funeral home.
The main form (the one with the comboboxes) is based on the 'deathinfo'
table.
This table has a primary key called [Casenum].

This [Casenum] serves as a "foriegn key?" in the "todo" table.
The structure of the "todo" table is as follows:
1.id - key
2.Casenum
3. todo item
4. notes
5. completed (y/n)

So for example: So depending on what the family wants for a funeral
service, the record, or deathcall might have the following items
appear in the "todo" table.
cboCemetery - call john doe gravedigger at 339-3434,
cboCemetery - contact cemetery sexton at 339-2121
cboMonument - contact monument company for last date
cboMinister - call Rev. Corning at 339-2121
cboOrganist - call betty at 339-2121

If the Cemetary, Monument, and Organist information is stored in the
deathinfo table, and can be uniquely identified by the Casenum, then I
see no point in storing the same information redundantly in the ToDo
table. You can store the notes; and you can create a query joining the
two tables to pull the information together. It appears that I'm
missing the point! If the Cemetary has the name and phone number of
the gravedigger, that information can be pulled from a Query; the date
information can come from the DeathInfo table; I'm not sure I see why
the ToDo table is even necessary, since all of the information it
contains is already available.

Ok... thinking about it - the one thing that ISN'T available is the
Completed yes/no field. Given that... you could create an Append query
joining the DeathInfo table to the tables of ministers, organists,
etc. and populate the ToDo list. I'd suggest not packing names and
phone numbers into a Notes field though; since most of the entries
have the same structure - "call <person X> in <role Y> at <phone>",
I'd say that you should have fields for the person, the role, and
their phone.

John W. Vinson[MVP]

 

[jake]

John, thank you for taking the time to help me.
I give the Append query a try... don't know anything about them...but I
will read up on them. I do get the concept though. If I don't
succeed, I come back for more.
Thanks again. Jake