Thanks Bob,
DB Design is not one of my strong points. I'll stop deleting members when
they leave and put the date they leave to save the design and keep the
database somewhat stable.
--
Gil Silva


"Bob Quintal" wrote:

=?Utf-8?B?R2lsIFNpbHZh?= wrote
in :

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.

Design error here. They should stay in the databsae, but have a
dateLeftOrganization field. Query the table for current members is
done by filtering on your new field 'is null'

Bob Q

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.

Hope I supplied what you requested.
Thanks for responding so quickly.

.