I have recently upgraded from VB4 to VB5 and I've run into
a {*filter*} of a problem.  I'd like to enlist the aid of the list/group
in providing a solution.  The problem is easily reproduced
and did NOT exist with VB4.

I have been using the ODBC SQL Server Driver since VB4.

I am connecting to a SQL Server 6.5 database using both RDO
and RDC.  I can use the OpenConnection method on my
rdoEnvironment (0) with the CursorDriver set to rdUseNone.
No problem so far.  I then Refresh my RDC which uses another
CursorDriver (rdUseNone is NOT available to RDC).  For some
reason that causes the CursorDriver to change for my initial
RDO connection which has the effect of limiting subsequent
CreateQuery's to the rules of the CursorDriver associated
with the RDC.  This behavior continues even after Closing the
RDC.Resultset and even after setting everything (rdoEnvironment,
RDC, etc.) to Nothing and then attempting to re-establish a
connection.  I have to End the App and restart to get things reset.

Is this a known VB5 bug?  This problem effectively "broke" my
software after upgrading to VB5.

Suggestions are welcomed.
--
Dan DiNardo                                 "Who's John Galt?"
Ascent Inventory Management, Inc.  Camarillo, CA

Have you tried to use server-side cursors on SQL server? If not, you
blocked the SQL Server connection to a single open resultset (the statement
handle might be blocked as long as you do not explicitly move to the end of
the resultset).