Am Wednesday 30 August 2006 14:17 schrieb Wolfgang Schaible:
> hi Frank
> Am Wednesday 30 August 2006 07:58 schrieb Frank Schönheit - Sun
>
> Microsystems Germany:
> > Hi Andrew,
> >
> > > First can you refresh a resultset or rowset, as you can a
> > > dataForm with reload? For this I believe Xrowset would need
> > > to include the interface XLoadable, which it does not. So, to
> > > get a fresh set of data after issuing update/delete
> > > statements you are going to have to create a new rowset.
> >
> > You can re-execute the row set (simply call execute, again),
> > this will also refresh it. I'll add this to the RowSet's
> > documentation.
>
> Thanks for the tip.
> Needs 're-execute' less computer effort than calling the SQL
> again (is a time consuming operation)?
>
> 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)

Sorry, the following is wrong: It works fine...
Have had the statements after 'insertMaster' and before 
the 'insertChild'. 
> Re-execute the row after _Insert_ works not for me. After
> 'Insert' the cursor points to 'isBeforeFirst' (without
> oRoSe.execute() to 'isFirst'), after adding 'oRoSe.first()' the
> rowSet  does not contain the new item.
> The other way would be better: Usually I create more new records
> then delete it. Shure :=)
>
Ciao
Wolfgang
>
>
> -----------------------------------------------------------------
>---- To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to