- EpiData-list - University of Manitoba Mailing Lists

Suggestions for Analysis
by epidata-list＠lists.umanitoba.ca 01 Jan '12

01 Jan '12

Hello, Good year 2012 for Epidata members I have three suggestions about plans to improve Analysis : 1- Command "freq" : by default or with a new /"x", to sort ascending to even negative numbers or "0" number. With /sa ou others, sometimes, results of "freq" are mixed.. 2- Command "lifetable" : P50 (median) is sometimes false for little size of sample. 3- Command "scatter" : like with Epi-Info Dos, "/r", after scatter, was useful for the line of linear regression. Why not in Epidata Analysis ? Thank you for your work. Bernard Branger, Nantes, France (teacher of EPIDATA...)

1 0

Re: EpiData-list Digest, Vol 98, Issue 9
by epidata-list＠lists.umanitoba.ca 27 Dec '11

27 Dec '11

Hi, When I run the new Epidata manager and Epidata client, it failed with this error message: 'Windows cannot find "javaw". Make sure you typed the name correctly and then try again.' I am using 32 bit Windows 7 Home premium PC and it works well with old version of Epidata entry and Epidata analysis. Can anyone please help me with the installation? Thank you and happy New Year! Zaw On Mon, Dec 26, 2011 at 6: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. Epidata Client Setting Error (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 26 Dec 2011 06:32:32 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Epidata Client Setting Error > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: <3A9811F3D1FFEE41BE81EBA019B3640F39471A5E(a)HOEX3.aku.edu> > Content-Type: text/plain; charset="iso-8859-1" > > I have installed Epidata Manager & client. When I go to Epidata Client --> > Edit --> settings, when I click on Paths the epidata client Freeze and > cannot do anything. I am going close the program from task manager. I am > running Windows 7 professional, 32bit version. > > I think there is an error in the setup file. > > Thanks > > Rasool Bux > Sr. Data Management Coordinator & > Data Manager, > Hypertension Research Program, > Community Health Sciences Department, > Aga Khan University, Stadium Road, > P.O. Box 3500, Karachi 74800. > Pakistan. > > > > ________________________________ > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 98, Issue 9 > ******************************************* >

1 1

Epidata Client Setting Error
by epidata-list＠lists.umanitoba.ca 26 Dec '11

26 Dec '11

I have installed Epidata Manager & client. When I go to Epidata Client --> Edit --> settings, when I click on Paths the epidata client Freeze and cannot do anything. I am going close the program from task manager. I am running Windows 7 professional, 32bit version. I think there is an error in the setup file. Thanks Rasool Bux Sr. Data Management Coordinator & Data Manager, Hypertension Research Program, Community Health Sciences Department, Aga Khan University, Stadium Road, P.O. Box 3500, Karachi 74800. Pakistan. ________________________________ This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.

1 0

EpiData Manager installation jam
by epidata-list＠lists.umanitoba.ca 24 Dec '11

24 Dec '11

1 0

Sv: Re: [EpiData-list] First public relase of EpiData Manager and EpiData EntryClient
by epidata-list＠lists.umanitoba.ca 23 Dec '11

23 Dec '11

Thanks jamie. You are right. We should most likely change default tn e.g. Epidataxml. Please install into clean folder! Regards jens Lauritsen -oprindelig besk.- Emne: Re: [EpiData-list] First public relase of EpiData Manager and EpiData EntryClient Fra: epidata-list(a)lists.umanitoba.ca Dato: 23-12-2011 17:31 Congratulations to Jens and Torsten for this Christmas present (or for whatever occasion your faith celebrates). I would encourage everyone to install these into a new EpiData folder. Overwriting files, with the Mac version at least, led to some problems with the file I created. No problem after I did a clean installation. Jamie On 2011-12-22, Jens wrote: > We are quite aware of possible problems in relation to installation etc. since the new installation routines will not in reality be tested before you as users start to download and experience. > > Please do continue to report any problems found or difficulties experienced. > > There is definetely a need to develop further documentation, training materials etc. , but that will come. > > Following well deserved days off during the coming weeks more news will follow in the beginning of 2012. We wish all a happy new year and express hopes for continued support and fruitful discussions on this list. > > Kind regards on behalf of Torsten Christiansen and myself _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

First public relase of EpiData Manager and EpiData EntryClient
by epidata-list＠lists.umanitoba.ca 23 Dec '11

23 Dec '11

Dear all Following the development in recent years, choice of a new file format to replace chk+rec, a lot of testing and specification we have today placed the first version 1.0 of the new software on the public download page at Http://www.epidata.dk/download.php I will not make a lengthy statement at this point, since users who followed the development on this list will be rather well informed. Following installation you should have: 1 The software (manager and entryclient) 2 The sample file 3 Tutorials files (introduction pdf files) Notice: Just after January 1st 2012 we will release a new version of EpiData Analysis, which can read the data created with V1 of Manager and v1 EntryClient, so be a little patient on that aspect. The XML structure created by version 1 of the software will be guaranteed readable from now on. Any future change to the xml will be handled by the software. Whereas up to now we have modified the structure several times. The final format allows the XML to conform to export to the standard defined by DDI (Http://ddi-alliance.org). More about this later. EpiData Entry will remain available for download for quite a long time still. Much of the functionality has not yet been implemented in the new tools, so if you need some of these aspects you may well choose to continue to use the old EpiData Entry. We are quite aware of possible problems in relation to installation etc. since the new installation routines will not in reality be tested before you as users start to download and experience. Please do continue to report any problems found or difficulties experienced. There is definetely a need to develop further documentation, training materials etc. , but that will come. Following well deserved days off during the coming weeks more news will follow in the beginning of 2012. We wish all a happy new year and express hopes for continued support and fruitful discussions on this list. Kind regards on behalf of Torsten Christiansen and myself Jens Lauritsen EpiData Association Denmark

1 1

Sv: [EpiData-list] my os and stata version
by epidata-list＠lists.umanitoba.ca 21 Dec '11

21 Dec '11

please send copy of any file not working to info(a)epidata.dk! Send as zip or epz! Include version as pasted into the mail which you get from the mail menu. Regards jens lauritsen -oprindelig besk.- Emne: [EpiData-list] my os and stata version Fra: epidata-list(a)lists.umanitoba.ca Dato: 20-12-2011 23:49 Dear friendI am using windows 7 (en) and stata 11. I try to export my data in winxp (cn) but it failed too.Thanks! Regards, Richard zhou 2011.12.21 =============================================================================== > Date: Tue, 20 Dec 2011 12:00:34 -0600 > From: epidata-list-request(a)lists.umanitoba.ca > Subject: EpiData-list Digest, Vol 98, Issue 5 > To: epidata-list(a)lists.umanitoba.ca > > 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. Re: I can't normally export data to Stata > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 Dec 2011 10:19:54 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] I can't normally export data to Stata > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4EF0533A.3090609(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear Richard Zhou > > I'm sorry for that late reply. > > What Operating System are you using and what version of Stata do you use? > > Kind regards, > Torsten Bonde Christiansen. > EpiData Association. > > > On 2011-11-26 07:32, epidata-list(a)lists.umanitoba.ca wrote: > > > > Dear friends, > > I can't export my data file to Stata. In dta file, labels of variables are normally displayed in Chinese character, but contents of records all are irrecognizable. > > My settings about Export in EpiData Manager(v0.8.8): Stata version: Stata 8,9Stata file encoding: Chinese simple(CP936) > > If you need my data file, I will email it to you.Thanks! > > RegardsRichard Zhou > > 2011.11.26 > > =============================================================================== > > > > > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 98, Issue 5 > ******************************************* _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

my os and stata version
by epidata-list＠lists.umanitoba.ca 20 Dec '11

20 Dec '11

Dear friendI am using windows 7 (en) and stata 11. I try to export my data in winxp (cn) but it failed too.Thanks! Regards, Richard zhou 2011.12.21 =============================================================================== > Date: Tue, 20 Dec 2011 12:00:34 -0600 > From: epidata-list-request(a)lists.umanitoba.ca > Subject: EpiData-list Digest, Vol 98, Issue 5 > To: epidata-list(a)lists.umanitoba.ca > > 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. Re: I can't normally export data to Stata > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 Dec 2011 10:19:54 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] I can't normally export data to Stata > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4EF0533A.3090609(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear Richard Zhou > > I'm sorry for that late reply. > > What Operating System are you using and what version of Stata do you use? > > Kind regards, > Torsten Bonde Christiansen. > EpiData Association. > > > On 2011-11-26 07:32, epidata-list(a)lists.umanitoba.ca wrote: > > > > Dear friends, > > I can't export my data file to Stata. In dta file, labels of variables are normally displayed in Chinese character, but contents of records all are irrecognizable. > > My settings about Export in EpiData Manager(v0.8.8): Stata version: Stata 8,9Stata file encoding: Chinese simple(CP936) > > If you need my data file, I will email it to you.Thanks! > > RegardsRichard Zhou > > 2011.11.26 > > =============================================================================== > > > > > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 98, Issue 5 > *******************************************

1 0

I can't normally export data to Stata
by epidata-list＠lists.umanitoba.ca 20 Dec '11

20 Dec '11

Dear friends, I can't export my data file to Stata. In dta file, labels of variables are normally displayed in Chinese character, but contents of records all are irrecognizable. My settings about Export in EpiData Manager(v0.8.8): Stata version: Stata 8,9Stata file encoding: Chinese simple(CP936) If you need my data file, I will email it to you.Thanks! RegardsRichard Zhou 2011.11.26 ===============================================================================

1 1

Re: EpiData Analysis on Windows 7
by epidata-list＠lists.umanitoba.ca 08 Dec '11

08 Dec '11

Thank you all for the help you offered me... However, i have not managed to get around my problem. It seems that Jens Lauritsen did not understand my real issue and Hans explained that i did not exactly specify the error i received. Here is what exactly happens. Am using Windows 7 Professional (32 bit) and Epidata analysis 2.2.1.171. I read the rec files well, and the commands execute well .... but the problem comes when i open the Editor. After writing my code in the editor and try to run (whether Run selected or Run all), it brings this error "Cannot create file "C:\Users\Edson\AppData\Local\Temp\TMP9C60.Tmp". The process cannot access the file because it is being used by another process", When i try again, the error still comes but the TMP***.Tmp file keeps changing... However if i keep trying to run (whether Run selected or Run all), it final executes and brings my analysis.. When i tried to check online i came across this post (http://lists.umanitoba.ca/pipermail/epidata-list/2010q4/001618.html) which i highly believe had the same problem.. However in Jens Lauritsen's answer, he advises to correct the path (see the link above) in the edit setup ini file.. I dont see where to change that path in my ini file... below is how my ini file looks like; what exactly do i have to change! * EpiData Analysis default settings file * Edit the next lines to change size or font set echo=on * Viewer font and size: (plus editor and help windows) set browser font size =10 set graph font size =10 set window font size =10 set viewer font size =10 set editor font size =10 set language=English set viewer font name ="Verdana,Arial,Courier,System" * uncomment next two lines to display Chinese Characters *SET viewer font charset = "gb2312" *set viewer font name="Arial Unicode MS" ************************************************** * set options defined during installation: ************************************************** * To see other set: issue "set" command or look in help file (F1) ************************************************** set display variables=OFF set display databrowser=OFF set output open=ON * set options defined during installation: ************************************************** * Default folder defined as: cd C:\Program Files\Epidata\TestData set output folder="C:\Program Files\Epidata\TestData" set language=english set echo=ON Thank you all Edson Byamukama Kampala, Uganda On Tue, Dec 6, 2011 at 9: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. Re: EpiData Analysis on Windows 7 > (epidata-list(a)lists.umanitoba.ca) > 2. Label trouble (epidata-list(a)lists.umanitoba.ca) > 3. Re: EpiData Analysis on Windows 7 > (epidata-list(a)lists.umanitoba.ca) > 4. Re: EpiData Analysis on Windows 7 > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 05 Dec 2011 19:19:56 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] EpiData Analysis on Windows 7 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4EDD0B4C.2010000(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > On 2011-12-05 14:13, epidata-list(a)lists.umanitoba.ca wrote: > > Hello Colleagues, > > > > I keep getting an error message while executing the command in Epidata > > analysis. > To change this: > 1 > Copy your current epidatastat.ini to e.g. epidatastat.old.ini > then you have a copy to look into later. > > 2. > take the epidataanalysis.ini file into an editor, e.g. the built in > editor in analysis > > 3 > modify contents to: > * EpiData Analysis default settings file > set echo=off > set viewer font name ="Verdana,Arial,Courier,System" > > * Viewer font and size: (plus editor and help windows) > set browser font size =10 > set graph font size =10 > set window font size =10 > set window font size =10 > set editor font size =10 > set language=English > > Set echo=on > > 4 save again as epidatastat.ini > > To get paths etc. in place again look at the copy in epidatastat.old.ini > and experiment until it works for you. > > regards > Jens Lauritsen > EpiData Association > > > ------------------------------ > > Message: 2 > Date: Tue, 6 Dec 2011 12:03:05 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Label trouble > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: <CB03B4F9.2BD0%lfolkestad(a)health.sdu.dk> > Content-Type: text/plain; charset="Windows-1252" > > Hi List > I have no clue whats going on. But when i export to stata 11.2 my lables seems go. > I have a value called sex, with the lables 1=male, 0=female –9=unknown > When I export to stata i can only get either the male label or the female label but not both. > > Using: Mac OSX epidata version 0.8.8.0 > > Thank you. > > lars > > > ------------------------------ > > Message: 3 > Date: Tue, 06 Dec 2011 15:37:24 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] EpiData Analysis on Windows 7 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4EDE28A4.3010402(a)tbrieder.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Dear Edson: > > You do not specify the error EpiData Analysis gives, so it could be > anything. It often tells you pretty well what type of problem it > encounters. Thus, the answer to your specific question on the path is > easily answered, but it may or may not be the problem. > > In the top line you see Edit as the second icon from the right. On > clicking your get a drop down menu that lists among other things "Edit > Setup (EpiDataStat.ini)". Open it with single-click and it opens in > your text editor. If you write as the last execution stop a command: > > cd X:\folder\sub:folder > > Where "X" is the drive letter, and the rest is the location of your data > files, this is where EpiData Analysis will go to when you open it next > time (or execute now with F8 being on the line). > > Best regards, > > Hans > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > > Hello Colleagues, > > > > I keep getting an error message while executing the command in Epidata > > analysis. Searching through on Google, i got a thread of such request > > by another user on this link > > (http://lists.umanitoba.ca/pipermail/epidata-list/2010q4/001618.html). > > His problem seem to be the same one i have, but the solution is not > > clear.... Can someone please help me! I badly need to write my code in > > the editor and run it latter... > > > > I tried to change the directory as suggested by Jens Lauritsen in the > > ini file but i dont see where to change. > > > > I need help, i believe that some of you are using windows 7 too. Help > > me if you have got the work around of this use. > > > > Edson Byamukama > > Kampala, Uganda > > > > > ------------------------------ > > Message: 4 > Date: Tue, 6 Dec 2011 17:38:18 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] EpiData Analysis on Windows 7 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <CAKVQvhHBmKqM2e5xQy4K9xMW-U2NOaRt3Fx8ovRHugHMtqgHeg(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > > I also discovered that in Windows 7 strange things are happening: > > I have in the ini file this: > > * Default folder defined as: > cd C:\Program Files\EpiData\TestData > > However if I write > logopen "output.txt" /close > the program stores the text > in the folder: > C:\Users\Myname\Appdata\Local\VirtualStore\Program Files\Epidata\Testdata > > which is a conflict. > > Also if I put > * Default folder defined as: > cd D:\Data > then I have the same result > the program stores the text > in the folder: > C:\Users\Myname\Appdata\Local\VirtualStore\Program Files\Epidata\Testdata > I will try to manage - maybe it's my local problem. > > Best regards > Vladimir > > > > Best regards > 2011/12/6 <epidata-list(a)lists.umanitoba.ca> > > > Dear Edson: > > > > You do not specify the error EpiData Analysis gives, so it could be > > anything. It often tells you pretty well what type of problem it > > encounters. Thus, the answer to your specific question on the path is > > easily answered, but it may or may not be the problem. > > > > In the top line you see Edit as the second icon from the right. On > > clicking your get a drop down menu that lists among other things "Edit > > Setup (EpiDataStat.ini)". Open it with single-click and it opens in your > > text editor. If you write as the last execution stop a command: > > > > cd X:\folder\sub:folder > > > > Where "X" is the drive letter, and the rest is the location of your data > > files, this is where EpiData Analysis will go to when you open it next time > > (or execute now with F8 being on the line). > > > > Best regards, > > > > Hans > > > > > > > > On 20:59, epidata-list(a)lists.umanitoba.**ca<epidata-list(a)lists.umanitoba.ca>wrote: > > > >> Hello Colleagues, > >> > >> I keep getting an error message while executing the command in Epidata > >> analysis. Searching through on Google, i got a thread of such request > >> by another user on this link > >> (http://lists.umanitoba.ca/**pipermail/epidata-list/2010q4/**001618.html<http://lists.umanitoba.ca/pipermail/epidata-list/2010q4/001618.html> > >> ). > >> His problem seem to be the same one i have, but the solution is not > >> clear.... Can someone please help me! I badly need to write my code in > >> the editor and run it latter... > >> > >> I tried to change the directory as suggested by Jens Lauritsen in the > >> ini file but i dont see where to change. > >> > >> I need help, i believe that some of you are using windows 7 too. Help > >> me if you have got the work around of this use. > >> > >> Edson Byamukama > >> Kampala, Uganda > >> > > > > > > ______________________________**_________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.**ca <EpiData-list(a)lists.umanitoba.ca> > > http://lists.umanitoba.ca/**mailman/listinfo/epidata-list<http://lists.umanitoba.ca/mailman/listinfo/epidata-list> > > > > > > -- > Vladimir Prikazsky > tel: +46 858 601 636 > fax: +46 858 601 001 > mobil: +46 762 624 286 > _____________________________ > Motto: :-) > Kam chodi slunce, nechodi doktor! > An apple a day keeps the doctor away! > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 98, Issue 2 > *******************************************

1 2

EpiData Analysis on Windows 7
by epidata-list＠lists.umanitoba.ca 06 Dec '11

06 Dec '11

Hello Colleagues, I keep getting an error message while executing the command in Epidata analysis. Searching through on Google, i got a thread of such request by another user on this link (http://lists.umanitoba.ca/pipermail/epidata-list/2010q4/001618.html). His problem seem to be the same one i have, but the solution is not clear.... Can someone please help me! I badly need to write my code in the editor and run it latter... I tried to change the directory as suggested by Jens Lauritsen in the ini file but i dont see where to change. I need help, i believe that some of you are using windows 7 too. Help me if you have got the work around of this use. Edson Byamukama Kampala, Uganda

1 4

Label trouble
by epidata-list＠lists.umanitoba.ca 06 Dec '11

06 Dec '11

Hi List I have no clue whats going on. But when i export to stata 11.2 my lables seems go. I have a value called sex, with the lables 1=male, 0=female –9=unknown When I export to stata i can only get either the male label or the female label but not both. Using: Mac OSX epidata version 0.8.8.0 Thank you. lars

1 0

jumping variables
by epidata-list＠lists.umanitoba.ca 17 Nov '11

17 Nov '11

Dear List When i ad space, and than ad variables. They tend to jump around when i try to move them. Seems like there is no pattern to the jumping. Im using Program version 0.8.6.1 EpiData Manager on a Mac OSX system. Any tips or fixes? lars

1 4

Locking of a dataset in EpiData Entry
by epidata-list＠lists.umanitoba.ca 16 Nov '11

16 Nov '11

Dear Epi-data I have looked through all possible help-files for Epi-Data entry, but have not been able to find an answer. I am therefore writing now. Is it possible to lock the dataset in EpiData Entry, when entry has been finalized and the dataset is final? And will epi-data log any changes made - if possible with eg a password - if any are made after the data is locked? Thank you in advance for your help. Kind Regards Anna Aabakke M.D. and Ph.D.-student Dep. Gynaecology and Obstetrics University of Copenhagen, Holbæk Hospital

1 1

How to analyse for outcomes at specific periods during follow ups
by epidata-list＠lists.umanitoba.ca 15 Nov '11

15 Nov '11

Dear ALL I have a relational (Epidata entry) data base which I have data for over one year follow up of patients. I would like to analyse in Epidata analysis and check the Blood pressure, blood sugar readings......at every six months follow up for each patient since they were enrolled. How do I get to select six month, twelve month....visits for each patient form their date of enrollment. ( in my database I have var: entrydate at registration and visitdate on each visit) Thank you Walter

1 1

Double entry verification
by epidata-list＠lists.umanitoba.ca 10 Nov '11

10 Nov '11

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(a)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 ______________________________________________________________________

1 4

RE : EpiData-list Digest, Vol 97, Issue 7
by epidata-list＠lists.umanitoba.ca 09 Nov '11

09 Nov '11

Hi, A response to Réjean, I did not experience your "out of memory" problem, but I had the "Unable to open the file. An unknown error occured" one several times (because of ranges in DMY date fields, see my message on the list). In this case, you can edit the epx file in wordpad or notpad, and delete the wrong lines, supposing you can identify then (possibly lines concerning value labels in your case). Another solution is to backup files often, so that you don't have to start all over again each time. Sorry, this won't give you the solution of your problem, but maybe will help you keep your patience while testing the Manager! Confraternellement, Pascal Thibon, MD, Epidemiologist CHU Caen France

1 1

EpiData Manager bugs - Request for assistance - Follow-up.
by epidata-list＠lists.umanitoba.ca 08 Nov '11

08 Nov '11

Ma 08 nov 2011 To Torsten Bonde Christiansen: Dear colleague, As asked, the EpiData Manager version that was downloaded from the test web site on october 26 2011 is: Program Version: 0.8.8 r371 Core version: 0.8 r475 FPC Version: 2.4.4 Platform: i386-Win32 No installation was needed; it was simply copied on the desktop (bureau in french) by one of our IT peoples; should it be installed in a specific répertoire (folder)? It's a simple exe file that run after cliquing on the EpiData Manager icon. If of any use for you, the portable PC I use is a lenovo T400 running on Windows 7 and 64 bits (bibites in french?). If I can pass over those major bugs, especially this "out of memory" one, I could test this software and began my learning curve at the bottom. This "out of memory" bug remember me the old "runtime error" or "stack overflow" of the old Epi Info DOS; however, in the Win environment, it seem to be a fatal problem for the files... One of the things I also need to know is how to create something similar to the chek command COMMENTLEGAL (with codes and associated values). Many thanks for your support. Best regards, Réjean Réjean Dion, M.D. Médecin-conseil en santé publique (maladies infectieuses) Institut national de santé publique du Québec (INSPQ) / Laboratoire de santé publique du Québec (LSPQ) 20045, chemin Sainte-Marie, Sainte-Anne-de-Bellevue (Québec) Canada H9X 3R5 Tél.: (514) 457-2070 poste 325 Fax.: (514) 457-6346 Courriel / Lotus Notes: rejean.dion(a)inspq.qc.ca

1 1

encryption fields in EpiData
by epidata-list＠lists.umanitoba.ca 08 Nov '11

08 Nov '11

Greetings, I am implementing an application that has to import .REC files, including encryption fields. EpiData documentation says the encryption used is AES/Rijndael, and nothing more. That information is not sufficient, unfortunately. Therefore I would like to ask: (1) What is the keylength used? (2) What is the cipher mode of operation used? (3) If the cipher mode is ECB or CBC, what kind of padding is used? (4) Is an initialization vector or salt used? (I guess none, since EpiData creates the same encrypted text in the first line of the .REC file, whenever the same password is used). Probably these questions should be answered by a technical person, i.e. EpiData developer. Thank you in advance, Theodore Lytras

1 2

Epidata Manager tests
by epidata-list＠lists.umanitoba.ca 08 Nov '11

08 Nov '11

Bonjour à tous ! I have tested ED manager and entry client. It seems to me that this new version works fine and already looks very "professional". I only found 2 bugs (I hope this is the right place to report them) : 1/ ranges in DMY date fields : programming ranges for YMD date fields works fine, but for DMY date fields, the project will refuse to open in ED Entry Client. I only managed to open it after editing the xml file and erasing the lines containing the date range specification ; 2/ crash when trying to edit value labels of boolean fields Althought it's quite illogical, I tried to edit value labels for a boolean field. This caused an immediate crash 4 questions : 1/ I would like to program conditionnal jumps (in field X : jump to fiels Y if field Z=1). In previous versions, this was possible with AFTER ENTRY in chk files. 2/ It would be very useful to test a data structure directly in ED manager (CTRL-T in previous versions) 3/ In ED Entry client: at the end of a record, if you answer "NO" to "Save Y/N", all of the fields are cleared 4/ I work with sas for advanced analysis. Who do I export from ED ? Thanks again for this great software! Pascal THIBON, MD, Epidemiologist CHU Caen France

1 0

Missing example and pdf in linux packages
by epidata-list＠lists.umanitoba.ca 08 Nov '11

08 Nov '11

I just want to inform, if you downloading the Linux packages from the testing area the example file and pdf are only symbolic links and not the documents itself. By the way it seems that the Linux versions are not running under Ubuntu 11.10 due to changes in GTK libraries. I will try to use it on another system later on.

1 0

EpiData Manager bugs - Request for assistance.
by epidata-list＠lists.umanitoba.ca 08 Nov '11

08 Nov '11

Lu 07 nov 2011 This message was sent to epidata-list(a)lists.umanitoba.ca two days ago, but only the tittle was published in the Digest; for this reason, I'm sending it again, with the added mention "Request for assistance". Dear colleagues, I'm exploring EpiData Manager for creating a very simple data entry form. Here is the major bugs I encountered: - I can't save the epx file outside of the "bureau". - Each time I try to use the field value label editor (adding a new value) the system crash with an error message "out of memory"; this jump me out of Manager and when I try to open the existing epx file I can't and the following error message is displayed: "Unable to open the file. An unknown error occured". The file can't be recovered (I recreated a new epx file, but I lost all of them [including my patience after 10 trials]). - Displacing a field on the screen is somewhat erratic; the question beside the field seems to go farther away each time I try to correct the alignment. - Creating a new section box is problematic; I keep creating boxes over and over again and it's impossible to go back or to delete the empty boxes. Giving those bugs, I'm unable to create a project. Is there a manual explaining a little bit more how to use this new interface? The short orientation document is too general to be really usefull for a novice. The concept is interesting and I would like to test it, but I fly in the dark or in the mist actually. Cordialement, Réjean Réjean Dion, M.D. Médecin-conseil en santé publique (maladies infectieuses) Institut national de santé publique du Québec (INSPQ) / Laboratoire de santé publique du Québec (LSPQ) 20045, chemin Sainte-Marie, Sainte-Anne-de-Bellevue (Québec) Canada H9X 3R5 Tél.: (514) 457-2070 poste 325 Fax.: (514) 457-6346 Courriel / Lotus Notes: rejean.dion(a)inspq.qc.ca

1 1

EpiData Manager bugs.
by epidata-list＠lists.umanitoba.ca 05 Nov '11

05 Nov '11

1 0

Re: EpiData-list Digest, Vol 97, Issue 3
by epidata-list＠lists.umanitoba.ca 05 Nov '11

05 Nov '11

Dear Christine Would you please share me your experience of using epidata for outbreak investigation. Thanks Mohammed On Thu, Nov 3, 2011 at 6: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. How to save an epx file? (epidata-list(a)lists.umanitoba.ca) > 2. Re: How to save an epx file? (epidata-list(a)lists.umanitoba.ca) > 3. Re: EpiData and MPH Training (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 2 Nov 2011 13:24:34 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to save an epx file? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > OF1D1F6BD8.0C8A41FB-ON8525793C.005EA698-8525793C.005FA215(a)isn.rtss.qc.ca> > > Content-Type: text/plain; charset="ISO-8859-1" > > Me 02 nov 2011 > > Hello all/Bonjour à tous, > > I'm testing latest EpiData Manager test version but my start is a bit > problematic, because I can't save the epx file of my new project. > > When I cliq on "Save project" or "Save project as", the following error > message with a big "x" surrounded by a red circle is shown: > Unable to create file "C:\folder\subfolder\filename.epx". > > I work in Windows 7 (for Windows, of course). Can anybody has a solution > to this very simple problem? > > Best regards/Cordialement, > > Réjean > > Réjean Dion, M.D. > Médecin-conseil en santé publique (maladies infectieuses) > Institut national de santé publique du Québec (INSPQ) / > Laboratoire de santé publique du Québec (LSPQ) > 20045, chemin Sainte-Marie, > Sainte-Anne-de-Bellevue (Québec) > Canada H9X 3R5 > Tél.: (514) 457-2070 poste 325 > Fax.: (514) 457-6346 > Courriel / Lotus Notes: rejean.dion(a)inspq.qc.ca > > > ------------------------------ > > Message: 2 > Date: Wed, 02 Nov 2011 19:39:39 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] How to save an epx file? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4EB18E6B.9000504(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Good to see that you are testing Rejean > I would assume that the explanation could be, that the > > Unable to create file "C:\folder\subfolder\filename.epx". > > is due to problems with the folder names. > Are you sure you that folder structure and also that you have write > access to it if it exists. > > Before you actually do the save, try to move to a folder, where you have > proper rights, could be "documents" or desktop. > > Regards > Jens Lauritsen > EpiData Association > > On 2011-11-02 18:24, epidata-list(a)lists.umanitoba.ca wrote: > > When I cliq on "Save project" or "Save project as", the following error > > message with a big "x" surrounded by a red circle is shown: > > Unable to create file "C:\folder\subfolder\filename.epx". > > I work in Windows 7 (for Windows, of course). Can anybody has a solution > > to this very simple problem? > > > > > > ------------------------------ > > Message: 3 > Date: Thu, 03 Nov 2011 08:55:21 +1300 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] EpiData and MPH Training > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <4EB256FA020000CA0000C02B(a)gw.hvh.co.nz> > Content-Type: text/plain; charset="US-ASCII" > > Hi Eric > > it was good to see your post. I teach some short courses using Epidata to > investigate outbreaks as part of an epi skills development programme > offered by ESR (the New Zealand equivalent of CDC). These are short courses > for public health field staff. I've also used Epidata as part of a mainly > online MPH programme (although the course itself was face to face) in > biosecurity for Drs and Vets from South Asia - again the focus has been > outbreak detection so far. However we are looking at using Epidata as part > of some ongoing project work e.g. knowledge attitude prevalence surveys. If > you would like to talk some more about this maybe we could have a > discusssion off line. > > best wishes > > Christine > > > > Christine Roseveare| Senior Public Health Analyst, Systems Quality and > Intelligence | Clinical Leadership and Intelligence Group | > T 04 570 9194 | M 027 495 9671 | F 04 570 9211 | Regional Public Health | > Private Bag 31-907 Lower Hutt 5040 | www.rph.org.nz > > My hours of work are 9 - 5.30 Monday to Thursday > > > >>> <epidata-list(a)lists.umanitoba.ca> 1/11/2011 9:25 a.m. >>> > Greetings from Burlington, > > > > I am a new member of epidata-list, and I am keen to receive advice about > incorporating training in EpiData Entry and Analyst in the MPH Program at > the Dalla Lana School of Public Health at the Univ. of Toronto. I teach the > course on Public Health Surveillance in the second term. This will be the > second year that I oversee this course, and I would like to find some > better > way to integrate the lectures and the exercises, perhaps through EpiData > training. I suspect that EpiData would be ideal for introducing the > principles and basic skills required for CD outbreak detection and > management. But I think it might also be useful for cluster investigation, > socio-demographic profiles (e.g., recent immigrants in a PHU area) and > monitoring behavioural RF over time. > > > > Keen to hook up with epidata-list members who have some experience offering > training in EpiData at the MPH level. Keen to find useful teaching > exercises > that are shareable, too. > > > > Most grateful for any advice! > > > > Sincerely, > > > > Eric J. Holowaty, > > Professor, Div. of Epidemiology, > > Dalla Lana School of Public Health, > > Univ. of Toronto. > > > > -- > The information contained in this email and > any attachments is confidential and may be > legally privileged. If you have received this > message in error, please notify the sender > immediately and remove all copies of the message, > including any attachments. Any views or > opinions expressed in this email (unless > otherwise stated) may not represent those of > Hutt Valley DHB. > Thank you. > ** Disclaimer added by HVDHB ** > > > > ______________________________________________________________________________ > > This email has been scrubbed for your protection by SMX. > For more information visit http://smxemail.com > > ______________________________________________________________________________ > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 97, Issue 3 > ******************************************* >

1 2

Re: [EpiData-list] EpiData and MPH Training
by epidata-list＠lists.umanitoba.ca 02 Nov '11

02 Nov '11

Hi Eric it was good to see your post. I teach some short courses using Epidata to investigate outbreaks as part of an epi skills development programme offered by ESR (the New Zealand equivalent of CDC). These are short courses for public health field staff. I've also used Epidata as part of a mainly online MPH programme (although the course itself was face to face) in biosecurity for Drs and Vets from South Asia - again the focus has been outbreak detection so far. However we are looking at using Epidata as part of some ongoing project work e.g. knowledge attitude prevalence surveys. If you would like to talk some more about this maybe we could have a discusssion off line. best wishes Christine Christine Roseveare| Senior Public Health Analyst, Systems Quality and Intelligence | Clinical Leadership and Intelligence Group | T 04 570 9194 | M 027 495 9671 | F 04 570 9211 | Regional Public Health | Private Bag 31-907 Lower Hutt 5040 | www.rph.org.nz My hours of work are 9 - 5.30 Monday to Thursday >>> <epidata-list(a)lists.umanitoba.ca> 1/11/2011 9:25 a.m. >>> Greetings from Burlington, I am a new member of epidata-list, and I am keen to receive advice about incorporating training in EpiData Entry and Analyst in the MPH Program at the Dalla Lana School of Public Health at the Univ. of Toronto. I teach the course on Public Health Surveillance in the second term. This will be the second year that I oversee this course, and I would like to find some better way to integrate the lectures and the exercises, perhaps through EpiData training. I suspect that EpiData would be ideal for introducing the principles and basic skills required for CD outbreak detection and management. But I think it might also be useful for cluster investigation, socio-demographic profiles (e.g., recent immigrants in a PHU area) and monitoring behavioural RF over time. Keen to hook up with epidata-list members who have some experience offering training in EpiData at the MPH level. Keen to find useful teaching exercises that are shareable, too. Most grateful for any advice! Sincerely, Eric J. Holowaty, Professor, Div. of Epidemiology, Dalla Lana School of Public Health, Univ. of Toronto. -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 0

How to save an epx file?
by epidata-list＠lists.umanitoba.ca 02 Nov '11

02 Nov '11

Me 02 nov 2011 Hello all/Bonjour à tous, I'm testing latest EpiData Manager test version but my start is a bit problematic, because I can't save the epx file of my new project. When I cliq on "Save project" or "Save project as", the following error message with a big "x" surrounded by a red circle is shown: Unable to create file "C:\folder\subfolder\filename.epx". I work in Windows 7 (for Windows, of course). Can anybody has a solution to this very simple problem? Best regards/Cordialement, Réjean Réjean Dion, M.D. Médecin-conseil en santé publique (maladies infectieuses) Institut national de santé publique du Québec (INSPQ) / Laboratoire de santé publique du Québec (LSPQ) 20045, chemin Sainte-Marie, Sainte-Anne-de-Bellevue (Québec) Canada H9X 3R5 Tél.: (514) 457-2070 poste 325 Fax.: (514) 457-6346 Courriel / Lotus Notes: rejean.dion(a)inspq.qc.ca

1 1

epidata as relational database for disaster electronic medical record
by epidata-list＠lists.umanitoba.ca 01 Nov '11

01 Nov '11

In 2006, our region suffered massive flooding. We even had to evacuate one hospital to another. We opened an evacuation shelter in the gymnasium at the local university. One section was basically a field hospital for the medically needy evacuees. Our patient record-keeping at that time was a little week. We recently suffered another massive flood, several-fold worse than 2006. 30,000 people, 15% of our county's population,were evacuated. We had 1800 people in an evacuation shelter in that same gymnasium. About 100 were "medical needs" evacuees--oxygen, BiPAP, skilled nursing needs, etc. Our record keeping was better this time, but still left something to be desired. I'm brainstorming ideas, both paper and electronic. Does anyone have any experience using Epidata as a relational database, so as to serve as a simple lightweight electronic medical record during a disaster? Thanks. --Chris Ryan, MD Clinical Associate Professor of Family Medicine SUNY Upstate Medical University, Binghamton, NY and Medical Director, Broome County Health Department

1 7

EpiData and MPH Training
by epidata-list＠lists.umanitoba.ca 01 Nov '11

01 Nov '11

Greetings from Burlington, I am a new member of epidata-list, and I am keen to receive advice about incorporating training in EpiData Entry and Analyst in the MPH Program at the Dalla Lana School of Public Health at the Univ. of Toronto. I teach the course on Public Health Surveillance in the second term. This will be the second year that I oversee this course, and I would like to find some better way to integrate the lectures and the exercises, perhaps through EpiData training. I suspect that EpiData would be ideal for introducing the principles and basic skills required for CD outbreak detection and management. But I think it might also be useful for cluster investigation, socio-demographic profiles (e.g., recent immigrants in a PHU area) and monitoring behavioural RF over time. Keen to hook up with epidata-list members who have some experience offering training in EpiData at the MPH level. Keen to find useful teaching exercises that are shareable, too. Most grateful for any advice! Sincerely, Eric J. Holowaty, Professor, Div. of Epidemiology, Dalla Lana School of Public Health, Univ. of Toronto.

1 2

EpiData 3.1. blank line output
by epidata-list＠lists.umanitoba.ca 25 Oct '11

25 Oct '11

Dear members of the EpiData-Team, I am writing to you with the following question/concern: I am using the programme EpiData 3.1. to insert data from a questionnaire, where in the end every line contains the data from one questionnaire. In a newly established table the first line is without entry while the following lines contain data, though I thought that this is impossible in EpiData - is there any explanation how this blank line could have happened? Is it possible to save a line without having inserted any data in the original questionnaire form? Thanks a lot to everybody, greetings from Germany, Nina-Claire Himpe

1 3

importing data to epidata from excel sheet
by epidata-list＠lists.umanitoba.ca 23 Oct '11

23 Oct '11

Dear friend Hope all is well. Would you please remind me of how to import data from excel sheet into epidata. Thanks alot for your help and time Mohd

1 4

Backup command truncation problem
by epidata-list＠lists.umanitoba.ca 17 Oct '11

17 Oct '11

Hello Everyone, I have encountered backup command truncation isuue. I am using the following commands for backup, AFTER FILE BACKUP C:\research\CD\Epidata\backup\epi ENCRYPT filenameXXX PASSCODEXXX [TODAY] END This code works perfectly when I am using it. Once I close the program and reopen, it is truncated to, AFTER FILE BACKUP C:\research\CD\Epidata\backup\epi END I will appriciate your thoughts and help on this issue. Thank you. Bijay Adhikari, PhD CD Epidemiologist

1 1

release candidate for manager and entryclient - please test and comment
by epidata-list＠lists.umanitoba.ca 15 Oct '11

15 Oct '11

We have now uploaded what is intended as the release candidate for version 1 of EpiData Manager and EntryClient. Users are encouraged to: a. test the software b. comment on this list whether you find the products ready for release with the currently implemented functionality. Remaining issues before actual release are: a. Completing technical documentation on the wiki system at www.epidata.org/dokuwiki/ including a schema file for the xml b. Updating and finalising introduction documents and guides c. Updating wiki system with examples d. Fixing any bugs reported Following release of version 1 development continues and will focus on: Translation of interface, several dataforms in one project, key (unique), validation of duplicate files, GCP etc. In the current test release the following has been changed: Core changes: (mostly used in manager) Enhanced export to Stata (Notes, time fields, encoding of strings, string fields) Notes on Field/Dataset during import. Entry: Saves recent file after load/save of file. Manager: Open project automatically added to reportlist Settings for export to stata Bugs fixed: deleting section did not cleanup components correctly shortcuts (wrong form execution, paste as bug, ....) extend space function adds one "page down" Regards Torsten Christiansen and Jens Lauritsen EpiData Association

1 0

Re: How to jump a line in a Warning box?
by epidata-list＠lists.umanitoba.ca 11 Oct '11

11 Oct '11

Hi Zaw, I'm feeling like stupid for not having seen this....Many thanks for your help. Regards, Sophie. --Pièce jointe du message transmise-- From: epidata-list(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Date: Tue, 11 Oct 2011 07:37:28 +0100 Subject: [EpiData-list] Re: How to jump a line in a Warning box? Hi, Sophie, It should be a backslash "\n". Your syntax should be as below: BEFORE ENTRY HELP "Mesurez le périmètre à mi-distance*\n* entre le rebord postérieur de l’acromion et le sommet de l’olécrane" END Best wishes, Zaw > > Message: 2 > Date: Sun, 9 Oct 2011 19:37:49 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to jump a line in a Warning box? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <BAY155-W509A6867E535C4760997897FC0(a)phx.gbl> > Content-Type: text/plain; charset="Windows-1252" > > > Hi everybody, > I would like to have a two-line warning box. I saw that I need to add "/n" > but this does not work.Here my syntax: > armcirc > MUSTENTER > BEFORE ENTRY > HELP "Mesurez le périmètre à mi-distance/n entre le rebord postérieur de > l’acromion et le sommet de l’olécrane" > END > END > I would appreciate if someone can help me. > Sophie. > > >

1 0

Re: How to jump a line in a Warning box?
by epidata-list＠lists.umanitoba.ca 11 Oct '11

11 Oct '11

Hi, Sophie, It should be a backslash "\n". Your syntax should be as below: BEFORE ENTRY HELP "Mesurez le périmètre à mi-distance*\n* entre le rebord postérieur de l’acromion et le sommet de l’olécrane" END Best wishes, Zaw On Mon, Oct 10, 2011 at 6: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. How to calculate age (epidata-list(a)lists.umanitoba.ca) > 2. How to jump a line in a Warning box? > (epidata-list(a)lists.umanitoba.ca) > 3. Chi square for tren (epidata-list(a)lists.umanitoba.ca) > 4. Re: Chi square for tren (epidata-list(a)lists.umanitoba.ca) > 5. How to calculate chi square for trend > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 9 Oct 2011 19:08:30 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to calculate age > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <BAY155-W179F539EAF514289D1437E97FC0(a)phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > > Dear Hans, > Thank you for your reply but I also saw this mistakes. > Many thanks. > > --Pièce jointe du message transmise-- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Sat, 8 Oct 2011 19:24:19 +0200Envoyer > Subject: Re: [EpiData-list] How to calculate age > > Dear Sophie: > > You cannot have "BEFORE ENTRY" in a "NOENTER" field because no command > in that field can ever be executed. > > Better choose an "AFTER ENTRY" block in the field in which you added the > last component that is needed to calculate the age, i.e., in the field DoB. > > To this end you may try: > > Your QES file: > age ##.# > recdate <Today-dmy> > dob <dd/mm/yyyy> > other _ > > Your CHK file: > age > NOENTER > END > > dob > MUSTENTER > AFTER ENTRY > age=(recdate-dob)/365.25 > END > END > > Regards, > > Hans > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > > Hello everybody, > > I am trying to write a syntax in .chk file to automatically calculate age > during the data entry from the today's date and the DoB.The syntax is : > > " ddn > > MUSTENTER > > END > > > > > > age > > NOENTER > > BEFORE ENTRY > > let age=ound(int((date-ddn)/(365.25)))) > > END > > END" > > The variables are coded in the .qes file as follows: > > {DATE} automatique<Today-dmy>{DDN} DATE DE NAISSANCE (DATE OF > BIRTH)<dd/mm/yyyy>{AGE} automatique > ### > > What's wrong with my syntax? > > Sincerely hope you can help me. > > Regards, > > Sophie PilleronPhD student. > > > > -- > Hans L Rieder, MD, MPH > Jetzikofenstr 12 > 3038 Kirchlindach > Switzerland > > Tel: +41 31 829 4577 > Mob: +41 79 321 9122 > Web: http://www.tbrieder.org > > > > > > --Pièce jointe du message transmise-- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Sat, 8 Oct 2011 20:04:14 +0200 > Subject: [EpiData-list] How to calculate age > > > > Many thanks Jamie. It works now. I will never have found out my mistake > without your support. Thanks again. > Sophie. > > > --Pièce jointe du message transmise-- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Sat, 8 Oct 2011 16:41:29 +0200 > Subject: [EpiData-list] How to calculate age > > > Hello everybody, > I am trying to write a syntax in .chk file to automatically calculate age > during the data entry from the today's date and the DoB.The syntax is : > " ddn > MUSTENTER > END > > > age > NOENTER > BEFORE ENTRY > let age=(round(int((date-ddn)/(365.25)))) > END > END" > The variables are coded in the .qes file as follows: > {DATE} automatique > <Today-dmy>{DDN} DATE DE NAISSANCE (DATE OF BIRTH) > <dd/mm/yyyy>{AGE} automatique > ### > What's wrong with my syntax? > Sincerely hope you can help me. > Regards, > Sophie PilleronPhD student. > > > > --Pièce jointe du message transmise-- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Sat, 8 Oct 2011 12:42:47 -0400 > Subject: Re: [EpiData-list] How to calculate age > > You cannot have a field named DATE because that is the name of a function. > EpiData doesn't complain when you do this, but you cannot use any function > names as field names. > > Jamie > > On 2011-10-08, at 10:41 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > let age=(round(int((date-ddn)/(365.25)))) > > > > > > ------------------------------ > > Message: 2 > Date: Sun, 9 Oct 2011 19:37:49 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to jump a line in a Warning box? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <BAY155-W509A6867E535C4760997897FC0(a)phx.gbl> > Content-Type: text/plain; charset="Windows-1252" > > > Hi everybody, > I would like to have a two-line warning box. I saw that I need to add "/n" > but this does not work.Here my syntax: > armcirc > MUSTENTER > BEFORE ENTRY > HELP "Mesurez le périmètre à mi-distance/n entre le rebord postérieur de > l’acromion et le sommet de l’olécrane" > END > END > I would appreciate if someone can help me. > Sophie. > > > ------------------------------ > > Message: 3 > Date: Sun, 9 Oct 2011 21:54:56 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Chi square for tren > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <CAEJOQjcQ1a2MdohdRM_DbYFwdLtKVqs-dey9Bqo7zKcCF30tOA(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > Dear all > Hope you are doing well. I would appreciate it if you can kindly tell me > how > I can perform Chi square for trend in epidata analysis. > Thanks a lot > Mohammed > > > ------------------------------ > > Message: 4 > Date: Sun, 09 Oct 2011 22:36:52 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Chi square for tren > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4E9205E4.1040604(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 2011-10-09 21:54, epidata-list(a)lists.umanitoba.ca wrote: > > Dear all > > Hope you are doing well. I would appreciate it if you can kindly tell me > how > > I can perform Chi square for trend in epidata analysis. > > Thanks a lot > > Mohammed > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > Currently a chi square test for trend is NOT implemented. But it is > quite easy. > > Just do the tabulation (crosstable) and when you have the numbers. Start > internet and get to the http://openepi.com webpage, where you can enter > the table and get the statistic from the menu at "dose response" or the > direct link: > http://openepi.com/OE2.3/DoseResponse/DoseResponse.htm > > If you have no direct internet link, you can download openepi when you > have access and use without persistent internet connection. > > regards > Jens Lauritsen > EpiData Association > > > ------------------------------ > > Message: 5 > Date: Mon, 10 Oct 2011 10:30:24 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to calculate chi square for trend > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <CAEJOQjcQ_dgW_TPK7r-xtLroK5QWJzgSOc5kOvXnD8fRy5z-MA(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > Dear all > > Would you please let me know if we can can calculate chi square in EpiData > analysis and if yes how we do that? > > Thanks > Mohammed > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 96, Issue 4 > ******************************************* >

1 0

How to calculate chi square for trend
by epidata-list＠lists.umanitoba.ca 10 Oct '11

10 Oct '11

Dear all Would you please let me know if we can can calculate chi square in EpiData analysis and if yes how we do that? Thanks Mohammed

1 0

Chi square for tren
by epidata-list＠lists.umanitoba.ca 09 Oct '11

09 Oct '11

Dear all Hope you are doing well. I would appreciate it if you can kindly tell me how I can perform Chi square for trend in epidata analysis. Thanks a lot Mohammed

1 1

How to jump a line in a Warning box?
by epidata-list＠lists.umanitoba.ca 09 Oct '11

09 Oct '11

Hi everybody, I would like to have a two-line warning box. I saw that I need to add "/n" but this does not work.Here my syntax: armcirc MUSTENTER BEFORE ENTRY HELP "Mesurez le périmètre à mi-distance/n entre le rebord postérieur de l’acromion et le sommet de l’olécrane" END END I would appreciate if someone can help me. Sophie.

1 0

How to calculate age
by epidata-list＠lists.umanitoba.ca 09 Oct '11

09 Oct '11

Dear Hans, Thank you for your reply but I also saw this mistakes. Many thanks. --Pièce jointe du message transmise-- From: epidata-list(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Date: Sat, 8 Oct 2011 19:24:19 +0200Envoyer Subject: Re: [EpiData-list] How to calculate age Dear Sophie: You cannot have "BEFORE ENTRY" in a "NOENTER" field because no command in that field can ever be executed. Better choose an "AFTER ENTRY" block in the field in which you added the last component that is needed to calculate the age, i.e., in the field DoB. To this end you may try: Your QES file: age ##.# recdate <Today-dmy> dob <dd/mm/yyyy> other _ Your CHK file: age NOENTER END dob MUSTENTER AFTER ENTRY age=(recdate-dob)/365.25 END END Regards, Hans On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > Hello everybody, > I am trying to write a syntax in .chk file to automatically calculate age during the data entry from the today's date and the DoB.The syntax is : > " ddn > MUSTENTER > END > > > age > NOENTER > BEFORE ENTRY > let age=ound(int((date-ddn)/(365.25)))) > END > END" > The variables are coded in the .qes file as follows: > {DATE} automatique<Today-dmy>{DDN} DATE DE NAISSANCE (DATE OF BIRTH)<dd/mm/yyyy>{AGE} automatique ### > What's wrong with my syntax? > Sincerely hope you can help me. > Regards, > Sophie PilleronPhD student. > -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org --Pièce jointe du message transmise-- From: epidata-list(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Date: Sat, 8 Oct 2011 20:04:14 +0200 Subject: [EpiData-list] How to calculate age Many thanks Jamie. It works now. I will never have found out my mistake without your support. Thanks again. Sophie. --Pièce jointe du message transmise-- From: epidata-list(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Date: Sat, 8 Oct 2011 16:41:29 +0200 Subject: [EpiData-list] How to calculate age Hello everybody, I am trying to write a syntax in .chk file to automatically calculate age during the data entry from the today's date and the DoB.The syntax is : " ddn MUSTENTER END age NOENTER BEFORE ENTRY let age=(round(int((date-ddn)/(365.25)))) END END" The variables are coded in the .qes file as follows: {DATE} automatique <Today-dmy>{DDN} DATE DE NAISSANCE (DATE OF BIRTH) <dd/mm/yyyy>{AGE} automatique ### What's wrong with my syntax? Sincerely hope you can help me. Regards, Sophie PilleronPhD student. --Pièce jointe du message transmise-- From: epidata-list(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Date: Sat, 8 Oct 2011 12:42:47 -0400 Subject: Re: [EpiData-list] How to calculate age You cannot have a field named DATE because that is the name of a function. EpiData doesn't complain when you do this, but you cannot use any function names as field names. Jamie On 2011-10-08, at 10:41 AM, epidata-list(a)lists.umanitoba.ca wrote: > let age=(round(int((date-ddn)/(365.25))))

1 0

How to calculate age
by epidata-list＠lists.umanitoba.ca 08 Oct '11

08 Oct '11

Many thanks Jamie. It works now. I will never have found out my mistake without your support. Thanks again. Sophie. --Pièce jointe du message transmise-- From: epidata-list(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Date: Sat, 8 Oct 2011 16:41:29 +0200 Subject: [EpiData-list] How to calculate age Hello everybody, I am trying to write a syntax in .chk file to automatically calculate age during the data entry from the today's date and the DoB.The syntax is : " ddn MUSTENTER END age NOENTER BEFORE ENTRY let age=(round(int((date-ddn)/(365.25)))) END END" The variables are coded in the .qes file as follows: {DATE} automatique <Today-dmy>{DDN} DATE DE NAISSANCE (DATE OF BIRTH) <dd/mm/yyyy>{AGE} automatique ### What's wrong with my syntax? Sincerely hope you can help me. Regards, Sophie PilleronPhD student. --Pièce jointe du message transmise-- From: epidata-list(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Date: Sat, 8 Oct 2011 12:42:47 -0400 Subject: Re: [EpiData-list] How to calculate age You cannot have a field named DATE because that is the name of a function. EpiData doesn't complain when you do this, but you cannot use any function names as field names. Jamie On 2011-10-08, at 10:41 AM, epidata-list(a)lists.umanitoba.ca wrote: > let age=(round(int((date-ddn)/(365.25))))

1 0

How to calculate age
by epidata-list＠lists.umanitoba.ca 08 Oct '11

08 Oct '11

Hello everybody, I am trying to write a syntax in .chk file to automatically calculate age during the data entry from the today's date and the DoB.The syntax is : " ddn MUSTENTER END age NOENTER BEFORE ENTRY let age=(round(int((date-ddn)/(365.25)))) END END" The variables are coded in the .qes file as follows: {DATE} automatique <Today-dmy>{DDN} DATE DE NAISSANCE (DATE OF BIRTH) <dd/mm/yyyy>{AGE} automatique ### What's wrong with my syntax? Sincerely hope you can help me. Regards, Sophie PilleronPhD student.

1 2

problems downloading to Mac OS X 10.6.8
by epidata-list＠lists.umanitoba.ca 01 Oct '11

01 Oct '11

HI, I attend college in CA and my professor insists that I use Epidata for our quantitative analysis. I am taking a research tools class. Everyone with Windows was able to download Epidate, except me, the only Mac user. Actually, it downloaded or appears to have downloaded, but I am not able to open it up. When I try to open it up, it looks lke a corrupt document. It's not acting independently as a software program. I appreciate your help and aide. Sincerely, Mic

1 2

new manager ready on epidata.dk/testing.php
by epidata-list＠lists.umanitoba.ca 30 Sep '11

30 Sep '11

Dear all A new test build version of the EpiData Manager has been placed for download on http://www.epidata.dk/testing.php The latest changes in Manager are: a. The value label editor has been completely rewritten. Including the way the editor is started. It now much resembles the entry principle. If you press the + button on the field property form, then a single value label for the current field is created or edited. If you wish to edit value labels in general use the manage button or the menu - tools. b. Export to stata of epz files is now possible. Formerly only epx files could be exported c. Pasting "as", e.g. as integer would create field names, that could not be read into analysis. This is fixed. The changes above to manager (a) unfortunately means that we will have to exclude the windows 64 bit version for a while. After december 1st we will see if we can add that version again. However this should pose no problem to anyone just now, since windows 64 bit pc's can use the 32 bit windows version. Regarding current EpiData EntryClient: It turns out that the default colour setting for the entry field is not very good in some windows installations. As soon as you have installed (unzipped) the entry client please make sure to change the colours to something you can see appropriately. This is done under "edit" and settings. With the mentioned changes to Manager we are quite close to release as v1. If someone can assist on finetuning icons let us know. regards Jens Lauritsen EpiData Association

1 1

Re: EpiData-list Digest, Vol 95, Issue 15
by epidata-list＠lists.umanitoba.ca 30 Sep '11

30 Sep '11

On 9/30/11, epidata-list-request(a)lists.umanitoba.ca <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..." > -- Sent from my mobile device ............ MENSAH KOJO SEDZRO Postal P.O.Box AS 387| Ashaiman -Tema | Ghana Skype: rasbesa web rasbesafari.blogspot.com House : +233-3033-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

Error message "out of memory"
by epidata-list＠lists.umanitoba.ca 23 Sep '11

23 Sep '11

Hello, I am starting out with Epidata Analysis so this might be a very basic question. I tried to run a very lengthy script (over 800,000 lines of commands) and it went about 3/4 through when I got the following error message (I had left the program open overnight to let it run): "PGM Error: Out of memory" What "memory" is it referring to? How can I fix this? Thank you very much for any help! Yvonne Yvonne Cao | Senior Research Analyst, International Projects NORC at the University of Chicago 4350 East-West Highway, 8th Floor, Bethesda MD 20814 cao-yvonne(a)norc.org <mailto:cao-yvonne@norc.org> | office +1 (301) 634-9476 | fax +1 (301) 634-9301

1 1

error in CHK file: cannot apply opGTE to missing operands
by epidata-list＠lists.umanitoba.ca 16 Sep '11

16 Sep '11

Hi I receive the following error with the CHK file coding that follows: CHECK MOUS >= MOUSTR cannot apply opGTE to missing operands And here's the coding: CONSISTENCYBLOCK CHECK "impossible # treated nets" MOUS >= MOUSTR CHECK "impossible # children sleeping under nets" ENFANTS >= DORMI END I cannot figure out why this is. MOUS, MOUSTR, ENFANTS and DORMI are all names for numerical variables in the REC file. Any assistance (however obvious) would be helpful. Thank you, Ruwan

1 2

Re: EpiData-list Digest, Vol 95, Issue 9
by epidata-list＠lists.umanitoba.ca 12 Sep '11

12 Sep '11

On 9/11/11, epidata-list-request(a)lists.umanitoba.ca <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..." > -- Sent from my mobile device ............ MENSAH KOJO SEDZRO Postal P.O.Box AS 387| Ashaiman -Tema | Ghana Skype: rasbesa web rasbesafari.blogspot.com House : +233-3033-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

Re: EpiData-list Digest, Vol 95, Issue 8
by epidata-list＠lists.umanitoba.ca 10 Sep '11

10 Sep '11

Thank you Jens. It worked perfectly with minor change, as I was looking for EntryClient as below, DateAIDS AFTER ENTRY DateAIDS=DateDiag1 IF (DateDiag2 < DateAIDS) THEN DateAIDS=DateDiag2 ENDIF IF (DateDiag3 < DateAIDS) THEN DateAIDS=DateDiag3 ENDIF IF (DateDiag4 < DateAIDS) THEN DateAIDS=DateDiag4 ENDIF IF (DateDiag5 < DateAIDS) THEN DateAIDS=DateDiag5 ENDIF IF (DateDiag6 < DateAIDS) THEN DateAIDS=DateDiag6 ENDIF IF (DateDiag7 < DateAIDS) THEN DateAIDS=DateDiag7 ENDIF END END I tested, works just fine. THANK YOU!!! Bijay On Sat, Sep 10, 2011 at 11:00 AM, <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. How to select earlier date from multiple dates > (epidata-list(a)lists.umanitoba.ca) > 2. Re: How to select earlier date from multiple dates > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 9 Sep 2011 14:34:44 -0600 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to select earlier date from multiple dates > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <CAEHHyTmiNvCm7zPcw+vtxBu2U8biViuecby-OG37jikcg1XG1w(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > Dear Forum Members, > > I was looking a way to select earliest date from multiple date fields. > Example, > > Five date fields with dates as below, > DateA - 13/01/2002 > DateB - *13/01/2001* > DateC - 13/01/2002 > DateE - 13/01/2003 > DateF - 13/01/2004 > > So, the programming to select earliest date (13/01/2001) in the field > called > "DateDiagnosis" > > Thanks in advance. > > Bijay Adhikari, PhD > CD Epidemiologist > Regina, SK > > > ------------------------------ > > Message: 2 > Date: Fri, 09 Sep 2011 22:50:12 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] How to select earlier date from multiple > dates > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4E6A7C04.9070701(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 2011-09-09 22:34, epidata-list(a)lists.umanitoba.ca wrote: > > Dear Forum Members, > > > > I was looking a way to select earliest date from multiple date fields. > > Example, > > > > Five date fields with dates as below, > > DateA - 13/01/2002 > > DateB - *13/01/2001* > > DateC - 13/01/2002 > > DateE - 13/01/2003 > > DateF - 13/01/2004 > > > > So, the programming to select earliest date (13/01/2001) in the field > called > > "DateDiagnosis" > I have not tested this solution, but I would do something like: > > I assume this is in analysis: > define datetmp <dd/mm/yyyy> > > datetmp = datea > if (dateb < datetmp) then datetmp = dateb > if (datec < datetmp) then datetmp = datec > if (dated < datetmp) then datetmp = dated > if (datee < datetmp) then datetmp = datee > if (datef < datetmp) then datetmp = datef > if (dateg < datetmp) then datetmp = dateg > > * now the datetmp contains the earliest of the dates mentioned. > > regards > Jens Lauritsen > EpiData Association > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 95, Issue 8 > ******************************************* >

1 0

How to select earlier date from multiple dates
by epidata-list＠lists.umanitoba.ca 09 Sep '11

09 Sep '11

Dear Forum Members, I was looking a way to select earliest date from multiple date fields. Example, Five date fields with dates as below, DateA - 13/01/2002 DateB - *13/01/2001* DateC - 13/01/2002 DateE - 13/01/2003 DateF - 13/01/2004 So, the programming to select earliest date (13/01/2001) in the field called "DateDiagnosis" Thanks in advance. Bijay Adhikari, PhD CD Epidemiologist Regina, SK

1 1

Combining logical operators
by epidata-list＠lists.umanitoba.ca 08 Sep '11

08 Sep '11

Is it possible to combine AND and OR into a single IF statement. If so, how? I have variables for the number of cups of tea consumed per day/week/month. The 3 variables are teapd, teapwk and teapmth. Only one of these should be filled in. -1 is the missing code and a value>0 indicates the number of cups consumed. I tried the following: BEFORE ENTRY IF ((teapd>0) AND (teapwk>0)) OR ((teapd>0) AND (teapmth>0)) OR ((teapwk>0) AND (teapmth>0)) THEN HELP "Only one of tea per day/week/month should have contain the number of cups" TYPE=ERROR ENDIF END This works for the paring of teapd and teapwk, but not the other parings, i.e. the "if" condition seems to stop at the first OR. A way around it is to split this into 3 statements (see below), but I suspect there may be a more elegant way to do what I want. BEFORE ENTRY IF (teapd>0) AND (teapwk>0) THEN HELP "Only one of tea per day/week/month should have contain the number of cups" TYPE=ERROR ENDIF END BEFORE ENTRY IF (teapd>0) AND (teapmth>0) THEN HELP "Only one of tea per day/week/month should have contain the number of cups" TYPE=ERROR ENDIF END BEFORE ENTRY IF (teapwk>0) AND (teapmth>0) THEN HELP "Only one of tea per day/week/month should have contain the number of cups" TYPE=ERROR ENDIF END 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(a)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 ______________________________________________________________________

1 2

I can't export questions including chinese characters to Stata
by epidata-list＠lists.umanitoba.ca 08 Sep '11

08 Sep '11

Dear friends, I can't normally export questions including chinese characters to Stata. When I open .dta file in Stata, the variables just display "???" in label.Can you help me? Thanks! Best regards,Richard Zhou > Date: Mon, 5 Sep 2011 12:00:27 -0500 > From: epidata-list-request(a)lists.umanitoba.ca > Subject: EpiData-list Digest, Vol 95, Issue 5 > To: epidata-list(a)lists.umanitoba.ca > > 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. Updated version of EpiData Manager release for MAC only. > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 05 Sep 2011 14:41:46 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Updated version of EpiData Manager release for > MAC only. > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4E64C38A.6020208(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear list. > > Due to a significant bug in EpiData Manager we have release a new > updated version of the program. > > The bug allowed a user to overwrite an existing project file > (.epx/.epz), by using "Save As...", > but without being warned that the file would be overwritten. > > This bug only affects the MAC version of EpiData Manager. > > > Kind regards, > Torsten Bonde Christiansen > EpiData Association. > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 95, Issue 5 > *******************************************

1 0

Updated version of EpiData Manager release for MAC only.
by epidata-list＠lists.umanitoba.ca 05 Sep '11

05 Sep '11

Dear list. Due to a significant bug in EpiData Manager we have release a new updated version of the program. The bug allowed a user to overwrite an existing project file (.epx/.epz), by using "Save As...", but without being warned that the file would be overwritten. This bug only affects the MAC version of EpiData Manager. Kind regards, Torsten Bonde Christiansen EpiData Association.

1 0

New test version of Manager and Analysis
by epidata-list＠lists.umanitoba.ca 03 Sep '11

03 Sep '11

The release of September 2nd is a minor update for Manager and EpiData Analysis, in which a few bug have been found and fixed. Manager: * Fixed bug where exporting to STATA did not export valuelabels. * Added support for importing .rec files with password protection. * Fixed minor bug where importing .rec files with valuelabels under special circumstances were not imported correctly. * Fixed significant bug in importing structure of STATA files could render computer useless (HUGE memory usage). * Fixed significant bug where deleting a section, with fields/heading moved out of could also delete the fields/headings. * Added "space extender". A heading is placed a "page" down on the designer, to extend the working area for placing fields, sections and headings. Analysis: * Fixed a bug where importing project files .epx/.epz would create a buggy .chk file on saving data from within Analysis. ==================================== Regards Torsten Christiansen and Jens Lauritsen EpiData Association

1 0

Re: conditional value label look-up?
by epidata-list＠lists.umanitoba.ca 03 Sep '11

03 Sep '11

We can use the following for the conditional value label look-up, disease AFTER ENTRY IF (disease='A') THEN GOTO subtypeA EXIT ENDIF IF (disease='B') THEN GOTO subtypeB ENDIF END END subtypeA COMMENT LEGAL USE label_subtypea SHOW TYPE COMMENT END subtypeB COMMENT LEGAL USE label_subtypeb SHOW TYPE COMMENT END Bijay Adhikari On Fri, Sep 2, 2011 at 11:00 AM, <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. Re: conditional value label look-up? > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 1 Sep 2011 20:29:35 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] conditional value label look-up? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP55572154E8DD723E0CAE91FD180(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > This is possible in the current version of EpiData. The syntax is shown in > the help file (.chk commands --> comment legal). It only works for comment > legal, not for legal. In my tests, it sometimes get confused. You can also > implement it, if your lists are short (as in your example), using nested if > ... then blocks. This may be better as the logic should be simple enough and > it will be bullet-proof. You can also provide error messages using the help > command. > > In the test version, there is not yet an equivalent way to do this, but > here is what I would do: > > create 4 fields: > > disease > sub1 > sub2 > subtype (string only will work) > > disease has jumps, to either sub1 or sub2, depending on its value > sub1 and sub2 have appropriate legal values, ranges or value labels > sub1 and sub2 have a calculation: subtype=sub1 in sub1 and subtype=sub2 in > sub2 > > subtype is NOENTER > > sub1 and sub2 have to jump to the field past subtype. I'm not sure whether > an unconditional jump is implemented yet. This may be problematic. > > Jamie > > On 2011-08-31, at 4:30 PM, epidata-list(a)lists.umanitoba.ca wrote: > > > Is there a way to do a conditional value label look up in either the > current or in the new test version of EpiData? > > > > For instance, if field disease equals A then field subtype has values > 1,2,3 for selection, if field disease equals B then field subtype has values > 4,5,6, etc. > > > > Thank-you, and well done to the development team for excellent progress. > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 95, Issue 2 > ******************************************* > -- Regards, ABJ "It is not the strongest of the species that survives, nor the most intelligent, but the one most responsive to change." Charles Darwin

1 0

Re: conditional value label look-up
by epidata-list＠lists.umanitoba.ca 03 Sep '11

03 Sep '11

Greetings. Is there a way to do a conditional value label look up in either the current or in the new test version of EpiData? For instance, if field disease equals A then field subtype has values 1,2,3 for selection, if field disease equals B then field subtype has values 4,5,6, etc. Thank-you, and well done to the development team for excellent progress. _______________________________________ Stephen Drew Health Data Analyst Region of Waterloo Public Health Waterloo, ON ======================================================================== Thanks Stephen, what about using the expression if: Example for disease A disease_A BEFORE ENTRY IF disease_A = 1 or "AFP" THEN Symptom = 1 GOTO admission ENDIF END END Next thing to be done is the following expression IF disease_B = 2 or "Yellow_Fever" THEN Symptom = 3 GOTO admission_tropic (i.e another subtype) ENDIF END END As you can see this can be very time consuming, however it could best done at the data management stage where you could create or generate new variable appropriately before cracking on with the analysis. However, if you really want to proceed with: "A then field subtype has values 1,2,3 for selection" then the other thing that you could do would be to assign a unique code; such as if field subtype has values 1,2,3, then coded it 1, for value 4-7 coded it 2; this will make it easy. I am struggling to understand why you need values 1, 2, 3 in the same field at the same time? Hope this helps Best wishes Tieble On 1 September 2011 18:00, <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. conditional value label look-up? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 31 Aug 2011 16:30:53 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] conditional value label look-up? > To: "'epidata-list(a)lists.umanitoba.ca'" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: > < > 51AB587E44A99647912C34562ECADA570AF45AFBA1(a)MAIL.region.waterloo.on.ca> > > Content-Type: text/plain; charset="us-ascii" > > Greetings. > > Is there a way to do a conditional value label look up in either the > current or in the new test version of EpiData? > > For instance, if field disease equals A then field subtype has values 1,2,3 > for selection, if field disease equals B then field subtype has values > 4,5,6, etc. > > Thank-you, and well done to the development team for excellent progress. > _______________________________________ > Stephen Drew > Health Data Analyst > Region of Waterloo Public Health > Waterloo, ON > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 95, Issue 1 > ******************************************* > -- <http://www.vet2011.org/calendrier3.php>http://vet2011.org Vet for health, Vet for food, Vet for the planet ! <http://www.mgavm.ru/>

1 0

conditional value label look-up?
by epidata-list＠lists.umanitoba.ca 01 Sep '11

01 Sep '11

Greetings. Is there a way to do a conditional value label look up in either the current or in the new test version of EpiData? For instance, if field disease equals A then field subtype has values 1,2,3 for selection, if field disease equals B then field subtype has values 4,5,6, etc. Thank-you, and well done to the development team for excellent progress. _______________________________________ Stephen Drew Health Data Analyst Region of Waterloo Public Health Waterloo, ON

1 1

IF... THEN LEGAL
by epidata-list＠lists.umanitoba.ca 30 Aug '11

30 Aug '11

Hi all, I'm trying to combine IF... THEN with LEGAL but somehow I'm having problems with it. Basically, what I want to do is to determine valid values for one variable based on the answer given to another variable. In the example below, the two vars are stateid and countyid: If stateid = 1 then countyid could be 01 or 04; if stateid = 2 then countyid could be 02, 03 or 05. Example: countyid IF stateid = 1 THEN LEGAL 01 04 END ENDIF IF stateid = 2 THEN LEGAL 02 03 05 END ENDIF MUSTENTER END -- Thomaz A.

1 2

I can't normally export value labels to Stata 11
by epidata-list＠lists.umanitoba.ca 27 Aug '11

27 Aug '11

Dear friends, I can't normally export value labels to Stata 11 data file even using the newest sample.epx. Why? RegardsRichard Zhou > Date: Fri, 26 Aug 2011 12:00:29 -0500 > From: epidata-list-request(a)lists.umanitoba.ca > Subject: EpiData-list Digest, Vol 94, Issue 13 > To: epidata-list(a)lists.umanitoba.ca > > 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. Re: New test versions (manager, entryclient, template cmd > tool) (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 26 Aug 2011 13:25:02 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] New test versions (manager, entryclient, > template cmd tool) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4E57828E.2030904(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear All. > > As promised in our previous mail, we have released a new test version of > EpiData Analysis on our website today. > > This test release have been modified to support the new XML structure > used by the most recent versions of EpiData Manager and EpiData EntryClient. > > Along with this change, EpiData Analysis is now also capable of reading > the zipped versions of the project files. That is, it is now possible to > read the .epz files. > > With kind regards, > Torsten Bonde Christiansen. > EpiData Association. > > > On 2011-08-24 16:38, epidata-list(a)lists.umanitoba.ca wrote: > > > > Dear All > > > > As previously announced the programs released today have had a > > significant change to the underlying structure of the project file > > (the .epx/.epz XML structure). > > > > The reason for this is that the previous structure could not be > > described by a XML Schema file. A schema file is a standardised way of > > describing the structure and internal logic of an XML file. Some of > > the logical properties of the structure were inconsistent and > > therefore changed. This has as a positive "side effect" that the > > overall loading and saving time for a project file has improved quite > > a bit. > > > > The changes will - as warned two times on this list - break > > compatibility with > > previously created files. An updated version of the sample.epx file is > > provided with the downloads and additionally the EpiData Commandline > > Tool has been updated (and release for all platforms) to support the > > new XML structure. > > > > Please read previous mails on the list to see further explanation and > > how you can avoid problems in relation to the changed XML structure. > > > > The currently available test version of EpiData Analysis does NOT > > support the new XML structure. An updated version will be released in > > a few days. > > > > Common fixes/changes: > > * Updated XML structure > > * Import from STATA 12 now supported. > > * New saving algorithm, for improved speed. > > > > Manager: > > * Fixed a bug where removing a control marked for copy would cause > > breakdown if copy/paste was later invoked. > > * Fixed shortcuts for MAC. > > * Added boolean field to "other fields" > > * Fixed bug with "delete all" > > * Speed improvements for copy/paste and placing new controls (mainly > > visible with very many controls). > > > > EntryClient: > > * Fixed shortcut overlap in MAC > > * Speed improvements with loading project files. > > * Speed improvements when browsing records. > > > > EpiC: > > * Updated to support new XML structure. > > > > Regards > > > > Torsten Christiansen and Jens Lauritsen > > EpiData Association > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 94, Issue 13 > ********************************************

1 0

New test versions (manager, entryclient, template cmd tool)
by epidata-list＠lists.umanitoba.ca 26 Aug '11

26 Aug '11

Dear All As previously announced the programs released today have had a significant change to the underlying structure of the project file (the .epx/.epz XML structure). The reason for this is that the previous structure could not be described by a XML Schema file. A schema file is a standardised way of describing the structure and internal logic of an XML file. Some of the logical properties of the structure were inconsistent and therefore changed. This has as a positive "side effect" that the overall loading and saving time for a project file has improved quite a bit. The changes will - as warned two times on this list - break compatibility with previously created files. An updated version of the sample.epx file is provided with the downloads and additionally the EpiData Commandline Tool has been updated (and release for all platforms) to support the new XML structure. Please read previous mails on the list to see further explanation and how you can avoid problems in relation to the changed XML structure. The currently available test version of EpiData Analysis does NOT support the new XML structure. An updated version will be released in a few days. Common fixes/changes: * Updated XML structure * Import from STATA 12 now supported. * New saving algorithm, for improved speed. Manager: * Fixed a bug where removing a control marked for copy would cause breakdown if copy/paste was later invoked. * Fixed shortcuts for MAC. * Added boolean field to "other fields" * Fixed bug with "delete all" * Speed improvements for copy/paste and placing new controls (mainly visible with very many controls). EntryClient: * Fixed shortcut overlap in MAC * Speed improvements with loading project files. * Speed improvements when browsing records. EpiC: * Updated to support new XML structure. Regards Torsten Christiansen and Jens Lauritsen EpiData Association

1 2

Warning: Changes in XML structur in the next test release of Manager and EntryClient
by epidata-list＠lists.umanitoba.ca 22 Aug '11

22 Aug '11

Dear all As I already informed on August 17th the next test release for Manager and EntryClient will require ALL current EPX and EPZ files to be recreated. The next test release will be available within the next few days. Obviously this can be annoying, but as previously announced we do need to have the flexibility of changes all the way to release of version 1. If you are preparing projects for future use I recommend that you either: a. - Export your data with current test version into stata format - import again with the new test version (when this is ready) - add jumps, calculations etc after the import. (Labels will be imported correctly) or b look at the template principles explained in http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat and then use the template command tool to create the epx files. A revised template tool will be released at the same time as the next test release. In other words: Do not spend too much time on fine tuning epx files at this point. Datastructures are fine, but details must be expected to change, e.g. specifications of jumps, range, notes etc. The XML structure used in v1.0 will be supported for all future releases after that. regards Jens Lauritsen EpiData Association

1 1

key unique code not working fully
by epidata-list＠lists.umanitoba.ca 17 Aug '11

17 Aug '11

I have a database with 2 unique keys: stickno and randid. The CHK file contains the following code for these fields: stickno KEY UNIQUE 1 RANGE 1 500 MUSTENTER END randid KEY UNIQUE 2 RANGE 100 1699 MUSTENTER AFTER ENTRY IF (randid>899) and (randid<1300) THEN HELP "randid must be 100-899 or 1300-1699" TYPE=WARNING ENDIF END END Despite the KEY UNIQUE commands, I found 2 records with stickno=290 and randid==227. I believe KEY UNIQUE was present in the CHK file prior to beginning data entry, but even if not, when attempting to open the REC file I should receive a warning alerting me to the duplicates. This doesn't happen when I keep the EIX file in the same directory as the database. After deleting the EIX file from the directory, when attempting to open the REC file I do get a warning alerting me to the duplicates. What information does the EIX file store? I've attached it in case you're able to determine where the error lies. I haven't attached the database because it contains data on real patients and I can't edit it without changing the EIX file. Any insights would be much appreciated. 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(a)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 ______________________________________________________________________

1 0

Revision of XML structure and changes in next test release of Manager and EntryClient
by epidata-list＠lists.umanitoba.ca 17 Aug '11

17 Aug '11

Dear all Since last test release of July 15th summer vacation is now over and the following has been fixed or worked on: a. copy-paste bugs b. other minor issues c. develop a scripting tool to validate function (simulate user performance) d. WIKI documentation updated - e.g. see: http://www.epidata.org/dokuwiki/doku.php/documentation:program_keys e. Critical external review of the XML structure The next test release will follow when these aspects are all covered. More comments below. Comments: Yesterday a critical review of the current XML structure for the data files was performed with the Danish Data Archive. It turns out that a few issues requires some changes to the XML structure (tag-attribute), to ensure consistence and possibility of developing a schema file for the XML. Schema files are content describing files, which will enable other software to read the epx files and validate contents against the formal specification. While this is rather technical - and of no interest - to most users, it means that with the next test release the XML structure will change (again). If you are preparing projects for future use I recommend that you either: a. - plan to export your data with current test version into stata format - import again with the new test version (when this is ready) or b look at the template principles explained in http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat and then use the template command tool to create the epx files. A revised template tool will be released at the same time as the next test release. In other words: Do not spend too much time on fine tuning epx files at this point. Datastructures are fine, but details must be expected to change, e.g. specifications of jumps, range, notes etc. The XML structure used in v1.0 will be supported for all future releases after that. regards Jens Lauritsen EpiData Association

1 0

Excel data upload into EpiData
by epidata-list＠lists.umanitoba.ca 12 Aug '11

12 Aug '11

Jens & Jamie, Thank you for suggestions time to time on Epidata programming that I am working on. We are replacing existing disease database (specific disease) that is in Access plateform with Epidata. The access database was not stable over the years, so lost a chunk of data few times. Hope Epidata is the solution. I completed most programming including several calculated fields, some are very complex assiging risk factors. The data is in MS Excel. It has ~ 2000 data with ~ 100 variables. All the data fields in both (Epiadta QES and Excel) systems are identical except IDNUM is extra in Epidata. I am looking the best way to migrate excel data into the blank epidata. May be I should convert excel to .REC file first, then import, or may be .TXT is better. I have tested with small dataset by cerating .REC file first then import. It did work. Any suggestion would be appriciated. Thanks Bijay On Fri, Aug 12, 2011 at 11:01 AM, <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. Re: Export EpiData to Excel - is there a solution/an > alternative? (epidata-list(a)lists.umanitoba.ca) > 2. relational files on epodata analysis > (epidata-list(a)lists.umanitoba.ca) > 3. Re: relational files on epodata analysis > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 11 Aug 2011 19:03:19 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Export EpiData to Excel - is there a > solution/an alternative? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <23065_1313082200_ZZh0y4eF~ > 8kfp.00_4E440B57.4040905(a)uni-bielefeld.de> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hey everybody, > > thank your so much for your efforts and the enormous help! I need some > time to consider your proposals and the next steps now :-) > > My boss has done a lot of work with Excel and she is just worried 1. > that we have to adapt to a new system and 2. that we can't combine the > data from the Open Office sheets with already existing Excel sheets. > > Thanks again and greetings, > Nina > > > > Am 11.08.2011 17:45, schrieb epidata-list(a)lists.umanitoba.ca: > > I suppose the starting point really is to answer the question, "What do I > want to do with the data in Excel?" > > > > ? look at it in a spreadsheet view? - EpiData Analysis can do this > (Browse) > > ? do some simple calculations on some fields? - EpiData Analysis can do > this > > ? do some really complicated calculations on some fields? - just export > some key identifying fields and the fields you need into Excel and merge the > results back into your EpiData file > > ? do some special analysis that is only available in Excel? - same idea, > but I can't think of any that would use very many fields > > ? create a database that will support mail-merge ? - you won't need many > fields for this > > > > If your boss has a fixation on an old version of Excel, then you are > limited to exporting 256 fields (columns). Excel 2010 or newer can handle > over 16,000 columns > > > > Jamie > > > >> thank you very much! I tried to suggest that to my boss but she is not > convinced yet. Are there any other possibilities available? > > > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > -- > Nina-Claire Himpe > Wiss. Mit. von Prof. Dr. Ulrike Davy > Lehrstuhl für öffentliches Recht, deutsches und > internationales Sozialrecht, Rechtsvergleichung > Fakultät für Rechtswissenschaft > Universität Bielefeld > Postfach 10 01 33 > 33 501 Bielefeld > > UHG T7-109 > Tel.: 0521 - 106 2508 > > > ------------------------------ > > Message: 2 > Date: Thu, 11 Aug 2011 13:59:24 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] relational files on epodata analysis > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <6c3a19b721250cea381f09c055a1d1f1.squirrel(a)webmail.uady.mx> > Content-Type: text/plain;charset=iso-8859-1 > > I woul like to request a simple exaple to relate 2 files and create a new > one using epidata analysis. > Thank you in advance > > Jose Farfan > > > ----------------------------------------- > "Universidad Autónoma de Yucatán" > http://www.uady.mx/ > > > > ------------------------------ > > Message: 3 > Date: Thu, 11 Aug 2011 16:50:49 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] relational files on epodata analysis > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP24D73CD429C739981CD0C1FD220(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > This is quite simple. Please read the help for the MERGE command in > Analysis. > Here is a simple example in a zip file. >

1 1

relational files on epodata analysis
by epidata-list＠lists.umanitoba.ca 12 Aug '11

12 Aug '11

I woul like to request a simple exaple to relate 2 files and create a new one using epidata analysis. Thank you in advance Jose Farfan ----------------------------------------- "Universidad Autónoma de Yucatán" http://www.uady.mx/

1 2

Export EpiData to Excel - is there a solution/an alternative?
by epidata-list＠lists.umanitoba.ca 11 Aug '11

11 Aug '11

Dear member of the team, dear all, I am having the following problem and would be very grateful if there was a solution (or alternative) to it: The data I want to export to Excel consists of approximately 960 lines in Epidata formats (= 960 colums in .xls). As I understand EpiData (and as the test with the used data showed) it is impossible to export more than 256 lines to Excel (version 2003) because of the Excel 2003 column limit . Is there any way to export the 960 lines to Excel? Or is there another alternative I should consider? Thank you very much in advance! Greetings, Nina-Claire Himpe

1 6

follow up: big data sets
by epidata-list＠lists.umanitoba.ca 05 Aug '11

05 Aug '11

I tried the new Entryclient with two large data sets. Set 1: 500 integer fields, 500 records, uncompressed size: 1.1 MB as .epx 45K as .epz - load the file: 150 seconds - jump from record 1 to last record: 1 or 2 seconds - * to get empty record: 5 seconds - save file: 3 second - load in Analysis (running under Wine, so a bit slower than on an equally powered PC): 5 seconds - freq v500: immediate - no difference with .epz file Set 2: 20 integer fields, 10,560 records, uncompressed size: 1.1 MB - load the file: immediate - jump to end or new record: immediate - load in Analysis: 7 seconds - freq v1: immediate I expect the typical "large" data set would be somewhere between these two. Most large data sets I have used are like Set 2 and have been extracts of national databases. I might use the Entryclient on these, but unlikely. I've seen others using data like Set 1, but never really understood why they used such large data sets as most data items were unused and interesting only in a clinical review of individual subjects. (technical note: time to execute a Javascript loadxml() <500 msec) Jamie

1 2

File size and program freezing
by epidata-list＠lists.umanitoba.ca 02 Aug '11

02 Aug '11

Hello, I was hoping to get an idea for the size of files people are working with in the new EpiData Manager. I am currently trying to work out issues when I try to open a .epx file. The file is quite large at 60,000 Kb. I don't know if the problem is with Manager being able to handle a file of this size, or if the file contains some sort of corruption. The file is quite important, so any feedback or assistance would be most appreciated. Cheers, Jonathan Edwin -------------------------------------------------------------------------------------------------------- Jonathan Edwin Outbreak Management Division Public Health Agency of Canada jonathan.edwin(a)phac-aspc.gc.ca

1 1

Adding sections or fields inEpiData Manager(length/height of dataform)
by epidata-list＠lists.umanitoba.ca 02 Aug '11

02 Aug '11

My understanding of a section is for the logical grouping of a set of questions (such as personal details, which one may wish to password protect, for instance). Such a section may consist of many questions. If that is the case, then it seems reasonable to me that a section could thus take the whole page. Such a section could be just one of many (which may be any size, smaller or bigger), so that indeed one doesn't just have one section. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

Adding sections or fields in EpiData Manager(length/height of dataform)
by epidata-list＠lists.umanitoba.ca 02 Aug '11

02 Aug '11

Thanks to Jonathan and Jens for their postings. The approach that Jens suggests works for headings and fields as long a section isn't already full-screen. The approach that Jonathan suggests for sections works for the first such section to be created (i.e. the one that extends the height of the dataform). After that (i.e. after having a section which has extended the height so that it is full screen) it doesn't seem possible to add further sections. In such a situation, even pressing shift+5, for instance, puts the heading within that (now full-screen) section, rather than extending the form. I look forward to Jens and his team handling this situation. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

Adding sections or fields in EpiData Manager
by epidata-list＠lists.umanitoba.ca 02 Aug '11

02 Aug '11

When creating a form in the Manager, such a form will, generally, contain many fields and possibly more than one section. It is not clear to me how one adds sections and/or fields upon reaching the bottom of the screen (which seems to occur at a height of about 610 as measured from the top) as there is no vertical scroll bar to move a blank page into focus into which such fields or sections can be added. If this can't be done, then surely this limits how many sections and fields can be created. The sample file, for instance, spreads over two pages, so how were the later sections added after the first few were created? Apologies if a stupid question ... All thoughts on this would be most appreciated. Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 2

How to Delete Records Based on a Variable
by epidata-list＠lists.umanitoba.ca 25 Jul '11

25 Jul '11

Hello, I would like to add an alternative way of deleting records in Epidata entry if you just want to delete certain number of records. When you move to the record you want to delete in the database, there is a “X” sign in red at the left bottom of the screen beside the area showing the number of records, navigation buttons and the button for new record entry “*” . If the red “X” button is hit, “DEL” will show up right beside. Save the record. Apply this “DEL” to the records you would like to delete in the database. Next step is to PACK the data file. To do this, close the data entry form and go to ‘ Tools > Pack data file ‘ and select the data file which contains the records you would like to delete. This will delete the records marked as “DEL” permanently. At the same time, filename.old.rec will be created if you would like to undo the deleting. Marking the records “DEL” does not permanently delete the records until you PACK the data file. Hope this help. Zaw Myanmar On Sat, Jul 23, 2011 at 11:30 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. How to Delete Records Based on a Variable > (epidata-list(a)lists.umanitoba.ca) > 2. Re: How to Delete Records Based on a Variable > (epidata-list(a)lists.umanitoba.ca) > 3. Re: How to Delete Records Based on a Variable > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 22 Jul 2011 18:49:20 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to Delete Records Based on a Variable > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <679902537E215D43805DEA9BE833090E06C213D5(a)NORCEX1.norc.org> > Content-Type: text/plain; charset="us-ascii" > > Hello, > > > > I am trying to delete a subset of records in my dataset based on the > value of one of the variables (hhid) in either EpiData Entry or > Analysis. I am guessing it is easy, but I cannot figure it out. Can > someone please advise? > > > > Thanks, > > Sam > > > > > > ------------------------------ > > Message: 2 > Date: Fri, 22 Jul 2011 21:20:08 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] How to Delete Records Based on a Variable > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP18F9651A4055C04D6E8A53FD310(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > It's quite easy > > In Analysis: > > select hhid <> [value for delete] > savedata newfile > > You can then copy your old file as a backup and rename "newfile.rec" if you > want. > > In EpiData Entry: > > -export data to EpiData > Choose your current data (.rec) > Make sure all variables are checked > Check off "Use record filter" > In the Filter box: hhid <> [value for delete] > > You can put a more complex logical expression in the filter. > Your new data are in filename.new.rec > > Jamie > > On 2011-07-22, Sam wrote: > > > I am trying to delete a subset of records in my dataset based on the > > value of one of the variables (hhid) in either EpiData Entry or > > Analysis. I am guessing it is easy, but I cannot figure it out. Can > > someone please advise? > > > > ------------------------------ > > Message: 3 > Date: Fri, 22 Jul 2011 21:22:17 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] How to Delete Records Based on a Variable > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <0bf801cc48d6$f2ee5c62$ae9510ac(a)norc.org> > Content-Type: text/plain; charset="utf-8" > > Perfect, thank you! > > "epidata-list(a)lists.umanitoba.ca" <epidata-list(a)lists.umanitoba.ca> wrote: > > It's quite easy > > In Analysis: > > select hhid <> [value for delete] > savedata newfile > > You can then copy your old file as a backup and rename "newfile.rec" if you > want. > > In EpiData Entry: > > -export data to EpiData > Choose your current data (.rec) > Make sure all variables are checked > Check off "Use record filter" > In the Filter box: hhid <> [value for delete] > > You can put a more complex logical expression in the filter. > Your new data are in filename.new.rec > > Jamie > > On 2011-07-22, Sam wrote: > > > I am trying to delete a subset of records in my dataset based on the > > value of one of the variables (hhid) in either EpiData Entry or > > Analysis. I am guessing it is easy, but I cannot figure it out. Can > > someone please advise? > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 93, Issue 13 > ******************************************** >

1 0

Re: [EpiData-list] How to Delete Records Based on a Variable
by epidata-list＠lists.umanitoba.ca 22 Jul '11

22 Jul '11

Perfect, thank you! "epidata-list(a)lists.umanitoba.ca" <epidata-list(a)lists.umanitoba.ca> wrote: It's quite easy In Analysis: select hhid <> [value for delete] savedata newfile You can then copy your old file as a backup and rename "newfile.rec" if you want. In EpiData Entry: -export data to EpiData Choose your current data (.rec) Make sure all variables are checked Check off "Use record filter" In the Filter box: hhid <> [value for delete] You can put a more complex logical expression in the filter. Your new data are in filename.new.rec Jamie On 2011-07-22, Sam wrote: > I am trying to delete a subset of records in my dataset based on the > value of one of the variables (hhid) in either EpiData Entry or > Analysis. I am guessing it is easy, but I cannot figure it out. Can > someone please advise? _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

How to Delete Records Based on a Variable
by epidata-list＠lists.umanitoba.ca 22 Jul '11

22 Jul '11

Hello, I am trying to delete a subset of records in my dataset based on the value of one of the variables (hhid) in either EpiData Entry or Analysis. I am guessing it is easy, but I cannot figure it out. Can someone please advise? Thanks, Sam

1 1

permission
by epidata-list＠lists.umanitoba.ca 21 Jul '11

21 Jul '11

Dear the Epidata community Please allow me to post on your list Regards, -- Lê Phương Loan Project Assistant - ACT 2 0167 28 55 567

1 1

New test version for EpiData Manager, EntryClient and EpidataCMD
by epidata-list＠lists.umanitoba.ca 15 Jul '11

15 Jul '11

Dear All Today a new set of test versions have been placed on the Http://www.epidata.dk/testing.php for general download. The development during most recent weeks has focused on solving all reported bugs and fixing issues related to keyboard shortcuts across operating systems. Keyboard short cuts will be operating system typical (or should be) from now on. Bugs reported recently are also fixed. The list of major changes in the versions release today: =============================================================== Changes to Manager: - bug fix: * creating sections on MAC was nearly impossible, and difficult at times on Windows. * Assigning jumps to a UPPERCASE string field would cause the program to crash. * Typing an invalid date/time in range, would not always give a warning. On MAC this would lead to a large black screen, show for a few seconds. Changes to EntryClient: * Fixed bug where closing at times could save a "New Record" without data. * Major changes in short-cuts on MAC. * Performing "New Record" on a "new record" will clear content (but ask user first). =============================================================== Kind regards, Torsten Bonde Christiansen. Jens Lauritsen EpiData Association.

1 0

New test version for EpiData Manager, EntryClient and EpidataCMD
by epidata-list＠lists.umanitoba.ca 15 Jul '11

15 Jul '11

Dear All Today a new set of test versions have been placed on the Http://www.epidata.dk/testing.php for general download. The development during the last week have mainly been focus on solving some large outstanding bugs in the programs. This mean that today release does not have any new feature, but will hopefully add to the feeling that we rapidly approaching the first stable release (Version 1) of EpiData Manager and EpiData EntryClient. With todays release we have also tried to address the problem of how different Operating Systems use different sets of keyboard short-cuts. Our initial goal was to have the programs use the same set of short-cuts across all OS's, but we have found this to be virtually impossible. Instead we have now focused on have a small set of common short-cuts, but try to use the "normal" short-cut for regular functions (such as search, copy & paste, etc.) Hopefully this will in the future lead to a point where we integrate a list of command the programs are capable of and let users customize the associated shortcuts as they wish. The list of major changes in the versions release today: =============================================================== Changes to Manager: * Fixed the longest outstanding bug: Creating sections on MAC was nearly impossible, and difficult at times on Windows. * Assigning jumps to a UPPERCASE string field would cause the program to crash. * Typing an invalid date/time in range, would not always give a warning. On MAC this would lead to a large black screen, show for a few seconds. Changes to EntryClient: * Fixed bug where closing EntryClient at times could same the "New Record". * Major changes in short-cuts on MAC. * Performing "New Record" on a "new record" will clear content (but ask user first). =============================================================== Kind regards, Torsten Bonde Christiansen. EpiData Association.

1 0

Re: Managing two related unique IDs in data entry
by epidata-list＠lists.umanitoba.ca 12 Jul '11

12 Jul '11

> > Jamie, Unfortunately this solution is not working here. Did you tests it? Did it work with you? The problem is that like this EpiData only accepts sample2 in blank, ie, missing data for this field. Also, when the warning comes up, the (@sample1, @sample2) does not show any data. My guess is that EpiData is not creating the checksamp variable correctly or is being able to type sample1 comment correctly into sample2. Another good guess, might be that the error is above the chair in front of the keyboard. Thanks anyway for the ideia. I will try to make this warning work later and let you know. > , > > before file > define checksamp ### > hide checksamp > end > > sample1 > comment legal use recfile.rec > type comment checksamp > end > > sample2 > after entry > if sample2 <> checksamp then > help "This pair of sample numbers (@sample1, @sample2) do not match > those assigned. \nPlease check and re-enter both." type=error > goto sample1 > endif > end > end > > Jamie > > Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.libreoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com - sistema operacional

1 1

Troubleshooting skip pattern crash
by epidata-list＠lists.umanitoba.ca 12 Jul '11

12 Jul '11

Hello, I recently posted in regards to an error/crash message I was receiving with entering skip patterns. These errors were in the previous Manager version and I have since upgraded to the most recent upgrade. Unfortunately the trouble has persisted. Is anyone else experiencing this issue? Suggestions for getting around it? The epx file is a hypothesis-generating questionnaire, therefore it is relatively large. In addition, the skip patterns are being generated before value labels have been given...is it possible that one of these two factors is contributing to the error? Any help would be appreciated. Regards, Jonathan Edwin -------------------------------------------------------------------------------------------------------- Outbreak Management Division Public Health Agency of Canada Unit 120, 255 Woodlawn Road West Guelph, Ontario N1H 8J1 jonathan.edwin(a)phac-aspc.gc.ca

1 0

Need help: Check codes truncated
by epidata-list＠lists.umanitoba.ca 11 Jul '11

11 Jul '11

Dear colleagues, I would apprciate your help in solving check codes truncation proble. I am currently creating one database using epidata. I have one of the check codes of about 600 charecters long(example below), however after applying chk codes, it is automatically truncated to 207 charecters when I open to see next time. Any clues or ways to code alternatively? *check code:* IF (Sex=2) AND (Msex=0) OR (Msex=9) OR (Msex=99) AND (Fsex=0) OR(Fsex=9) (Fsex=99) AND (IDU=0) OR (IDU=9) OR (IDU=99) AND (CFac=0) OR (CFac=9) OR (CFac=99) AND(Trans=0) OR (Trans=9) OR (Trans=99) OR (coag=0) OR (coag=9) OR (coag=99) OR(HetSexEND=0) OR (HetSexEND=9) OR (HetSexEND=99) OR (ConSusHIV=0) OR (ConSusHIV=9) OR(ConSusHIV=99) AND (OccuExp=0) OR (OccuExp=9) OR (OccuExp=99) AND (OthMedExp=1) OR(OthMedExp=0) OR (OthMedExp=9) OR (OthMedExp=99) AND (NMNOcc=1) OR (NMNOcc=0) OR(NMNOcc=9) OR (NMNOcc=99) *THEN* * **Risk="OtherMedExp-10"* Thank you. Bijay Adhikari, PhD CD Epiodemiologist Saskatchewean Ministry of Health

1 2

Managing two related unique IDs in data entry
by epidata-list＠lists.umanitoba.ca 11 Jul '11

11 Jul '11

Hello EpiData friends, Im involved in a reliability study. I planned to collect two blood samples at same time to measure the very same biomarker from the same patient. I would like to measure the variability of this biomarker when the lab responsible does not know what sample comes from what patient. Thus I have a (patient) ID and two samples ids. My control/recruiting qes would look like patientid Unique identifier ##### sample1 ### sample2 ### My results qes would look like sampleid Sample identifier ### sampres Sample result ####### Later, I intend to connect these two files. I generated random numbers that would be stick as blood sample stamps from 1 to 500. Thus, when a patient collects a pair of blood sample these numbered stamps are stick on the container, before they get to the lab. My problem is that, for the patient to be blind to the lab professionals, each patient should have two different sample number. Im concerned that the professional that enroll the patient might give the samples a correct pair of stamps to the blood samples but mistype this pair in the enrollment control data. FOr example: random numbers 1 106 303 2 236 168 3 302 228 4 107 197 I made a rec file with these pairs of stamps numbers like this sample1 #### sample2 #### If the enrollment professional recruits a patient with medical chart 19992 and gives him/her the third pair of stamps, this means that he should type 302 in the sample1 variable. I would like EpiData to fill or to check if the sample2 for this patients is 228. If not a warning should come to check these numbers. I did try using the chk command as sample1 comment legal use recfile.rec type comment sample2 end sample2 legal 303 168 228 197 ... end end It looks it works nicely. But I reckon if there is any more elegant way to do it. Is there? Kind regards . Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.libreoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com - sistema operacional

1 1

want to delete all records in epi data
by epidata-list＠lists.umanitoba.ca 11 Jul '11

11 Jul '11

Dear colleagues, I would really appreciate if you could help me out in deleting all records from rec file in epidata. I used the pack file funcationin in *the Tools * menu.but still i couldnt delete all records. see the attached error. thanks and best regards muhammad

1 2

new test version for Manager and EntryClient
by epidata-list＠lists.umanitoba.ca 06 Jul '11

06 Jul '11

Dear All Today a new set of test versions have been placed on the Http://www.epidata.dk/testing.php for general download. =============================================================== Changes to Manager: * HTML Report window stays open. * Added additional reports. * Fixed bug on MAC where valuelabels could not be deleted at all in the ValueLabel Editor. * Fixed bug on Windows where valuelabels, comparison and "write valuelabel to" definitions could be added randomly to a field. Changes to EntryClient: * Added a WorkTool bar to main form. * Fixed bug where skip records (F5/F8) would cause program crash if dataset was empty. * Fixed bug where jumping to a field would not work under certain circumstances. * Fixed long standing bug where pasting text into uppercase field was not automatically made uppercase. =========================== The bug fix since last test versions are essential to Windows users, which in the previous version could mess up use and definition of Value Labels and field definitions. Another issue was only relevant for Mac users. Please notice that files produced with the previous version might contain errors. This underlines the fact that supporting multiple operating systems effectively creates a lot more work and complications, since the same problems - now fixed - was not seen in a Linux computer. It also underlines the need for a batch testing procedure, which we are developing now, such that functionality simulating user behaviour will be implemented sometime soon. We plan to use the scripting engine to automate tests as shown below. More on this later. The simulations will be done on all supported operating systems. Once we have a few scripts developed they will be posted on the web such that users can enhance and extend the tests. regards Jens Lauritsen EpiData Association List of tasks for simulator: 1. Create user simulation and gui automation tests. 1. Create a macro/script template for benchmarking tests. 1. create datafile structure (all field types first, then a new section with all field types) 2. define value labels 3. extend definition of datafile with more "checks" from field property page 1 4. extend definition of datafile with more "checks" from field property page 2 (extended) 5. extend definition of datafile with more "checks" from field property page 3 (jumps) 6. extend definition of datafile with more "checks" from field property page 4 (calculations) 2. Import/export data between the versions of epidata (in different formats) and check import/export success. - specifically import and export of bromar, lifetable and tiramisu datasets - import as reg file or stata file (where labels are attached directly). 1. Create a scrip to automate this 1. data integrity checks: e.g. go to record no xxx and compare the actual data with the imported value. Check data type (int,float,string,Date-time) 2. Check inconsistencies between xml/rec formats (if any) and see how gui interprets the xml data

1 0

EpiData data entry competitors. Where are they?
by epidata-list＠lists.umanitoba.ca 06 Jul '11

06 Jul '11

Hello EpiData friends, Last week I did teach the 6th edition of "introduction of softwares for research porpuses" here at Rio de Janeiro. Usually we present to the students three softwares: EpiData, zotero, SPSS (although Im have been trying to replace SPSS for R-project for a while). Because of this course, yesterday, the principal of the institution I work at came to me and asked if it is worth to get engaged at this initiative: http://www.project-redcap.org/ Actually, it seems to be pretty similar to epidata projects in content, except that it is web based and it seems that it is necessary to become a partner to use it. Since then I have looked around and trade a couple of emails with some friends and some other stuff came up... http://www.rch.org.au/dmo/services.cfm?doc_id=13999 This is one is pretty good, but very expensive, and we had a tough time trying to manage the operator limitations (need to be highly skilled to operate this software) and as more projects are running more licenses are required to get the job done in time and more money is necessary. http://www.sphinxdevelopment.co.uk/about.html this one has not many information at the webpage, but a friend of mine told me that they have a software similar to teleform, which scans the form and fill the the dataset from the scanned image. Once in a while a hear someone is using pendragon: http://pendragonsoftware.com/ But this one is for portable devices such as palmOS iPad Android and stuff. Im writing all this stuff to ask you guys if you have any bad/good experience with other dataentry softwares? This time particularly with redcap. Every time someone asks me about other dataentry software, I take some time trying it and I always come back to EpiData. I believe that there isnt really a good competitor to EpiData so far... free, small, portable, easy to use, and does the job. Also, I imagine that looking at what other data entry softwares do, may give some insight to improve EpiData functionality. This web idea may be something to think about. Kind regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com - sistema operacional

1 6

Corruption error
by epidata-list＠lists.umanitoba.ca 04 Jul '11

04 Jul '11

Hello. I am working with the new EpiData Manager, and every now and then when I click within a field I receive the following corruption error: "epidatamanager.0.8.2.0.i386.win32 Press OK to ignore and risk data corruption. Press Cancel to kill the program" I am forced to kill the program, as clicking OK blocks me from making edits because the same message pops up. Does anyone have any suggestions or fixes to handle this issue? Many thanks. ------------------------------------------------------------------------------------------------------- Jonathan Edwin Public Health Agency of Canada

1 0

a Short status on development (Manager and EntryClient) - what to expect the coming month
by epidata-list＠lists.umanitoba.ca 01 Jul '11

01 Jul '11

Dear All Just now development has focus on removing bugs and clarifying issues, which prevent release as first public v1.0 In recent days a number of important issues have solved, such as: a. Pasting into upper case fields (fixed) b. Strange behaviour sometimes with jumps (fixed) (resulted in jumping to a wrong field) The plan is to release the next test versions towards the end of next week, just before we close for vacation until August 1st. regards Jens Lauritsen EpiData Association

1 0

How to edit a .qes file imported from old EpiData version
by epidata-list＠lists.umanitoba.ca 29 Jun '11

29 Jun '11

Hi, I have imported a .qes file into EpiData Manager and re-saved it in the new format. The document is a questionnaire and I am trying to make updates to the fields. I have two questions... 1) Is it possible to insert a new text field in between two already established fields? 2) I've noticed that the label names no longer show up on the form; will this effect coding capabilities? Thanks for the assistance. -------------------------------------------------------------------------------------------------------- Jonathan E. Outbreak Management Division Centre for Food-borne, Environmental and Zoonotic Infectious Diseases Infectious Disease Prevention and Control Branch Public Health Agency of Canada

1 2

SV: [EpiData-list] It is possible to have labels that are inconsistent with previously entered data
by epidata-list＠lists.umanitoba.ca 18 Jun '11

18 Jun '11

Hi David It is correct that neither Manager nor EntryClient checks the datafile for consistency upon opening. We are thinking that this type of check will be available as a tool within Manager and/or Analysis. Since these are the programs used by the project maintainers. Please feel free to discuss if this is sufficient or another solution is better. Kind regards, Torsten Bonde Christiansen. Epidata Association. ----- Reply message ----- Fra: epidata-list(a)lists.umanitoba.ca Dato: fre., jun. 17, 2011 19:45 Emne: [EpiData-list] It is possible to have labels that are inconsistent with previously entered data Til: <epidata-list(a)lists.umanitoba.ca> Hi, Using the new data manager and client it is possible to create a data entry system, enter data, then add labels that don't match the labels. E.g. enter "dogs", "cats", "cows" then add labels for that field that only has "dogs" and "cats". This results in the labels defined in the XML file not matching the previously entered data. One solution is "don't do that!" but at the moment it is too easy to do so, possibly accidentally. I've certainly seen situations where a data entry system has evolved. Removing a set of labels removes the link between the labels and the field (and warns before doing so) and I wonder if epidata should also warn when creating this inconsistency. It could potentially mean a lot of checking if the data file is large and the set of labels is used for many fields. I wouldn't want the system to over-write any data, but perhaps have a way of reporting which fields and values are inconsistent with the label set. David -- _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 2

It is possible to have labels that are inconsistent with previously entered data
by epidata-list＠lists.umanitoba.ca 17 Jun '11

17 Jun '11

Hi, Using the new data manager and client it is possible to create a data entry system, enter data, then add labels that don't match the labels. E.g. enter "dogs", "cats", "cows" then add labels for that field that only has "dogs" and "cats". This results in the labels defined in the XML file not matching the previously entered data. One solution is "don't do that!" but at the moment it is too easy to do so, possibly accidentally. I've certainly seen situations where a data entry system has evolved. Removing a set of labels removes the link between the labels and the field (and warns before doing so) and I wonder if epidata should also warn when creating this inconsistency. It could potentially mean a lot of checking if the data file is large and the set of labels is used for many fields. I wouldn't want the system to over-write any data, but perhaps have a way of reporting which fields and values are inconsistent with the label set. David --

1 1

Epidata XML to R: how to handle labels?
by epidata-list＠lists.umanitoba.ca 14 Jun '11

14 Jun '11

I would like to hear opinions about using epidata labels when importing into R. Here's a fragment of XML showing a value label set from sample.epx that comes with the data manager. <ValueLabelSet id="valuelabelset_id_1"> <Type>3</Type> <Name>Float Set</Name> <Internal> <ValueLabel order="1" value="1,11"> <Label lang="en">Float value A</Label> </ValueLabel> <ValueLabel order="2" value="2,22"> <Label lang="en">Float value B</Label> </ValueLabel> <ValueLabel order="3" value="3,33"> <Label lang="en">Float value C</Label> </ValueLabel> <ValueLabel order="4" value="8,88" missing="true"> <Label lang="en">Second last missing</Label> </ValueLabel> <ValueLabel order="5" value="9,99" missing="true"> <Label lang="en">Float missing</Label> </ValueLabel> </Internal> </ValueLabelSet> This says that a numeric (float) variable that uses this label set should give the numeric value 1.11 the label "Float value A", etc. and defines two types of missing value: 8.88 and 9.99. R does not have a concept of labelling values in this way (unless things have changed recently; I have not kept up with the R list for a couple of years or so). R also does not have the concept of multiple missing values, you either have a value to work with, or you don't. It is possible to attach a comment to an R object, but these are not transferred when an object is copied, so they can easily become lost. I think we have the following options: 1) use the actual stored value (e.g. 1.11), ignore the labels except for the missing value definitions and for these just make them NA. This loses information that might be useful, but means that numeric values (and dates, etc) keep their data type and can be analysed appropriately, i.e. it is possible to calculate the mean of 1.11, but not the mean of "Float value A"; 2) use the labels in all cases. The result of this is the opposite of option 1: we keep the extra information that the labels provide, but coerce all data to characters/factors and can no longer do many statistical analyses; 3) create a new column for each variable that uses a label set, so that we have both the original data and next to it a column with the labels. This could result in a much larger data set in R, and possible confusion, especially if analyses change the value of one column and not the other. 4) Code in options 1-3, allowing the user to specify which approach to take; 5) Code in options 1-3, allowing the user to specify for each column which approach to take. 6) Do nothing at all to the data, just return the label information as part of the result of the read function (in the same way that the table structure is returned and the study meta data will be returned) so that the user can then easily read it in R and use it to recode variables/values appropriately. This would mean manually recoding missing values. I could write functions that are able to work with this information so that users can then fairly easily query the label set representation to find out the label information. In R this could work like this, assuming that x is an object that contains label information: epidata.label.value(1.11, x, "Float Set") > "Float value A" epidata.label.value(8.88, x, "Float Set") > "Second last missing" ## If the value is not in the value set, return NA epidata.label.value(1.66, x, "Float Set") > NA is.epidata.label.na(1.11, x, "Float Set") > FALSE is.epidata.label.na(8.88, x, "Float Set") > TRUE is.epidata.label.na(1.66, x, "Float Set") > NA As I work through this I am tending towards option 6; I would probably have to write functions like this anyway, and I think that making them visible to the user provides the greatest flexibility and probably limits the risk of being surprised. Recoding a variable in R using the labels would then work like this, assuming that x is an object created by importing an epidata XML file into R, and that the dataframe contains a field called "height": ## Extract the data frame and labels into new objects to make the code easier to read y <- x[[1]] z <- x[["value.labels"]] ## Apply the labels y$height <- epidata.label.value(y$height, z, "Float Set") ## Set the missing values is.epidata.label.na(y$height, z, "Float Set") <- NA David -- David Whiting, PhD | Senior Epidemiology & Public Health Specialist tel +32-2-6437945 | mob +32-496-266436 | David.Whiting(a)idf.org International Diabetes Federation 166 Chaussée de La Hulpe, B-1170 Brussels, Belgium tel +32-2-5385511 | fax +32-2-5385114 info(a)idf.org | www.idf.org | VAT BE 0433.674.528 IDF | Promoting diabetes care, prevention and a cure worldwide

1 6

question about double entry
by epidata-list＠lists.umanitoba.ca 14 Jun '11

14 Jun '11

Hello My question is if there are any possibilities to check up for double entry in EPIDATA ? Susann R Susann Regber Pediatric nurse, MPH, PHD-student Nordic School of Public Health Tel.: +46 (0)31 69 39 01 Mobile: +46(0) 738 19 04 19 E-mail: susann.regber(a)nhv.se Homepage: www.nhv.se P.O. Box 12133, SE-402 42 Gothenburg

1 1

Value labels and variable labels in R
by epidata-list＠lists.umanitoba.ca 14 Jun '11

14 Jun '11

Hello EpiData (Dungeons & Dragons :-D) Masters, I did read this post but after a second reply the messages get a little confused. So please forgive me if Im a little repetitive. I see at least three types of labels: 1. Data label 2. Variable label 3. Value label Im not aware of any data label function in R. In R, the variable label is the variable name, which is the charater vector on the top of the columns. So, if you have a dataset on object *data* and type > labels(data) # It will returns the columns and rows names > colnames(data) # will return the same columns names as labels. Value labels does not make sense in R, because labels are a discription of numeric values which represent categories. Thus, these numbers are not really numbers, rather categories. Most importing functions transforms these into factors, which will make sense in most analysis functions. What are value labels for? If you run a table analysis the labels comes in place of 1 or 2 or 99 or whatever values the labels should represent. R does it through the factors and their levels. What are the variable labels for? If you run a table analysis the labels comes in marginals in place of the variables names (in this case as dimnames()) that could be something meaningless such as v22. However the table and other functions in R do not recognize labels wherever they are. Thus importing variable labels would be of little use. Im awere of two packages that have importing functions that bring together with the data the variable labels and transform the value labels into factors, and uses these variables labels at the analysis functions automatically. epicalc and rms. epicalc does through the label.var()functionand Im not really sure where the label is stored. rms (or perhaps Hmisc... not sure) package uses the label() function - not the labels() function - and store the labels as attributes of each variable. If you type for example > attr(data$v22) # the label should appear as one of the variable attributes such as 'Age' or 'Sex'. Both packages uses these functions throughout all analysis functions and have functions to print a map of labels such as describe() and desc(). Describe is more rich and also returns some summaries of the variables. rms also has a datadist() function which is able to store at the R option() the distributions of variables values, which may be useful to set potential values in analysis tha your data is not representing (such as a bar plot that should range from 10 to 80 but your lowest and highest values are 12 and 68). But see, these variable labels will only work on analysis functions of epicalc if I use the importing function from epicalc - use() - and for rms if I use the rms importing functions - stata.get(), spss.get(), sas.get(). If I import with stata.get for example and run analysis with any other package than rms, the labels are ignored. :-( At the moment, I cant see how these can be improved unless a package EpiData comes along with analysis functions that automatically call the variable labels on tables and graphs. If variables labels are to be imported then storing them as variable attributes seems to be reasonable, instead of storing them at a second column in the same dataframe. But the way I see, the next step (analysis functions to be used) is the one that should guide how labels should be handled. Kind regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com - sistema operacional

1 1

Reading the new XML files into R
by epidata-list＠lists.umanitoba.ca 12 Jun '11

12 Jun '11

To save me maybe re-inventing the wheel, has anyone looked at reading the new native XML files directly into R, ideally with SQL queries. There is an XML package for R http://www.omegahat.org/RSXML/c but it would be really useful if someone more capable than me, had already put together a method. Many thanks, Graham

1 20

release candidate of Manager
by epidata-list＠lists.umanitoba.ca 10 Jun '11

10 Jun '11

Dear All A "feature complete" version of EpiData Manager has been uploaded today - the expectation (read as "hope") is, that this version with bug removal can be released as version 1.0 * *NEW: *Create reports in HTML format using "Tools" * Default settings for a project * Change font and colour in program settings The reports on project structure (question lists, value label lists, combined lists) are produced when you click on tools menu. All epx/epz files in that folder are included. (Notice they must be of most recent format). For Entry Client a similar version will be released within the next days . The following aspecs will be fixed/clarified before release: a. A Proper About box will be added. b. For reports a grid of included files will be shown to the user - just like "add structure" to allow for in- and exclusion of single files. c. known and reported bugs. d. any bugs reported from now on by users. e. updating of documentation on the wiki. Another interesting development has taken place in the last week. We have localised an open-source based cross-platform testing system for interactive simulation of user behavior. We will spend some energy and time to develop validation tests to secure that the visual interface behaves properly after each new compilation. More news on this later. Therefore please: Now is the time to challenge the software and report problems and viewpoints on the products - before releasing as v1. Documentation and instruction files could be more elaborate obviously - this will come later. In practice it has turned out, that unless features work almost without instruction, users will not use it. Kind regards Torsten Christiansen Jens Lauritsen EpiData Association Denmark

1 5

new version of command line tool
by epidata-list＠lists.umanitoba.ca 06 Jun '11

06 Jun '11

Yesterday a new version of the command line template parser tool was compiled based on the most recent html structure for the epx files. Users can read more about this tool on: http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat (the documentation will be finalised, but in general is correct) And get the updated version from: http://www.epidata.dk/testing.php regards Jens Lauritsen EpiData Association

1 1

request of help
by epidata-list＠lists.umanitoba.ca 03 Jun '11

03 Jun '11

Dear members in the group, I will be teaching an course of bioestatistics to a group of psychiatry residents. The idea is to teach statistic methodology but using scientific papers related to psychiatry. I would appreciate if any of you have some papers with the databases that could provide me. Best wishes Jose Farfan Mexico

1 0

new test release of Manager and Entry Client
by epidata-list＠lists.umanitoba.ca 02 Jun '11

02 Jun '11

Dear List. Today we have release updated versions of the EpiData Manager and EntryClient programs. The release today is a minor test release with focus on Manager enhancements and user customization. Common fixed/changes: * Is is now possible to change font type, size and colour in both programs. This is done independently of the project. * A long standing problem where a projectfile contained exactly 13 fields would make the programs crash during load is finally fixed. * Other minor bugs related to importing/exporting to stata have been fixed. Manager: * The "import/add structure" window now gives the user the option of keeping/renaming field and valuelabels if types and names match (produces smaller/smarter project files if there are overlapping fields/valuelabels). * In the program settings is it possible to define a default setup for a new project. * Using the "tools" no longer requires the project file to be open. * Using "importing structure" could under some circumstances produce fields without fieldnames. * Several bugfixes related to deleting field(s) involved in calculations, jumps, etc. Entry: * Font changes as described above. * Some minor bug-fixes. During the most recent weeks experimentation has been made with the creation of pdf formatted reports on structure, labels etc. Unfortunately we had to stop the pdf development due to various reasons and time constraints. Instead an html based solution will be created. This will be part of next test release. Kind regards, Jens Lauritsen and Torsten Bonde Christiansen EpiData Association.

1 3

fill fields from COMMENT LEGAL file
by epidata-list＠lists.umanitoba.ca 01 Jun '11

01 Jun '11

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,

1 1

RE EpiData-list Digest, Vol 91, Issue 9 - EpiData statistics documentation.
by epidata-list＠lists.umanitoba.ca 30 May '11

30 May '11

Lu 30 mai 2011 Hello Jamie, Thank's for your quick answer. You are the spirit of EpiData users. I'll try to get this reference book. I would be glad to work with you about this topic and for the cause of EpiData. If it may help Jens, it will help us all. Cordialement, Réjean Dion, M.D. epidata-list-request@lists.umanitoba.ca@lists.umanitoba.ca Envoyé par : epidata-list-bounces(a)lists.umanitoba.ca 2011-05-30 13:00 Veuillez répondre à epidata-list(a)lists.umanitoba.ca A epidata-list(a)lists.umanitoba.ca cc Objet EpiData-list Digest, Vol 91, Issue 9 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. EpiData statistics documentation. (epidata-list(a)lists.umanitoba.ca) 2. Re: EpiData statistics documentation. (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 May 2011 10:30:02 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData statistics documentation. To: epidata-list(a)lists.umanitoba.ca Message-ID: <OFCEE0BD3B.825D84B0-ON852578A0.004A567F-852578A0.004FA7C8(a)isn.rtss.qc.ca> Content-Type: text/plain; charset="ISO-8859-1" Lu 30 mai 2011 Hello EpiData users, I'm a new subscriber to this list. I used recently EpiData Analysis for a matched case-control with a controls:case ratio of 38:19 or 2:1 (TAB DISEASE EXPOSURE COMMONID /O /t /ex). In the results output, and in the online help, for the crude table, I could'nt find the type of test used, for example, which kind of Chi-square (I was able to deduced it was uncorrected), of odds ratio (maximun likelihoodestimate [MLE]?) and associated confidence interval (95%?), and Fishers exact test (bilateral?). In the adjusted table, the OR [MLE?] is provided with a CI (MLE and 95%?), followed by a Chi-square (unspecified kind) and another p value (which kind?). The provided p values are rounded at 3 digits after the decimal point. The last column provide p-exact values (Fishers?), and the one on the adjusted line seems to refer to another Chi-squared provided at the bottom of the table. Finally, the exact p value for the adjusted results (e.g.: 0.3140) doesn't match with the "probability of MLE >= value of MLE of OR (e.g. 6.10) if population OR = 1.0" that I obtain (e.g..: 0.00196) with the command MATCH COMMONID DISEASE EXPOSURE of Epi Info 6.04d DOS (which is probably equivalent to an exact test), and seem discordant with the values of the CI (e.g.: 1.62 to 34.17). Using the cohort approach (TAB DISEASE EXPOSURE /RR /t /ex), I found similar lack of documentation about statistical tests. I would suggest the following to the conceptors of EpiData: - provide some documentation about statistical tests used in Analysis (do any of the users have those answers?); - provide notes at the bottom of tables to eliminate any ambiguities about statistical methods; - provide p values in the ajusted table with 4 digits after the decimal point. This software work pretty well, but need some ajustments. Keep on the good work. Best regards, Réjean Réjean Dion, M.D. Médecin-conseil en santé publique (maladies infectieuses) Institut national de santé publique du Québec (INSPQ) / Laboratoire de santé publique du Québec (LSPQ) 20045, chemin Sainte-Marie, Sainte-Anne-de-Bellevue (Québec) Canada H9X 3R5 Tél.: (514) 457-2070 poste 325 Fax.: (514) 457-6346 Courriel / Lotus Notes: rejean.dion(a)inspq.qc.ca ------------------------------ Message: 2 Date: Mon, 30 May 2011 11:02:37 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] EpiData statistics documentation. To: epidata-list(a)lists.umanitoba.ca Message-ID: <BLU0-SMTP98AFF72F724FC7BE103867FD7B0(a)phx.gbl> Content-Type: text/plain; charset="iso-8859-1" Hi Réjean, The current version uses the statistics recommended in the book Statistics with Confidence: Confidence intervals and statistical guidelines, 2nd Edition Douglas Altman (Editor), David Machin (Editor), Trevor Bryant(Editor), Stephen Gardner (Editor) ISBN: 978-0-7279-1375-3 The help file references this book only with respect to Confidence Intervals. I agree that, in time, a more complete description of the statistical results is warranted. That's something we might want to work together on, to give Jens a hand--what do you think? This version of Analysis does not provide an option to increase the number of decimal positions shown with statistics, but more precise results are available from results variables such as $exact The command result shows all of the results accessible to the user. Jamie Hockin ------------------------------ End of EpiData-list Digest, Vol 91, Issue 9 *******************************************

1 0

EpiData statistics documentation.
by epidata-list＠lists.umanitoba.ca 30 May '11

30 May '11

Lu 30 mai 2011 Hello EpiData users, I'm a new subscriber to this list. I used recently EpiData Analysis for a matched case-control with a controls:case ratio of 38:19 or 2:1 (TAB DISEASE EXPOSURE COMMONID /O /t /ex). In the results output, and in the online help, for the crude table, I could'nt find the type of test used, for example, which kind of Chi-square (I was able to deduced it was uncorrected), of odds ratio (maximun likelihoodestimate [MLE]?) and associated confidence interval (95%?), and Fishers exact test (bilateral?). In the adjusted table, the OR [MLE?] is provided with a CI (MLE and 95%?), followed by a Chi-square (unspecified kind) and another p value (which kind?). The provided p values are rounded at 3 digits after the decimal point. The last column provide p-exact values (Fishers?), and the one on the adjusted line seems to refer to another Chi-squared provided at the bottom of the table. Finally, the exact p value for the adjusted results (e.g.: 0.3140) doesn't match with the "probability of MLE >= value of MLE of OR (e.g. 6.10) if population OR = 1.0" that I obtain (e.g..: 0.00196) with the command MATCH COMMONID DISEASE EXPOSURE of Epi Info 6.04d DOS (which is probably equivalent to an exact test), and seem discordant with the values of the CI (e.g.: 1.62 to 34.17). Using the cohort approach (TAB DISEASE EXPOSURE /RR /t /ex), I found similar lack of documentation about statistical tests. I would suggest the following to the conceptors of EpiData: - provide some documentation about statistical tests used in Analysis (do any of the users have those answers?); - provide notes at the bottom of tables to eliminate any ambiguities about statistical methods; - provide p values in the ajusted table with 4 digits after the decimal point. This software work pretty well, but need some ajustments. Keep on the good work. Best regards, Réjean Réjean Dion, M.D. Médecin-conseil en santé publique (maladies infectieuses) Institut national de santé publique du Québec (INSPQ) / Laboratoire de santé publique du Québec (LSPQ) 20045, chemin Sainte-Marie, Sainte-Anne-de-Bellevue (Québec) Canada H9X 3R5 Tél.: (514) 457-2070 poste 325 Fax.: (514) 457-6346 Courriel / Lotus Notes: rejean.dion(a)inspq.qc.ca

1 1

header intact
by epidata-list＠lists.umanitoba.ca 27 May '11

27 May '11

thank you Deepthi Sutapalli

1 0

FW: Multiple Forms like Tabs in Internet Explorer
by epidata-list＠lists.umanitoba.ca 19 May '11

19 May '11

I would like to know that, Is there any option to open different Data Entry Forms in One program Like opening different sites in Internet Explorer? Thanks & Regards Rasool Bux Sr. Data Management Coordinator & Data Manager, Hypertension Research Program, Community Health Sciences Department, Aga Khan University, Stadium Road, P.O. Box 3500, Karachi 74800. Pakistan. Office Contact: +9221-34864897, +9221-34864812 Fax Number: +9221-3494294, +9221-34932095 ________________________________ This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.

1 4