>For data access, it's a no-op. It's all the same whether you set it or
>not, since it's not used. But what if an application happens to be using
>the connection component for creating a database or restoring a
>backup? Are you saying that the property shouldn't be writable because
>there might be some developer who doesn't understand that the connection
>classes have multiple uses?
>
>Helen
>
>
>

Good point. I thought from your initial comment that it had no impact
at all but I guess that it actually does if components doing DB creation
/ backup / restores are connected to them. This is the case in our
application. I agree with you that for the most flexibility it should
be writable.


Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd