Select records

[Ricoy_Chicago]

I work for a small business school. I have set up the
a "back-end" database (Masters.mdb) that can be accessed
by all (7) admissions Reps. The database contains about
1600 records (Contacts interested in attending the
school). However, out of those 1600 records only about 100
records are actually needed because they represent the
students who register to start in the oncoming quarter.

I have linked the table "Contacts" (in the Masters.mdb)to
the "Enrolled.mdb" (front-end) but it links all 1600
records. I have a "yes/no" field that allows me to query
the 100 records needed. i know I cannot link to a query.

The problem is once the "contact" is enrolled additional
fields are needed, fields that are nonexisting on
the "Contacts" table. If add the fields to the "Contacts"
table it is going to have way too many fields (so far, it
already has 55)

Is there anything I can do?

Thank yo for your help.

 

[Dirk Goldgar]

I work for a small business school. I have set up the
a "back-end" database (Masters.mdb) that can be accessed
by all (7) admissions Reps. The database contains about
1600 records (Contacts interested in attending the
school). However, out of those 1600 records only about 100
records are actually needed because they represent the
students who register to start in the oncoming quarter.

I have linked the table "Contacts" (in the Masters.mdb)to
the "Enrolled.mdb" (front-end) but it links all 1600
records. I have a "yes/no" field that allows me to query
the 100 records needed. i know I cannot link to a query.

What makes you say that? You can certainly base a form on a query, and
a query can certainly join tables to other queries and pull fields from
both tables and queries. If you mean you can't create a linked table in
your front-end that is linked to a query in the back-end, that is true,
but you don't really need to. You can just create a linked table in the
front-end that is linked to the back-end Contacts table, create a query
in the front-end that selects only the enrolled records, and base all
forms and other operations on that query.

The problem is once the "contact" is enrolled additional
fields are needed, fields that are nonexisting on
the "Contacts" table. If add the fields to the "Contacts"
table it is going to have way too many fields (so far, it
already has 55)

Is there anything I can do?

It sounds like you may -- just may -- need an Enrollments table that is
related one-to-one with the Contacts table. If you had that, you
wouldn't need the check-box field, because the presence of a record in
this table would indicate that the Contact is enrolled. Now, it isn't
clear to me whether a Contact might have multiple enrollments, in which
case the Enrollments table would actually be related many-to-one with
contacts, a more normal arrangement. it could work either way.