[AccessD] Double Data Entry Requirement

The data is coming via paper.
The database will be used to collect information from paper copies of surveys.
There are seven different surveys - color coded by a survey participant attribute (youth, parent, staff).
Participant ID and protocol have been defined by the agency.
Surveys will be paired by participant, who will take at least three surveys from different color groupings.
Statistical analysis of the surveys are the end result, hence their "need" to ensure data integrity.

Thanks,
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of MartyConnelly
Sent: Wednesday, April 20, 2005 3:33 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Double Data Entry Requirement


Double Data entry used to be done by two separate operators even going 
back to the old IBM 029 card key punch verifiers (which didn't punch 
only read)
and the later key to disk systems. As the same operator may read a 9 as 
an 8 both times. Not to mention there were batch totals kept  i.e. 
number of sheets punched to ensure an operator didn't skip a sheet in a 
batch. Most data entry errors are caused by transposition of digits. 
Hence the use of checkdigits
for things like ISBN,VIN, credit cards and social security number (but 
not in US)
You might want to consider optical scanning unless the data is coming 
from handwriting.

Jim Hewson wrote:

>That might work.
>A tabbed form where the first data entry on tab 0 then second data entry on tab 1, compare data then save.
>I'm going to try to change their minds before we end up double data entry.
>Thanks.
>Jim
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Bobby Heid
>Sent: Wednesday, April 20, 2005 1:10 PM
>To: 'Access Developers discussion and problem solving'
>Subject: RE: [AccessD] Double Data Entry Requirement
>
>
>I favor #1 the most and #3 the least.
>
>I guess a lot of it depends on how it will be entered.  You might consider
>an unbound form where the data is entered twice and compare fields before
>writing out the data record.
>
>Bobby
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Hewson
>Sent: Wednesday, April 20, 2005 1:52 PM
>To: AccessD
>Subject: [AccessD] Double Data Entry Requirement
>
>
>Has anyone done this before?
>
>I am working on a proposal and one criteria is to "provide for the entry
>of... data twice to ensure accuracy."
>I thought of three methods of doing this.
>1. Create a table for the second data entry and then compare the record with
>the first table.  Delete the record(s) of the second table when they match.
>2.  Use an unbound form for the second data entry and compare the results
>with the table to ensure they match then delete the data. 
>3.  Recommend the second person print the record and compare the documents
>without doing a double data entry.  Suggesting it would take less time and
>therefore save money.  There is the issue of paper, printing, etc.....
>
>Thoughts!
>
>Thanks,
>
>Jim
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com