Re: Commit problem

[Terri Jenkins <LDYGLFR@AOL.COM>]

Take into consideration whether later rows will be updating earlier rows.  If
so, you may want to commit the earlier updates, maybe even one row at a time.
 One example I'm thinking of is when a user makes the wrong update, then
makes another update with the correct information.  They would effectively be
keying in an undo action in the second update which may need to locate the
'incorrect' info from before.

Regardless of the method you choose, add a row counter in your program, and
display the count after each commit.