I have noticed the following 'feature' under S+ 6.1 (r1) with Win2K and
SQL Server 2000
Calling a stored procedure (see below) with the returnData=F, causes
the obdc driver to
fail until S+ is restarted.
Problem can be worked around by using returnData=T (even if data are
not returned).
Unsure if the problem still exists with the native SQL drivers under S+
6.2
--------------
odbcCx <- "DSN= ..."
# the following SQL code is executed as a stored procedure on the
server
# CREATE PROCEDURE test
# AS
# -- start procedure code
#
# RETURN 100
# GO
#
executeSql(odbcConnection=odbcCx, odbcSqlQuery="exec dbo.test",
returnData=T) #works
executeSql(odbcConnection=odbcCx, odbcSqlQuery="exec dbo.test",
returnData=F) #breaks odbc driver
executeSql(odbcConnection=odbcCx, odbcSqlQuery="exec dbo.test",
returnData=T) #odbc broken until S+ restart
---------------
James Scandol
NSW Department of Primary Industries
Cronulla Fisheries Centre
PO Box 21; Cronulla NSW 2230
James.Scandol@fisheries.nsw.gov.au
ph: (612) 9527 8540
fx: (612) 9527 8576
mob: 0408 608 988
This message is intended for the addressee named and may contain
confidential information. If you are not the intended recipient, please
delete it and notify the sender. Views expressed in this message are
those of the individual sender, and are not necessarily the views of
the NSW Department of Primary Industries.
This message is intended for the addressee named and may contain confidential
information. If you are not the intended recipient, please delete it and notify
the sender. Views expressed in this message are those of the individual sender,
and are not necessarily the views of the NSW Department of Primary Industries.
|