|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
July 4th, 2008, 06:41 PM
posted to microsoft.public.access.queries
|
|||
|
|||
Query Too Complex
I have nested queries that when run on a local table runs correctly. When I
switch the first query to use ODBC tables I get query too complex. If I run the individual queries (in the nest) they work all the way to the very last one (that the report uses). Other than the ODBC connection the difference is local table is single table, ODBC is two linked tables. I've see here that there is a 64k compiled limit to the size of the query. Is there a way to identify the size? Is there a different limit when using and ODBC connection? Thanks in advance 
|
| Thread Tools | |
| Display Modes | |
|
|
Threaded Mode