Thanks John and Duanne. I found a way out . I reduced the number of criteria to run the first query. I then did a make table query from this first query.
Lastly I ran a second query on the table thus created with my remaining criteria .
I think this might work for those who have challenges of having so many criteria in their queries.
Ade
From: "John Viescas JohnV@msn.com [MS_Access_Professionals]" <MS_Access_Professionals@yahoogroups.com>
To: MS_Access_Professionals@yahoogroups.com
Sent: Monday, 1 December 2014, 7:00
Subject: Re: [MS_AccessPros] MAXIMUM NUMBER OF CRITERIA IN MSACCESS QUERY
It's not the number of columns, it's the complexity of the SQL. The query engine "compiles" your query into something like a 64K "workspace", and if the compile won't fit in that, you'll get query too complex. A very complex WHERE clause is often the culprit.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Dec 1, 2014, at 1:51 AM, Duane Hookom duanehookom@hotmail.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:
__._,_.___
Posted by: Adeboyejo Oyenuga <aoye_99@yahoo.co.uk>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (11) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar