Re: forms3.0, number of rows

Off hand, I can't think of a reason why this could happen.

What is the block and form status after the commit? Does it indicate that no changes are pending as it should do?

If it's an automatic process to query, trawl through each record received, change it and then finally commit, could yousupply the trigger text as there may be afault in that.

Have you checked that teh number of records retreived (you could see the record count at the bottom of the screen as you go through the records or use count query hits in query mode for this) matches the number of records committed?

--
Alan D. Mills

Corinna Becker wrote in message
<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 Fri Jul 24 1998 - 08:13:24 CDT