So, for me (and I hope, for You too) the situation is clear. You open recordset with adLockOptimistic, which is default when updating records in the recordset. (ADO thinks that you are about doing some updates). As Peter has written before - updating recordset which were created with statement containing GROUP clause isn't possible (it's obvious, because which records should DB update if You get only aggregates - let's say "records which are the results of some calculation"). Try to replace adLockOptimistic with adLockReadOnly and everything should be fine. If not - please let me know. Good luck and have a nice weekend, Marcin Pytel
Uzytkownik "Benjamin Lukner" <[EMAIL PROTECTED]> napisal w wiadomosci news:[EMAIL PROTECTED] > Marcin P wrote: > > Could you paste your VB code? > > Maybe I could help you with that.... > > I think the statement is rather ok. > > > > Marcin Pytel > > The code is: > > Private oAdoRec As Recordset > > ... > > Set oAdoRec = New Recordset > > oAdoRec.Open sSQL, oMain.ADO.ADOConnection, adOpenStatic, > adLockOptimistic, adCmdText > > I'll have a look at it with our 'chief programmer' because the open code > line comes from her. We only use SELECT with that code. UPDATE and > DELETE is done by a completely other class and via > oMain.ADO.ADOConnection.Execute sSQL, lRowsAffected > (oMain.ADO.ADOConnection is of type Connection) > So I didn't look at the code above. > > Thanks for your advice! :-) > > > Kind regards, > > Benjamin Lukner > trinomix GmbH _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
