March 2015 - EpiData-list - University of Manitoba Mailing Lists

Jumps in Epidata Entry
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

Dear list, I have two questions regarding Jumps in EpiData Entry. 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of course this works: v8 RANGE 1 9 COMMENT LEGAL USE oplcat JUMPS 1 v10 2 v10 3 v10 4 v10 5 v10 6 v10 7 v10 END MUSTENTER END Is a shorter syntax possible and if so, how? 2) Is it possible to make a jump defination that depends on the value entered in a previous question? For example: After entering the value for variable v5 I want to jump to v8 if the answer on question v3=1. Kind Regards, Pieter van Groenestijn The Netherlands

2 3

fill fields from COMMENT LEGAL file
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

I'm studying the copydata example to learn how to extract several variables from a file identified in a COMMENT LEGAL statement. In A3.chk, the statement "TYPE COMMENT atransfer" appears. What is atransfer? I don't see where it has been defined as a variable and I don't find it as a system variable. Further, the program seems to be parsing the string in atransfer according to the position of punctuation. Where is the format of this string defined? Perhaps to be a bit more explicit: I have file with a list of CHWs: District, Village, CHW name and a survey conducted by the CHWs. As the data is entered for the survey, I'd like to present pick lists to facilitate entry. The data is quite strictly hierarchical: Villages occur within Districts, an CHWs live in villages. Thank you,

2 3

Updated (bug-fix) versions of EpiData EntryClient and Manager
by epidata-list＠lists.umanitoba.ca 06 Mar '15

06 Mar '15

The following bug-fixes has been made and new versions uploaded today. EpiData Manager Program Version: 2.0.1.27 EpiData Entry Client Program Version: 2.0.2.13 Both: * Fixed bug where File assocation under Windows did not work. Manager: * ProjectFrame splitter wasn't changed on Restore Default. * Prepare-double-entry new name was not added to recent. * Using Ctrl+N when creating Value labels would cause Access Violation on Windows. * Certain actions for relational dataforms in relation to flow from one to the other * Export: Simplifying naming for exported files. Notice that this includes as well cycle number (automatic version number) and dataform name. The latter excluded with only one dataform in a project. * Data Content validation: did not always work. Known existing bugs at this point: Id variable(-s) in Data Content Validation are not listed (Will be fixed and new update uploaded without further notice). EntryClient: Fixed bugs: * Jumping btw. dataforms according to relate information did not work properly * Sometimes incorrect record number was used to calculate Master-Detail key-field value. Hence displayed records data could be incorrect. * If no legal values are left in the value label list after the filter, a caption message will be given. * Added Restore Default to preferences. * MAC Os X only: moved "Preferences" and "About" menu item to standard Mac OS positions. Regards Jens Lauritsen EpiData Association

1 0