Re: "Identical" query SQL Throws Error
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 21:38:45 +0800
Larry, I can only guess that the issue was one of the many bugs in the JET
query engine, so I can't pinpoint it for you.
Microsoft seems to be uninterested in fixing these JET bugs. Naturally
enough, each new version has its own bugs, so when these are added and the
old ones are not fixed, the very engine that Access runs on is becoming more
and more unstable.
For examples of some of those I have personally struck, see:
http://allenbrowne.com/tips.html#Bug%20Engine
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"LarryP" <LarryP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B95DEC8E-8DF4-469F-91CB-AE7480B27CFC@xxxxxxxxxxxxxxxx
First, Allen, thanks for your interest and persistence in trying to help
me
through this.
In the course of yesterday I made a change that resulted in the second
query
(strSQL2) running correctly, but I'm completely sure why, so if you have
time, maybe you can explain it to me and others who might encounter
something
similar.
As you saw, in the second query I was trying to set up a filter on the
MYear
value (e.g., 2006) to be sure I was only getting one year's worth of data.
The second query of course got that value from the first query, and the
first
query got it from tblSPIData. My "fix" involved adding MasterCal back
into
the second query as a left join to tblSPIData, and setting up the filter
to
use the MYear value from MasterCal rather than the one in tblSPIData.
Presto, Jet was happy and the query ran as intended. Go figure. I can't
understand how that added anything significant to the earlier SQL
statement,
but obviously Jet did.
If you can shed any light, it'd be welcome. "It works now!" is good, "It
works now because...!" is better.
.
- References:
- Re: "Identical" query SQL Throws Error
- From: Allen Browne
- Re: "Identical" query SQL Throws Error
- From: LarryP
- Re: "Identical" query SQL Throws Error
- From: Allen Browne
- Re: "Identical" query SQL Throws Error
- From: LarryP
- Re: "Identical" query SQL Throws Error
- From: Allen Browne
- Re: "Identical" query SQL Throws Error
- From: LarryP
- Re: "Identical" query SQL Throws Error
- Prev by Date: Re: "Identical" query SQL Throws Error
- Next by Date: Re: Create ODBC Connection
- Previous by thread: Re: "Identical" query SQL Throws Error
- Next by thread: Re: Object Not Supported FOr This Type Of Object
- Index(es):
Relevant Pages
|
|