Double entry verification
Is it possible to use the Double Entry Verification tool on a relational database?
The related REC files are:
* Infant health diary.rec (the "Parent" file), and
* Infant health diary weekly record.rec (the "Child" file)
I created the double entry databases:
* Infant health diary_dbl.rec, and
* Infant health diary weekly record_dbl.rec
In "Infant health diary_dbl.chk" I edited the code for the relate command so that the double entry file is linked:
RELATE idchild "Infant health diary weekly record_dbl.rec"
When opening "Infant health diary_dbl.rec" for entry, I'm not given a warning stating that EpiData is in double entry verification mode. Is there something else I need to do to make this work? If not, I realise I can set up a second relational database and check for inconsistencies once all the data's been entered.
Cheers,
Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit
Murdoch Childrens Research Institute Royal Children's Hospital Flemington Road Parkville Victoria 3052 Australia
telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000 email: suzanna.vidmar@mcri.edu.au www.mcri.edu.au http://www.mcri.edu.au/
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Suzanna:
I believe it to require a unique identifier not just in the parent but also in the child file. After you have entered the data into the second pair of related file, you would then validate parent1-parent2 and child1-child2. However, I have done it only without the prospective "*_dbl" using the default of independent sequence of entering.
Hans
On 20:59, epidata-list@lists.umanitoba.ca wrote:
Is it possible to use the Double Entry Verification tool on a relational database?
Hi Hans,
Yes I have a unique identifier for both the "parent" and "child" files. They are childid for the "parent" file and a combination of childid and "week starting" for the "child" file. I used these unique identifiers for each file when selecting "match records by field". I entered data into both the "parent" and "child" _dlb.rec files, deliberately entering a discrepant value for one field in the "child" file and found the verification didn't take effect. If there's a step in the process I've missed, I'm not aware of what it is.
Thanks for responding to my previous email.
Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit
Murdoch Childrens Research Institute Royal Children's Hospital Flemington Road Parkville Victoria 3052 Australia
telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000 email: suzanna.vidmar@mcri.edu.au www.mcri.edu.au -----Original Message----- From: epidata-list-bounces@lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list@lists.umanitoba.ca Sent: Friday, 11 November 2011 6:06 AM To: epidata-list@lists.umanitoba.ca Subject: Re: [EpiData-list] Double entry verification
Suzanna:
I believe it to require a unique identifier not just in the parent but also in the child file. After you have entered the data into the second pair of related file, you would then validate parent1-parent2 and child1-child2. However, I have done it only without the prospective "*_dbl" using the default of independent sequence of entering.
Hans
On 20:59, epidata-list@lists.umanitoba.ca wrote:
Is it possible to use the Double Entry Verification tool on a relational database?
_______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
If you have any question, please contact MCRI IT Helpdesk for further assistance. ______________________________________________________________________
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Hi Suzanna,
I have tried to find a solution for the same issue in the past, but was unsuccessful even after consulting this list serve. I ended up using the other method of double entry (where the data is entered independently and compared afterwards) after many futile attempts.
Thanks, Sam
Sam Haddaway | Research Analyst, International Projects NORC at the University of Chicago 4350 East-West Highway, 8th Floor, Bethesda MD 20814 haddaway-sam@norc.org | office +1 (301) 634-9423
-----Original Message----- From: epidata-list-bounces@lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list@lists.umanitoba.ca Sent: Thursday, November 10, 2011 6:38 PM To: epidata-list@lists.umanitoba.ca Subject: RE: [EpiData-list] Double entry verification
Hi Hans,
Yes I have a unique identifier for both the "parent" and "child" files. They are childid for the "parent" file and a combination of childid and "week starting" for the "child" file. I used these unique identifiers for each file when selecting "match records by field". I entered data into both the "parent" and "child" _dlb.rec files, deliberately entering a discrepant value for one field in the "child" file and found the verification didn't take effect. If there's a step in the process I've missed, I'm not aware of what it is.
Thanks for responding to my previous email.
Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit
Murdoch Childrens Research Institute Royal Children's Hospital Flemington Road Parkville Victoria 3052 Australia
telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000 email: suzanna.vidmar@mcri.edu.au www.mcri.edu.au -----Original Message----- From: epidata-list-bounces@lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list@lists.umanitoba.ca Sent: Friday, 11 November 2011 6:06 AM To: epidata-list@lists.umanitoba.ca Subject: Re: [EpiData-list] Double entry verification
Suzanna:
I believe it to require a unique identifier not just in the parent but also in the child file. After you have entered the data into the second pair of related file, you would then validate parent1-parent2 and child1-child2. However, I have done it only without the prospective "*_dbl" using the default of independent sequence of entering.
Hans
On 20:59, epidata-list@lists.umanitoba.ca wrote:
Is it possible to use the Double Entry Verification tool on a relational database?
_______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
If you have any question, please contact MCRI IT Helpdesk for further assistance. ______________________________________________________________________
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Hi Sam, Thanks for letting me know of your experience. I thought I might have to use the less efficient method of comparing data that's been entered in 2 independent databases. Cheers,
Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit
Murdoch Childrens Research Institute Royal Children's Hospital Flemington Road Parkville Victoria 3052 Australia
telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000 email: suzanna.vidmar@mcri.edu.au www.mcri.edu.au
-----Original Message----- From: epidata-list-bounces@lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list@lists.umanitoba.ca Sent: Friday, 11 November 2011 10:46 AM To: epidata-list@lists.umanitoba.ca Subject: RE: [EpiData-list] Double entry verification
Hi Suzanna,
I have tried to find a solution for the same issue in the past, but was unsuccessful even after consulting this list serve. I ended up using the other method of double entry (where the data is entered independently and compared afterwards) after many futile attempts.
Thanks, Sam
Sam Haddaway | Research Analyst, International Projects NORC at the University of Chicago 4350 East-West Highway, 8th Floor, Bethesda MD 20814 haddaway-sam@norc.org | office +1 (301) 634-9423
-----Original Message----- From: epidata-list-bounces@lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list@lists.umanitoba.ca Sent: Thursday, November 10, 2011 6:38 PM To: epidata-list@lists.umanitoba.ca Subject: RE: [EpiData-list] Double entry verification
Hi Hans,
Yes I have a unique identifier for both the "parent" and "child" files. They are childid for the "parent" file and a combination of childid and "week starting" for the "child" file. I used these unique identifiers for each file when selecting "match records by field". I entered data into both the "parent" and "child" _dlb.rec files, deliberately entering a discrepant value for one field in the "child" file and found the verification didn't take effect. If there's a step in the process I've missed, I'm not aware of what it is.
Thanks for responding to my previous email.
Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit
Murdoch Childrens Research Institute Royal Children's Hospital Flemington Road Parkville Victoria 3052 Australia
telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000 email: suzanna.vidmar@mcri.edu.au www.mcri.edu.au -----Original Message----- From: epidata-list-bounces@lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list@lists.umanitoba.ca Sent: Friday, 11 November 2011 6:06 AM To: epidata-list@lists.umanitoba.ca Subject: Re: [EpiData-list] Double entry verification
Suzanna:
I believe it to require a unique identifier not just in the parent but also in the child file. After you have entered the data into the second pair of related file, you would then validate parent1-parent2 and child1-child2. However, I have done it only without the prospective "*_dbl" using the default of independent sequence of entering.
Hans
On 20:59, epidata-list@lists.umanitoba.ca wrote:
Is it possible to use the Double Entry Verification tool on a relational database?
_______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
If you have any question, please contact MCRI IT Helpdesk for further assistance. ______________________________________________________________________
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list _______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
If you have any question, please contact MCRI IT Helpdesk for further assistance. ______________________________________________________________________
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
participants (1)
-
epidata-list＠lists.umanitoba.ca