Raul

>> <<It's pretty simple to write something for example that closes it all
>> from "bottom up".>>
>>
>>
>> Yes, but why bother - just closing the engine should close everything else.
>>
>
>If all you want to do is close then possibly yes but closing engine is
>bit of a sledgehammer approach.

I'd view either as appropriate if you need to close everything

>I have found that managing your sessions/db/datasets long term is lot
>more maintenable - especially if you want to close and then open or
>maybe have different sessions mixed etc

Fully agree with this

Roy

Roy  & Raul

You are both right, and I have added a bit of code to iterate DB.Datasets[i] ... which is great.

DB.Close does close all the datasets, so DB.Datasets[i].Close isn't necessary, but as the EDBDataset includes a SessionName property, if you connect to a new session any "dangling" dataset with the wrong SessionName will cause an error when it reopens, so DB.Datasets[i].SessionName is really useful to iterate and change (if this is the behaviour you need!).