- EpiData-list - University of Manitoba Mailing Lists

Re: [EpiData-list] EpiData-list Digest, Vol 148, Issue 1
by EpiData development and support 17 Apr '16

17 Apr '16

Dear Konan Diby, Currently Epidata is meant for desktop and not mobile, I stand for correction.However there are various version of other software which are free you can use for your data collection. CSpro and Epiinfo are some public software you can use for free and they have mobile platform. Hope this information, will be useful to you. Regards, Sedzro On Sun, Apr 17, 2016 at 5:00 PM, <epidata-list-request(a)lists.umanitoba.ca> wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > EpiData-list mailing list > ___________________________________ > Today's Topics: > > 1. Epidata on Smartphone? (EpiData development and support) > 2. Re: Epidata on Smartphone? (EpiData development and support) > > > ---------- Forwarded message ---------- > From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > To: Epidata <epidata-list(a)lists.umanitoba.ca> > Cc: > Date: Sun, 17 Apr 2016 08:01:30 +0000 (UTC) > Subject: [EpiData-list] Epidata on Smartphone? > Hello everyone, > I have to conduct a survey for which we decided to use Epidata for data > collection. > Could anyone tell me if it is possible to install Epidata on a smartphone? > If so, I shall be happy to know the procedure.Best regards > _______________________________________Konan Diby JP, MD, MPH > Attaché de Recherche > Labo. Biostatistique & Informatique Médicale > UFR Sciences Médicale, Univ. F. Houphouët-Boigny > 22 BP 1041 Abidjan 22, Côte d'Ivoire > Tel./Fax: (+225) 22 401 403 > GSM: (+225) 05 994 326 / 07 250 561 > skype's: dibykonanjp > > > > ---------- Forwarded message ---------- > From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > To: EpiData List <epidata-list(a)lists.umanitoba.ca> > Cc: > Date: Sun, 17 Apr 2016 08:17:28 -0400 > Subject: Re: [EpiData-list] Epidata on Smartphone? > I expect that you can get the Linux version of EpiData EntryClient running > on an Android phone or tablet, but it won’t be simple. > See > https://www.androidpit.com/turn-your-android-device-into-a-linux-pc-without… > < > https://www.androidpit.com/turn-your-android-device-into-a-linux-pc-without… > > > I have not tried this and don’t intend to, but this could be interesting. > > > I have to conduct a survey for which we decided to use Epidata for data > collection. > > Could anyone tell me if it is possible to install Epidata on a > smartphone? > > If so, I shall be happy to know the procedure.Best regards > > _______________________________________Konan Diby JP, MD, MPH > > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > -- ............................... * MENSAH KOJO SEDZRO* Postal P.O.Box AS 387| Ashaiman -Tema | Ghana Skype: rasbesa web rasbesafari.blogspot.com House : +233-303-300789 Cell : +233-244-458788 *“If there is a problem to be solved, seek statistical advice instead of appointing a committee of experts. Statistics can throw more light than the collective wisdom of the articulate few by Crammer Rao”* *DISCLAIMER**:* 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, re-transmission 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

Epidata on Smartphone?
by EpiData development and support 17 Apr '16

17 Apr '16

Hello everyone, I have to conduct a survey for which we decided to use Epidata for data collection. Could anyone tell me if it is possible to install Epidata on a smartphone? If so, I shall be happy to know the procedure.Best regards _______________________________________Konan Diby JP, MD, MPH Attaché de Recherche Labo. Biostatistique & Informatique Médicale UFR Sciences Médicale, Univ. F. Houphouët-Boigny 22 BP 1041 Abidjan 22, Côte d'Ivoire Tel./Fax: (+225) 22 401 403 GSM: (+225) 05 994 326 / 07 250 561 skype's: dibykonanjp

1 1

SAS export
by EpiData development and support 17 Mar '16

17 Mar '16

Hi all, I have a problem with SAS export in Epidata manager (v2.0.8.56). The SAS program generated by the software is unable to read the CSV file created. In other words, the program is written to import fixed column file and The CSV is comma separated. Has anybody a solution to fix the problem? (Except rewriting the SAS program to fit the datafile format) Thanks, Jean-Marc VIRION Service d'Épidémiologie & Évaluation Cliniques Centre d'Épidémiologie Clinique, CIC-EC Inserm CHRU de Nancy

1 1

EpiData question / help
by EpiData development and support 08 Mar '16

08 Mar '16

HI I am accustomed to using JUMP when the 'jump to' questions are the next (consecutive) questions. IS there a way to use JUMP or something else to 'jump to' a future question ? For example, here is the order of the questions : Q1 Age Q2 Status 1=Self 2=Other Q3 Gender 1=Female 2=Male Q4 Systolic blood pressure Q5 Diastolic blood pressure Q6 Height Q7 Weight JUMP if Q2=1 then Jump to Q4 (the order Q2, Q3, Q4) if Q2=2 then Jump to Q6 (the order Q2, Q3, Q6) Thank you.

1 1

Drag-dropping a prior created field into a section
by EpiData development and support 26 Feb '16

26 Feb '16

EpiData Manager: (2016/02/26 - 18:33:39)Program Version: 2.0.8.56 r1286Core version: 2.0.0.0 r1254FPC Version: 2.6.4Platform: i386-Darwin Is there a way to move a field inside a section if the field was created BEFORE the section? As it is if I forgot to create the section before am not able to drag-drop or cut-paste a previously created field into a newly created section. Manager v2.0.8.56 PhilipKenya Please use the alternate email powiti(a)ampath.or.ke for any AMPATHplus communication---------------------------------------- Philip OwitiCell: +254 720 678625 skype/twitter: p_owiti Alternate email: powiti(a)ampath.or.ke ____________________________________ We must add life to years inasmuch as we endeavor to add years to life! CallSend SMSAdd to SkypeYou'll need Skype Credit

1 1

aggregate counts
by EpiData development and support 25 Feb '16

25 Feb '16

Dear colleagues from my rec file with individual data I created and aggregate file with district, agegroup and year of notification. For each combination I have a cummulative count of cases. Now I am not able to use this aggregate table as it was possible in Epiinfo v6. Something like: sumtable agegroup n /by=district (to have a agegroup table with cumulative numbers for each district) Thanks for advise -- Vladimír Príkazský tel: +46 858 601 636 fax: +46 858 601 001 mobil: +46 *720 436 206* _____________________________ Motto: :-) Kam chodi slunce, nechodi doktor! An apple a day keeps the doctor away!

1 1

Child records
by EpiData development and support 20 Jan '16

20 Jan '16

Dear all, I have experienced the same thing in the past. But I must admit that it's really brilliant what epiData has done. In the dataform property of child form, there are two options to choose for having records. No limit (If we want limitless numbers of child records, this is the option) fixed limit (which EpiData has set its value to 1 by default) Because of option 2, more than one child records can't be created. And option 1 or 2 with big numbers will be the solution to creating more than one child records. Best, Myo -- Myo Minn Oo, M & E Officer (HIV Unit) (original message trailer edited by list administrator)

1 0

Creating new records in child file
by EpiData development and support 20 Jan '16

20 Jan '16

Manager v2.0.8.56 EntryClient v2.0.7.22 Windows 10 Home Hi all, I am trying to build a relational database with 1 parent and 2 child dataforms. When entering data, I could not enter more than one records in child dataforms. I could create new parent data form though. Any help would be appreciated. Thanks. Best wishes, Zaw

1 1

Need help for designing form on Epidata manager.
by EpiData development and support 16 Dec '15

16 Dec '15

Dear Sir/Madam, I am trying to design a form using Epidata Manager v2.0.8.56. I need urgent help on the following: 1. How to link multiple forms under one project through unique key? I will have four forms needed to be linked through unique ID. These forms will be filled by different data entry persons. 2. How can I put questions in two lines containing two different fonts? It is needed to give translation of question in local language. Thanking in advance. Warm regards, Peeyush peeyush1902(a)gmail.com

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 144, Issue 1
by EpiData development and support 15 Dec '15

15 Dec '15

Dear Jens Thank you That was very helpful regards Thambu ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca <epidata-list-bounces(a)lists.umanitoba.ca> on behalf of epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Sent: Sunday, December 13, 2015 11:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 144, Issue 1 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-list Digest, Vol 143, Issue 6 (EpiData development and support) 2. Re: EpiData-list Digest, Vol 143, Issue 6 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 12 Dec 2015 19:03:58 +0000 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: "epidata-list(a)lists.umanitoba.ca" <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 143, Issue 6 Message-ID: <1449947036534.70875(a)cmcvellore.ac.in> Content-Type: text/plain; charset="iso-8859-1" Dear All While trying to export from Manager and i have related data forms how do i export. Two separate forms are exported. Do i use stata to merge them? Is there a way of merging the files as 1 in manager/client and then exporting them? Thanks Thambu ------------------------------ Message: 2 Date: Sat, 12 Dec 2015 21:58:20 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 143, Issue 6 Message-ID: <107FB122-4797-4548-8894-38330BEC98A2(a)epidata.dk> Content-Type: text/plain; charset=UTF-8 You just export to one file per dataform in the project as you indicate. Afterwards merge the files with the correct relation in Epidata analysis or In Stata use dataform1 merge 1:1 key variables using dataform2 Continue with other dataforms. Maybe sometimes you need to summarize within a key before merge. use visits gen N = 1 collapse (sum) N (min) hb , by(id) save sumvisit And then merge to other data on id. Since we cannot know in Epidata how you wish to analyze the related dataforms we will not develop this in manager, but do remember that as well collapse and merge can be made with epidata analysis. Regards jens Lauritsen On 12. dec. 2015 20.03.58 CET, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: > >Dear All >While trying to export from Manager and i have related data forms how >do i export. Two separate forms are exported. Do i use stata to merge >them? Is there a way of merging the files as 1 in manager/client and >then exporting them? >Thanks >Thambu >_______________________________________________ >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 144, Issue 1 ********************************************

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 143, Issue 6
by EpiData development and support 12 Dec '15

12 Dec '15

Dear All While trying to export from Manager and i have related data forms how do i export. Two separate forms are exported. Do i use stata to merge them? Is there a way of merging the files as 1 in manager/client and then exporting them? Thanks Thambu

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 143, Issue 5
by EpiData development and support 25 Nov '15

25 Nov '15

Thank you very very much for your help I will try it today Again thanks Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion _____ From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 25 Nov 2015 22:00:24 +0400 Subject: EpiData-list Digest, Vol 143, Issue 5 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: NEED OF HELP ON EPIDATA. DATES MANAGEMENT. RELATIVELY URGENT PLEASE (EpiData development and support) 2. Experimental Release of EpiData Manager/EntryClient (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 24 Nov 2015 20:12:25 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] NEED OF HELP ON EPIDATA. DATES MANAGEMENT. RELATIVELY URGENT PLEASE Message-ID: <5654B699.5080304(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Pierre-Yves: In EpiData Analysis: select bd>dmy(30,04,2013) and bd<dmy(01,08,2014) [the zero's are not necessary]. In Help (F1) go to Functions, and look for Date functions. Best regards, Hans On 24-Nov-15 07:34, EpiData development and support wrote: > > Hello > > How do you handle the dates in Epidata? > I want to select a database from june 2013 to july 2014 (birthdate "BD") > If I do like in Epiinfo > > select bd > "30/04/2013" and bd < "01/08/2014" > it does not work . I havez tried with and without "", or commas, and no result > > > I HAVE BEEN STUCK FOR 3 DAYS > > Can you help me? > > Best regards > > > > Dr Pierre-Yves Robillard > R?animation n?onatale et pediatrique, n?onatologie > Centre Hospitalier R?gional > Groupe Hospitalier Sud-R?union > BP 350. 97448 Saint-Pierre cedex > Ile de la r?union > > -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ Message: 2 Date: Wed, 25 Nov 2015 15:05:57 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Experimental Release of EpiData Manager/EntryClient Message-ID: <5655C045.3000002(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Dear List. It is with great pleasure that we announce the next experimental release of EpiData Manager and EpiData EntryClient. The main new aspects are: 1. Controlled user login (Extended Access): With Extended Access users can have different roles in a project, some may change the structure of data and others only enter data or reset passwords for other users. This extends the security of the project from encryption of data to encryption of the whole project. For entry of data rights to edit and read data is defined at the dataform level. A full explanation of how you work with user controlled login is available from the testing download page: http://www.epidata.dk/testing.php. Anexample project is included with the installation package, this includes an extension of the "Clinical Example Project" with defined groups. A readme.txt contains user name and password. 2. Customised Statusbar: In addition to a modernised design the content of the Statusbar can now be adapted with various elements. The Dataform Information panel can display a text or contents of the currently active dataform. For those familiar with the old EpiData Entry 3.1 this is much like the "type statusbar" command of the .chk file. Please notice that as usual: DO NOT use the experimental version for routine work and do not use on your real projects. Work on copies of data. Changes to data structure and definitions will change until the features are included in public release versions. Please test the following: 1. Addition of users to the example project to defined groups. 2. Addition of groups and rights for a project you start from scratch. 3. The new statusbar Next phase of development will focus on these aspects: a. recording of what the user did after logging into a project (transaction log) b. reporting of defined groups and users in a given project. You find the experimental versions here: http://www.epidata.dk/testing.php Regards, Torsten B. Christiansen & Jens M. Lauritsen EpiData Association, Denmark. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 143, Issue 5 ******************************************** -- Ce message a été vérifié par le CHU de la Réunion. -- Ce message a été vérifié par le CHU de la Réunion.

1 0

Experimental Release of EpiData Manager/EntryClient
by EpiData development and support 25 Nov '15

25 Nov '15

Dear List. It is with great pleasure that we announce the next experimental release of EpiData Manager and EpiData EntryClient. The main new aspects are: 1. Controlled user login (Extended Access): With Extended Access users can have different roles in a project, some may change the structure of data and others only enter data or reset passwords for other users. This extends the security of the project from encryption of data to encryption of the whole project. For entry of data rights to edit and read data is defined at the dataform level. A full explanation of how you work with user controlled login is available from the testing download page: http://www.epidata.dk/testing.php. Anexample project is included with the installation package, this includes an extension of the "Clinical Example Project" with defined groups. A readme.txt contains user name and password. 2. Customised Statusbar: In addition to a modernised design the content of the Statusbar can now be adapted with various elements. The Dataform Information panel can display a text or contents of the currently active dataform. For those familiar with the old EpiData Entry 3.1 this is much like the "type statusbar" command of the .chk file. Please notice that as usual: DO NOT use the experimental version for routine work and do not use on your real projects. Work on copies of data. Changes to data structure and definitions will change until the features are included in public release versions. Please test the following: 1. Addition of users to the example project to defined groups. 2. Addition of groups and rights for a project you start from scratch. 3. The new statusbar Next phase of development will focus on these aspects: a. recording of what the user did after logging into a project (transaction log) b. reporting of defined groups and users in a given project. You find the experimental versions here: http://www.epidata.dk/testing.php Regards, Torsten B. Christiansen & Jens M. Lauritsen EpiData Association, Denmark.

1 0

NEED OF HELP ON EPIDATA. DATES MANAGEMENT. RELATIVELY URGENT PLEASE
by EpiData development and support 24 Nov '15

24 Nov '15

Hello How do you handle the dates in Epidata? I want to select a database from june 2013 to july 2014 (birthdate "BD") If I do like in Epiinfo select bd > "30/04/2013" and bd < "01/08/2014" it does not work . I havez tried with and without "", or commas, and no result I HAVE BEEN STUCK FOR 3 DAYS Can you help me? Best regards Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion -- Ce message a été vérifié par le CHU de la Réunion.

1 2

Updated versions Manager 2.0.8.56 & EntryClient 2.0.6.20
by EpiData development and support 07 Nov '15

07 Nov '15

Dear all users New versions were placed yesterday for general download on http://www.epidata.dk/download.php Many bugs have been fixed during recent releases and we therefore encourage all to get the new versions and replace older ones. The new versions will work with all epx project files. But it is always good practice to have a backup copy if some unexpected problem shows up. The two updated versions fixes several details of related file systems and export. Related file principles are now sufficiently developed for routine use, including handling of "mark for deletion", "count by id", "compare duplicate", export etc. See the complete list of changes here: Http://epidata.dk/epidatamanager.changelog.txt Http://epidata.dk/epidataentryclient.changelog.txt Conversion from flat file systems to related structure is rather simple, provided you define the keys correctly. A step by step recipe for this will be published here later and added to the wiki system at http://epidata.info/dokuwiki/doku.php?id=start Regards Jens Lauritsen EpiData Association, Denmark

1 2

Export into Excel
by EpiData development and support 02 Nov '15

02 Nov '15

Dear all, I was using the old version of EpiData. I am not a statistician. Now I wanted to use the EpiData at my new workplace, had to install the new version and am struggling with the export into Excel. The export is possible but then I get a table in Excel where everything is together, in one column. Is it a bug, will it be fixed or am I doing something wrong? I tried to read everything but I am not coming further. Please help. Thank you. Lukas

1 0

New MOOC course features Epidata
by EpiData development and support 02 Sep '15

02 Sep '15

Epidata list members may be interested to know that Epidata is featured in a new MOOC (Massive Open On-line course) soon to be offered as part of the by Peking University. It is called Using Software apps in epidemiological research. For those who are not familiar with MOOCS they are free on line courses, often offered by top universities and usually made up of videos, short quizzes and on-line discussion groups. They can have very large enrollment numbers. I enjoy MOOCs and have taken eight or nine already, but I can't do this one as it is in Chinese. Perhaps chinese speaking list members could try it. Here is a link. https://www.coursera.org/course/epiapps?utm_medium=email&utm_source=recomme…. best wishes Christine ______________________________________________________________________________ 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. ______________________________________________________________________________

1 0

Batch conversion of .epx/.epz files to Stata
by EpiData development and support 01 Sep '15

01 Sep '15

Hi! I have a large number of .epx files that require conversion to another format (Stata in this case). Is it possible to do some kind of batch conversion (using the command line tool, for example?). Thanks in advance for the help. María Rodrigo Domingo MSc, PhD, Biostatistician AALBORG UNIVERSITY HOSPITAL Denmark

1 0

Information to user while working with Manager and EntryClient
by EpiData development and support 28 Aug '15

28 Aug '15

Dear all One of the design options we are discussing internally is whether to re-design the "status-bar" at the bottom of Manager and EntryClient. For input to this design, which is now "hard-coded" we are considering implementation of a user defined mode of content. Please discuss or add viewpoints of what you would like to see on a statusbar or information toolbar. Focus on which information you would like to see, not the actual visual design. Although ideas are obviously always welcomed. e.g : key for a project, do we need field names, field types, number of sections etc. Separate the input btw. Manager and EntryClient and whether you wish to have some obligatory and other user defined. Just respond to this mail and the discussion should form a "thread" . If you recieve the digest summary form of mails from the list, then delete other non-relevant parts to make your suggestion more readable. regards before you submit your suggestions. Rember not to include pictures or similar since these are blocked in the system. Jens Lauritsen EpiData Association

1 0

AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 31/08/2015)
by EpiData development and support 24 Aug '15

24 Aug '15

I am out of the office until 31/08/2015. Please contact Carol ODonnell on 074 910 4744 or Tracey McCole on 071 9852900 if you require further assistance, otherwise I will attend to your email when I return Note: This is an automated response to your message "EpiData-list Digest, Vol 141, Issue 10" sent on 24/08/2015 18:00:19. This is the only notification you will receive while this person is away. *************************************************************************** "Tá an fhaisnéis sa ríomhphost seo (ceangaltáin san áireamh) faoi rún. Baineann sé leis an té ar seoladh chuige amháin agus tá sé ar intinn go bhfaighfidh siadsan amháin é agus gurb iadsan amháin a dhéanfaidh breithniú air. Más rud é nach tusa an duine ar leis é, tá cosc iomlán ar aon fhaisnéis atá ann, a úsáid, a chraobhscaoileadh, a scaipeadh, a nochtadh, a fhoilsiú, ná a chóipeáil . Seains gurb iad tuairimí pearsanta an údar atá san ríomhphost agus nach tuairimí FSS iad. Má fuair tú an ríomhphost seo trí dhearmad, bheadh muid buíoch dá gcuirfeá in iúil don.Deasc Seirbhísí ECT ar an nguthán ag +353 71 9820555 nó ar an ríomhphost chuig ICT.Helpdesk(a)hse.ie agus ansin glan an ríomhphost seo ded' chóras." *************************************************************************** "Information in this email (including attachments) is confidential. It is intended for receipt and consideration only by the intended recipient.If you are not an addressee or intended recipient, any use, dissemination,distribution, disclosure, publication or copying of information contained in this email is strictly prohibited..Opinions expressed in this email may be personal to the author and are not necessarily the opinions of the HSE. If this email has been received by you in error we would be grateful if you could immediately notify the ICT Service Desk by telephone at +353 71 9820555 or by email to ICT.Helpdesk(a)hse.ie and thereafter delete this e-mail from your system" ***************************************************************************

1 0

Updated versions of EpiData Manager v2.0.7.53 and EntryClient v2.0.5.17:
by EpiData development and support 24 Aug '15

24 Aug '15

Today new versions have been released today with bug-fixes and minor additions. . Our strategy just now is to release bug-fixes, such that we can focus on development of logging and dataprotection. The EntryClient release today adds the F5 "copy field" with a user format. e.g.: %gd %gn %gf %gp %q,%d,%v%n will now add "global" information such as date and dataform name, see: http://www.epidata.info/dokuwiki/doku.php?id=documentation:clipboardformat Such one can now copy as well current field and whole record to clipboard. For Manager: 2.0.7.53: Texts to describe exports have been added and also a new mechanism to work with dataforms with very many fields and labels. It seems that in practice one should keep number of fields on a given form below 200. More than that will work but with longer load times for the files. A complete list of changes is always shown on the download page in one of these links: http://epidata.dk/epidatamanager.changelog.txt http://epidata.dk/epidataentryclient.changelog.txt . Please inform the list of any non-solved problems or report to the database here: http://www.epidata.info/flyspray As always if you find problems and report to the list include version information, which you easily copy to a mail from the help menu "copy version info" regards Jens Lauritsen EpiData Association

1 0

Access violation message- still unable to open database
by EpiData development and support 12 Aug '15

12 Aug '15

Dear Jamie, Many thanks for your email. Yes there was a lock file in the folder, even though the database was not open in either manager or EntryClient. I have deleted this. Now when I try to open the database in Manager it skips the message 'this file is locked by another program' etc, instead going straight to the Access Violation message. I've used the 'Prepare for double data entry' function, but the _double database file also will not open. Any idea how I can adjust the permissions on the file? (On either Mac or PC as it won't open on either). Seeing as I can open it in EntryClient is there any way I can save this database through Entry Client and get it back to a new Manager file? Best wishes Laura

1 2

Access violation message- unable to open database
by EpiData development and support 11 Aug '15

11 Aug '15

Hi, I am in the middle of creating a database on Epidata Manager v2.0.5.51 for Mac. There is one dataform and no relational databases. There are 13 sections and 468 fields so far. Today when I tried to open the database I get the message: “The file [xxxx] is locked by another program! The file was locked at [last time I tried to open it] by [my username]. Continue opening this file?” If I say No, the box just closes. If I say Yes, the database opens in the background but I get the message: “Access violation. Press OK to ignore and risk data corruption. Press Cancel to kill the program”. I have tried pressing OK many times but I can’t get beyond the error message and can’t access the database which I can see behind it. I can see that I haven't lost any sections of the database since I last saved it last night. If I press Cancel then Epidata Manager shuts down. I’ve been through this process many times. I can open the database on Epidata EntryClient. I can open other databases on Manager with no problem. I have tried opening the ‘problem’ database in the latest version of Manager on a PC but it also doesn’t work. I have downloaded the software again but that doesn’t work. I’ve restarted my Mac.. Any advice on how to open this database again would be very gratefully received. I can’t see any relevant entries on this particular scenario in the archives. Kind regards Laura Dr Laura Asher MBBS MSc MFPH Wellcome Trust Clinical Research Fellow Centre for Global Mental Health, London School of Hygiene and Tropical Medicine /Department of Psychiatry, Addis Ababa University UK Phone: +44 (0) 207 2994668 UK Mobile: +44 (0) 7800 820978 Ethiopia Mobile: +251 (0) 912 649754 Email: laura.asher(a)lshtm.ac.uk

1 1

Epidata Team
by EpiData development and support 11 Aug '15

11 Aug '15

Sir/Madam, I have just upgraded to windows 10. I wish to know the following - 1. Whether the current version of Epidata is compatible with Windows 10? 2. Whether anyone had faced any issues in exporting data from epidata to SPSS Version 21? I am involved in academic field work related to my MPH course requirement. I would be grateful for the feedback on my queries as it might save time in creating platform for data entry based on my interview schedule. In case epidata is not compatible with MS Windows 10, I may have to use excel or other data entry softwares for this purpose. Thanking you. Regards Aayam Gupta MPH Scholar, SCTIMST, Trivandrum, INDIA Yours sincerely, Aayam Gupta (6606, MPH 2014) Mobile- 0091-8301864169 --------------------------------------------------------------------------------------------- "There is no such thing as sacrifice in a person's life aiming for excellence": Bedi ---------------------------------------------------------------------------------------------

1 2

Re: [EpiData-list] EpiData-list Digest, Vol 141, Issue 6
by EpiData development and support 09 Aug '15

09 Aug '15

Dear Hans No problem. I hope you do in future out up some podcats to guide us through manager and client Students and faculty at my medical school are slowly but surely catching on and we do 3-4 workshops a year with the older epidata software Still have cold feet about doing a workshop with manager! warmly appreciate all that you are doing regards Thambu ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Sunday, August 09, 2015 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 141, Issue 6 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-list Digest, Vol 141, Issue 4 (EpiData development and support) 2. Epidata Team (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 8 Aug 2015 22:11:22 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 141, Issue 4 Message-ID: <55C6626A.4010502(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Thambu: There must be a misunderstanding: there is an EpiData course (in the tab "EpiData course"), but this is not a talk; there are several things about epidemiology in the tab "Epidemiology", including talks accompanying a series of flash clips, annotated slide shows, etc, but this is not about "EpiData". I only pointed to the latter because Christine was interested what was behind the password. This is not an EpiData site per se as the home page defines, but it also has one tab dedicated to the course material on EpiData we prepared. Apologies if this created confusions. Regards, Hans On 08-Aug-15 09:23, EpiData development and support wrote: > Dear Hans > Many thanks for all the resources > I downloaded the zip file and also tried the online version-i could only view your presentation on TB epidemioloy;could not get to the epidata talk? > perhaps i missed some step? > regards > Thambu ------------------------------ Message: 2 Date: Sun, 09 Aug 2015 11:06:35 +0530 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Epidata Team Message-ID: <WC20150809053635.061FDE(a)sctimst.ac.in> Content-Type: text/plain; charset="us-ascii" Sir/Madam, I have just upgraded to windows 10. I wish to know the following - 1. Whether the current version of Epidata is compatible with Windows 10? 2. Whether anyone had faced any issues in exporting data from epidata to SPSS Version 21? I am involved in academic field work related to my MPH course requirement. I would be grateful for the feedback on my queries as it might save time in creating platform for data entry based on my interview schedule. In case epidata is not compatible with MS Windows 10, I may have to use excel or other data entry softwares for this purpose. Thanking you. Regards Aayam Gupta MPH Scholar, SCTIMST, Trivandrum, INDIA Yours sincerely, Aayam Gupta (6606, MPH 2014) Mobile- 0091-8301864169 --------------------------------------------------------------------------------------------- "There is no such thing as sacrifice in a person's life aiming for excellence": Bedi --------------------------------------------------------------------------------------------- ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 141, Issue 6 ********************************************

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 141, Issue 4
by EpiData development and support 08 Aug '15

08 Aug '15

Dear Hans Many thanks for all the resources I downloaded the zip file and also tried the online version-i could only view your presentation on TB epidemioloy;could not get to the epidata talk? perhaps i missed some step? regards Thambu Dr Thambu David Sudarsanam MD, DipNB Professor and Head Medicine Unit 2 and Clinical Epidemiology Unit Christian Medical College, Vellore 632004, India CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Friday, August 07, 2015 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 141, Issue 4 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-list Digest, Vol 141, Issue 3 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 6 Aug 2015 21:44:08 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] EpiData-list Digest, Vol 141, Issue 3 Message-ID: <55C3B908.4040103(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Christine: The restricted page is reserved for course participants in an upcoming course in Tartu. However, similar material is available on the same site in the navigation panel under "Epidemiology". On the opening page click on the "TBRiederEpiFlash" to watch (and listen) online or download the zip file and unzip to your PC and watch / listen offline. As you noted, the teaching material on EpiData has been developed by Jens Lauritsen and myself over several years of closely working together and is continuously updated. It has tremendously benefited from colleagues such as Ajay Kumar, Nguyen Binh Hoa, and Zaw Myo Tun to name just a few (the whole background and acknowledgments are in the beginning of the course material) In a next step we will adjust Part B to switch to reading *.epx files (rather than as currently *.REC / *.CHK). Best regards, Hans Hi Hans Thank you for giving the link to the module, I was very interested to read through it as it is the first time I have seen teaching material using the new version of Epidata. I see there is also a link to a presentation on the site but it takes you to a restricted area that needs a password. Are the presentations available through a public site at all? It would be good to watch this material being taught Many thanks Christine -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 141, Issue 4 ********************************************

1 1

EpiData-list Digest, Vol 141, Issue 3
by EpiData development and support 06 Aug '15

06 Aug '15

Dear Christine: The restricted page is reserved for course participants in an upcoming course in Tartu. However, similar material is available on the same site in the navigation panel under "Epidemiology". On the opening page click on the "TBRiederEpiFlash" to watch (and listen) online or download the zip file and unzip to your PC and watch / listen offline. As you noted, the teaching material on EpiData has been developed by Jens Lauritsen and myself over several years of closely working together and is continuously updated. It has tremendously benefited from colleagues such as Ajay Kumar, Nguyen Binh Hoa, and Zaw Myo Tun to name just a few (the whole background and acknowledgments are in the beginning of the course material) In a next step we will adjust Part B to switch to reading *.epx files (rather than as currently *.REC / *.CHK). Best regards, Hans Hi Hans Thank you for giving the link to the module, I was very interested to read through it as it is the first time I have seen teaching material using the new version of Epidata. I see there is also a link to a presentation on the site but it takes you to a restricted area that needs a password. Are the presentations available through a public site at all? It would be good to watch this material being taught Many thanks Christine -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org

1 0

notes during dataentry in EDEC
by EpiData development and support 06 Aug '15

06 Aug '15

Dear list-members In the "old" EpiData Entry, a note editor can be opened during data entry using F5, the note is stamped with the time, observation (record), and field from which you hit F5. This allow easy documentation of decisions made during data entry, as the person entering information can describe the situation and decision. This seems not to be implemented in the Manager/Entry Client structure, so my question is whether any of my fellow users have developed an alternative using other software, allowing parsing of information on record and variable? My experience is that the information is not always noted if using a paper or notepad solution leading to poorer documentation than in the EDE days. Best wishes Henrik Henrik Bøggild Associate professor, PhD, MD (specialist in public health) Department of Health Science and Technology / Public Health and Epidemiology Group Faculty of Medicine Aalborg University Denmark

1 1

Current stable versions of new manager/client for teaching
by EpiData development and support 05 Aug '15

05 Aug '15

Hello there I am thinking of giving an introduction to the new EpiData manager/client to our 2015/16 intake of MSc Epidemiology students. The teaching would take the form of a three-hour practical in which they would design a simple data-entry form, carry out double-entry comparison and export some data to Stata. Which is the current stable version of both client and manager that I could make available to the students over our network? Please let me know if you have any questions about this request. Many thanks Keith Tomlin Lecturer in Epidemiology Department of Disease Control Faculty of Infectious & Tropical Diseases London School of Hygiene & Tropical Medicine Room 445, Keppel Street, London, WC1E 7HT, UK +44 (0)207 927 2716 ( tel:02079272257) e: keith.tomlin(a)lshtm.ac.uk ( mailto:tkeith.tomlin@lshtm.ac.uk)

1 2

Value label export to Stata
by EpiData development and support 31 Jul '15

31 Jul '15

Hello, When exporting to Stata (ver13), value labels don't seem to follow the data. We are using Epidata Manager 2.0.5.51 and first I thought it was due to value labels being external rather than internal, but then I tried with a dataset with internal value labels, but the result was just the same, no value labels visible in Stata. Help much appreciated! Pekka Isosomppi

1 5

Re: [EpiData-list] Access violation when comparing duplicate files
by EpiData development and support 14 Jul '15

14 Jul '15

It works perfectly with the latest version. Thank you so much. Kind regards, Suparee Boonmanunt > ------------------------------ > > Message: 2 > Date: Thu, 09 Jul 2015 11:35:51 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > Subject: Re: [EpiData-list] Access violation when comparing duplicate > files > Message-ID: <B3DDB8E1-29FF-4F06-A0FD-91B376D68C46(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8 > > Please dowload latest version which is 2.0.5.51, you have used a previous version. > > Try again and inform here if it works. > 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 140, Issue 5 > ********************************************

1 1

Re: [EpiData-list] Access violation when comparing duplicate files
by EpiData development and support 09 Jul '15

09 Jul '15

Thank you for your reply 1. I use version 2.0.4.43 for Mac Program Version: 2.0.4.43 r1156 Core version: 2.0.0.0 r1161 FPC Version: 2.6.4 Platform: i386-Darwin 2. Both dataforms have the same identical 10 sections. I have created 1 dataform with 10 sections and let 2 people insert data parallel. 3. I haven’t defined any key, but I have defined an ID as a variable for each subject. However, it is not used for coupling the two files. This is what I did: Document -> Compare duplicate files -> (the new window pops up) -> Click on “Compare” -> Click on “Add files” -> select those 2 files -> select the sections I would like to compare Thank you so much. Suparee Boonmanunt > > ------------------------------ > > Message: 2 > Date: Wed, 08 Jul 2015 12:20:51 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > Subject: Re: [EpiData-list] Access violation when comparing duplicate > files > Message-ID: <88C2E6EF-3317-4256-81A5-212A9B9228BF(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8 > > Please inform us of: > 1 the version of manager You are using. > 2 are you working with sections on one dataform or a related system with fields and sections on all dataforms > 3 have you defined a key, and if so is that used for coupling of the two project files? > > You get the version from the help menu "copy version " > > /Jens Lauritsen, Epidata association. > > On 8. jul. 2015 12.09.45 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: >> Dear all, >> >> I am trying to compare the duplicate files. I did it for each section. >> In some sections with small number of fields and just integer, the >> comparison goes well. But in other sections with larger number of >> fields, the program always shows the message ?Access violation? and ask >> whether I will ignore it and continue and kill the program. >> I always choose to ignore and the program seems to work on something. >> But nothing has really happened. >> >> Should I just wait, because the program is still working? Or should I >> fix something in the entries? >> >> I would be very grateful if someone could suggest me what to do. >> >> Kind regards, >> Suparee >> _______________________________________________ >> 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 140, Issue 4 > ********************************************

1 1

Access violation when comparing duplicate files
by EpiData development and support 08 Jul '15

08 Jul '15

Dear all, I am trying to compare the duplicate files. I did it for each section. In some sections with small number of fields and just integer, the comparison goes well. But in other sections with larger number of fields, the program always shows the message “Access violation” and ask whether I will ignore it and continue and kill the program. I always choose to ignore and the program seems to work on something. But nothing has really happened. Should I just wait, because the program is still working? Or should I fix something in the entries? I would be very grateful if someone could suggest me what to do. Kind regards, Suparee

1 1

EntryClient 2.0.3.15: Problem with lack of update of existing records
by EpiData development and support 07 Jul '15

07 Jul '15

In a specific project where we wanted to enter one field extra following extract and import of hospital records the following two problems emerged. Both aspects will be fixed in August. Just now there is a pause in development until August. Be reassured that we do all we can to solve such issues since they are in essense what we call "show stoppers" of using the software - unless we manage to find and fix the cause. Which we - expressed with modesty - have done until now. Apart from a special issue in estimation of certain lifetables in EpiData Analysis. But for that one have decided to fix it as part of the rewriting of the software to the "epx based" standa The current two issues relates to: EpiData Entry Client Program Version: 2.0.3.15 r481, Core version: 2.0.0.0 r1161, FPC Version: 2.6.4, Platform: i386-Win32 1. Lack of "value changed" upon entry in existing field with currently no information in that field Normally when you use the value label box (F9) to select values and change a value, then the current record is marked internally as edited. Upon change to the next record the system should ask "save record". But apparently this does not happen, the EntryClient just moves to the next record without saving the value 2. The standard behaviour of EpiData software when a user moves a given window to a new "non-default" position is that next time that window is opened it will be placed in that same position. This is currently not the done with EntryClient for the value label box and the "confirm change to records" box. The remedy until fixed was the following: I added an integer field of length 1. Then I changed the range to 1-1 and added mustenter requirement. In other words the only possible entry is a 1 (one). This shows that sometimes combinations of attributes can give problems, which we - unfortunately - have not identified yet. When we see such situations they are then added to the list of structured testing, which we apply before public release. The list is increasing with increased number of handled special situations. The solution could only be identified by a structured "trial and error" process, where I managed to find the cause, which can then be remedied. Unfortunately in some situations it is very difficult to create such a process. In particular when an issue is only present in some versions. An example of this is the 32/64 bit windows v8.1 issue which have struck some users and another issue where we have seen that a given epx related file works very well in Linux and Mac, but in Windows 7 creates an access violation on attempt to edit an existing record. . Any structured input to solving such problems is highly welcomed. Regards Jens Lauritsen EpiData Association Denmark.

1 0

Searching the List Archives
by EpiData development and support 03 Jul '15

03 Jul '15

Would there be a way to set up the EpiData-list Archives to implement a search function? As they are set up now: Archive View by: Downloadable version Second quarter 2015: [1][ Thread ] [2][ Subject ] [3][ Author ] [4][ Date ] [5][ Gzip'd Text 20 KB ] First quarter 2015: [6][ Thread ] [7][ Subject ] [8][ Author ] [9][ Date ] [10][ Gzip'd Text 14 KB ] they appear to be not very user-friendly if one tries to look for something specific. Thanks for considering, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: [11]http://www.tbrieder.org References 1. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/thread.html 2. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/subject.html 3. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/author.html 4. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/date.html 5. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2.txt.gz 6. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/thread.html 7. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/subject.html 8. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/author.html 9. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/date.html 10. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1.txt.gz 11. http://www.tbrieder.org/

1 4

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 13
by EpiData development and support 30 Jun '15

30 Jun '15

Thanks, that was the case. The chk file was not residing in the same folder as the rec file. martin On 27 June 2015 at 17: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. Version 3.1 used to keep the value labels in documents|view > data (EpiData development and support) > 2. Re: Version 3.1 used to keep the value labels in > documents|view data (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 26 Jun 2015 17:19:46 +0000 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Version 3.1 used to keep the value labels in > documents|view data > Message-ID: > <CAMUv7ZSFxFB0rP==gK55_pTa6K3gfiygH=KpHpmpY= > L0tj5hag(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I am using Epidata 3.1,When I open the data in Document | View data, from > Edit, I see the the data are checked to "Show labels", but the labels are > not shown. That means when I export to say, Stata, I don't have the > labels. I remember this used to work. Is there anything I am doing wrong? > > > regards > > -- > Martin Alhassan Adjuik > Statistician > Cell : +233 (0) 243714441 > madjuik(a)gmail.com > > > ------------------------------ > > Message: 2 > Date: Sat, 27 Jun 2015 12:32:41 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > Subject: Re: [EpiData-list] Version 3.1 used to keep the value labels > in documents|view data > Message-ID: <7C0F38CC-BD35-4DD9-9D98-64BEA7F6B5E5(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8 > > Most likely your chk file is not residing in the same folder as your rec > file or has a different name. > Regards jens Lauritsen > Epidata association > > On 26. jun. 2015 19.19.46 CEST, EpiData development and support < > epidata-list(a)lists.umanitoba.ca> wrote: > >I am using Epidata 3.1,When I open the data in Document | View data, > >from > >Edit, I see the the data are checked to "Show labels", but the labels > >are > >not shown. That means when I export to say, Stata, I don't have the > >labels. I remember this used to work. Is there anything I am doing > >wrong? > > > > > >regards > > > >-- > >Martin Alhassan Adjuik > >Statistician > >Cell : +233 (0) 243714441 > >madjuik(a)gmail.com > >_______________________________________________ > >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 139, Issue 13 > ********************************************* > -- Martin Alhassan Adjuik Statistician Cell : +233 (0) 243714441 madjuik(a)gmail.com

1 0

Re: [EpiData-list] Importing data to Epidata (v.2.0.5.51)
by EpiData development and support 28 Jun '15

28 Jun '15

Thank you very much Jamie, your help was indeed very helpful. I believe it also makes sense to convert yes/no/NA cells to have a numerical value e.g. 1,2,3 ? Is there a way to change the field type afterwards other than touching the XML code and if so, is it wise/dangerous? Pekka Jamie wrote: > > I have found that import from the clipboard works well if the Excel data > are prepared for the import. Here is what I do. > > In Excel, format the columns they way you want them to appear in EpiData > (text columns, numbers with set decimal places, dates as YYYY/MM/DD is > best). > I usually then format the columns to fit the data > No spaces in your column names - these should be valid EpiData field names > for consistency > Make sure that the first and last rows of data are complete; I often put > dummy data in these and then delete the records in EpiData. I believe the > main thing here is to have valid data (not empty cells) in the last column > of data for the first and/or last rows. > Ideally, have no blank cells - put missing values in. This is probably not > necessary, as EpiData handles empty cells well. > > > You may find that fields are not the length that you want. You can safely > edit these fields to change the size. Text, number and data fields should > all come through with the correct type. > > I don?t know of any simple way to convert data for an Excel column to > coded values with ?value labels?. Unless your data set is massive, there is > no real penalty to keeping the values in full. > > When I had to automate repeated conversion of messy Excel data to EpiData, > I made a new sheet within the Excel file and used formulas to put copies of > the original data into the new sheet, with all of the cleaning. For > example, we had some inconsistencies in coding province, so I used a lookup > table to convert the original values (Ontario, Ont, ON) to be consistent > (ON). This is one way to do your data coding, by the way, but you still > cannot automate getting the value labels into EpiData. In my case, the data > set was small and existing data might change, so I just kept importing the > whole thing. You can also just convert the new data, import to a new > EpiData project and then append this to your complete project. > > You will have problems with import from the clipboard if you have commas > in your text fields. In my testing, the import fails without an error > message. > > EpiData is very fussy about importing data, as it should be, since it does > such a good job of maintaining the integrity of data when you use it for > data entry. Import of csv data does work, but you have to be very sure to > have clean data and to not have stray delimiters in your data. In any case, > your data should be in good shape since it originates in a database (what > database?? Maybe there is another more direct way to get into EpiData) > --? > Jamie > > Pekka wrote: > What I want to do is to import a spreadsheet with field labels and data to > Epidata. The spreasheet contains field names on the top row and records on > the following rows. Once I have imported the initial data, I would like to > ammend the records with additional fields, i.e. have the initial > spreadsheet data as the seed data in records. I think this is a very normal > practice to do, but I have run into several difficulties: > > 1. I have tried to import the spreadsheet with "File/Import file" but I > don't seem to get it working. I have turned the spreasheet from Excel to > CSV, but the dialogue box that opens doesn't recognize data. I made a > workaround by copying a part of the spreadsheet and used "File/Import from > clipboard" and that did work. The downside is that you have to do it part > by part, and the fundamental problem is why it doesn't work in the first > place. Is Epidata Manager very picky as to what field separators are used > in CSV? I have tried changing field separators but with no luck. Clipboard > seems to be the only workaround, but even still I have to do it in parts. > (I am using Ubuntu and the latest Linux 64-bit version) > > 2. With the copy-paste method I noticed that Epidata was smartly able to > interpret some fields with the right type (e.g. date, but not all > date-fields, but I believe this is the issue of my spreadsheet), but not > all. I have not discovered a way to change the field type afterwards, is it > at all possible? The only hack I figured out was to manually change the > field type in XML code directly, but I would be very hesitant to do it. If > I touch XML code directly, will that mess up everything, or is it the > simple fix to the problem? > > 3. Value-labels: My spreadsheet contains no value labels, obviously. It has > for example field "Country of origin" and the value is string "Nepal". Is > there a way for me to easily convert strings of text into value labels as a > part of the import process? String values are consistent (the spreadsheet > is an output file from a database), so I should imagine it would be > possible do so. > > 4. Provided I get questions 1,2 and 3 adequately resolved, I should be fine > with the initial data import. But what do I do if I want to later import > additional records from the same spreadsheet structure to my Epidata > project? Is this something that Append is supposed to do? There I have the > same issue with the spreadsheet compatibility: The CSV file does not open > in a recognisable way, hence I haven't been able to play around and test it > either. > > > >

1 4

Version 3.1 used to keep the value labels in documents|view data
by EpiData development and support 27 Jun '15

27 Jun '15

I am using Epidata 3.1,When I open the data in Document | View data, from Edit, I see the the data are checked to "Show labels", but the labels are not shown. That means when I export to say, Stata, I don't have the labels. I remember this used to work. Is there anything I am doing wrong? regards -- Martin Alhassan Adjuik Statistician Cell : +233 (0) 243714441 madjuik(a)gmail.com

1 1

transfer questionnaire created in Mac version (2) to same version in PC?
by EpiData development and support 25 Jun '15

25 Jun '15

Dear friends apologies for this is a very simple question - may be I missed it in the documentation I would like to create a questionnaire on my Mac then take it to the field where there will be PCs. Will this work? Also using the data entry tool for PCs with a questionnaire created in the MAC programme? grateful for your advice Hilary

1 2

Importing data to Epidata (v.2.0.5.51)
by EpiData development and support 23 Jun '15

23 Jun '15

Hello, I am a newcomer to Epidata, so I apologize if my questions are not sophisticated. I am exploring the latest version and it is fantastic with many ingenious features, great work and great programming philosophy, thank you! As the version is new, I understand that the documentation is not yet fully developed, and hence if someone can help me with these questions, I think they can be of use to many others as well. What I want to do is to import a spreadsheet with field labels and data to Epidata. The spreasheet contains field names on the top row and records on the following rows. Once I have imported the initial data, I would like to ammend the records with additional fields, i.e. have the initial spreadsheet data as the seed data in records. I think this is a very normal practice to do, but I have run into several difficulties: 1. I have tried to import the spreadsheet with "File/Import file" but I don't seem to get it working. I have turned the spreasheet from Excel to CSV, but the dialogue box that opens doesn't recognize data. I made a workaround by copying a part of the spreadsheet and used "File/Import from clipboard" and that did work. The downside is that you have to do it part by part, and the fundamental problem is why it doesn't work in the first place. Is Epidata Manager very picky as to what field separators are used in CSV? I have tried changing field separators but with no luck. Clipboard seems to be the only workaround, but even still I have to do it in parts. (I am using Ubuntu and the latest Linux 64-bit version) 2. With the copy-paste method I noticed that Epidata was smartly able to interpret some fields with the right type (e.g. date, but not all date-fields, but I believe this is the issue of my spreadsheet), but not all. I have not discovered a way to change the field type afterwards, is it at all possible? The only hack I figured out was to manually change the field type in XML code directly, but I would be very hesitant to do it. If I touch XML code directly, will that mess up everything, or is it the simple fix to the problem? 3. Value-labels: My spreadsheet contains no value labels, obviously. It has for example field "Country of origin" and the value is string "Nepal". Is there a way for me to easily convert strings of text into value labels as a part of the import process? String values are consistent (the spreadsheet is an output file from a database), so I should imagine it would be possible do so. 4. Provided I get questions 1,2 and 3 adequately resolved, I should be fine with the initial data import. But what do I do if I want to later import additional records from the same spreadsheet structure to my Epidata project? Is this something that Append is supposed to do? There I have the same issue with the spreadsheet compatibility: The CSV file does not open in a recognisable way, hence I haven't been able to play around and test it either. Help is much appreciated, thank you! Pekka

1 1

EpiData Project: Current development focus and Strategy over next 1-2 years
by EpiData development and support 22 Jun '15

22 Jun '15

Development these months is focused on getting towards compliance with the legal regulations on access to data containing health information. In short this concerns: - definition of users and what they can do (change structure, modify users, export data ....) - logging of which users did what The total development list contains as well: - inclusion of scripting during Entry. Could be used for user defined functions such as summation af scales or reading of data from external lookup software). - rewriting of Analysis based on the new xml file format. And extension with more specific functions for routine reporting. A number of International Standards describe requirements of user control and logging in detail (piles of descriptions). This is difficult legal and technical documentation. For those using ISO standards this referes to ISO 27001 and 27002. A formal certification with an external auditing body would be a huge investment and NOT possible within the economic constrains of the EpiData project. Just as an example rewriting from one standard to another would cost 5000 Euro. Which is better spent on development. But implementation of the principles is required to secure continued use in some countries and some situations. E.g. for research in pharmaceutical products. More news will follow on this development, which is also dependent on continued donation of funding for the development of the EpiData software products. The remaining development is expected to take about 2-2½ years. Software will be released as open-source, when specific modules are ready with all decided functionality. The reason for working in this way is that before principles are settled it is a highly fragile situation. There is however continued correspondance and exchange of components with other users applying the Free-Pascal solution in Lazarus, which is the basis of EntryClient and Manager programming. Regards Jens Lauritsen EpiData Association.

1 0

bug fix release for Manager
by EpiData development and support 22 Jun '15

22 Jun '15

Just before the weekend a bug-fix release has been made available for general download from http://www.epidata.dk The changes in Manager are always available as a short list on this link: <http://epidata.dk/epidatamanager.changelog.txt> as well as in EntryClient on this link: <http://epidata.dk/epidataentryclient.changelog.txt> For the most recent Manager this is: 2.0.5.51: * Fixed bug in double entry validation, that could lead to A/V due to incorrect order of adding selectiong of key fields * Fixed bug where 32-bit Windows could drop the .epx/.epz extension with "Save As" on existing projects. * Fixed bug where double clicking a locked Keyfield, would cause A/V * ExportForm: changed filename edit to regular edit, to avoid confusion regarding paths. A/V indicates Access Violation. Stata 13/14 export will be implemented with next release of Manager, but Stata 13/14 import was implemented already in 2.0.4.43 regards Jens Lauritsen and Torsten Bonde Christiansen EpiData Association

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 6
by EpiData development and support 22 Jun '15

22 Jun '15

Dear Hans, Thanks for your concern. I'm on a 64 bit system, however the 64 bit software version won't work at all on my computer. I looked through the archives and saw that other people with 64 bit systems were complaining about this, and finally and successfully installed the 32 bit software version on their machine. Best regards, Michael van Straten -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Thursday, June 18, 2015 8:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 139, Issue 6 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-list Digest, Vol 139, Issue 3 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Wed, 17 Jun 2015 20:06:40 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 3 Message-ID: <5581B730.3040308(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Michael: Do you indeed have a 32-bit architecture on your Win 8 machine? I am asking to exclude a mismatch between software version and PC architecture. Regards, Hans On 17-Jun-15 16:50, EpiData development and support wrote: > Dear Torsten, > > Sorry for my late reply. > > 1. Version: EpiData Manager > Program Version: 2.0.4.43 r1156 > Core version: 2.0.0.0 r1161 > FPC Version: 2.6.4 > Platform: i386-Win32 -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 139, Issue 6 ********************************************

1 2

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 8
by EpiData development and support 21 Jun '15

21 Jun '15

Dear Hans, Thanks for the clarification. I guess then that it's back to square 1 for me.. Best regards, Michael van Straten -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Sunday, June 21, 2015 8:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 139, Issue 8 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-list Digest, Vol 139, Issue 6 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 20 Jun 2015 20:03:29 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 6 Message-ID: <5585AAF1.1040308(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Michael: I'm afraid then, that this mismatch is the cause of the problem. In some systems, a 32-bit version of EpiData software appears to work (superficially), but then one runs into a problem sooner or later. Unfortunately, a 64-bit PC requires the 64-bit software. We need thus to figure out why 64-bit software does not work on your 64-bit PC. It is not a Win 8 problem per se (we tried it and it works). Unfortunately, I run out of suggestions on what to check next... Regards, Hans On 19-Jun-15 11:43, EpiData development and support wrote: > Dear Hans, > > Thanks for your concern. I'm on a 64 bit system, however the 64 bit > software version won't work at all on my computer. I looked through > the archives and saw that other people with 64 bit systems were > complaining about this, and finally and successfully installed the 32 > bit software version on their machine. > > Best regards, > > Michael van Straten -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 139, Issue 8 ********************************************

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 3
by EpiData development and support 17 Jun '15

17 Jun '15

Dear Torsten, Sorry for my late reply. 1. Version: EpiData Manager Program Version: 2.0.4.43 r1156 Core version: 2.0.0.0 r1161 FPC Version: 2.6.4 Platform: i386-Win32 2. Yes. There was an error message but the program closed down so fast I could just see it flash for a moment, with no chance of reading it. The program just closes down. Disappears. Nothing is saved and I am returned to my desktop. 3. I open the program, start a new project, open a new data form and add a string variable. In the field properties box, the moment I try to add a value label by pressing on "new", the program shuts down without saving anything. Scenario 2: I open a new data form, add a string variable without a value label, save the project and close the program. Then I open the project and try to add a value label to the existing string variable: the same thing happens. Program close down. This happens also when I try to add a value label via "Project Details" >> "Value labels". I hope this helps understand the problem. TIA, Michael van Straten -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Friday, June 12, 2015 8:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 139, Issue 3 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 Manager closing down on Windows 8.1 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Fri, 12 Jun 2015 11:17:17 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData Manager closing down on Windows 8.1 Message-ID: <557AA39D.6090105(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Hi Michael. I have tried to make a few simple projects in Windows 8.1 here and I am not able to reproduce what you describe. Can you please elaborate on the following: 1: Version of EpiData Manager you have tested with (use "Help" -> "Copy Version Info...") 2: Was there any errormessage 3: Please make a more detailed description of the steps you took for this happen Regards, Torsten B. Christiansen. EpiData. On 2015-06-08 12:57, EpiData development and support wrote: > Dear users, > > I have installed EpiData Manager on a machine working on Windows 8.1 > 64 bit. I used the latest versions available: 2.0.4.43 r1156 > > 1. At first I used the 64 bit version but could not open or save projects: this led to the program shutting down. In the archives I saw other users experienced similar problems. > 2. I then uninstalled the above and installed the 32 bit version (Platform i386-Win32). This version seemed to be working well, until I tried to set value labels: when I do this, either by using the "Field properties" box or by trying to access through "Project Details" >> "Value labels", the program shuts down. I am just able to see that some error notice appears but the program shuts down so fast I cannot read it. > > Any suggestions? > > Thanks in advance, > > Michael???? ?????? ??????? ??? > _______________________________________________ > 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 139, Issue 3 ********************************************

1 1

AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 29/06/2015)
by EpiData development and support 12 Jun '15

12 Jun '15

I am out of the office until 29/06/2015. Please contact Tracey McCole on 071 9852900 if you require further assistance, otherwise I will attend to your email when I return Note: This is an automated response to your message "EpiData-list Digest, Vol 139, Issue 3" sent on 12/06/2015 18:00:22. This is the only notification you will receive while this person is away. *************************************************************************** "Tá an fhaisnéis sa ríomhphost seo (ceangaltáin san áireamh) faoi rún. Baineann sé leis an té ar seoladh chuige amháin agus tá sé ar intinn go bhfaighfidh siadsan amháin é agus gurb iadsan amháin a dhéanfaidh breithniú air. Más rud é nach tusa an duine ar leis é, tá cosc iomlán ar aon fhaisnéis atá ann, a úsáid, a chraobhscaoileadh, a scaipeadh, a nochtadh, a fhoilsiú, ná a chóipeáil . Seains gurb iad tuairimí pearsanta an údar atá san ríomhphost agus nach tuairimí FSS iad. Má fuair tú an ríomhphost seo trí dhearmad, bheadh muid buíoch dá gcuirfeá in iúil don.Deasc Seirbhísí ECT ar an nguthán ag +353 71 9820555 nó ar an ríomhphost chuig ICT.Helpdesk(a)hse.ie agus ansin glan an ríomhphost seo ded' chóras." *************************************************************************** "Information in this email (including attachments) is confidential. It is intended for receipt and consideration only by the intended recipient.If you are not an addressee or intended recipient, any use, dissemination,distribution, disclosure, publication or copying of information contained in this email is strictly prohibited..Opinions expressed in this email may be personal to the author and are not necessarily the opinions of the HSE. If this email has been received by you in error we would be grateful if you could immediately notify the ICT Service Desk by telephone at +353 71 9820555 or by email to ICT.Helpdesk(a)hse.ie and thereafter delete this e-mail from your system" ***************************************************************************

1 0

EpiData Manager closing down on Windows 8.1
by EpiData development and support 12 Jun '15

12 Jun '15

Dear users, I have installed EpiData Manager on a machine working on Windows 8.1 64 bit. I used the latest versions available: 2.0.4.43 r1156 1. At first I used the 64 bit version but could not open or save projects: this led to the program shutting down. In the archives I saw other users experienced similar problems. 2. I then uninstalled the above and installed the 32 bit version (Platform i386-Win32). This version seemed to be working well, until I tried to set value labels: when I do this, either by using the "Field properties" box or by trying to access through "Project Details" >> "Value labels", the program shuts down. I am just able to see that some error notice appears but the program shuts down so fast I cannot read it. Any suggestions? Thanks in advance, Michaelנשלח ממכשיר הסמסונג שלי

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 138, Issue 3
by EpiData development and support 31 May '15

31 May '15

I have sent an example of the bug, including logfile, .epx, .dta, to info at epidata.dk. I have received the following automatic answer: This e-mail is unfortunately heavily burdened by spam. If you have a general comment or question on the use of EpiData Software, please search the EpiData list. To join the list or see contents follow the link on the main EpiData site frontpage. Join the list to ask the question again. According to Stata the variable format is %5.0f. Best wishes Patrick -----Ursprüngliche Nachricht----- Message: 2 Date: Wed, 27 May 2015 11:15:46 +0000 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: "'epidata-list(a)lists.umanitoba.ca'" <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Bug Report Message-ID: <D5708C0652AF0845914EE5DACE98380670FD45(a)DS-00521.usz.ch> Content-Type: text/plain; charset="iso-8859-1" Dear all, We have just discovered that if we export our data into Stata format, numbers above 32741 are not handled correctly by the export routine. The values 32741 to 32767 are converted to (extended) missing data, above 32768 numbers are converted to negative numbers. Since the range [-32767 - 32768] contains 2^16 Numbers, I assume the export routine handles integer as 16bit Integers. We've tested it with EpiData Manager v2.0.2.28 and Stata 12,13,14. Best wishes Patrick ------------------------------ Message: 3 Date: Wed, 27 May 2015 22:31:08 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] Bug Report export - STATA Message-ID: <5566298C.700(a)epidata.dk> Content-Type: text/plain; charset=windows-1252; format=flowed Good point, but to ascertain whether it is a misinterpretation we need to know which format the given variable/field has in Stata. Can you send an example copy of the dta file to: info at epidata.dk Jens Lauritsen EpiData Association On 27/05/15 13:15, EpiData development and support wrote: > Dear all, > > We have just discovered that if we export our data into Stata format, numbers above 32741 are not handled correctly by the export routine. The values 32741 to 32767 are converted to (extended) missing data, above 32768 numbers are converted to negative numbers. Since the range [-32767 - 32768] contains 2^16 Numbers, I assume the export routine handles integer as 16bit Integers. > > We've tested it with EpiData Manager v2.0.2.28 and Stata 12,13,14. > > Best wishes > Patrick > _______________________________________________ > 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 138, Issue 3 ********************************************

1 1

Bug Report
by EpiData development and support 27 May '15

27 May '15

Dear all, We have just discovered that if we export our data into Stata format, numbers above 32741 are not handled correctly by the export routine. The values 32741 to 32767 are converted to (extended) missing data, above 32768 numbers are converted to negative numbers. Since the range [-32767 - 32768] contains 2^16 Numbers, I assume the export routine handles integer as 16bit Integers. We've tested it with EpiData Manager v2.0.2.28 and Stata 12,13,14. Best wishes Patrick

1 1

Double entry in epidata entryclient
by EpiData development and support 25 May '15

25 May '15

To double enter in EntryCĺlent you do this: A enter data once in a project B create copy for double entry in manager C enter All data again in second file created in B. D compare the two files in manager You cannot compare while entering data in the second file. Regards jens Lauritsen Epidata association.

1 0

RE: EpiData-list Digest, Vol 138, Issue 1
by epidata-list＠lists.umanitoba.ca 11 May '15

11 May '15

Dear Jens Many thanks Is the export to SPSS issue sorted out? regards Thambu Dr Thambu David Sudarsanam MD, DipNB Professor and Head Medicine Unit 2 and Clinical Epidemiology Unit Christian Medical College, Vellore 632004, India CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Monday, May 11, 2015 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 138, Issue 1 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 (bug-fix) versions of EpiData EntryClient and Manager (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 11 May 2015 09:09:46 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Updated (bug-fix) versions of EpiData EntryClient and Manager To: epidata-list(a)lists.umanitoba.ca Message-ID: <555055BA.3080402(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed The following bug-fixes has been made and new versions uploaded today. EpiData Manager Program Version: 2.0.4.43 EpiData Entry Client Program Version: 2.0.3.15 Both: * Fixed potential bug where opening file as parameter would fail. * Fixed bug where reading empty file would cause A/V * New shortcut for restoring default window postion: * - Ctrl + Shift + 0 (Windows & Linux) * - CMD + Shift + 0 (MAC) Manager: * All New Export form: * - Export multiple dataforms at the same time * - Export EPX as either new single project OR as individual projects. * Windows + Mac: Double clicking a field/heading/section opens the properties form. * NEW: Import Stata 13 + Stata 14 (No export yet) * Variuos minor bug-fixes EntryClient: * Other minor bug fixes. Jens Lauritsen, Torsten Bonde Christiansen 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 138, Issue 1 ********************************************

1 1

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

11 May '15

The following bug-fixes has been made and new versions uploaded today. EpiData Manager Program Version: 2.0.4.43 EpiData Entry Client Program Version: 2.0.3.15 Both: * Fixed potential bug where opening file as parameter would fail. * Fixed bug where reading empty file would cause A/V * New shortcut for restoring default window postion: * - Ctrl + Shift + 0 (Windows & Linux) * - CMD + Shift + 0 (MAC) Manager: * All New Export form: * - Export multiple dataforms at the same time * - Export EPX as either new single project OR as individual projects. * Windows + Mac: Double clicking a field/heading/section opens the properties form. * NEW: Import Stata 13 + Stata 14 (No export yet) * Variuos minor bug-fixes EntryClient: * Other minor bug fixes. Jens Lauritsen, Torsten Bonde Christiansen EpiData Association _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

SPSS export issue
by epidata-list＠lists.umanitoba.ca 22 Apr '15

22 Apr '15

Dear Jens and team I tried with the latest version When i try export to SPSS with the sample epx file in Epidata i get this error on running the spss file >Error # 4100 in column 3. Text: ENCODING >Unrecognized text appears on the DATA LIST command in the file >specification section. This text will be ignored. >This command not executed. >Error # 100. Command name: VARIABLE LABELS >This command is not permitted before the beginning of file definition >commands. >This command not executed. >Error # 100. Command name: VALUE LABELS >This command is not permitted before the beginning of file definition >commands. >This command not executed. >Error # 105. Command name: EXECUTE >This command is not valid before a working file has been defined. >This command not executed. Dr Thambu David Sudarsanam MD, DipNB Professor and Head Medicine Unit 2 and Clinical Epidemiology Unit Christian Medical College, Vellore 632004, India CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Saturday, April 18, 2015 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 137, Issue 3 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 to SPSS not working well (epidata-list(a)lists.umanitoba.ca) 2. Re: Error opening the project in EpiData Entry Client (epidata-list(a)lists.umanitoba.ca) 3. Course materials in French (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Sat, 18 Apr 2015 10:32:53 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Export to SPSS not working well To: epidata-list(a)lists.umanitoba.ca Message-ID: <553216B5.5080205(a)epidata.dk> Content-Type: text/plain; charset=windows-1252; format=flowed Can you be a bit more specific ? Which version of EpiData Manager ? If it is earlier than the current most up to date ( *v2.0.2.28)*, then get the latest and try again. What types of fields are in the files where it does not work ? regards /Jens Lauritsen EpiData Association On 17/04/15 12:09, epidata-list(a)lists.umanitoba.ca wrote: > Dear Sir > The export of files to SPSS does not work all the time with the Epidata manager > Often no data gets exported > Perhaps i am doing something wrong? > Need help > regards > Thambu > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > ------------------------------ Message: 2 Date: Sat, 18 Apr 2015 10:38:24 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Error opening the project in EpiData Entry Client To: epidata-list(a)lists.umanitoba.ca Message-ID: <55321800.6000201(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Any project which just once has been opened and saved by version 2 of EpiData Manager og EntryClient will have the file updated to version 3. The version mentioned refers to the structure of the XML file, not the version of the software. So someone in your organisation have opened and saved the file with the newest version. Which you should also use, since we have fixed many bugs. Manager: v2.0.2.28 EntryClient: v2.0.2.13 It will always be such that a later version of the software can open ANY earlier public release version. BUT also such that you should NEVER use the testing version of Manager or EntryClient found on epidata.dk/testing.php on real project data. Since during the testing we might have changes to the xml structure of the project which are later abandoned. Is there a reason why you would like to use v1.4.4.4 and not 2.0.2.13 for your project ? Regards Jens Lauritsen EpiData Association * *On 15/04/15 14:40, epidata-list(a)lists.umanitoba.ca wrote: > Dear List, > > A project was developped in the field. Since recently, without any apparent > reason we can't open anymore the .epx with the database and continue the > data entry. > > The error message indicates: > > "project has incorrect XML. Max supported XML Version 2: Project XML > version 3???. The version we have is v1.4.4.4. > Although a different version was used in the past, I was always able to > open it with the v1.4.4.4 which is not the case anymore. > > Could you please specify what the error message means? or way forward to be > able to open the project again? > > Many thanks in advance > > Sophie Masson > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > ------------------------------ Message: 3 Date: Sat, 18 Apr 2015 15:54:31 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Course materials in French To: epidata-list(a)lists.umanitoba.ca Message-ID: <55326217.1080100(a)wanadoo.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello, Thank you to change link of "Course materials in French" in site (Download for Epidata Entry in Frenche and Epidata Analysis). The new link is : _http://www.epi-sure.com/ _ Thank you. Bernard BRANGER 11 bis, rue Gabriel LUNEAU 44000 NANTES T?l +33 (0)2 40 73 13 32 Mobile +33 (0)6 32 70 33 80 Mel : branger-bono(a)wanadoo.fr ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 137, Issue 3 ********************************************

1 1

Course materials in French
by epidata-list＠lists.umanitoba.ca 18 Apr '15

18 Apr '15

Hello, Thank you to change link of "Course materials in French" in site (Download for Epidata Entry in Frenche and Epidata Analysis). The new link is : _http://www.epi-sure.com/ _ Thank you. Bernard BRANGER 11 bis, rue Gabriel LUNEAU 44000 NANTES Tél +33 (0)2 40 73 13 32 Mobile +33 (0)6 32 70 33 80 Mel : branger-bono(a)wanadoo.fr

1 0

Error opening the project in EpiData Entry Client
by epidata-list＠lists.umanitoba.ca 18 Apr '15

18 Apr '15

Dear List, A project was developped in the field. Since recently, without any apparent reason we can't open anymore the .epx with the database and continue the data entry. The error message indicates: "project has incorrect XML. Max supported XML Version 2: Project XML version 3”. The version we have is v1.4.4.4. Although a different version was used in the past, I was always able to open it with the v1.4.4.4 which is not the case anymore. Could you please specify what the error message means? or way forward to be able to open the project again? Many thanks in advance Sophie Masson

1 1

Export to SPSS not working well
by epidata-list＠lists.umanitoba.ca 18 Apr '15

18 Apr '15

Dear Sir The export of files to SPSS does not work all the time with the Epidata manager Often no data gets exported Perhaps i am doing something wrong? Need help regards Thambu

1 1

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

06 Mar '15

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

1 0

Query in Epidata manager
by epidata-list＠lists.umanitoba.ca 24 Feb '15

24 Feb '15

Dear Sir, I am currently using EpiData manager for my data entry. I am facing few difficulties for which i am seeking solution from your expert team. My difficult is as follows. 1. Few questions in my questionnaire are relevant only for Married. My 3rd question captures about marital status. My 7th questions intends to find information relevant to married only. So, if a person is unmarried (when i enter in Q3 as unmarried) this Q7 should automatically get skipped because he is not married. But i am unable to do it in Epidata manager, because Epidata manager allows me to jump from Q3 to Q5 by skipping Q4, but not serving my purpose. Can suggestions on this ? 2. I have 4 boxes, 1st is year, 2nd is months, 3rd is week and 4th is days. I would like to create a 5th box which should automatically calculate [(1st box value *365) + (2nd box value *30) + (3rd box value *7) + (4th box value)]. How do i do this in epidata manager. Please help me out how best i can do this. Thanks & Regards, -- *Thiru*

1 1

Manager and EntryClient - Identified bugs in latest release ?
by epidata-list＠lists.umanitoba.ca 06 Feb '15

06 Feb '15

Regarding the latest public release: _Manager_ *v2.0.0.25* _EntryClient_ *v2.0.0.10* During classes today (35 participants) for 5 hours I noticed very few problems aside from the following: 1 Users should be very much aware that they are NOT starting the software from within zip archives. Windows hides the actual folder type - unless you are aware of this. 2 EpiData Analysis: Some users had NOT installed the latest EpiData Analysis and could therefore not read the epx files created. Remedy: Check that you have V2.2 Rel. 2 (Build 183 ) (see caption). 3 In Manager: Ctrl+Z will NOT restore a deletion of a field - only moving the field to another position. 4 In Windows-8: Strange behaviour for three users having installed the software twice. They were not sure if they had taken the 64 or 32 bit versions. One pc in particular gave problems: After removing the installed versions and installing the 32 bit version, function was restored without problems. 4 A few bugs: a. If you select more than 2 project files for "double entry validation" - and then unselect files. Then the test of comparing the two files is NOT done. Remedy: Deselect all files and just mark two of them for comparison. Then it works. b. On Machintosh: Sometimes an entry field could be outside the "visible dataform" in EntryClient - and users could then not access that field c. On one particular pc with Windows 8 the EntryClient confused period and comma during entry in a float field, rejecting saving of a given record. Upon "save of record" the program crashed. Problem was solved after removal of software and fresh install from EpiData website . Please report problems and function as done previously. In particular on issues above. Following end of the classes (mid March) I will attempt to release all exercises for download from the website. regards Jens Lauritsen Initiator and Coordinator EpiData Association Denmark.

1 2

RE: EpiData-list Digest, Vol 135, Issue 1
by epidata-list＠lists.umanitoba.ca 04 Feb '15

04 Feb '15

Dear Jens Humble request: please could you have a podcast of your classes online? sincerely Thambu Dr Thambu David Sudarsanam MD, DipNB Professor and Head Medicine Unit 2 and Clinical Epidemiology Unit Christian Medical College, Vellore 632004, India CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Tuesday, February 03, 2015 11:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 135, Issue 1 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. Manager and EntryClient - Identified bugs in latest release ? (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 02 Feb 2015 23:33:05 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Manager and EntryClient - Identified bugs in latest release ? To: EpiData-list(a)lists.umanitoba.ca Message-ID: <54CFFB21.80202(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Regarding the latest public release: _Manager_ *v2.0.0.25* _EntryClient_ *v2.0.0.10* During classes today (35 participants) for 5 hours I noticed very few problems aside from the following: 1 Users should be very much aware that they are NOT starting the software from within zip archives. Windows hides the actual folder type - unless you are aware of this. 2 EpiData Analysis: Some users had NOT installed the latest EpiData Analysis and could therefore not read the epx files created. Remedy: Check that you have V2.2 Rel. 2 (Build 183 ) (see caption). 3 In Manager: Ctrl+Z will NOT restore a deletion of a field - only moving the field to another position. 4 In Windows-8: Strange behaviour for three users having installed the software twice. They were not sure if they had taken the 64 or 32 bit versions. One pc in particular gave problems: After removing the installed versions and installing the 32 bit version, function was restored without problems. 4 A few bugs: a. If you select more than 2 project files for "double entry validation" - and then unselect files. Then the test of comparing the two files is NOT done. Remedy: Deselect all files and just mark two of them for comparison. Then it works. b. On Machintosh: Sometimes an entry field could be outside the "visible dataform" in EntryClient - and users could then not access that field c. On one particular pc with Windows 8 the EntryClient confused period and comma during entry in a float field, rejecting saving of a given record. Upon "save of record" the program crashed. Problem was solved after removal of software and fresh install from EpiData website . Please report problems and function as done previously. In particular on issues above. Following end of the classes (mid March) I will attempt to release all exercises for download from the website. regards Jens Lauritsen Initiator and Coordinator EpiData Association Denmark. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 135, Issue 1 ********************************************

1 1

comments
by epidata-list＠lists.umanitoba.ca 28 Jan '15

28 Jan '15

Dear all, I did a small test with a few variables to test the new program 2.0. This are my comments. Is clear that the visual result can be modified more easily, but in the 3.1 version is possible to make some changes to help improve the data load. The ease of incorporating commands from the contextual menu is also really important. Another positive aspect is the impossibility of data entry to modify the program load (which is possible in version 3.1) Now I’ll discuss the negatives: 1. I couldn't export an easy project to spss. I get error messages and of course does not generate the corresponding database. 2. when generating the value labels I found that the 3.1 was easier because I could cut and paste and then give properly. In the new program must copy and paste each of the categories slowing the process. 3. The check file is missing. Except jumps to other questions you can't (at least I didn't understand how) to use the very useful ‘if then end if’, ‘hide’, etc. etc. It will be possible to use these tools in the future? If not, I think version 3.1 will remain well above the new 2.0 I Take this opportunity to thank you, the program EpiData 3.1 has been (and still is) a very useful tool. For example right now we are putting in place a loading program for a study of climate and school violence (from the ministry of education) to about 20,000 cases. The program does not disappoint EVER. So thank you very much for yours efforts. Sorry for my poor English, bellow you will find my comments in spanish Mg. Luis D'Angelo - Ministerio de Justicia y Derechos Humanos - Argentina Estimados, he hecho una pequeña prueba con unas pocas variables para probar el nuevo programa 2.0. Van mis comentarios al respecto. Como positivo es claro que el resultado visual puede ser modificado con mayor facilidad, aunque en la versión 3.1 también es posible hacer algunas modificaciones que ayudan a mejorar la carga de datos. La facilidad de incorporar los comandos a partir del menú contextual es también algo realmente importante. Otro aspecto positivo a destacar es la imposibilidad del data entry de modificar el programa de carga (cosa que sí es posible en la versión 3.1) Ahora van las críticas 1. no pude exportar un archivo muy sencillo al spss. Me da mensajes de error y por supuesto no genera la base de datos correspondiente. 2. al momento de generar los value labels encontré que el 3.1 era más sencillo porque podía cortar y pegar y luego darle forma adecuada. En el nuevo programa se debe copiar y pegar cada una de las categorías haciendo más lento el proceso. 3. El archivo check se echa de menos. Salvo los saltos a otras preguntas no se puede (al menos yo no he comprendido cómo) utilizar el muy útil 'if then end if', el comando 'hide', etc. Va a ser posible utilizar estas herramientas en el futuro? Si no es así pienso que la versión 3.1 va a continuar siendo muy superior a la nueva 2.0 Aprovecho para agradecer el programa epidata 3.1 que ha sido (y sigue siendo) una herramienta de gran utilidad. Por ejemplo en estos momentos estamos poniendo a punto un programa de carga para un estudio de clima y violencia en la escuela (desde el ministerio de educación) para alrededor de 20.000 casos. El programa no decepciona NUNCA. De modo que muchas gracias por los esfuerzos realizados. Mg. Luis D'Angelo - Ministerio de Justicia y Derechos Humanos - Argentina

1 0

Major step forward: V2.0 of EpiData Software released today for General Use !!
by epidata-list＠lists.umanitoba.ca 27 Jan '15

27 Jan '15

Dear All Today we have placed v2.0 for general download on Http://www.epidata.dk/download.php We hope that the users regard this release as a major step forward in securing prime data quality for all projects be they small and simple or complex. The main changes since last release in June 2014 are: Creation of Relational databases - that is multiple dataforms within a project. Graphical re-design of interface and icons Backup file principle now places backups in a sub-folder to the epx data file Securing function at all levels in view of reported bugs and problems Version control at start of software against what is current version. More news will come later, but please do advice users to make sure that all is well functioning. As with other software one should also secure backups before starting to use a new version. As users of this list you will know that very much work went into securing functionality, removing bugs and finding suitable design for the new aspects. Should you find problems or unexpected closures do report to the bug system or here on the list. The only functionality not implemented in the EPX file based new versions and therefore only available in EpiData Classic is scripting, e.g. calculation of complex summary scores following entry. This will come later after we have developed restricted user access and possibly GCP compliancy. During the following days we will focus on updating the website - "recent changes lists" and similar aspects. We are aware that some functions and ways of working are not fully documented on the website, wiki or in the pdf introduction documents. But these will follow. Comments and reports on experiences with the new versions are highly welcomed on the list. regards Torsten Bonde Christiansen Jens Lauritsen EpiData Association, Denmark

1 0

Mac Workarounds?
by epidata-list＠lists.umanitoba.ca 21 Jan '15

21 Jan '15

Hello all: This appears to have been addressed back in 2013 for v1.4.2, but nothing from that discussion is working. I have downloaded EpiData Entry Client on my Mac (intel), but it does not work. No matter which download method--zip versus dmg--the client opens, but does absolutely nothing. I cannot open any of the .epx files, can't actually quit, etc. There were some terminal and script workarounds in the 2013 discussion. These also do not work. What is going on? _______________________________________________________________ Mark G Shrime, MD MPH FACS Harvard Interfaculty Initiative in Health Policy Clinical Instructor, Harvard Medical School shrime(a)gmail.com scholar.harvard.edu/shrime hsph.harvard.edu/mark-shrime/ Keep me away from the wisdom which does not cry, the philosophy which does not laugh, and the greatness which does not bow before children. —Kahlil Gibran With purity and with holiness I will pass my life and practice my art. —Hippocrates

1 1

EpiData Analysis (v. 2.2.2.183)
by epidata-list＠lists.umanitoba.ca 16 Jan '15

16 Jan '15

Thank you for the new version of the EpiData Analysis software. Unfortunately, the available zipped version is only the setup.exe file which has been zipped, so there is no readme file. For those without administrator rights, the setup file is not useful. Could you please upload a zipped version which can be used by those of us without administrator rights. Many thanks, 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 Public Health England, 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 by Symantec.Cloud, but please re-sweep any attachments before opening or saving. http://www.gov.uk/PHE **************************************************************************

1 1

RE: Error Opening the Project in EpiData Manager
by epidata-list＠lists.umanitoba.ca 16 Jan '15

16 Jan '15

Thanks Torsten, for updating the test version as I was facing the same issue. I have just tried to use it and I have created a small relational project in it. I am able to enter the data in it via Entry Client but unable to reopen the project file in EpiData Manager. Following error occurs while opening the project: Unable to open the file: C:\Users\...\MyProject.epx ERROR: A required XML attribute was not found. The tag #document->EpiData->DataFiles->DataFile(dataform_1) expected an attribute with the name "afterRecordState"! I am using the following version of EpiData Manager: Program Version: 2.0.23[RC3] r1078 Core version: 2.0.0.0 r1103 FPC version: 2.6.4 Plateform: i386-Win32 Please suggest me, if I am making a mistake or not doing it proper way. Thanks & best regards, Rasool Bux Manager, Information Services, Aga Khan University, Stadium Road, Karachi. Pakistan -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Thursday, January 15, 2015 6:27 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Updated testversion of EpiData Manager v2.0 RC3 Dear List. Due to an error in building the test version of EpiData Manager v2.0 RC3, the version intended for Windows (32-bit, standard) edition could not create related datastructures. Today we have updated the installation on the testing webpage (here <http://epidata.dk/testing.php>) with a new version (2.0.0.23 RC3). We encourage all to test this new version and report any errors back on the mailing list or on the bugtracker <http://www.epidata.info/flyspray/>. Kind regards, Torsten Bonde Christiansen. EpiData Association. _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list ________________________________ 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 3

New EpiData Analysis.
by epidata-list＠lists.umanitoba.ca 15 Jan '15

15 Jan '15

Hi List. Since EpiData Manager and EntryClient have reached the public testing stage, EpiData Analysis have been updated to support the new EPX file format (v3) as well as the format used by Manager & EntryClient v1.4. With the test release of Manager & EntryClient v2.0 we started supporting multiple dataforms/datasets. However EpiData Analysis only supports one dataset and therefor when loading files made with Manager v2.0 only the first dataform/dataset will be loaded. If you wish to load any other dataforms than the first, you should use the "Export" tool in EpiData Manager where you can select the dataform you wish to load in Analysis, and export it to a new EPX file. The new version of EpiData Analysis (v. 2.2.2.183) is available from our normal download webpage: http://epidata.dk/download.php Kind regards, Torsten Bonde Christiansen EpiData Association.

1 0

Updated testversion of EpiData Manager v2.0 RC3
by epidata-list＠lists.umanitoba.ca 15 Jan '15

15 Jan '15

Dear List. Due to an error in building the test version of EpiData Manager v2.0 RC3, the version intended for Windows (32-bit, standard) edition could not create related datastructures. Today we have updated the installation on the testing webpage (here <http://epidata.dk/testing.php>) with a new version (2.0.0.23 RC3). We encourage all to test this new version and report any errors back on the mailing list or on the bugtracker <http://www.epidata.info/flyspray/>. Kind regards, Torsten Bonde Christiansen. EpiData Association.

1 0

User manual and podcast
by epidata-list＠lists.umanitoba.ca 13 Jan '15

13 Jan '15

Dear Jens Fabulous work I do hope that we can get you to do some podcasts of basic and advanced functions of Epidata manager! Thank you Sincerely Thambu Dr Thambu David Sudarsanam MD, DipNB Professor and Head Medicine Unit 2 and Clinical Epidemiology Unit Christian Medical College, Vellore 632004, India CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Tuesday, January 13, 2015 11:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 134, Issue 5 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-list Digest, Vol 133, Issue 2 (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 12 Jan 2015 23:16:03 +0000 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] RE: EpiData-list Digest, Vol 133, Issue 2 To: "'epidata-list(a)lists.umanitoba.ca'" <epidata-list(a)lists.umanitoba.ca> Message-ID: <8E2983B7618DB64E98E570D92FB07DF58C71FF66(a)HV0NTEML01.AD.CCDHB.HEALTH.NZ> Content-Type: text/plain; charset="us-ascii" Thanks Jens - this is very good news. Looking forward to seeing the instruction manual. Best wishes Christine -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Wednesday, 24 December 2014 7:01 a.m. To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 133, Issue 2 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..." ______________________________________________________________________________ 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. ______________________________________________________________________________ ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 134, Issue 5 ********************************************

1 0

RE: EpiData-list Digest, Vol 133, Issue 2
by epidata-list＠lists.umanitoba.ca 12 Jan '15

12 Jan '15

Thanks Jens - this is very good news. Looking forward to seeing the instruction manual. Best wishes Christine -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Wednesday, 24 December 2014 7:01 a.m. To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 133, Issue 2 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..." ______________________________________________________________________________ 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. ______________________________________________________________________________

1 0

Any Problems identified in Pre-release Manager and EntryClient ? - if so please report these.
by epidata-list＠lists.umanitoba.ca 08 Jan '15

08 Jan '15

Dear All It is now about 2 weeks since we copied the pre-release versions of EpiData Manager and Epidata EntryClient to the testing page for download. It seems that no major problems have been identified - since we have received no reports of such errors. We are just now building an in-house test schedule, which will allow us to do a structured test of the functionality and aspects of the software before public release. All the way from defining a project, to exporting data. Once the routines are ready they will be laid out for public download. Such routines are a requirement for meeting GCP (Good Clinical Practice guidelines) standards, which are at the core of the next release cycle following current. Should any users have found problems do let us know at this point. Since we wish as soon as possible to exchange current public release version with the latest version 2.x capable of related dataforms. You can comment to this list or send a "private" e-mail to info-at-epidata.dk (exchange -at- with @) regards Jens Lauritsen EpiData Association

1 0

Re:cannot read local sign in EpiData Entry classic 3.1
by epidata-list＠lists.umanitoba.ca 08 Jan '15

08 Jan '15

TRY THIS FIELD1 BEFORE ENTRY IF (oeoe="湖") THEN GOTO FIELD2 ENDIF END END‍ ------------------ ------------------ NAME：梁铭坚 ADD：广州市越秀区东风中路503号东建大厦9楼广州社情民意研究中心调查室数据组 Tel： 83548519 13826023620 E-mail:17526206@qq.com ------------------ Original ------------------ From: "epidata-list-request";<epidata-list-request(a)lists.umanitoba.ca>; Date: Thu, Jan 8, 2015 02:00 AM To: "epidata-list"<epidata-list(a)lists.umanitoba.ca>; Subject: EpiData-list Digest, Vol 134, Issue 2 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:cannot read local sign in EpiData Entry classic 3.1 (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Jan 2015 19:04:40 +0000 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re:cannot read local sign in EpiData Entry classic 3.1 To: epidata-list(a)lists.umanitoba.ca Message-ID: <CACEkZF9YvsoP6kMoXxkqOHgwPtzrSi0xoJn_YVScpYreSzKEoQ(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Try to follow the chronology may be After Entry rather than Before Entry Not really clear from your command lines Other issue, you may want to try is: Clear the field first then Jump into I hope that this will help Tieble On 6 January 2015 at 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. cannot read local sign in EpiData Entry classic 3.1 > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 06 Jan 2015 07:25:45 GMT > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] cannot read local sign in EpiData Entry > classic 3.1 > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <1420529145447.8033.23498@webmail5> > Content-Type: text/plain; charset=UTF-8 > > A user has sent this:I find a bug. > > EpiData (Classic) Entry v3.1 donot read "湖" > > for example > > FIELD1 > BEFORE ENTRY > IF oeoe="湖" THEN > GOTO FIELD2 > ENDIF > END > END > > the command cannot jump to field2. it has any way tosolve the problem. > I suggest to use the new EntryClient and Manager instead . It seems for > this standard jump, that you could use that one. > > Or else use numbers or a letter a....z instead of the local sign "湖" > regards > Jens Lauritsen > EpiData Association > > > > > > <wuyonggang3852(a)vip.qq.com> > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 134, Issue 1 > ******************************************** > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 134, Issue 2 ********************************************

1 1

Re:cannot read local sign in EpiData Entry classic 3.1
by epidata-list＠lists.umanitoba.ca 06 Jan '15

06 Jan '15

Try to follow the chronology may be After Entry rather than Before Entry Not really clear from your command lines Other issue, you may want to try is: Clear the field first then Jump into I hope that this will help Tieble On 6 January 2015 at 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. cannot read local sign in EpiData Entry classic 3.1 > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 06 Jan 2015 07:25:45 GMT > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] cannot read local sign in EpiData Entry > classic 3.1 > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <1420529145447.8033.23498@webmail5> > Content-Type: text/plain; charset=UTF-8 > > A user has sent this:I find a bug. > > EpiData (Classic) Entry v3.1 donot read "湖" > > for example > > FIELD1 > BEFORE ENTRY > IF oeoe="湖" THEN > GOTO FIELD2 > ENDIF > END > END > > the command cannot jump to field2. it has any way tosolve the problem. > I suggest to use the new EntryClient and Manager instead . It seems for > this standard jump, that you could use that one. > > Or else use numbers or a letter a....z instead of the local sign "湖" > regards > Jens Lauritsen > EpiData Association > > > > > > <wuyonggang3852(a)vip.qq.com> > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 134, Issue 1 > ******************************************** >

1 0

cannot read local sign in EpiData Entry classic 3.1
by epidata-list＠lists.umanitoba.ca 06 Jan '15

06 Jan '15

A user has sent this:I find a bug. EpiData (Classic) Entry v3.1 donot read "湖" for example FIELD1 BEFORE ENTRY IF oeoe="湖" THEN GOTO FIELD2 ENDIF END END the command cannot jump to field2. it has any way tosolve the problem. I suggest to use the new EntryClient and Manager instead . It seems for this standard jump, that you could use that one. Or else use numbers or a letter a....z instead of the local sign "湖" regards Jens Lauritsen EpiData Association <wuyonggang3852(a)vip.qq.com>

1 0

RE: [EpiData-list] New pre-public release of Manager (v2.0.0.22) and EntryClient (v2.0.0.7)
by epidata-list＠lists.umanitoba.ca 23 Dec '14

23 Dec '14

Dear Jens, Can we run EntryClient in multiple instances? As Epidata classic 3.1 version. Because I have used the relational double entry verification with Epidata using the execute wait command instead of relate in the _dbl.chk file for relational file in real time. This is the my Idea for double entry & verification for relational files in Epidata 3.1. Thanks & best regards, Rasool Bux -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Tuesday, December 23, 2014 5:28 AM To: EpiData-list(a)lists.umanitoba.ca Subject: [EpiData-list] New pre-public release of Manager (v2.0.0.22) and EntryClient (v2.0.0.7) Dear all We have published new test versions of Manager and EntryClient Manager is now at: v2.0.0.22 EntryClient is now at: v2.0.0.7 With this version we have moved both products from the experimental to the pre-public release version area of the testing page on http://www.epidata.dk/testing.php We have removed quite many bugs and changed principles to what we find is rather stable for the usage of: - relational datasets - "one form" datasets - external value labels in a different file - importing data into labels - Many other possibilities for import, export etc, but with added support for import from clipboard, alignment and many other features, which will be documented in introduction manuals in early 2015. Another implemented feature is the automatic checking of version against test versions and public versions. WARNING: Although we think this is quite stable do NOT use on production data or real projects still. If you install from the test page, the ordinary distribution version will be overwritten. So to continue with that one get the zipped/tar compressed version of the test software instead and unpack to a different folder on your computer. Please test and report . We are now working with details on the passage to a full public release version. Next evaluation of discussions and reported bugs will take place early 2015. To analyse data in a relational dataset you should export one dataform at a time. EpiData Analysis cannot read related data sets at this point. regards Jens Lauritsen EpiData Association _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list ________________________________ 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 1

New pre-public release of Manager (v2.0.0.22) and EntryClient (v2.0.0.7)
by epidata-list＠lists.umanitoba.ca 22 Dec '14

22 Dec '14

Dear all We have published new test versions of Manager and EntryClient Manager is now at: v2.0.0.22 EntryClient is now at: v2.0.0.7 With this version we have moved both products from the experimental to the pre-public release version area of the testing page on http://www.epidata.dk/testing.php We have removed quite many bugs and changed principles to what we find is rather stable for the usage of: - relational datasets - "one form" datasets - external value labels in a different file - importing data into labels - Many other possibilities for import, export etc, but with added support for import from clipboard, alignment and many other features, which will be documented in introduction manuals in early 2015. Another implemented feature is the automatic checking of version against test versions and public versions. WARNING: Although we think this is quite stable do NOT use on production data or real projects still. If you install from the test page, the ordinary distribution version will be overwritten. So to continue with that one get the zipped/tar compressed version of the test software instead and unpack to a different folder on your computer. Please test and report . We are now working with details on the passage to a full public release version. Next evaluation of discussions and reported bugs will take place early 2015. To analyse data in a relational dataset you should export one dataform at a time. EpiData Analysis cannot read related data sets at this point. regards Jens Lauritsen EpiData Association

1 0

merging two rec files
by epidata-list＠lists.umanitoba.ca 04 Dec '14

04 Dec '14

i have not been able to merge two rec files and can it be done. Regards

1 0

Re: EpiData-list Digest, Vol 132, Issue 7
by epidata-list＠lists.umanitoba.ca 27 Nov '14

27 Nov '14

Check for update would be a good idea However, it could be done as Check for update now, or Check for update in a week or next time when EpiData is launched. Kind regards Tieble On 22 November 2014 at 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. Re: automatic warning/information on versions ? > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 22 Nov 2014 13:02:09 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] automatic warning/information on versions > ? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > CAGCnkGU66_DiM0mdvC0ruoaNuSUndFgMXdjQ5EgXGdYBQR6n4Q(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi Jens > > This option sound good for me :) > As ouy say, many users are not listening the list. > > Regards > Gilles > > > > > > > *Dr Gilles DESVE Epiconcept consultant Mobile : 33 (0)6 87 73 50 88 Fax : > 33 (0)9 72 12 20 81 * > > 2014-11-20 23:51 GMT+01:00 <epidata-list(a)lists.umanitoba.ca>: > > > I would like this option, Jens. It is very commonly used - along with a > > preference to NOT check for updates. > > Jamie > > > > On Nov 20, 2014, Jens wrote: > > > > > We could therefore consider to have the end user decide an option > saying > > "check for new version every x days" (e.g. x could be 7). Please give > > viewpoints and considerations on this. > > > > > > > _______________________________________________ > > 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 132, Issue 7 > ******************************************** >

1 0

automatic warning/information on versions ?
by epidata-list＠lists.umanitoba.ca 22 Nov '14

22 Nov '14

With development of the software new versions are released every time development has reached a certain point. It can be annoying to be informed very often about new releases from software, since this takes time and processor and sometimes also for users costly Internet connections. On the other hand we know that some users run into problems due to NOT having updated to a newer version in which a given problem was solved. We could therefore consider to have the end user decide an option saying "check for new version every x days" (e.g. x could be 7). Please give viewpoints and considerations on this. Also I noted today that some "semi-comercial" sites most likely running from the advertisements on that site offer download of the software . The webplace in question have been contacted by me. If we have automatic checking with reference to the true EpiData website, that problem would be minimized . Is this a desired option or does it work fine with the users getting information from this list in general ? . We know the list have about 700 persons "listening", but the number of actual users is very much larger and these other users do not easily know that there is a new version around. regards Jens Lauritsen EpiData Association

1 2

Default behaviour in EntryClient during entryentry - and simplification
by epidata-list＠lists.umanitoba.ca 20 Nov '14

20 Nov '14

The next test build of Manager and EntryClient will be released rather soon, but not this week. The aspects we are working on - apart from securing stability - regards handling complex relational entry. To do so properly and with sufficient stability accross projects, operating systems and countries we need to be very focused on the niche in which EpiData Software is working. This demands some simplifications, which will be seen in the next test release: 1 backup after entry: Until now the backup files (e.g. Clinical_Example_2014-10-28_0.epz) would be placed in the "home" dir of the EntryClient user (e.g. for user jla = c:\documents and settings\jla\documents\EpiData\backup) . This resulted in a complex demand to handle a large number of combinations of operating systems and user rights. >From now on the backup file will be placed in a subfolder to the folder where EntryClient opens a given epx/epz file for entry. If the user want the backup placed in another folder this must be defined with a startup option. 2 Which status of addition/editing of records in EntryClient Aspects of this has been defined in preferences for EntryClient. >From now on EntryClient is assumed to be adding records to projects always. But obviously in such a way that if a given dataform has a key and that key is typed in, then the user will be informed and given the opportunity to jump to the relevant record. 3 For related systems the order of activation of "child" forms is part of the project epx file. Not a "preference" setting. This might seem a bit technical, but is needed in order to make sure that the software creates consistent data and also that we can complete the work within the funding of the project. Funding is always an issue for this and other development projects. Comments to this or other aspects of development are welcome. regards Jens Lauritsen EpiData Association

1 1

Help
by epidata-list＠lists.umanitoba.ca 12 Nov '14

12 Nov '14

HI, I am very new to EpiData and am looking to use it for a Study which will require a relational database ie one study participant with multiple visits and tests Am I right in interpreting that only EpiData Classic Entry 3.1 is the only software that I can currently use. I have had a trial run using EpiData Manager 2.0.0.1 and it seems perfect for our study. Is it worth holding off setting up my database for the beta release of this version? When is it likely to be released? Kind regards, Emma Emma Jamieson ORCHID Study SouthWest Coordinator RCSWA - UWA Building 3, Edith Cowan University, Robertson Drive, PO Box 412, BUNBURY WA, 6230 Ph: +61 8 9722 0510 M: 0478 193 116 F: +61 8 9722 0555 -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Friday, 7 November 2014 2:01 AM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 132, Issue 3 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. Status testversions of 2.0 Manager and EntryClient (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 05 Nov 2014 21:13:16 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Status testversions of 2.0 Manager and EntryClient To: EpiData-list(a)lists.umanitoba.ca Message-ID: <545A84DC.30204(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed The status and reported problems in the development of v2x of Manager and EntryClient is such that: a. Basically we find rather stable function with few access violations and remaining major problems b. We found reason to further change the xml structure contained in the epx file when dataforms are in a relational structure. This means that examples you have worked with in the testing of v2x might not work, when we release the next test build. c. A number of minor points have been found in various parts of the system. Mostly these were of text formulations, which had not taken the relational dataform aspect into consideration. I expect that the next test version will be moving from experimental level to pre-release level. This is an indication that we are approaching something which in the end will be applicable for true data entry and documentation. Further thoughts and reports of or examples of malfunction are highly appreciated. Jens Lauritsen EpiData Association, Denmark ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 132, Issue 3 ********************************************

1 0

Merging two rec files
by epidata-list＠lists.umanitoba.ca 12 Nov '14

12 Nov '14

Dear EpiData users and experts I am trying to merge two files with different number of records and fields! The first file (intake) contains 1433 records and there is 21 fields in each record. The second one contains 1301 records and and each record contains 31 fields. Each one of the 1301 record has a corresponding record in the first file (same code). I would like to merge the two files, based on the code, so that I have a third file with 1301 records and 52 fields. I tried to use the merge function in EpiData Entry, but it didn't work (the product was a file with only 47 fields instead of 52 ). I must say that some fields in the two files have the same name-can this be a reason for not merging these fields? Your help will be highly appreciated Best, MK

1 1

Status testversions of 2.0 Manager and EntryClient
by epidata-list＠lists.umanitoba.ca 05 Nov '14

05 Nov '14

The status and reported problems in the development of v2x of Manager and EntryClient is such that: a. Basically we find rather stable function with few access violations and remaining major problems b. We found reason to further change the xml structure contained in the epx file when dataforms are in a relational structure. This means that examples you have worked with in the testing of v2x might not work, when we release the next test build. c. A number of minor points have been found in various parts of the system. Mostly these were of text formulations, which had not taken the relational dataform aspect into consideration. I expect that the next test version will be moving from experimental level to pre-release level. This is an indication that we are approaching something which in the end will be applicable for true data entry and documentation. Further thoughts and reports of or examples of malfunction are highly appreciated. Jens Lauritsen EpiData Association, Denmark

1 0

Re: EpiData-list Digest, Vol 132, Issue 1
by epidata-list＠lists.umanitoba.ca 03 Nov '14

03 Nov '14

1 0

Epola Contact tracing and risk assessment system
by epidata-list＠lists.umanitoba.ca 02 Nov '14

02 Nov '14

Hello List, As a District Medical Officer, I will have to prepare for Contact tracing and risk assessment/managing the follow-up of contacts if an unsuspected Ebola case should surface in my community. I have started to think of a call center / health care registration system in EpiData Manager with relate feature: One event/Index case, several contacts with contact details, and follow-up details of contacts. In the event that one of the contacts should develop symptoms, then the secondary case´s contacts will have to be traced. The design of the system certainly needs some consideration. This is a global concern, and I imagine several organizations probably already have made or have plans to develop such a system. EpiData´s share-friendly approach should be ideal under current circumstance. ECDC have already done so for food/waterborne outbreak investigation. 1. Anybody already made a system, wiling to share? 2. Any major Organization seeing the benefit of same-format reporting, and willing to support development of system/templates? 3. I assume that final release of ED 2.0 with relate feature is imminent. I therefore start to work on a functional but simple local system anyway, and will seek advice from the list as needed. Where I am right now, I struggle to carry the content of more than one unique key variable over from the parent to the child record. Any comments? Best regards, Vegard Hoegli District Medical Officer Skien, Norway

1 2

Adding value labels in EpiData Manager 2.0.0.1 RC2 24. Oct
by epidata-list＠lists.umanitoba.ca 28 Oct '14

28 Oct '14

Hello, I am experimenting with the new release candidae, and I´m trying to design a simple registration form in EpiData Manager. I have a couple problems that may be trivial, but nevertheless, I´m a bit stuck: 1: In the Win 64 bit version I struggle to edit Value labels for an integer field. I click "New" in the Valuelabel button and bring up the Value label editor, but I am not able to add any labels. I can, However add new values, but seen not to be able to get the label line to get focus. Tried with Enter, Tab, arrow keys, Mouse click etc but nothing works. When I Open the same file in Mac, However, There are no problems at all creating and editing a set of Value labels. I notice that i first choose between "Internal" and "external" values - a choice which didm´t appear in the Windows version. 2: Is there a way to edit the sequence the various variables get focus? After a bit of editing, the flow of focus has become mixed up. 3. Is If-then calculations implemented? I experiment with making a registration form for a call-center. First i define a variable "Caller´s name" Then a boolean variable: Do you call us on behalf of yourself? Then a variable with the name of the patient. If the call is about the caller herself, I would like to copy the content from "caller´s name" to "patient´s name" and then skip the patient name field. I realize that this not strictly necessary, but just for the experiment´s sake.. Regards, Vegard Hoegli, Skien, Norway

1 3

SV: [EpiData-list] Adding value labels in EpiData Manager 2.0.0.1 RC2 24. Oct
by epidata-list＠lists.umanitoba.ca 28 Oct '14

28 Oct '14

Such reports are very valuable. Since we upload minor adaptations quite frequently please also include build, which you get from version info in the help menu. Regards Jens Lauritsen EpiData Association epidata-list(a)lists.umanitoba.ca skrev: >Hello, >I am experimenting with the new release candidae, and I´m trying to design >a simple registration form in EpiData Manager. > >I have a couple problems that may be trivial, but nevertheless, I´m a bit >stuck: > >1: In the Win 64 bit version I struggle to edit Value labels for an integer >field. I click "New" in the Valuelabel button and bring up the Value label >editor, but I am not able to add any labels. I can, However add new values, >but seen not to be able to get the label line to get focus. Tried with >Enter, Tab, arrow keys, Mouse click etc but nothing works. > >When I Open the same file in Mac, However, There are no problems at all >creating and editing a set of Value labels. I notice that i first choose >between "Internal" and "external" values - a choice which didm´t appear in >the Windows version. > >2: Is there a way to edit the sequence the various variables get focus? >After a bit of editing, the flow of focus has become mixed up. > >3. Is If-then calculations implemented? I experiment with making a >registration form for a call-center. First i define a variable "Caller´s >name" Then a boolean variable: Do you call us on behalf of yourself? Then a >variable with the name of the patient. If the call is about the caller >herself, I would like to copy the content from "caller´s name" to >"patient´s name" and then skip the patient name field. I realize that this >not strictly necessary, but just for the experiment´s sake.. > > >Regards, > >Vegard Hoegli, >Skien, Norway >_______________________________________________ >EpiData-list mailing list >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Updated experimental test version of relational datasets (Manager and EntryClient 2.0.0.0)
by epidata-list＠lists.umanitoba.ca 24 Oct '14

24 Oct '14

On Oct. 9th. we announced release of an experimental test version capable of creating relational structures. See: http://lists.umanitoba.ca/pipermail/epidata-list/2014q4/002546.html The following major bugs have been fixed and new versions are available: Updated versions are placed for download on http://www.epidata.dk/testing.php Manager: 1. Reports were not saved correctly as txt or html 2. Value labels could not be edited 3. Export had malfunction EntryClient: Would not propagate correctly the key from one level to the next in some instances. Please test and verify function in as well simple and complex situations. Please notice that version is still - in this upload - 2.0.0.0, but creation date is Oct 22nd., It is a good idea to use a particular ini file and recent file saving, when you are testing. To do this you add parameters/options to the start. To see the options you can run from a terminal, epidatamanager -h entryclient -h which will give the explanation, e.g. for configurations files: -i=mytest.cfg recent file list: -r=testfiles.txt regards Torsten Bonde Christiansen and Jens Lauritsen EpiData Association To verify correct version: "Copy version Info" found in the help menu and check: Manager: Program version: 2.0.0.0[RC2] r1010 EntryClient: Program version: 2.0.0.0[RC2] r411 Both of them: Core version: 2.0.0.0 r1080

1 2

Condensing several Y/N results into one table
by epidata-list＠lists.umanitoba.ca 10 Oct '14

10 Oct '14

Dear list, I try to condense the frequency of several yes/no variables into one table: In a patient file I register 12 specific procedures, where each patient get a variable number of "yes" i.e. Intravenous antibiotics N % Y 126 27.8 . 328 72.2 Total 454 100.0 Pain relief N % Y 113 24.9 . 341 75.1 Total 454 100.0 etc I want to transform the result into: Treatment summary N % Intravenous antibiotics 126 27.8 Pain relief 113 24.9 etc Total 454 100.0 In the old Epi Info v6 this was relatively simple via the REPORT command, where a template .RPT file could pick specific values from tablecells across several variables. I can copy and paste values from individual tables into a spreadsheet, but it would obviosly be more user-friendly to a routine user to be able to present the result in EpiData.directly. Any suggestions? Best regards, Vegard Hogli CMO, Skien, Norway

1 1

New test release of Manager and EntryClient (v2....)
by epidata-list＠lists.umanitoba.ca 10 Oct '14

10 Oct '14

Dear all Following a remarkable effort in many areas it is now possible to download experimental versions 2 of Epidata Manager and EntryClient from the page: http://epidata.dk/testing.php#alpha The overall new aspect is: relational databases This is also explained in the introduction document, which you find here: http://epidata.dk/php/downloadc.php?file=epidatamanagerintro.pdf We have worked a bit to further secure immediate transparency of function. In practice it seems that users are NOT reading manuals, so intuitive function is important, Suggestions to enhance intuitive function are welcomed. For projects with only one single dataform the main change will be new icons and hopefully more stability, since we have removed a number of bugs. Another new aspect is that study information is placed at the front. This is to enhance datadocumentation levels in projects. It is NOT necessary to complete the study information to define data. So if you are not interested in that part just skip it. When you create a new project an instruction is given on screen with a sequence for developing relational data. Be aware that these versions are still in the early testing phase. Which means that you should NOT use them for ongoing projects, and also that you should use them with new projects only. If you have generated relational databases with a previous testversion, then do not continue on that project. What we need - optimally during the coming week - is feedback on: - function, - access violations, - stability in EntryClient - stability in documentation - whether EntryClient creates correct datacontent based on the tree structure of relational databases. It is a rather complex system now, so please be patient and report, such that we can get to a stable level of function soon. We will summarise reports in about 10 days following a well deserved break in development. Following clarification of these issues we will release another test build, and once all problems are solved or fixed in a stable way the first public v2.0 will be released. If you have longer test files and explanations that you wish to send us and not to the list, then use info at epidata.dk for such mails - disregard the warning sent to you, we will read it. regards Jens Lauritsen Epidata Association

1 1

Re: EpiData-list Digest, Vol 130, Issue 8
by epidata-list＠lists.umanitoba.ca 01 Oct '14

01 Oct '14

Thanks to all of you for your response. Jens and Renate, the syntax worked perfectly. Walter On Tue, Sep 30, 2014 at 8: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-list Digest, Vol 130, Issue 7 - count number of > records (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 29 Sep 2014 17:26:21 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] RE: EpiData-list Digest, Vol 130, Issue 7 - > count number of records > To: "'epidata-list(a)lists.umanitoba.ca'" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <FE3BD206B1C952409F1892C47023A625AF98A1(a)PDHU-EXCHANGE1.pdhu.on.ca> > Content-Type: text/plain; charset="us-ascii" > > Hi Walter, > > You could create a count of the number of records per unique individual > and then select the first record: > > Sort idunique visitdate > > gen i count = 1 > Var Name count of type Integer and length: 9 decimals 0 > if idunique = idunique[_n-1] then count= count[_n-1] + 1 > count= count[_n-1] + 1 > the [_n] indicates recnumber and by subtracting one "_n-1" we get > the previous record > > select if count=1 > > Hope this helps, > > Renate > > -----Original Message----- > From: epidata-list-bounces(a)lists.umanitoba.ca [mailto: > epidata-list-bounces(a)lists.umanitoba.ca] On Behalf Of > epidata-list-request(a)lists.umanitoba.ca > Sent: Monday, September 29, 2014 1:01 PM > To: epidata-list(a)lists.umanitoba.ca > Subject: EpiData-list Digest, Vol 130, Issue 7 > > 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. (no subject) (epidata-list(a)lists.umanitoba.ca) > 2. Re: (no subject) (epidata-list(a)lists.umanitoba.ca) > 3. Re: first observation among several for each person (no > subject) (epidata-list(a)lists.umanitoba.ca) > 4. Re: (no subject) (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 29 Sep 2014 15:41:17 +0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] (no subject) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <CAMLtmTBnDMV9Lrnq2UxM5t9H4Nd9B41aHJULbr1Y5qDL= > 3NY5Q(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Dear ALL, > > I have a data set where some patients have more than one entry (visit) i.e. > same patient with different visit dates, while some have only one entry > (visit). I would like to select only the first visit from each patient (The > variables to use are id_unique and visit_date) > > Regards > > Walter > > > ------------------------------ > > Message: 2 > Date: Mon, 29 Sep 2014 15:56:52 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] (no subject) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > CAHDXojvVqiyuSKVToxE4q82DFva6Bv6+bddzpKhxqX7FNbmV1w(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi. > I cannot give you the comand syntax in epidata (maybe in Stata) but what > you could simply do is the following: > Create a variable first_visit_date = min(visit_date) by (id_unique) select > where visit_date = firs_visit_date. > > Serge > > 2014-09-29 14:41 GMT+02:00 <epidata-list(a)lists.umanitoba.ca>: > > > Dear ALL, > > > > I have a data set where some patients have more than one entry (visit) > i.e. > > same patient with different visit dates, while some have only one > > entry (visit). I would like to select only the first visit from each > > patient (The variables to use are id_unique and visit_date) > > > > Regards > > > > Walter > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > -- > *M. Aymar Serge SOMDA, BEng. MMath. MSPH.* > *M?thodologiste - Biostatisticien* > * > Chef Unit? de Formation et d'Appui M?thodologique Centre MURAZ > Bur: (226) 20 97 01 02 Poste 438 > GSM: (226) 70 44 33 22 > Bobo Dioulasso, Burkina Faso > Email: serge.somda(a)centre-muraz.bf > http://www.centre-muraz.bf/ > > Cellule de Biostatistique > Institut Universitaire du Cancer > Toulouse - Oncopole > Bur: (33) (0)531 155 860 > GSM: (33) (0)604 521 773 > Toulouse, France > Email: somda.serge(a)iuct-oncopole.fr > http://www.oncopole-toulouse.com/ > > * > * > > > ------------------------------ > > Message: 3 > Date: Mon, 29 Sep 2014 15:26:53 GMT > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] first observation among several for each > person (no subject) > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <1412004413115.66366.16794@webmail5> > Content-Type: text/plain; charset=UTF-8 > > In analysis just do this: > read "your datafile name" > sort idunique visitdate > gen i number = 1 > if idunique = idunique[_n-1] then number = number[_n-1] + 1 > > * now you have a variable "number", which gives the sequence of > observations for each person. > > select number = 1 > * will now make sure you only analyse the first observation. > > You may also use the commands aggregate, but there would be a problem (as > I remember it) with dates, which are then just integers and no longer dates. > > regards > Jens Lauritsen > EpiData Association > > > > Den 29. sep. 2014, epidata-list(a)lists.umanitoba.ca skrev: > > Hi. > > I cannot give you the comand syntax in epidata (maybe in Stata) but > > what you could simply do is the following: > > Create a variable first_visit_date = min(visit_date) by (id_unique) > > select where visit_date = firs_visit_date. > > > > Serge > > > > 2014-09-29 14:41 GMT+02:00 <<epidata-list(a)lists.umanitoba.ca>>: > > > > > Dear ALL, > > > > > > I have a data set where some patients have more than one entry (visit) > i.e. > > > same patient with different visit dates, while some have only one > > > entry (visit). I would like to select only the first visit from each > > > patient (The variables to use are id_unique and visit_date) > > > > > > Regards > > > > > > Walter > > > _______________________________________________ > > > EpiData-list mailing list > > > EpiData-list(a)lists.umanitoba.ca > > > <http://lists.umanitoba.ca/mailman/listinfo/epidata-list> > > > > > > > > > > > > -- > > *M. Aymar Serge SOMDA, BEng. MMath. MSPH.* *M??thodologiste - > > Biostatisticien* > > * > > Chef Unit?? de Formation et d'Appui M??thodologique Centre MURAZ > > Bur: (226) 20 97 01 02 Poste 438 > > GSM: (226) 70 44 33 22 > > Bobo Dioulasso, Burkina Faso > > Email: <serge.somda(a)centre-muraz.bf> > > <http://www.centre-muraz.bf/> > > > > Cellule de Biostatistique > > Institut Universitaire du Cancer > > Toulouse - Oncopole > > Bur: (33) (0)531 155 860 > > GSM: (33) (0)604 521 773 > > Toulouse, France > > Email: <somda.serge(a)iuct-oncopole.fr> > > <http://www.oncopole-toulouse.com/> > > > > * > > * > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > <http://lists.umanitoba.ca/mailman/listinfo/epidata-list> > > > > > ------------------------------ > > Message: 4 > Date: Mon, 29 Sep 2014 11:36:11 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] (no subject) > To: EpiData List <epidata-list(a)lists.umanitoba.ca> > Message-ID: <BLU436-SMTP2503B22D35AA5A8742A58E3FDBA0(a)phx.gbl> > Content-Type: text/plain; charset="windows-1252" > > In Epidata Analysis, do this: > (I?m using id and visit - you cannot have names with underscores in > classic Epidata and it is probably not a good idea in new Epidata) > > define vfirst # > vfirst = 1 > sort id visit > if id = id[recnumber-1] then vfirst = 0 > select vfirst=1 > > id[recnumber-1] refers to the value of id in the previous record. Since > the data are sorted first by id and then visit, this will leave vfirst=1 > whenever id changes. > > Jamie > > On Sep 29, 2014, at 8:41 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > Dear ALL, > > > > I have a data set where some patients have more than one entry (visit) > i.e. > > same patient with different visit dates, while some have only one > > entry (visit). I would like to select only the first visit from each > > patient (The variables to use are id_unique and visit_date) > > > > Regards > > > > Walter > > _______________________________________________ > > 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 130, Issue 7 > ******************************************** > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 130, Issue 8 > ******************************************** >

1 0

RE: EpiData-list Digest, Vol 130, Issue 7 - count number of records
by epidata-list＠lists.umanitoba.ca 29 Sep '14

29 Sep '14

Hi Walter, You could create a count of the number of records per unique individual and then select the first record: Sort idunique visitdate gen i count = 1 Var Name count of type Integer and length: 9 decimals 0 if idunique = idunique[_n-1] then count= count[_n-1] + 1 count= count[_n-1] + 1 the [_n] indicates recnumber and by subtracting one "_n-1" we get the previous record select if count=1 Hope this helps, Renate -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Monday, September 29, 2014 1:01 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 130, Issue 7 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. (no subject) (epidata-list(a)lists.umanitoba.ca) 2. Re: (no subject) (epidata-list(a)lists.umanitoba.ca) 3. Re: first observation among several for each person (no subject) (epidata-list(a)lists.umanitoba.ca) 4. Re: (no subject) (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 29 Sep 2014 15:41:17 +0300 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] (no subject) To: epidata-list(a)lists.umanitoba.ca Message-ID: <CAMLtmTBnDMV9Lrnq2UxM5t9H4Nd9B41aHJULbr1Y5qDL=3NY5Q(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Dear ALL, I have a data set where some patients have more than one entry (visit) i.e. same patient with different visit dates, while some have only one entry (visit). I would like to select only the first visit from each patient (The variables to use are id_unique and visit_date) Regards Walter ------------------------------ Message: 2 Date: Mon, 29 Sep 2014 15:56:52 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] (no subject) To: epidata-list(a)lists.umanitoba.ca Message-ID: <CAHDXojvVqiyuSKVToxE4q82DFva6Bv6+bddzpKhxqX7FNbmV1w(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi. I cannot give you the comand syntax in epidata (maybe in Stata) but what you could simply do is the following: Create a variable first_visit_date = min(visit_date) by (id_unique) select where visit_date = firs_visit_date. Serge 2014-09-29 14:41 GMT+02:00 <epidata-list(a)lists.umanitoba.ca>: > Dear ALL, > > I have a data set where some patients have more than one entry (visit) i.e. > same patient with different visit dates, while some have only one > entry (visit). I would like to select only the first visit from each > patient (The variables to use are id_unique and visit_date) > > Regards > > Walter > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > -- *M. Aymar Serge SOMDA, BEng. MMath. MSPH.* *M?thodologiste - Biostatisticien* * Chef Unit? de Formation et d'Appui M?thodologique Centre MURAZ Bur: (226) 20 97 01 02 Poste 438 GSM: (226) 70 44 33 22 Bobo Dioulasso, Burkina Faso Email: serge.somda(a)centre-muraz.bf http://www.centre-muraz.bf/ Cellule de Biostatistique Institut Universitaire du Cancer Toulouse - Oncopole Bur: (33) (0)531 155 860 GSM: (33) (0)604 521 773 Toulouse, France Email: somda.serge(a)iuct-oncopole.fr http://www.oncopole-toulouse.com/ * * ------------------------------ Message: 3 Date: Mon, 29 Sep 2014 15:26:53 GMT From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] first observation among several for each person (no subject) To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <1412004413115.66366.16794@webmail5> Content-Type: text/plain; charset=UTF-8 In analysis just do this: read "your datafile name" sort idunique visitdate gen i number = 1 if idunique = idunique[_n-1] then number = number[_n-1] + 1 * now you have a variable "number", which gives the sequence of observations for each person. select number = 1 * will now make sure you only analyse the first observation. You may also use the commands aggregate, but there would be a problem (as I remember it) with dates, which are then just integers and no longer dates. regards Jens Lauritsen EpiData Association Den 29. sep. 2014, epidata-list(a)lists.umanitoba.ca skrev: > Hi. > I cannot give you the comand syntax in epidata (maybe in Stata) but > what you could simply do is the following: > Create a variable first_visit_date = min(visit_date) by (id_unique) > select where visit_date = firs_visit_date. > > Serge > > 2014-09-29 14:41 GMT+02:00 <<epidata-list(a)lists.umanitoba.ca>>: > > > Dear ALL, > > > > I have a data set where some patients have more than one entry (visit) i.e. > > same patient with different visit dates, while some have only one > > entry (visit). I would like to select only the first visit from each > > patient (The variables to use are id_unique and visit_date) > > > > Regards > > > > Walter > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > <http://lists.umanitoba.ca/mailman/listinfo/epidata-list> > > > > > > > -- > *M. Aymar Serge SOMDA, BEng. MMath. MSPH.* *M??thodologiste - > Biostatisticien* > * > Chef Unit?? de Formation et d'Appui M??thodologique Centre MURAZ > Bur: (226) 20 97 01 02 Poste 438 > GSM: (226) 70 44 33 22 > Bobo Dioulasso, Burkina Faso > Email: <serge.somda(a)centre-muraz.bf> > <http://www.centre-muraz.bf/> > > Cellule de Biostatistique > Institut Universitaire du Cancer > Toulouse - Oncopole > Bur: (33) (0)531 155 860 > GSM: (33) (0)604 521 773 > Toulouse, France > Email: <somda.serge(a)iuct-oncopole.fr> > <http://www.oncopole-toulouse.com/> > > * > * > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > <http://lists.umanitoba.ca/mailman/listinfo/epidata-list> > ------------------------------ Message: 4 Date: Mon, 29 Sep 2014 11:36:11 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] (no subject) To: EpiData List <epidata-list(a)lists.umanitoba.ca> Message-ID: <BLU436-SMTP2503B22D35AA5A8742A58E3FDBA0(a)phx.gbl> Content-Type: text/plain; charset="windows-1252" In Epidata Analysis, do this: (I?m using id and visit - you cannot have names with underscores in classic Epidata and it is probably not a good idea in new Epidata) define vfirst # vfirst = 1 sort id visit if id = id[recnumber-1] then vfirst = 0 select vfirst=1 id[recnumber-1] refers to the value of id in the previous record. Since the data are sorted first by id and then visit, this will leave vfirst=1 whenever id changes. Jamie On Sep 29, 2014, at 8:41 AM, epidata-list(a)lists.umanitoba.ca wrote: > Dear ALL, > > I have a data set where some patients have more than one entry (visit) i.e. > same patient with different visit dates, while some have only one > entry (visit). I would like to select only the first visit from each > patient (The variables to use are id_unique and visit_date) > > Regards > > Walter > _______________________________________________ > 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 130, Issue 7 ********************************************

1 0

(no subject)
by epidata-list＠lists.umanitoba.ca 29 Sep '14

29 Sep '14

Dear ALL, I have a data set where some patients have more than one entry (visit) i.e. same patient with different visit dates, while some have only one entry (visit). I would like to select only the first visit from each patient (The variables to use are id_unique and visit_date) Regards Walter

1 3

SV: [EpiData-list] Epidata Manager key unique handling
by epidata-list＠lists.umanitoba.ca 19 Sep '14

19 Sep '14

All you have to do, is to define a key, which you find under project properties. After definition of a key, only one observation can be entered for each value. In entryclient a key is always what was "key unique" in Classic Epidata 3.1. Regards Jens Lauritsen epidata-list(a)lists.umanitoba.ca skrev: >Dear all, > >I have tried to use epidata manager & client. The Entry client is not indicating on duplicate entry of id field as in Epi data classic 3.1. Please let me know if there is any option to give message just after entering the key field and stop the entry to next fields. > >Thanks & best regards, >Rasool Bux > >________________________________ > >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 mailing list >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 5

Is there a web tutorial for Epidata manager?
by epidata-list＠lists.umanitoba.ca 15 Sep '14

15 Sep '14

Dear Jens, Is there a web-tutorial for Epidata manager and Client? It would be of great help Basic things are simple to figure out as they are simple if you know the epidata entry 3.1 More advanced work requires some help! regards Thambu

1 0

Epidata Manager key unique handling
by epidata-list＠lists.umanitoba.ca 12 Sep '14

12 Sep '14

Dear all, I have tried to use epidata manager & client. The Entry client is not indicating on duplicate entry of id field as in Epi data classic 3.1. Please let me know if there is any option to give message just after entering the key field and stop the entry to next fields. Thanks & best regards, Rasool Bux ________________________________ 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

transferring a field value
by epidata-list＠lists.umanitoba.ca 09 Sep '14

09 Sep '14

Dear Epidata users I am facing a problem transferring a field value from a parent file to a child file. In the parent file I have initial SRQ (srqinit) and I want the same value to appear in the chiled file. I did the following: In the parent file before file Define Gsrqinit ## Global srqinit MUSTENTER AFTER ENTRY LET Gsrqinit=srqinit END END In the child file BEFORE RECORD srqinit=varsrqinit END However, this doesn't seem to work. Your help will be most appreciated. Mohammed -- *---------------------------------------------------------*

1 1

Relational database
by epidata-list＠lists.umanitoba.ca 09 Sep '14

09 Sep '14

Hi there I have created a relational database for two files. A pre-entry data file (parent file) and an intake file (child file). the relate command is working well. However, when finishing information entry in the child file and go back to the main file using F10 , EpiData doesn't take me automatically to a new parent file but to the previous file and a new parent file will only open when using the navigation bottom. Also when I fill in the second parent file and automatically move to the child file, I found the information entered for the previous child file. Hope you can help me solving this problem Thanks Mohamed -- *---------------------------------------------------------*

1 0

Which type of testing is good for securing stable software and enhance development ?
by epidata-list＠lists.umanitoba.ca 30 Jul '14

30 Jul '14

Dear all As you can see in the recent days communication on the list aspects of the "relate" system has been tested and in a collaborating process btw. V. Høgli and T.Christiansen, the issue of a wrongly place information window was clarified. This is exactly the type of correspondence which is helpful to the development. So therefore I encourage with time and interest in the future function and stable software developed to take part. It does not mean that all should spent days and weeks, but just a small exercise of say half an hour twice a week is not much for each of you. regards Jens Lauritsen EpiData Software Initiator and coordinator Denmark

1 0

Re: EpiData-list Digest, Vol 129, Issue 9
by epidata-list＠lists.umanitoba.ca 30 Jul '14

30 Jul '14

Torsten, Seems you located the problem:-) Funny though, the same phenomenon appears in Windows 7. The "show all button" is greyed out, but the other fix - Selecting Edit - Default windows position before I open any project, and then restart EDM fixes the problem. Glad if this testing can be useful. Regards, Vegard Høgli Torsten Bonde Christiansen wrote: > The reason why the program freeze at step 7) is because the window for > "Define Key" appears > outside your monitor. This happens due to a programming error from my side. > > You can see the window if you right-click the Manager icon in the dock > and select "Show All...". > ... > An easy fix for this is to use the "Default window position" which will > reset the position of ALL > windows within EpiData Manager. Then the next time you click "Define > Key" you should have > the window positioned properly. > > Kind regards, > Torsten Bonde Christiansen. > EpiData Association. > > > > On 2014-07-22 23:48, epidata-list(a)lists.umanitoba.ca wrote: > > "Then set as key" - embarrassed to admit - Still don't get it: > > Here's exactly what I do: > > 1. Define new project > > 2. Save as myfile (even tried without save first) > > 3. click on Dataform 1 > > 4. Define field name IDNO Integer length 4 > > 5. Apply, then close field properties pane > > 6. Select IDNO field with select tool (small boxes appear enclosing > > selected field) > > 7. Click on Dataform button (or menu item) - then choose Define key > > 8. Freeze - Nothing happens, not possible to define new dataform, not > able > > to save or edit field, have to kill process in program manager (windows), > > small green plus sign when hovering mouse over field (OSX). > > > > Where do I go wrong? anyway: apparent program freeze should be replaced > by > > error message if I do something in the wrong order, like for example: > when > > I tried to add a child dataform first, i get the error message: must > create > > at least one key first. > > > > Vegard > > > > > >> on Jul 22, Jamie wrote: > >> > > I have not had this problem (OSX-Mavericks). On Dataform1, I define an > >> integer field. Then set as key. add a related dataform and my key field > >> shows up on the new form. When you add a field to Dataform1, the Relate > tab > >> appears. You have to define a related dataform firstThen ; then the > Relate > >> tab shows up. > >> > >> Jamie > >> > >> > > _______________________________________________ > > 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 129, Issue 9 > ******************************************** >

1 0

Auto Response
by epidata-list＠lists.umanitoba.ca 29 Jul '14

29 Jul '14

1 0