I am an attorney and have a database of clients. Each client record
has a listing of upcoming appearance dates (I want these in the same
client record so they can all be viewed when I look at the client). I
then want a report that gives me all appearance dates, sorted by date,
for all clients.

Sample
1st Record
Client 1
9/24/03 - Appearance 1
10/15/03 - Appearance 2
12/15/03 - Appearance 3
2nd Record
Client 2
10/13/03 - Appearance 1
12/23/03 - Appearance 2

Report
9/24/03 - Client 1 - Appearance 1
10/13/03 - Client 2 - Appearance 1
10/15/03 - Client 1 - Appearance 2
12/15/03 - Client 1 - Appearance 3
12/23/03 - Client 2 - Appearance 2

On 8/14/03 11:21 AM, in article
fdd71043.0308141021.4201f56f (AT) po...OT) google.com, "Daniel G. Emilio"
<danielemilio (AT) earthlink (DOT) net> wrote:


When you say "Each client record has a listing of upcoming appearance
dates", what do you mean? How have you set this up? Did you use a
relationship, or a repeating field, or several fields? It's important to
understand so that we can suggest good solutions to your problem.

- -

Overall, it looks like you WANT a "classic" relation ship between 2 files.

The first file is the "Clients" file. It has their name and pertinent
information.

The second file is the "Appearances" file. It contains the client name,
their appearance date, and appearance number.

The "Clients" file would have a relationship to the "Appearance" file using
the client's name.

You could then use a "Portal" on the "Client" layout to view his/her related
"Appearances". The portal can be set to add/delete appearances as well as
sort them in date order.

You can also run a report from the "Appearance" file that would give you the
report of all appearances for all clients.

Make sense so far? If you want to run the report in the manner you
mentioned, you need to break the data up into separate files.

- -

Before we more involved let us know what you have in terms of design at this
point.


Matt Revenaugh