Double Entry and Autosearch: Danger!
After having stuggled with the problem that double entry did not work properly we found a solution to the following problem:
When we tried to double enter data using the "match records by fields" option, EpiData did only check the data of the first record entered. Starting with a second record we only accidentally noticed that EpiData did actually not check the data. We tried different things to overcome this problem but EpiData behaved erratic if we went back to an already entered record. This behavior is dangerous because you might think that EpiData checks your data during double entry (all the more if you encountered an entry error in the first record).
The solution: If the .REC file to enter data in double check mode uses a .CHK-file, don't use "AUTOSEARCH" (at least not for the field/variable that is used in the "match records by fields" option)! You may use "KEY UNIQUE", instead.
Current EpiData version: 3.1 (120306)
Dirk
************************************************* Dr. Dirk Enzmann Institute of Criminal Sciences Dept. of Criminology Edmund-Siemers-Allee 1 D-20146 Hamburg Germany
phone: +49-(0)40-42838.7498 (office) +49-(0)40-42838.4591 (Billon) fax: +49-(0)40-42838.2344 email: dirk.enzmann@uni-hamburg.de www: http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/En... *************************************************
participants (1)
-
epidata-list@lists.umanitoba.ca