Re: Call a FORM in QUERY_ONLY mode

From: Stefan Kursawe <skursawe_at_earthlink.net>
Date: Mon, 06 Nov 2000 17:23:11 GMT
Message-ID: <3OBN5.23154$rl.1997294_at_newsread2.prod.itd.earthlink.net>


Hi Eric,

thanks for the idea, I am doing exactly what you proposed, just thought there might be
an easier way like a property that tells me the state of the form.

regards

    Stefan

"Eric Givler" <egivler_at_flash.net> wrote in message news:JLkN5.6422$pq3.485432_at_news.flash.net...
> I ran into a similar problem before and I didn't find any way of
 determining
> that (via a property or something).
>
> BUT, maybe you can attempt to modify something in a field, set a form
 level
> on-error and trap for the "form is running in query only mode" error. If
> you do that on startup, you can set a package level variable to hold the
> "query only mode" status. You'll have to generate the error first to see
> what to look for.
> Good luck.
>
> "Stefan Kursawe" <skursawe_at_earthlink.net> wrote in message
> news:FhmM5.11377$rl.949815_at_newsread2.prod.itd.earthlink.net...
> > Hello,
> >
> > if FORM A calls FORM B with the parameter QUERY_ONLY.
> >
> > Is there a way in FORM B, like a build_in that tells me, that it was
> > opened in QUERY_ONLY ? I didnt find anything in the documentation.
> >
> > regards
> > Stefan
> >
> >
> >
> >
>
>
>
Received on Mon Nov 06 2000 - 18:23:11 CET

Original text of this message