Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > LLBLGen Pro Runtime Framework> OleDb Call Failed. *
 

Pages: 1
LLBLGen Pro Runtime Framework
OleDb Call Failed. *
Page:1/1 

  Print all messages in this thread  
Poster Message
bclark00
User



Location:

Joined on:
30-May-2008 22:10:29
Posted:
5 posts
# Posted on: 30-May-2008 22:58:41.  
I'm not sure where to start with this problem. The code was working fine and broke spontaneously. I've tested similar code that I haven't touched and it is now producing the same error.

The way I have this setup is a bit tricky to begin with. I'm using an Access database with linked tables to a Caché (InterSystems) database and LLBLGen to generate code.

I can fetch data without issue through access--nothing has changed there. As far as I know there haven't been any code changes. The error is occuring on a GetMulti call with a single condition in the predicateexpression. I've debugged all I know how to do. Let me know any other information that will be helpful.

Stack Trace:
at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)
at System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at SD.LLBLGen.Pro.ORMSupportClasses.RetrievalQuery.Execute(CommandBehavior behavior)

(Changed the title, as it's OleDb not ODBC Wink) -- Otis
  Top
daelmo
Support Team



Location:
Guatemala City
Joined on:
28-Nov-2005 23:35:24
Posted:
8081 posts
# Posted on: 31-May-2008 04:32:47.  
Please post the exact error message. Also the LLBLGenPro version and RuntimeLibraries version (http://llblgen.com/TinyForum/Threads.aspx?ForumID=7).
Did you move the app to another machine (to Vista, Vista64, for instance)?


David Elizondo
LLBLGen'ing (articles and code snippets) | linkedin | twitter
 
Top
bclark00
User



Location:

Joined on:
30-May-2008 22:10:29
Posted:
5 posts
# Posted on: 02-Jun-2008 18:30:23.  
"An exception was caught during the execution of a retrieval query: ODBC--call failed.. Check InnerException, QueryExecuted and Parameters of this exception to examine the cause of this exception."

The original subject was correct. The error message I'm getting is "ODBC--call failed"
  Top
goose
User



Location:
Central America
Joined on:
06-Aug-2007 18:21:05
Posted:
386 posts
# Posted on: 02-Jun-2008 19:40:31.  
seems like a driver problem, did you check the inner exception?, please double check you connectivity and availability of your access database.

gansodesoya  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37604 posts
# Posted on: 03-Jun-2008 11:00:15.  
Seems like the access db isn't able to access the linked database over ODBC. Make sure this is possible.

Also, linked servers aren't supported by LLBLGen Pro btw, as queries often have to be made in the SQL dialect of the related server.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.