Gustav Brock
gustav at cactus.dk
Mon Jun 24 10:23:27 CDT 2013
Hi Jim Thanks. Yes, that seems to be it. As ODBCdirect has been dropped, there is just no use for it any longer, and I believe we can quietly forget about it. /gustav -----Oprindelig meddelelse----- Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af Jim Dettman Sendt: 24. juni 2013 16:39 Til: 'Access Developers discussion and problem solving' Emne: Re: [AccessD] QyeryDef.Type dbQCompound Gustav, Believe I have found your answer. Apologies if any of this has been hit. As you thought, it's related to ODBCDirect Workspaces, which is why in regular Access, you don't see this query type at all. dbQCompound is a DAO constant and there's no direct corresponding object type in Access. It's strictly used with DAO in code. I located this: http://office.microsoft.com/en-gb/access-help/HV080204679.aspx It's just as the help described "Multiple select statements" (not a UNION) and it's meant to be used in working with multiple record sets at one time. Jim.