Hi Eyvind,

>I cannot understand how this can be by design. First of all, if one does not change this property, then if you delete from a cursor that is based on a select from two related tables, rows are deleted in both when you call tableupdate(), even though the tables property only contains the name of one of the tables.

Then it is his responsibility to configure the Recordset object properly. Have you seen anywhere in documentation that CursorAdapter should set "Unique table" based on Tables property?


>Furthermore, this behavior is different when using native tables - deleting then works as expected and respects the tables property.
>
Support for each data source type has it's own specifics.


>Secondly, if you try to set the property ("Unique table") in the cursorFill method, it is reset to the empty string when this method is completed. Is that by design as well?
>

I am sure that CursorAdapter doesn't change that property explicitly. It might be cleared by ADO when the Recordset is opened using Open method, you just have to set it in AfterCursorFill event or override the CursorFill method, call default implementation and then set the property.

Thanks,
Aleksey.