ODBC --call failed @#!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an ADO 'SELECT' query that runs from Access against an Oracle database
that does the following:

*Run existing code and it works fine, no SQL issues;

*Next session: ODBC -call failed
Remove a few fields - code runs
Put removed fields back in - code runs

*20 minutes later: ODBC -call failed
Remove a few fields - code runs
Put removed fields back in - code runs

*10 minutes later: ODBC -call failed

It's making me crazy. Which fields I remove or put back is random. I cannot
tie this issue back to any particular field and the data being retrieved is
essentially the same (batch system).

Does anyone have a clue?
 
BTW I am using AccessXP on Win 2000 with ADO 2.5.

The code can sometimes run 5 or 6 times with no error in the same session,
then the 6th or 7th try fails.

Please help if possible, thanks much in advance.
 
Hi quartz,

My first guess is that query is timing out. You can set the timeout to zero
to force to never time out. Do not know if that is causing your problem.
 
Thanks JL, but I have the following lines included in my code:

cn.CursorLocation = adUseClient
cn.CommandTimeOut = 0

Any other thoughts???
 
Actually, I think that command is for DAO rather than ADO. Autosensing didn't
pick it up. But, I did add:

cn.ConnectionTimeOut = 0

Unfortunately, this didn't help either. I may try switching to DAO, it may
be more stable. Please post back if you have any other ideas.

Thanks again.
 
Hi quartz,

I do not know if this is still true or not. As I remember, Oracle has
config files that have a timeout variable in there. I forget which file it
is (sqlnet.ora, listener.ora, or tnsnames.ora).
 
Back
Top