not that i'm in any way qualified to offer help to others, but i
encountered a somewhat similar problem and solved it with using the
invalidate method...even if not directly related to the current
problem, it does apply to other query opening and closing problems.

j

--- In IBObjects@yahoogroups.com, "G. Nau" <b404_r66@y...> wrote:
> Lester,
> okay, than my way to close and reopen the query is the way to go.
> Thanks for your help.
> G.
>
> Am 3 Oct 2005 um 13:26 hat Lester Caine geschrieben:
>
> > G. Nau wrote:
> >
> > > Doing a ib_query.active:=false; ib_query.prepare and
ib_query.active:=true
> > > again is working. I'd like to speed things up a little bit and
avoid this query
> > > activation triggering.
> >
> > But you have changed the 'content' of the query SQL, so you HAVE
to
> > 're-open' the query. Prepare will only speed things up if you are
THEN
> > using parameters to change the way the query works.
> >
> > > The PrepareSQL event is triggered on the refresh click.
> > > Maybe I'm missing something here in my onprepareSQL event and
it's not
> > > directly related to the way to do a re-prepare?
> >
> > Having changed the SQL, you need your refresh action to be
close\reopen.
> > But actually I would Close the query before applying the new SQL.
> >
> > At least that is MY understanding ;)
> >
> > --
> > Lester Caine
>
>
>
>
>
>
> ___________________________________________________________
> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier
anmelden: http://mail.yahoo.de