Hi Wolfgang, > Needs 're-execute' less computer effort than calling the SQL again > (is a time consuming operation)?
It makes use of prepared statements, which, once prepared, can be executed multiple times, which allows the server to optimize this. > Re-execute the row set after _Delete_ works fine. The changed RowSet > documentation will be *very* helpfull (To make people more happy: > You may add > call curRow=oRoSe.getRow(), then delete and call > oRose.absolute(curRow) ->the user shows the next candidate) Actually, there is some extensive documentation about the delete behaviour of the RowSet. Unfortunately, due to a bug (69082) in the tool which is used to generate the online IDL reference, this information is not visible :(. I hope that this bug will be fixed before the 2.0.4-reference will be put online. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
