RE: Double Data Entry

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Mal .mullerjannie_at_hotmail.com> (.mullerjannie_at_hotmail.com)
Date: 10/22/04 

Date: Fri, 22 Oct 2004 07:11:03 -0700

First idea would be to validate the data on the client side.

If you can't do that, create a mechanism that displays the status of your
data,
like , awaiting verification, and verified... On same DB same table, same
column different values.

Data still awaiting verification, exclude them in selects and vice-versa.

Hope this is a step towards what you were looking for.

"Brandon Campbell" wrote:

> Hello,
>
> I have recently taken over a double data entry database. I feel that the
> design is not quite correct. The second data entry person has the right to
> verify the input. I feel that both people should be entering the data and a
> third person should be a verifier.
>
> Therefore, I was thinking along the lines of having two identical databases
> and merge the validated data into a production database. The other could be
> to have a data entry database with identical copies of the tables (I feel
> this would be a waste though).
>
> Does anyone have an Idea! I have seen some examples on the internet, but I
> would like to hear from others that use this method.
>
> Thank you,
> --
> --------------------------------------------
> Database Administrator
> bkc5 AT CDC dot GOV