ODBC failure with stored procedure

Question

Procedure runs without error when started from term window. Procedure will run from access using pass through query (module) iff one of the queries is commented out. If the query is present, I receive an ODBC failure on the record insert. It acts like a timing problem but I can't find the place to set it.
ANY help appreciated.

Answer 1

I'm assuming that your error is:
Newmars ea-fa     ENTER SQLExecDirectW
          HSTMT 09DD2910
          WCHAR * 0x0012BA00 [      -3] "BEGIN MARS_BIGSUM_PROCEDURE; END;\ 0"
          SDWORD -3
Newmars ea-fa     EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
          HSTMT 09DD2910
          WCHAR * 0x0012BA00 [      -3] "BEGIN MARS_BIGSUM_PROCEDURE; END;\ 0"
          SDWORD -3
          DIAG [S1T00] [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
ORA-06512: at "HQADM.MARS_BIGSUM_PROCEDURE", line 87
ORA-06512: at line 1
(1013)
although I'm not sure whether the earlier error
Newmars ea-fa     EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
          HSTMT 09DD17D0
          WCHAR * 0x1B0741C8 [      -3] "SELECT Config, nValue FROM MSysConf\ 0"
          SDWORD -3
          DIAG [S0002] [Oracle][ODBC][Ora]ORA-00942: table or view does not exist
(942)
is important.
For the timeout error, the most likely problem is that Access is putting a timeout on the call, and requesting that the driver cancel the query if it takes too long. Ideally, you'd be able to adjust the timeout parameter in Access, but I'm not aware of a way to do that. You can disable query timeout at the DSN level, though, there's a checkbox in the configuration screen for the DSN. This will disable query timeout for every application that uses the DSN, though.
For the table not found error, that's indicating that there's no table named MSysConf in whatever schema you're connected to.
Justin