Howdy Wolfgang,

Two things going on here.

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.


Second, the select statement you show would not create an updatable rowset, as you find can see by

Have tried the use the SDBC method
   oRoSe.deleteRow()
This results in "Delete privilege not available"

As for helping with a code around, let me ask you this. If you have a rowset built as your select statement shows what do you want to happen when you delete a row. Do you want the corresponding rows in both tables to be deleted?

Drew


Wolfgang Schaible wrote:

hi,
Have a rowSet (Scroll_sensitive, updatable) filled with
a SQL-Statement <Select *,* FROM TAB1,TAB2 Where id1=id2>
Everything is working (navigate, insert, change and delete) but I think suboptimal" :=)

Insert: After oStmt.executeUpdate("Insert Into TAB1 (f1,f2,...)+_
   Values('v1','v2',...))
   oStmt.executeUpdate("Insert Into TAB2 ...
the rowSet seems to be unchanged (not reachable with navigation).
After creating a _new_ rowSet the newcommer is visible.

Delete: After
   oStmt.executeUpdate("DELETE FROM TAB1 WHERE id1=id2)
the dialog does not change, the deleted row keeps visible.
After creating a _new_ rowSet the row is gone.

Recreating the rowSet seems not really efficient...

Have tried the use the SDBC method
   oRoSe.deleteRow()
This results in "Delete privilege not available"

and Google does not report a code snippet


Use OOo 2.1, HSQLDB on ARCH-Linux

Thanks for a better idea
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