When you prepare the rec file for double entry better to leave the box "Match by record" unchecked. However if the double entry appears to slow or cause some frustration, perhaps it might be better to use copy structure and enter the data for comparison.
Tieble
On 29 April 2010 18:06, epidata-list-request@lists.umanitoba.ca wrote:
Send EpiData-list mailing list submissions to epidata-list@lists.umanitoba.ca
To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request@lists.umanitoba.ca
You can reach the person managing the list at epidata-list-owner@lists.umanitoba.ca
When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..."
EpiData-list mailing list ___________________________________
Today's Topics:
- RE: Double Entry for Related Files (epidata-list@lists.umanitoba.ca)
- Access violation error with Codebook command in EpiData (second try) (epidata-list@lists.umanitoba.ca)
Message: 1 Date: Wed, 28 Apr 2010 13:48:41 -0500 From: epidata-list@lists.umanitoba.ca Subject: [EpiData-list] RE: Double Entry for Related Files To: epidata-list@lists.umanitoba.ca Message-ID: 679902537E215D43805DEA9BE833090E042A5B80@NORCEX1.norc.org Content-Type: text/plain; charset="us-ascii"
I understand the two different methods of double-entering data, and I do indeed want to "prepare for double-entry". The problem is that when I go to prepare the questionnaire for double entry, I can only choose to prepare either the parent OR the child file. If I choose the parent file, then a double-entry file is only created for the parent file - when I open it to double enter the data, it relates to the original child file, so it opens the parent double entry file along with the original child file. Since only one of the two files is a double entry file, the program thinks I am entering the data for the first time, and does not compare the alues entered to the values from the original file.
I cannot seem to find a way to prepare both the parent and the child file for double entry together. If I prepare them for double entry separately, I run into similar problems.
Sam
Message: 1
Date: Tue, 27 Apr 2010 19:13:58 +0200
From: epidata-list@lists.umanitoba.ca
Subject: Re: [EpiData-list] Double Entry for Related Files
To: epidata-list@lists.umanitoba.ca
Message-ID: 4BD71B56.7020800@tbrieder.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Sam:
There are two approaches to double-enter: 1) independently, 2) the second file depending on the first. You seemingly chose the latter ("prepare for double-entry"). If you choose that option, you must enter the records in the same sequence (I believe) and the value of each field in the second record will be compared to the corresponding one in the first and a discordance reported, so you can verify. Thus, no need to enter twice.
Alternatively, you enter your related file pairs independently between first and second entry. You must have a unique identifier in both the parent and the child file. The sequence then doesn't matter of course.
After you have entered parent1-child1 and parent2-child1, you validate
parent1-vs-parent2 on the unique identifier, then child1-vs-child2 on that identifier.
Hans
On 20:59, epidata-list@lists.umanitoba.ca wrote:
Hi,
I have a questionnaire that uses two related .rec files for data
entry.
I want to double enter the data by checking for discrepancies as the
data is entered the second time. Is it possible to do this for
questionnaires that span two .rec files? When I try to prepare for
double entry, the program creates a "file1_dbl.rec" file, but relates
it to the "file2.rec" file rather than creating a "file2_dbl.rec" file
to compare against.
I am thinking that I will just have to un-relate the file, and enter
and double-enter the survey in two parts, but any help would be
appreciated.
Thanks,
Sam
--
Hans L Rieder, MD, MPH
Jetzikofenstr 12
3038 Kirchlindach
Switzerland
Tel: +41 31 829 4577
Mob: +41 79 321 9122
--
Samuel Haddaway
Research Assistant, International Projects
National Opinion Research Center
haddaway-sam@norc.org
Phone: 301.634.9423
Message: 2 Date: Wed, 28 Apr 2010 21:50:13 +0200 From: epidata-list@lists.umanitoba.ca Subject: [EpiData-list] Access violation error with Codebook command in EpiData (second try) To: epidata-list@lists.umanitoba.ca Message-ID: OF120C2D35.551C97A0-ONC1257713.006CF7D1-C1257713.006CF7D4@sll.se Content-Type: text/plain; charset=ISO-8859-1
Hi! When trying to create a Codebook I get an access violation error. I have tried to carefully revise the check file with no result. The error seems to be related to only fields named with the pattern "xxxcom" which all are string variables. -If I choose all fields before "xxxcom" the Codebook for those variables will be created without error. -If I only check "xxxcom" --> access violation -If I check variables before and after "xxxcom" --> access violation -If I check only variables after "xxxcom" -->no error
Error message: "Access violation at address 00403347 in module 'EpiData.exe' Read of address 393938FB"
Epidata 3.1 (270108) Windows XP Pro
Thanks for help
Jonas Malmstedt, MD Department of Vascular Surgery, N1:06 Karolinska University Hospital SE-171 76 Stockholm
PS I have also noticed another problem: smtimes EpiData Will not read *.not and *.rec files. I get an error telling me that the file name are not valid or the file is used. When I try to open the same file not NotePad - no problem! DS
EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
End of EpiData-list Digest, Vol 78, Issue 17