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 ) -- Otis

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)?

"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"

seems like a driver problem, did you check the inner exception?, please double check you connectivity and availability of your access database.

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.