Grouping multiple records for tracking w/o additional entries

[TroyC]

I am trying to design a database where someone will enter multiple records to
create a single request. How can I set up a database that will do this
without that person having to fill an additional field that could then be
filtered. I would also like to know how to build in an email option that
would then allow the user to send an email which would identify that group of
records. Is any of this possible?

 

[Tim Ferguson]

I am trying to design a database where someone will enter multiple
records to create a single request.

It sounds like you need two tables, one for Requests and the other one for
Records, linked with a one-to-many relationship.

How can I set up a database that
will do this without that person having to fill an additional field
that could then be filtered.

Not quite sure what you mean by this: if there is going to be filtering,
then there is going to have to be some information to filter on. For
example, if it's an age thing, then you can use something like

WHERE BirthDate < #2000-01-01#

but someone will have to type in everybody's birthdate first. Et cetera.

I would also like to know how to build in
an email option that would then allow the user to send an email which
would identify that group of records. Is any of this possible?

Do you mean identify a group of records and send emails to the people in
them?-- usually easy, which is why spam is so cheap and plentiful.
Importing information from email messages automatically into the database
may or may be easy, depending on how well structured the emails are.

Hope that helps


Tim F