Re: Best point to commit in a Master/Dtl Form

From: Shawn Odekirk <shawno_at_erudite.com>
Date: 1997/03/17
Message-ID: <01bc330f$2769c360$050264c8_at_Shawno.erudite.com>#1/1


Steve Cosner <stevec_at_zimmer.csufresno.edu> wrote in article <858275805.12588_at_dejanews.com>...
> In article <19970312000600.TAA23693_at_ladder01.news.aol.com>,
> malh1156_at_aol.com (Malh1156) wrote:
> > I am trying to ascertain when should I commit a record in a
> > Master/Detail Form.
> > 1) I can commit the master block as I navigate to the detail
> > block, and subsequently commit each detail row as I
> > navigate to the next row.
> > OR
> > 2) wait till the operator is done and then commit all records
> > then when he presses save button.
> > Which one is better? If I implement 1), it is easy to check
> > for duplicate records entered in the detail block as user
> > enters them. But giving an explicit SAVE button to could be
> > tricky.
> > If I implement 2) then I am not sure If I can detect for
> > duplicate records entered into the detail block till the
> > operator TRIES to commit..

We chose method 1. If the user makes a lot of changes, and then makes a mistake on the last change, we found it much easier to undo the mistake if all of the previous changes have been commited to the database.

Shawn Received on Mon Mar 17 1997 - 00:00:00 CET

Original text of this message