Bi-Directional Cursors in ADO - URGENT HELP NEEDED !!
When a TADODataSet is attached to an Orpheus DBTable component, even
when CursorLocation is clUseClient, CursorType always changes to clStatic
when I open the query or stored procedure. This prevents me from moving
backwards and forwards in the DBTable component, and I need bi-directional
functionality. Help !!!
.
Relevant Pages
- Re: Current Recordset does not support updating.
... When the query is first opened all settings ... >> Current Recordset does not support updating. ... >> above CursorLocation to see if problem went away, ... I changed the CursorType to adOpenKeyset. ... (microsoft.public.vb.database.ado) - ADO query returning large dataset very slow
... I have to do some calculations on a very large dataset. ... The Query is setup like this: ... CursorLocation: clUseClient ... better component than the standard delphi ones. ... (borland.public.delphi.database.ado) - Re: ADO query returning large dataset very slow
... >I have to do some calculations on a very large dataset. ... >The Query is setup like this: ... >CursorLocation: clUseClient ... Normally you don't try to keep that many values in memory when you already have ... (borland.public.delphi.database.ado) - Re: Setting DBPROP_BOOKMARKS Property- Help!!!!!
... when CursorLocation is clUseClient, ... backwards and forwards in the DBTable component, ... Clientside cursors are always bidirectional. ... Try a query with a TadoDataset where you set the commandtext and then Connection ... (borland.public.delphi.database.ado) |
|