<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Dealing with the “ambiguous outer joins” message</title><link>http://blogs.msdn.com/access/archive/2009/07/02/dealing-with-the-ambiguous-outer-joins-message.aspx</link><description>Today’s guest blogger is Colin Wilcox, writer for Access Training on Office Online. When you query multiple tables for data, you sometimes see a message about “ambiguous outer joins.” The message tells you to create a separate query that performs one</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Dealing with the “ambiguous outer joins” message</title><link>http://blogs.msdn.com/access/archive/2009/07/02/dealing-with-the-ambiguous-outer-joins-message.aspx#9816898</link><pubDate>Fri, 03 Jul 2009 20:09:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9816898</guid><dc:creator>Bob Heifler</dc:creator><description>&lt;p&gt;Nice work Colin. &amp;nbsp;This will help many beginners with this common problem. What really makes it a great post is the illustrations. I will be adding more illustrations to my blog as well. Love the clean look of the Microsoft Access Team Blog as well. Maybe one day I will be chosen as a guest blogger. &lt;/p&gt;
</description></item><item><title>re: Dealing with the “ambiguous outer joins” message</title><link>http://blogs.msdn.com/access/archive/2009/07/02/dealing-with-the-ambiguous-outer-joins-message.aspx#9817024</link><pubDate>Fri, 03 Jul 2009 23:07:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9817024</guid><dc:creator>Kevin Nechodom</dc:creator><description>&lt;p&gt;This works ... if you are able to add queries. &amp;nbsp;Such is not always the case. &amp;nbsp;I have tried techniques such as subqueries, like the following:&lt;/p&gt;
&lt;p&gt;SELECT ...&lt;/p&gt;
&lt;p&gt;FROM (SELECT ThisTable.Key, MoreData FROM ThisTable &lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp;LEFT JOIN ThatTable&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp;ON ThisTable.Key = ThatTable.Key&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; ) ResultTable&lt;/p&gt;
&lt;p&gt;LEFT JOIN AnotherTable&lt;/p&gt;
&lt;p&gt;ON AnotherTable.Key = ResultTable.Key&lt;/p&gt;
&lt;p&gt;You can trick Access into doing this (which was a slight surprise to me, Kudos!!!), but DON'T let the query get munged by the QBE editor! &lt;/p&gt;
</description></item><item><title>re: Dealing with the “ambiguous outer joins” message</title><link>http://blogs.msdn.com/access/archive/2009/07/02/dealing-with-the-ambiguous-outer-joins-message.aspx#9817035</link><pubDate>Fri, 03 Jul 2009 23:20:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9817035</guid><dc:creator>Armen Stein (Access MVP)</dc:creator><description>&lt;p&gt;I don't agree with the statement:&lt;/p&gt;
&lt;p&gt;&amp;quot;Whenever an outer join points to a table, and that table also participates in another join of any kind, your query can't run.&amp;quot;&lt;/p&gt;
&lt;p&gt;In fact, if an outer join points to a table, and that table points to another table with an outer join, then your query will run.&lt;/p&gt;
&lt;p&gt;The problem is when your arrowheads point toward each other, or toward an inner join.&lt;/p&gt;
&lt;p&gt;The two simple rules I use to avoid ambiguous outer joins are:&lt;/p&gt;
&lt;p&gt;1. &amp;nbsp;All outer joins (arrowheads) must point away from the &amp;quot;main table(s)&amp;quot;.&lt;/p&gt;
&lt;p&gt;2. &amp;nbsp;The &amp;quot;main table(s)&amp;quot; may be a single table, or may be a group of tables joined with inner joins (no arrowheads).&lt;/p&gt;
</description></item><item><title>re: Dealing with the “ambiguous outer joins” message</title><link>http://blogs.msdn.com/access/archive/2009/07/02/dealing-with-the-ambiguous-outer-joins-message.aspx#9819550</link><pubDate>Mon, 06 Jul 2009 14:41:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9819550</guid><dc:creator>Frits Scholer</dc:creator><description>&lt;p&gt;If you make 2 queries, sometimes the first has to be huge. If you can resolve it by directly editing the sql code like Kevin showed the problem is easily solved.&lt;/p&gt;
</description></item><item><title>re: Dealing with the “ambiguous outer joins” message</title><link>http://blogs.msdn.com/access/archive/2009/07/02/dealing-with-the-ambiguous-outer-joins-message.aspx#9820058</link><pubDate>Mon, 06 Jul 2009 19:11:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9820058</guid><dc:creator>cdowns</dc:creator><description>&lt;p&gt;Kevin: Thanks for posting that trick!&lt;/p&gt;
&lt;p&gt;Armen: I'll pass on your comment and we'll make sure our Help and Training content is accurate on that point.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;Chris&lt;/p&gt;
</description></item></channel></rss>