Re: forms3.0, number of rows

From: Matt Brennan <mbrennan_at_gers.antispam.com>
Date: Tue, 28 Jul 1998 23:13:30 GMT
Message-ID: <01bdba7d$5a7c0f00$049a0580@mcb>

There was another post sort of like this one I think. I don't know Forms well, but I think someone mentioned an optional parameter on the post-query trigger called "all records" or something?

It sounds like in your query, the ones that are being updated might be only the ones the user scrolls through...? Search the other recent posts - the answer's probably there (similar situation to yours). --
Matt Brennan
SQL*Tools Specialist
GERS Retail Systems
9725-C Scranton Road
San Diego, California 92121
1-800-854-2263
mbrennan_at_gers.com
(Original email address is spam-blocked.)

Corinna Becker <Corinna.Becker_at_memo.ikea.com> wrote in article <01bdb6f9$0ef52260$a049100a_at_pc743-sode.seurope.ikea.com>...
> Hello,
> I am working with Forms 3.0. We have the problem that we select a set of
> data (ordered by zip codes), then we change a field in each row selected
> and commit.
> After the commit rows with high values of zip codes were not updated.
> We think that this could be a problem of the number of rows selected and
> the "records buffered" set in the Form.
> Does anybody know about this?
> Thanks for your help
> Corinna Becker
>
Received on Tue Jul 28 1998 - 18:13:30 CDT