[AccessD] QyeryDef.Type dbQCompound

Hi Stuart et al

OK, it seems like it settles here. A dead end pointing nowhere.

Thanks to all.

/gustav

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] På vegne af Stuart McLachlan
Sendt: 23. juni 2013 23:33
Til: Access Developers discussion and problem solving
Emne: Re: [AccessD] QyeryDef.Type dbQCompound

It certainly is looking that way,

I havent been able to create one yet in a test database and I've tried
everything I can think of.

--
Stuart

On 23 Jun 2013 at 18:08, DJK (John) Robinson wrote:

> That's what I'd expect.
> 
> And we still don't know what kind of query gives you the value 
> dbQAction - do you know?  I suspect that neither dbQAction nor dbQCompound
values are ever used.  Anyone disagree?
> 
> John
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav 
> Brock
> Sent: 23 June 2013 17:57
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] QyeryDef.Type dbQCompound
> 
> 
> Hi all
> 
> I found this:
> 
> http://office.microsoft.com/en-in/access-help/HV080753770.aspx
> 
> which could indicate that it is (was) a specific situation for an ODBC 
> Direct workspace - but these are no longer are supported.
> 
> I then tried to follow the guide, and it is possible to create a 
> pass-through query with a compound set of statements separated by
semicolon.
> 
> However, when I save such query, it is just marked as a normal 
> pass-through query, and the Type property doesn't indicate compound.
> 
> Confusing?
> 
> /gustav
> 
> >>> Gustav at cactus.dk 23-06-13 18:35 >>>
> Hi John
> 
> Well, yes, but it didn't exist in Access 2.0 but exists in A97 so it has a
purpose, I guess.
> 
> I found an Access 97 help file and it also states something like:
> 
> A query that is composed of at least one action query (a query that 
> copies or changes data) and at least one select query (a query that 
> returns a Recordset without changing data). In DAO, a compound query is
created by putting two or more SQL statements (separated by semicolons) in
the SQL property of a QueryDef object.
> 
> However, if I try that, an error is raised that characters are found after
the semicolon ...
> 
> So, does an example exist?
> 
> /gustav
> 
> 
> >>> djkr at msn.com 23-06-13 17:45 >>>
> Hi Gustav
> 
> Do you think it may not be possible to encounter this value?  That MS have
over-specified the QueryDefTypeEnum list?
> 
> For instance, I know four types of Action Queries in Access: Append, 
> Delete, MakeTable and Update, each of which appears in the list.  So what
kind of query gives you dbQAction?  Some other kind of Action Query?  Do you
know?
> 
> 
> As an aside, I note that the MSDN lists for A07 and A13 describe 
> dbQSetOperation as "Set operation", where the list for
> A10 lists it as "Union".  Both valid, given that Access doesn't implement
either INTERSECT or EXCEPT, at least AFAIK.
> 
> Good luck with the quest, but there may not be a pot of gold ...
> 
> John
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav 
> Brock
> Sent: 23 June 2013 16:00
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] QyeryDef.Type dbQCompound
> 
> 
> Hi John
> 
> Yes, I'm familiar with the word compound.
> 
> My question is how to create or where to meet an Access QyeryDef with
property Type of dbQCompound.
> 
> /gustav
> 
> >>> djkr at msn.com 23-06-13 15:41 >>>
> Hi Gustav
> 
> Well, a UNION query is compound in that it comprises two or more elements
(queries), however complex or simple each is.
> That's what 'compound' means in English.  But equally UNION (and 
> INTERSECT and EXCEPT) queries can be called Set Operation queries, because
they can be considered as doing set operations.  Set Theory.
> 
> But I feel that you're trying to figure out what kinds of queries 
> Access classifies as dbQCompound (and possibly dbQSetOperation).  Now
we're trying to second guess MS logic - the answer could be none!
> 
> John