EnviroInsite Forum

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Query is too complex error


Senior Member

Status: Offline
Posts: 271
Date:
Query is too complex error
Permalink  
 


I'm getting the following error when I try to plot 3d wells:

OpenRS

 ERROR [HY000] [Microsoft][ODBC Excel Driver] Query is too complex.

at System .Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)

at System .Data.Odbc.OdbcCommand,ExecuteReaderObject(CommandBehavior behavior, Siring method, Boolean needReader, Object

SQL API odbcApiMethod)

at System .Data.Odbc.OdbcCommand ExecuteReaderObject(CommandBehavior behavior, Siring method, Boolean needReader)

at System .Data.Odbc.OdbcCommand,ExecuteReader(CommandBehavior behavior)

at System .Data.Odbc.OdbcCom mand ExecuteReader()

       at ei_dblib3.1.NellTb1.0penRSO



-- Edited by admin on Thursday 2nd of August 2012 07:03:36 PM

__________________


Veteran Member

Status: Offline
Posts: 98
Date:
Permalink  
 

Typically this error occurs when you select too many locations after you click the list button in the query tab. First try removing all of the selected locations and see if you can get it to work. If it does then try to build a query without specifically selecting so many individual wells. You can use the wildcards in the well or screen name or select by location, elevation, or depth. Don't forget that if you don't select any locations from the list that that is equivalent to selecting all of them.

__________________


Member

Status: Offline
Posts: 8
Date:
Permalink  
 

The problem still occurred even with wildcards set to plot only a few wells.  I deleted a number of wells that I did not need, dropping the number of wells in my Excel database from 497 to 429.  Now I don't get the error.



__________________


Veteran Member

Status: Offline
Posts: 98
Date:
Permalink  
 

I'm glad you were able to get that to work. I see the misunderstanding. The problem is not the selection by wildcards. The problem occurs when you click on the List button in the Query tab and select too many wells from that list. I noticed that nearly all or maybe it was all of the wells selected. This results in an extraordinarily long query that gets passed to the database driver. There seems to be a technical limitation to the size of the query that occurs in this circumstance.

__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard