> Using filters like this works just fine, but I wonder if
> there is a better approach to simulate a master detail
> relationship between a non-dataware component and a dataset.

Client side filters are probably a good solution for slow network
connections (so all records are retrieved to the client and the view
filtered according to select).

Using parameters would be more consistent with master detail styled
processing (every time the node changes the parameters get updated and
new records retrieved from the server). Similar to what you are
already doing but...

q.Params.BeginUpdate;
try
q.ParamByName['categorie'].AsInteger := node.parent.overlayindex;
q.ParamByName['categorie'].AsInteger := node.overlayindex;
finally
q.Params.EndUpdate;
end;


Not exactly what you were doing, but hopefully you get the idea.


Geoff Worboys
Telesis Computing