L
Laurel
I have two tables, tblAcademics and tblScores. Each has an ID column and a
date column (Student_ID in both tables, and Assessment_Date and Score_Date
for the date columns. I want to create a query which has all of the
tblAcademics rows, whether or not there is an associated tblAttendance row,
matching on both ID and date. When I create two joins, and select option 2
(all of table 1 and only table 2 when the two values match), I get the error
"Ambiguous outer join. To force one of the joins to be performed first,
create a separate query that performs the first join and then include that
query in your SQL statement." I'm not sure how to implement this,
especially since both the ID and date are criteria on the select that are
entered at run time. This seems like a very common thing to have to do.
Can I make a combined column in each table somehow? Also, I need to add
another criterion on the 2nd table tblScores.PeriodCode = "O". I'm trying
to make this query because putting functions in the query, like "Dlookup" on
this and that in the report itself is slowing the report down in a server
environment to the point that it isn't usable.
date column (Student_ID in both tables, and Assessment_Date and Score_Date
for the date columns. I want to create a query which has all of the
tblAcademics rows, whether or not there is an associated tblAttendance row,
matching on both ID and date. When I create two joins, and select option 2
(all of table 1 and only table 2 when the two values match), I get the error
"Ambiguous outer join. To force one of the joins to be performed first,
create a separate query that performs the first join and then include that
query in your SQL statement." I'm not sure how to implement this,
especially since both the ID and date are criteria on the select that are
entered at run time. This seems like a very common thing to have to do.
Can I make a combined column in each table somehow? Also, I need to add
another criterion on the 2nd table tblScores.PeriodCode = "O". I'm trying
to make this query because putting functions in the query, like "Dlookup" on
this and that in the report itself is slowing the report down in a server
environment to the point that it isn't usable.