- EpiData-list - University of Manitoba Mailing Lists

Minor fix to EpiData Manager
by EpiData development and support 01 Nov '16

01 Nov '16

Dear List. A new version of EpiData Manager (2.0.13.63) has been released for public use. The new version contains a fix only related to linux, where moving fields no longer worked correctly. Hence if you are using EpiData Manager on Windows or Mac, there is no need for updating if you have the previous version (2.0.12.62) installed. The updated version can as always be downloaded from our website: http://www.epidata.dk/download.php <http://epidata.dk/download.php> Kind regards Torsten Bonde Christiansen EpiData Association

1 0

Is there any file size limit in Epidata Analysis 2.2.2.183
by EpiData development and support 28 Oct '16

28 Oct '16

Dear Jens,                       Thanks for the quick response. It was heartening to know that Epidata development is progressing. Keep up this good work for the public health cause.Regarding the record limit issue;I tried correcting the wrong dates and that did not help. I tried reading the file without date variables, still the same problem persisted.  However, I extracted 3 variables of interest and wrote a separate file of 4.9 Mb. Original file size is 9.2 Mb. This extracted small file was easily read by Epidata Analysis.Just a small point about Epidata Analysis.If there is adequate RAM (4 Gb) and hard disk space (1 Tb) on the PC, does Epidata Analysis have any file size limitation? Can size of the rec file be the problem here?With regards,Dr. Shavinder

1 0

Status and strategic decisions for development of EpiData Software
by EpiData development and support 28 Oct '16

28 Oct '16

For all users of EpiData Software I am writing today to explain some changes you may notice in future list postings from me. Due to regulatory demands in Denmark there is a need to formalize some of the development strategies, including how the EpiData list is used to support development. Some of the emails from me will have a form where statements made are understood as accepted unless further debate gives reason for changes. Any comment or indication of opinion is welcomed at any time. If no major comments are given within 5 days the paragraphs will be formally understood as accepted by the user base. I want to reassure you that there will be NO information given to anyone regarding who is on the discussion list, anything you say here or otherwise express in relation to development or preference in strategy. In the formal constitution of the Association this is formulated as stated below my signature. There will be a continued division of decision making in EpiData development in which the roles are: a. this EpiData-List: discuss principles, decisions, practical implementation, bug removal, questions on specific aspects etc. b. the core group: Definite strategic decisions including those with financial implications are placed here. The core group is comprised of those giving major input to development. Names are indicated in the section "Particularly Active" in the "Friends of EpiData" section on the credit page of the main webpage. c. specific implementation: These are ultimately made by me and Torsten Christiansen, who is assuring sound software principles. At the final level I am legally responsible for all decisions taken, but it is important that the whole user base is informed of the principles. Best regards to all Jens Lauritsen, MD, Phd. Initiator and Coordinator EpiData Association, Denmark ------------------------------------------------------------------------------------------------------------------------ Formal extract: Decisions on dissemination and development strategies is taken in an open discussion on the EpiData list, which is open for all users. Specific power users from the user base will be added to a group of core decision makers (the board), who can sign account balance’s and grant signing rights to one or more persons in the core group in relation to payments and salaries. The board is guided in the larger decisions by the ”Friends of EpiData” – an international collection of experienced persons within EpiDemiology, Public Health and Community Medicine supporting the aim of the EpiData Association. Updated lists of names are shown at www.epidata.dk/credit.htm. To ensure broad support in development decisions and strategies all major directional plans will be made publicly available on the EpiData discussion group list, which is open to all users. Such plans will be clearly formulated as such with proper timelimits for commenting and possible changes.

1 0

Is there any record limit in Epidata Analysis 2.2.2 (ver 183)
by EpiData development and support 28 Oct '16

28 Oct '16

Dear  Jens and Epidata Team,                                                       There ia prolonged silence on the list. I hope everything is fine and development is progressing.I have a unique concern. There is a flat file of classical Epidata Entry 3.1. The number of records is 93425. I am using Epidata Analysis 2.2.2 (ver 183).  Epidata Analysis does not read this file.Only message I get is “Loading data D:\EpiData\PH\D.REC, please wait...The indicator below is green. When I convert this “rec file”  to  “dbase file” using classical Epidata Entry 3.1,  the converted dbase file is easily read by Epidata Analysis. (However it adds decimal and two zeroes to the numeric data.My question is; Is there any record limit in Epidata Analysis 2.2.2 (ver 183)?With regards,Dr Shavinder 

1 1

Serious bug identified (only in a special type of projects with related dataforms) - update to new EntryClient
by EpiData development and support 24 Aug '16

24 Aug '16

Yesterday - We have identified a bug which have created incorrect data in a certain situation . therefore - an updated EntryClient version has been uploaded (EntryClient 2.0.9.25) today. The change is due to a serious bug in RELATED dataforms. With single dataforms there is NO problem. For most projects with related dataforms the situation is: 1 New observations are added with unique key fields (say "project id"+"date of visit") 2 key values are never changed. Then you have NO problem and your data are correct. But if a project has: a. related set of dataforms (main + one or more child dataforms) b. the key contains MORE than ONE field. c. you have edited (changed) values in one of the key fields after entering records "above" a child form d. child records for more than one observation have the same value in a key field which was edited at a higher level AND you can say YES to all of a+b+c+d there is reason to check your data. If there is doubt for a given project you are welcome to contact us by mail at "info at epidata.dk" for further advice. The situation arose when we changed a flat file structure to a related structure. We split the flat file to four subfiles and imported the data into a related structure. As a first step gave one of three fields of the key the same value, whereas obviously the combination of three fields was unique. Following import this was correct, but after changing all 1000 records we realized the problem. We apologize very much for the inconvenience this might incur, but do hope that you will continue to report any strange behaviour. Only by meticulous observation can we find such unfortunate bugs. regards Jens Lauritsen EpiData Association, Denmark

1 0

AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 29/08/2016)
by EpiData development and support 17 Aug '16

17 Aug '16

I am out of the office until 29/08/2016. 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 152, Issue 2" sent on 17/08/2016 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

RELATE-aware analysis
by EpiData development and support 17 Aug '16

17 Aug '16

Hello. I'm using EpiData 3.1 on windows 7 to enter data into a set of RELATEd .rec files: HNPforms.rec (these are visits to households; data about the building) Adults.rec (data about the adults living in the household) Children.rec (data about the children living in the households) Each visit to a household has a unique ID number, and that number is propagated to a field in each adult's and child's record. There can be multiple visits to each household, so an indicator of initial visit versus revisit is included in HNPforms.rec and is propagated to the records for the adults and children living in that household. Using EpiData Analysis, is there a way to "connect" the child records and the adult records to their own household records, for purposes of analysis? Merging on the unique ID number, so to speak. Thanks. --Chris

1 1

Upcoming updated software versions next week
by EpiData development and support 12 Aug '16

12 Aug '16

About a month ago users experienced unexpected problems with the most recently uploaded public version. The problems were basically very grave and would not allow various aspects of core functionality, e.g. working with value labels. Due to the documented problems we have now implemented a new test principle for EpiData Manager and EntryClient, which will be followed before public release. The tests are structured in a spreadsheet format and performed by local staff here in Denmark (public health students). Based on the tests performed we have found un-disclosed errors, which is a "proof of concept" of the idea to pre-test thoroughly before public release. In contrast to relying on unstructured testing. Early next week we will therefore release new versions for production use and also the spreadsheet, which documents what we do test before release. For coming releases I therefore suggest that users assist in the testing. You may then receive pre-release copies of the software, such that the overall testing can be thorough. Recent experience has shown that some combinations of operating system versions and types (32/64bit) etc have given problems that we have no possibility of neither catching or solving without the help of some of you. In short therefore: be prepared to download new production versions of EntryClient and Manager next week. Regards Jens Lauritsen EpiData Association

1 0

Error in exporting data
by EpiData development and support 08 Jul '16

08 Jul '16

Hi all - I'm working with an .epx file that I have successful exported in the past, but now all of a sudden I'm getting an when I try to export the data. The error says "Access violation." Has anyone gotten this kind of error before? Do you know how I can get around this to export the data that has been entered? Thanks, Margaret

1 2

Re: [EpiData-list] EpiData-list Digest, Vol 151, Issue 2
by EpiData development and support 08 Jul '16

08 Jul '16

Dear developers, How can we neutralize a record in a data file (for example a file which has been collected by error twice) In Epinfo 1997 it was F6. What is the equivalent in Epidata? Thank you 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: Thu, 07 Jul 2016 21:00:17 +0400 Subject: EpiData-list Digest, Vol 151, 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. EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2) (EpiData development and support) 2. EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2) (EpiData development and support) 3. Re: EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2) (EpiData development and support) 4. Re: EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2) (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 7 Jul 2016 09:50:34 +0000 (UTC) From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: Epidata <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2) Message-ID: <1164686741.5493023.1467885034808.JavaMail.yahoo(a)mail.yahoo.com> Content-Type: text/plain; charset=UTF-8 Dear Epidata Developers,I'm using Epidata Manager (v2.0.10.59).But when i ant to define Valuelabel it show an error (Invalid pointer operation).Ho can i resolve it?Best regards. My System: Windows 10 - 32 bits?_______________________________________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 ------------------------------ Message: 2 Date: Thu, 7 Jul 2016 09:50:34 +0000 (UTC) From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: Epidata <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2) Message-ID: <1164686741.5493023.1467885034808.JavaMail.yahoo(a)mail.yahoo.com> Content-Type: text/plain; charset=UTF-8 Dear Epidata Developers,I'm using Epidata Manager (v2.0.10.59).But when i ant to define Valuelabel it show an error (Invalid pointer operation).Ho can i resolve it?Best regards. My System: Windows 10 - 32 bits?_______________________________________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 ------------------------------ Message: 3 Date: Thu, 7 Jul 2016 07:57:57 -0400 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData List <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2) Message-ID: <14F055F7-DD0F-4AFA-A35D-DB77C802D655(a)bell.net> Content-Type: text/plain; charset=utf-8 This is also a problem with the Mac version. Jamie > On Jul 7, 2016, at 05:50, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: > > Dear Epidata Developers,I'm using Epidata Manager (v2.0.10.59).But when i ant to define Valuelabel it show an error (Invalid pointer operation).Ho can i resolve it?Best regards. > > My System: Windows 10 - 32 bits _______________________________________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 > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list ------------------------------ Message: 4 Date: Thu, 07 Jul 2016 17:51: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 151, Issue 1 - Bug to define Valuelabel (2) Message-ID: <9401D4EF-DE19-4407-A6B7-2763ED415A93(a)epidata.dk> Content-Type: text/plain; charset=UTF-8 We will try to fix this tomorrow. Best wishes Jens Lauritsen On 7. juli 2016 13.57.57 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: >This is also a problem with the Mac version. >Jamie >> On Jul 7, 2016, at 05:50, EpiData development and support ><epidata-list(a)lists.umanitoba.ca> wrote: >> >> Dear Epidata Developers,I'm using Epidata Manager (v2.0.10.59).But >when i ant to define Valuelabel it show an error (Invalid pointer >operation).Ho can i resolve it?Best regards. >> >> My System: Windows 10 - 32 bits >_______________________________________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 >> _______________________________________________ >> EpiData-list mailing list >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list > >_______________________________________________ >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 151, Issue 2 ******************************************** -- 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 1