Thanks, John
DB Design is not my strong point. But I am learning. I will stop deleting
records to keep the database stable. It probably would be better to append
the ID, Names, and Date of Class to a different database altogther if it can
be done.
I'll have to study up on appending records. Still learning.
Thanks again.
--
Gil Silva


"John W. Vinson" wrote:

On Tue, 20 Apr 2010 05:49:02 -0700, Gil Silva
wrote:

Why do you want to store the names redundantly in a second table?
Ans: The main table contains new hires and new report-ins. If they do not
travel to specific places in the three years and they leave the organization,
they are deleted from the database. They are required to take class prior to
traveling to specific places. The info is to be maintained to determine
sizes of class and historically who attended to budget for future type
classes. If I delete names off the master file I loose the names in the
tbl_class when I run a query. Other words the tbl_class should far exceed
the number of records in the main table. Looking the Properties Data tab
the Class form is:
Link Master Fields ID
Link Child Fields ID
Filter on Empty Master Yes
Enable Yes
Locked No

There is no primary key in master and no primary key in tbl_class because I
have to delete records in the master if no activity.
The tables are tbl_members and tbl_class
tbl_members (relevant fields) ID, Last_Name, First_Name
tbl_class (relevant fields) ID, LastName, First_Name, ClassDate

There is another subform on the main form which displays trips (tbl_trips)
and that is working fine but it does not contain names, just ID because if
the members take trips the record is saved and not deleted so I can do the
query you mentioned.

Tha tables are not related except tbl_trips and tbl_members. They show
relationships to the ID in both tables.

I'll absolutely agree with Bob Quintal. It's inappropriate to delete the
record in the master table *because you still need those names*. You can
instead add a Yes/No field Current to the table, and (where you don't need
historical data) use a query selecting only current employees.

The alternative would be to use the AfterUpdate event of the combo box to
"push" the names into tbl_class but I'd say that this would be A Very Bad
Design.
--

John W. Vinson [MVP]
.