Usually the calls to the Oracle stored procedures return
their "ref cursors" through ADO recordsets properly.  
However, under certain load and timing circumstances, the
ref cursors return an empty record set with zero records,
while the database table feeding the ref cursors have many
rows.  When this occurs, neither ADO or Oracle returns any
error messages to the application.  Oracle does not report
any error messages to any of its log files.

Without supplying the VC++ code for the calls, does anyone
know of any "issues" with running ADO in a multi-threaded
environment with Oracle?  This problem is strange, becuase
when this problem occurs, running the same stored
procedure that the threads are using, in SQL+ returns a
valid, non-zero length "ref cursor".  Thanks in advance
for any and all responses.

The only problems that we have ever come across with respect to ADO is when
we would share a connection across threads, and not manage concurrent
access -- that caused a lot problems.  Our solution was to either 1) create
connections in each thread, or 2) serialize all calls on a single connection
using a critical section associated with the connection.

Here is a note on the ODBC Driver:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc...
bcoraclethread_safety_notes_on_api_functions.asp

regards
roy fine

p/s/ if you use Oracle Native OLEDB drivers, download the latest 8i/9i from
the Oracle MetaLink site.