Current recordset does not support updating rowupdating get datakey

Posted by / 27-Jan-2020 21:59

Current recordset does not support updating

billegge wrote: I'm pretty sure the ODBC driver does not implement the equivalent of delphi's "Request Live" (but I'm not the primary developer of the ODBC driver and might be mistaken). It seems what you are saying is that the ODBC driver, in general, does not allow live data. This is not a Delphi issue because I am not use TData Set, just the ADO objects directly which any consumer (such as MS Access) would do. Command Text = "Select PODate, POLoc, POItem FROM Pur Ord " & _ "where PODate = #" & Selected Date & "# and POLoc = '" & str Loc & "' " & _ "AND POItem = " & CInt(str Item) POrst Data = C. I wish there was an example of someone reading a transaction file and updating a table (add, update & delete based on the transaction type). Thanks, Hexman On Mon, -0800, "Denny" OK, I looked at the examples in the SDK and other internet sources --- and now I'm even more confused. Lock Type Lock Optimistic, True) End Sub Private Sub Update Process() C. Add New() OK, I looked at the examples in the SDK and other internet sources --- and now I'm even more confused. I've seen ASP code, C code & VB code with ADO classic and ADO. Don't know which way to turn - just trying to get this task finished (along with being guided down the correct path of learning about this). I thought my approach in the code below was a good solution, but apparently not. Command Type Cmd Text 'create and open record set POrst Data = New ADODB. I've seen ASP code, C code & VB code with ADO classic and ADO. Don't know which way to turn - just trying to get this task finished (along with being guided down the correct path of learning about this). I thought my approach in the code below was a good solution, but apparently not. I wish there was an example of someone reading a transaction file and updating a table (add, update & delete based on the transaction type). "You" might not be using a TData Set, the ODBC driver on the other hand isn't magic and certainly does.

This may be a limitation of the provider, or of the selected locktype.

I have a website with some asp pages running off of a MS Sql db.

For reasons that I can't explain, whenever querying the database with a SELECT query containing an order by clause, the returned recordset is read-only, regardless of cursor or lock type.

Command Text = "Select PODate, POLoc, POItem FROM Pur Ord " & _ "where PODate = #" & Selected Date & "# and POLoc = '" & str Loc & "' " & _ "AND POItem = " & CInt(str Item) POrst Data = C.

Lock Type Lock Optimistic, True) End Sub Private Sub Update Process() C.

current recordset does not support updating-37current recordset does not support updating-22current recordset does not support updating-78

I tried to modify the field in my ASP page, and it yields the following error: I tried to use ad Lock Optimistic as follows, but still not working obj RS.