by      
Error # -2147217900 was generated by Microsoft OLE DB Provider for ODBC Drivers [Microsoft][SQL Server Native Client 10.0][SQL Server]Executing SQL directly; no cursor. Have you see this error? I have, and it's going to be difficult to explain but I'll do my best. It's going to be different for you I bet, but if you work with the code I bet you will find what is really causing this error.

Executing SQL directly; no cursor

Error # -2147217900 was generated by Microsoft OLE DB Provider for  ODBC Drivers [Microsoft][SQL Server Native Client 10.0][SQL  Server]Executing SQL directly; no cursor.

I was working on some new (old) scripts for one of my ASP Classic sites.

I use SQL Server 2008 and 2008 R2.

The connection is using the SQL Server Native Client 10.0

What I noticed was when I called several "Set RecordSet"

Let's say I had Set str1 = Server.CreateObject("ADODB.Recordset")

Then called Set str2 = Server.CreateObject("ADODB.Recordset")

Calling from the same table you'll see this error as long as the record set is open.

 

I tested this a couple of ways.

When I replaced the record set with Set str1 = Conn.Execute(" the issue was no longer present.

I've seen this error from time to time on a couple of my sites and I have read just about everything posted in the last 3 months about this issue.

If you have a rock solid solution feel free to email me.

From what I have seen it's how you are coding your work more than a Cursor issue.

 

 

Error # -2147217900 was generated by Microsoft OLE DB Provider for ODBC Drivers [Microsoft][SQL Server Native Client 10.0][SQL Server]Executing SQL directly; no cursor. Have you see this error? I have, and it's going to be difficult to explain but I'll do my best. It's going to be different for you I bet, but if you work with the code I bet you will find what is really causing this error.