Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-04-28 : 07:27:33
|
| Owen writes "I have been developing an application with SQL Server 2000 (under windows 2000). To make life easy I have been developing it using MSDE (MSDE and SQL Server both service pack 3).However under MSDE I have a few stored procs that do an insert or update, and then a select (to return me the recordset) Using VB 6 and ADO. Under MSDE that is all fine. Put it onto SQL Server however and an empty recordset is returned.What is the problem ?, and what's the solution ?... and ....I thought they were supposed to be compatible." |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-04-28 : 08:14:28
|
| suspect you need aset nocount onat the top of the SPs.Or to get the next recordset in VB until you find an open one.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Stored Procedure incompatibilities in MSDE and SQL Server 2000