I've just posted the latest version of my subclassed EDBTable to the extensions newsgroup. It now opens on any access. I currently have the switch that allows auto opening set to False.

I'm thinking of setting it to True, or even removing it. Can any of you lot think of a situation where you wouldn't want the table to open itself if not already open when you access it?

Roy Lambert

Hi Roy,

> I've just posted the latest version of my subclassed EDBTable to the extensions newsgroup. It now opens on any access. I currently have the switch that allows auto opening set to False.
>
> I'm thinking of setting it to True, or even removing it. Can any of you lot think of a situation where you wouldn't want the table to open itself if not already open when you access it?

A great idea. I'm not sure about situations where it wouldn't be
warranted, but maybe you could create a Boolean property called
'AutoOpen' which is defaulted to TRUE but the user could set to false if
they didn't want it automatically opened (or is this the 'switch' you're
referring too)?

Design time is probably the only time I wouldn't want it to
automatically open. (Such as if it's connected to a report or something
else that decides it wants the data).

Adam

>A great idea.

Well it would be apart from the fact that it ballses up in a live app. In the testbed it works perfectly. I have asked the guru for assistance.

>I'm not sure about situations where it wouldn't be
>warranted, but maybe you could create a Boolean property called
>'AutoOpen' which is defaulted to TRUE but the user could set to false if
>they didn't want it automatically opened (or is this the 'switch' you're
>referring too)?

Sure is - its called AllowAutoOpen

>Design time is probably the only time I wouldn't want it to
>automatically open. (Such as if it's connected to a report or something
>else that decides it wants the data).

Hmm - I hadn't thought of even trying to do that. My concept was for run time so that whenever you access a table if its not already open then it gets opened.

Roy

Hi Roy,

>> A great idea.
>
> Well it would be apart from the fact that it ballses up in a live app. In the testbed it works perfectly. I have asked the guru for assistance.

Sorry to hear. Hopefully Tim can give you a solution.

>> (or is this the 'switch' you're
>> referring too)?
>
> Sure is - its called AllowAutoOpen

Excellent - great minds think alike. You must be in good company.


>> Design time is probably the only time I wouldn't want it to
>> automatically open. (Such as if it's connected to a report or something
>> else that decides it wants the data).
>
> Hmm - I hadn't thought of even trying to do that. My concept was for run time so that whenever you access a table if its not already open then it gets opened.

I was more thinking from the point of view to make sure that your
component doesn't automatically open during design time, rather than
giving it that option.

I use report builder. One of the things I have to be careful with is
that it can automatically activate a dataset I have deactivated in
design time. If the dataset is a query that needs to have conditions
applied to it before opening, and it's accidentally opened in design
time (without me knowing) and given to the client - they have to wait a
loooong time before the form shows because it's trying to activate the
dataset and do all calculations with no restrictions / conditions at all
on a large database.

That's where my thought was in regards to your component - just making
sure it doesn't automatically open during design time if not wanted. If
it doesn't already - then IMO that's a good thing.

Cheers

Adam.

Adam

>I was more thinking from the point of view to make sure that your
>component doesn't automatically open during design time, rather than
>giving it that option.
>
>I use report builder. One of the things I have to be careful with is
>that it can automatically activate a dataset I have deactivated in
>design time. If the dataset is a query that needs to have conditions
>applied to it before opening, and it's accidentally opened in design
>time (without me knowing) and given to the client - they have to wait a
>loooong time before the form shows because it's trying to activate the
>dataset and do all calculations with no restrictions / conditions at all
>on a large database.
>
>That's where my thought was in regards to your component - just making
>sure it doesn't automatically open during design time if not wanted. If
>it doesn't already - then IMO that's a good thing.

As far as design time is concerned the behaviour should be that of a standard TEDBTable

Roy