Subject | Re: TIBODatabase.Open long delays |
---|---|
Author | eamonnm2002 |
Post date | 2003-05-01T14:32:45Z |
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
i'll switch to using connect instead of open and will let you know
what happens. looking at the source, Open is just a call to
Connect, so i'm not too hopeful.
FYI, this week i have seen the same problem in another app that uses
the same datamodule. Still have not seen it in another datamodule,
and am failry confident i havn't seen it outside of delphi, so i'm
still wondering about the delphi debugger (or how my code could
possibly interfere with it!)
cheers.
> I notice that you are referring to the 'Open' call ofTIBODatabase...this
> is a legacy from the VCL, which might well involve a lotmore "noise" in
> the connection event than necessary, because of its genericcharacter.
>the
> Would you like to try calling Connect instead, and report back on
> result. It's a good precaution always to test first whether it isalready
> connected, too:because this
>
> if not MyIBODatabase.Connected then
> MyIBODatabase.Connect;
>
> After that, explicitly open the datasets which you need to have
> open: avoid using the ib_SessionProps property StoreActive,
> is *very* noisy, especially for big datasets.Thanks Helen,
>
> Hmm, and don't overlook the golden rule of *NOT* opening large,
> unrestricted datasets at all.
i'll switch to using connect instead of open and will let you know
what happens. looking at the source, Open is just a call to
Connect, so i'm not too hopeful.
FYI, this week i have seen the same problem in another app that uses
the same datamodule. Still have not seen it in another datamodule,
and am failry confident i havn't seen it outside of delphi, so i'm
still wondering about the delphi debugger (or how my code could
possibly interfere with it!)
cheers.