One table is a list of teams and their historical venues/successes etc
I would suggest separating teams from their historical venues/successes etc.

Team table to only contain information that is not related to dates, games,
tournements, series, etc. If you will keep stats on players of the team then
use another table for players and still another for their records.

Your query would use a left join from team table to their records table.
Using a left join lets you display the team even if they do not have a record
in the joined table.

--
Build a little, test a little.


" wrote:

Hi

Just wanted to get some advice before I attempt to make a report that
will use 2 tables as source material.

Basically, my database stores information on a sport.
One table is a list of teams and their historical venues/successes etc
The second table is a list of the teams annual results.

The report I want to make will be a page per team report, that at the
top shows the data from the 'venues' table, so where there are more
than one venue, it would need to 'loop' through the table to show all
venues
As far as the 'successes' (League Championships/cup wins etc) goes, I
wouldn't want that in the loop! (IE only show it once per team.
Below this venue and successes data, I want to show the annual results
from the second table.

This is where I would value this groups advice.
Do I need to link the tables using relationships, and have the second
section as a sub-report of the first?

Many thanks
Neil
.