Hi Dean,
I think the problem may be with the type of connection you are making with MS SQL Server. The behaviour you describe sounds like the behaviour you get from a connection using a 'forward only' cursor. This is the default cursor type when you call the Execute method of the Command and Connection objects. To provide the functionality you are used to with Access use the static, keyset or dynamic cursor. The forward-only cursor is optimized for performance - a case of 'horses for courses'
Regards
Rob
Hi Rob!
You are right on the money. I have found out this very thing from another forum I posted the problem in as well. But there is something else that I need to address and that is the different objects involved.
* Command Object
* Connection Object
* Recordset Object
I use Dreamweaver v8.0.2 to develop and when you create a new Recordset (Query) it automatically writes the best possible code for you as I am sure you might be aware. Here is a sample of what it codes:
<%
Dim Recordset1
Dim Recordset1_cmd
Dim Recordset1_numRows
SET Recordset1_cmd = Server.CreateObject ("ADODB.Command")
Recordset1_cmd.ActiveConnection = MM_ADSystemSQL_STRING
Recordset1_cmd.CommandText = "SELECT * FROM tblGBook"
Recordset1_cmd.Prepared = true
SET Recordset1 = Recordset1_cmd.Execute
Recordset1_numRows = 0
%>
As you can see, DW by default uses the Command object and from what I can tell, there is no way to use the CursorType directive with the Command object alone.
Different sources of information on the subject offer different explanations of these objects. For instance, one source indicated that when using the Command object to connect to a database that the Connection object is automatically called into the scenario. In addition to this, using a SELECT statement with a Command object calls the Recordset object as well which I interpreted to mean that all three objects are in use despite only coding the Command object.
Still, the only way it seems possible to specify CursorType is to write in a call to the Recordset object and then specify the CursorType. Typically in these scenarios, you would not code the Command object at all, instead, you would write calls to the Connection and Recordset objects solely.
Why does DW do this?
I have looked into developing a custom Server Behavior but there is no way to mimic the complete automation of DW's default Recordset (Query) behavior. I was successful in getting it to mimic the default behavior to an extent using my default code, special parameters and such. But I cannot get it to automatically create a Connection script and place it into the Connections folder or create a folder for that matter. Nor can I duplicate the tables column selection feature with radio buttons (All, Selected) or the filter and sort features.
Here is a screen shot of DW's default Recordset behavior:
http://aboutdean.com/images/subject/...dwrsquery1.jpg
This is the closest I can get to duplicating it:
http://aboutdean.com/images/subject/...dwrsquery2.jpg
DW gives you a plethora of options that you can use to create these windows:
http://aboutdean.com/images/subject/...dwrsquery3.jpg
But there is no automated means of making many of them work without actually editing the EDML files that contain their logic.
This is certainly off topic and more work than I need. However, the prospect is great if you can actually get it to code what you need on the fly. Unfortunately, not without digressing from your true work to learn how DW works, EDML etc. :rolleyes:
Unsolved 
