Anyone,

I'm having a real problem running some stored procedures on a SQL Server 6.5
(SP5)platform using VB 5.0 (SP3) and ODBCDirect calls.  My stored procedures
consist of multiple select statements, batch updates, etc... and generally a
return code and/or several input parameters.  There is some very simple
control logic in all my stored procedures.  I am stuck with ODBCDirect and
DAO/Jet because I don't have access to VB5.0 Enterprise.

If I break out these stored procedures to individual text queries and call
them using DAO/Jet they work fine.  If I run the stored procedures directly
from Enterprise Manager, they run fine.  It is only when I attempt to call
them as stored procedures via ODBCDirect that I am having problems.  The odd
thing is I am running about 20 stored procedures and over half work.

Generally, when I attempt to run large queries that access 50,000+ records
from a table containing about 4,000,000 records using the current work date
as my selection criteria I encounter an error "S10008 - Operation Canceled"
from the server.  I am trying to extract records from an archive table into
a production table and am using an INSERT INTO SELECT FROM command to get
these records.   The error comes back withing 30 seconds after launch.  I
also see the error during subsequent bulk updates to the same table.

I'm assuming this error is due to some of my queries bumping into one
another at some level, or possibly an ODBC problem.  I'm thinking it could
be some kind of timing issue.  When I run the queries on empty tables, or
tables with minimal records they complete as expected.  I've actually got
one client machine that can run the processes to completion.  the rest fail
with the s10008 error.

Has anyone seen this problem before?  Am I making some obvious errors here?
I'd appreciate any help anyone could offer.

Thanks,

Kevin Black

Have you looked into using ADO instead.  You should be able to use it with
the professional version of VB5.  No specific help on S10008 though.  Sorry