[AccessD] QyeryDef.Type dbQCompound

Hi Arthur

Your atomic and molecular terms, if I understand your definitions, seem to exclude the majority of 'ordinary' queries of
the form:

SELECT Table1.n, Table1.t, Table2.t2
FROM Table1 INNER JOIN Table2 ON Table1.t = Table2.t

But maybe you'd say that this doesn't 'touch' Table2, even though the result includes a field from it?

John


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: 23 June 2013 13:59
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] QyeryDef.Type dbQCompound


The way I use the term, which may not be what was intended by the original author, is this: any query that uses two or
more queries is a compound query. I don't know whether this was the author's intention, and my practice has been to
refer to atomic and molecular queries, the former touching exactly one table and the latter touching at least two atomic
queries.

A.

-- 
AccessD mailing list
AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com