March 2012 - 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

Re: EpiData-list Digest, Vol 101, Issue 3
by epidata-list＠lists.umanitoba.ca 21 Mar '12

21 Mar '12

Kindly export it to stata. then launch your spss software and then select the stata file type and select your file and you will be able to have your data in spss. On Tue, Mar 20, 2012 at 5:00 PM, <epidata-list-request(a)lists.umanitoba.ca>wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)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(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)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: > > 1. Export to SPSS (epidata-list(a)lists.umanitoba.ca) > 2. Re: Export to SPSS (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: <epidata-list(a)lists.umanitoba.ca> > Cc: > Date: Mon, 19 Mar 2012 15:09:37 -0300 > Subject: [EpiData-list] Export to SPSS > Hello, > > I have just started using EpiData Manager v1.1.1 and didn’t find the > option to export data to SPSS (as it had in previous versions). > Coudl somedy help me to udnerstand how to do it? > > Thanks, > Paula > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Cc: > Date: Mon, 19 Mar 2012 17:27:31 -0400 > Subject: Re: [EpiData-list] Export to SPSS > SPSS will import Stata files. Have you tried exporting to Stata from > epidata manager? > Jamie > > On 2012-03-19, Paula wrote: > > I have just started using EpiData Manager v1.1.1 and didn’t find the > option to export data to SPSS (as it had in previous versions). > > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > -- ............ * MENSAH KOJO SEDZRO* Postal P.O.Box AS 387| Ashaiman -Tema | Ghana Skype: rasbesa web rasbesafari.blogspot.com House : +233-303-300789 Cell : +233-244-458788 ------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

Export to SPSS
by epidata-list＠lists.umanitoba.ca 19 Mar '12

19 Mar '12

Hello, I have just started using EpiData Manager v1.1.1 and didn’t find the option to export data to SPSS (as it had in previous versions). Coudl somedy help me to udnerstand how to do it? Thanks, Paula

1 1

A link problem in the web page
by epidata-list＠lists.umanitoba.ca 09 Mar '12

09 Mar '12

Hello Jens: There's a link problem that might be solved in http://www.epidata.dk/testing.php. The link is related with the Flyspray bug system. When someone click on the web browser to "Flyspray" go to http://flyspray.org/. The correct link should be http://www.epidata.info/flyspray/. Regards, -- Omar Bautista González - Colaborador en autogestión comunitaria desde República Dominicana

1 0

Version 1.1 of Manager and EntryClient release
by epidata-list＠lists.umanitoba.ca 09 Mar '12

09 Mar '12

Today we have released new versions of EpiData Manager and EpiData EntryClient. As with the first public release of Manager and EntryClient, this release has been packed in an installer which should work for Mac, Windows and Linux. The changes made are in short: * An issue with saving project files where pathnames/filename contained non-ASCII characters. * Fixed a number of bugs related to importing data. * Fixed a number of bugs related to saving colour settings in EntryClient. The updated versions are available from the download page on http://www.epidata.dk The release is part of the new principle, where a given new version first is placed as a beta version on the testing page and then moved to a public release on the download page if no problems show up. Therefore the v1.1 placed on the download page today is the same as the beta version placed for about a week on the testing page. On the testing page you will then find two versions: a. the next version to be released in general (such as v1.1) b. The current development (alpha) version, which you can consider a temporary "how far is the development currently" - users testing obviously must recognise that changes will occur during development. In all cases do not use the versions on the testing page for production work - only to influence development and test whether future releases have solved the problems identified. Kind regards, Torsten Bonde Christiansen, Jens M. Lauritsen. EpiData Association.

1 3