- EpiData-list - University of Manitoba Mailing Lists

Re: [EpiData-list] EpiData-list Digest, Vol 172, Issue 4 - McAfee wrong virus detection
by EpiData development and support 19 Jun '18

19 Jun '18

Dear all, This refers to McAfee Endpoint security ver 10.5.3.3178. This program is forced by my employer. I get a warning when downloading the exe file and when running manager/client. This applies both to the old Epidata version from 2007 and the new. There has been NO signs of malfunction or infection. I believe strongly that this issue is not related to an actual virus threat but rather that McAfee detects all non-standard programs. The logs from McAfee follows below (mostly for the Epidata team): Ryktet för programmet EPIDATAMANAGER.EXE är Okänt, vilket är under den konfigurerade inneslutningströskeln. Adaptivt skydd mot hot inneslöt inte programmet eftersom observationsläget är aktiverat. ------------------------- ANALYS/DETEKTOR Produktnamn McAfee Endpoint Security Produktversion 10.5.3.3113 McAfee GTI-fråga Ja Funktionsnamn On-Execute Scan HOT Vidtagen åtgärd Innesluts eventuellt Hotkategori Processklass eller -åtkomst Hot identifierat vid start Nej Hothändelse-ID 35111 Hanterat hot Ja Namn på hot ATP/Suspect!38626ef41d2c Allvarlighetsgrad för hot Varning Tidsstämpel för hotet 2018-6-17 20:31 Typ av hot Dynamic Application Containment KÄLLA Åtkomsttid för källan 2018-6-17 20:30 Skapelsetid för källan 2010-11-21 04:24 Källfilens storlek 2872320 Värddatornamn för källa SOSLS79102197 Ändringstid för källan 2010-11-21 04:24 Källfilens processnamn C:\WINDOWS\EXPLORER.EXE Källanvändarnamn GAIA\24jj MÅL Åtkomsttid för målet 2018-6-17 20:31 Skapelsetid för målet 2017-4-21 01:38 Målfilens storlek (byte) 7031808 Målhash 57522881d6cdf31353875012fb917976 Värddatornamn för mål SOSLS79102197 Ändringstid för målet 2018-5-30 13:46 Målnamn EPIDATAMANAGER.EXE Målsökväg C:\PROGRAM FILES\EPIDATA Målanvändarnamn GAIA\24jj ANNAT Vektortyp Lokalt system Avkänningsmeddelande Avkänning i Adaptivt skydd mot hot, observationsläge Tid före avkänning (dagar) 18 Even download of the old client is detected as a threat: GAIA\24jj använde C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE för att hämta http://epidata.dk/downloads/setup_epidata.exe, som är klassificerad som Röd. Hämtningen har Blockerad av McAfee Endpoint Security. ------------------------- ANALYS/DETEKTOR Produktnamn McAfee Endpoint Security Produktversion 10.5.3 McAfee GTI-fråga Ja Funktionsnamn Hämtnings-URL HOT Vidtagen åtgärd Blockerad Hotkategori Hämtning av skadlig fil Hothändelse-ID 18601 Hanterat hot Ja Namn på hot Web Control Violation Allvarlighetsgrad för hot Allvarliga Tidsstämpel för hotet 2018-6-17 20:05 Typ av hot Hämtning av skadlig fil KÄLLA Källfilens storlek 990228 Källans IPV4 46.30.213.252 Filhash för källans process 504c12f8bc573e324fdeb54919840243 Källfilens processnamn C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE Signerad källa Nej Käll-URL http://epidata.dk/downloads/setup_epidata.exe Klassificeringskod för käll-URL Röd Webbkategori för käll-URL Skadliga webbplatser Källanvändarnamn GAIA\24jj MÅL Målnamn setup_epidata[1].exe Målsökväg C:\Users\24jj\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\Q1PMWX53 Målanvändarnamn GAIA\24jj ANNAT Vektortyp Webbplats Even download of Entryclient is detected and blocked: GAIA\24jj använde C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE för att hämta http://epidata.dk/downloads/epidataentryclient.4.4.1.0.win.64.zip, som är klassificerad som Röd. Hämtningen har Blockerad av McAfee Endpoint Security. ------------------------- ANALYS/DETEKTOR Produktnamn McAfee Endpoint Security Produktversion 10.5.3 McAfee GTI-fråga Ja Funktionsnamn Hämtnings-URL HOT Vidtagen åtgärd Blockerad Hotkategori Hämtning av skadlig fil Hothändelse-ID 18601 Hanterat hot Ja Namn på hot Web Control Violation Allvarlighetsgrad för hot Allvarliga Tidsstämpel för hotet 2018-6-17 19:33 Typ av hot Hämtning av skadlig fil KÄLLA Källfilens storlek 3683108 Källans IPV4 46.30.213.252 Filhash för källans process 504c12f8bc573e324fdeb54919840243 Källfilens processnamn C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE Signerad källa Nej Käll-URL http://epidata.dk/downloads/epidataentryclient.4.4.1.0.win.64.zip Klassificeringskod för käll-URL Röd Webbkategori för käll-URL Skadliga webbplatser Källanvändarnamn GAIA\24jj MÅL Målanvändarnamn GAIA\24jj ANNAT Vektortyp Webbplats --- ------------------------- Jonas Malmstedt Munkedalsvägen 3 122 42 Enskede, Sweden 08-648 0838 (hem) +46 8 6480 838 (home) 070-758 6838 (mobil) +46 7 0758 6838 (cellular) 08-616 2893 (arbete) +46 8 6162 893 (work) 2018-06-19 19:00 skrev epidata-list-request(a)lists.umanitoba.ca: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. message to all EpiData users - we have received reports of an > important potential problem (EpiData development and support) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 18 Jun 2018 23:12:52 +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] message to all EpiData users - we have > received reports of an important potential problem > Message-ID: <bb216257-6184-0814-e210-1c4d83a93c0a(a)epidata.dk> > Content-Type: text/plain; charset=utf-8; format=flowed > > We have received two independent messages of a potential virus/viral > threat with the latest EntryClient in the Windows version. (From Sweden > and Switzerland) > > The programming and compilation of ALL EpiData software is done in Linux > and we have NOT changed any of the programming tools from the latest to > the previous version of EntryClient. > > Where we work these problems have not occurred, so it seems to be > dependent on which particular version of the anti-virus software is > blocking the function of EntryClient. > > We are reasonably convinced that the problem is some similarity of > internal code with a known virus or trojan. If our development system > had been infected, then this would also affect previous versions. > > To be sure of this we will obviously spent some time to look into the > problem in collaboration with the reporters. AND quite soon return with > a solution. (In the meantime I would personally mark in my virus > software the EntryClient as not-infected - if that is possible, but it > is obviously up to you. The reason being that we have not changed > anything here) > > Should you experience such problems please write an e-mail to info (at) > EpiData.dk - following solving the problem we will then contact you > directly. > > best wishes > > 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 172, Issue 4 > ********************************************

1 0

Major news : Rewritten EpiData Analysis v1.0, updated versions of EpiData Manager and EntryClient
by EpiData development and support 14 Jun '18

14 Jun '18

For all EpiData Users. Today we have taken a major step forward with the release of a rewritten EpiData Analysis in version 1.0 and version 4.4 of Manager and EntryClient. The ability to use relational structures, encryption, user logging and other complex aspects has been implemented. We do hope that users will find this an important step forward. It will not be long before further functionality is available in Analysis. In the test versions we have already a functional aggregate, and tables is next step. Get the new versions for Linux, Mac and Windows from: www.epidata.dk/download.php Read the introduction documents for each software from the help menu after you start the software. As always when versions of software change be particularly critical to ensure backup copies of all data in a secure place before updating. Analysis is ready as v1.0 in terms of: - read project files (epx/epz including encrypted files), but also Stata dta, CSV, Rec+Chk files) - data management - combine files (merge, append) - saving, exporting and archiving data files (epx, dta, csv, ddi-3.1) including metadata - frequencies, count, means - validation of files and other aspects For Windows there is a combined installer for all three types of software - regardless of whether you have a 32 or 64 bit computer. All three EpiData software tools use an updated data file structure. Once you have read and saved an epx file it will not be possible to open it in a previous version of the software. So make sure to update all copies of the software that you are using, e.g. if you have local data entry. All example files are now located in a specific user specified folder, which you may choose during installation. In that folder example pgm files for analysis and pdf introduction documents are contained. Observation: on some restricted systems (eg. in a hospital) the user might not be asked to decide the folder position during installation or other user specifications. We cannot apparently control the installation completely. As always discuss function on this list and contact us in case of serious or reproducible data errors occurring due to system functioning on info (at) epidata.dk We wish to express as well thanks for inspiration and help from in particular Jamie Hockin and Hans Rieder, but also received funding from The Union (DFID fund) and other funding bodies. Torsten B. Christensen and Jens Lauritsen EpiData Association Denmark

1 2

SELECT and LIST COMMAND of EPI ANALYSIS 1.2.0.0
by EpiData development and support 03 Jun '18

03 Jun '18

Dear Jens and Team,Thank you for the sustained effort for developing New Epidata Analysis. It can read large rec files easily and convert to epx file quite fast.I was testing the ver 1.2.0.0 of Analysis.The "select" command selects the appropriate records. Following ouput was obtained..select name="GURWINDER" do;Selecting, please wait...Selecting complete!(61 of 36243 selected)Browse  uno datev name age  ageu5 sex  area  revisit diagnosis1;When the browse or list command is given, it lists all the records of the database,not just the selected records. Please advise.Dr Shavinder Singh

1 1

new ANALYSIS (with tables and aggregate) available
by EpiData development and support 30 May '18

30 May '18

For all users Today we uploaded a revised (new) Analysis v1.2.0.0, which can create tables and do aggregation of data. Get the new versions from : http://www.epidata.dk/download.php On that page you may always see a complete list of changes with versions. The table module in (new) EpiData Analysis will now do proper row, column and total percentages, and the aggregate command may create tables of estimates (mean, Ci, percentiles) for all combinations defined by subgroups of other variables. You may also save the aggregate table as a separate dataset within the project. In the help file of (new) Analysis the header indicates that for doing: Graphs, SPC graphs, Kaplan-Meier lifetables and testing other than basic Chi2 you must still use EpiData Analysis Classic. We identified a few peculiar bugs related to combinations of missing data or specifications when reading rec files and saving Stata files (beyond version 13) . Since reading and writing of data files is a common core function shared between Manager, EntryClient and Analysis we have also uploaded rebuild versions of these. Please comment use and problems on this list. Jens Lauritsen and Torsten B. Christiansen EpiData Association Denmark

1 0

Re: [EpiData-list] A request for download page of previous versions
by EpiData development and support 22 May '18

22 May '18

A direct mail was sent regarding previous versions: Always use the latest public version. Test and experimental versions should never be used for "real" project data, but should be tested on copies of data. When bugs and errors are found we fix these and sometimes this may change the structure of the epx/epz project file. New public release versions can always read previous forms. If you find an error with a new version, please report the error, such that we can locate the problem and fix it. Jens Lauritsen Epidata Association Denmark >Dear Sir, > > >I have a request, can we have a page listing previous version to >download? >My friend's group meet an unexpected version incompatible, but unable >to >find the download link of previous versions, although I solved this by >editing the filename in the downloading link. > >Can we do some thing for that? Thank you very much. > >Yours sincerely, >Fan --

1 0

New Epidata Analysis 0.9.3.9 Editor background Colour
by EpiData development and support 30 Apr '18

30 Apr '18

Dear Jens,We work most of the time in Epidata Analysis main window 0.9.3.9or the Editor. You have added the code for getting the main windowbackground black.set "BROWSER BG COLOUR"       := "#FFFFFF";set "BROWSER FONT COLOUR"     := "#000000";Please do the same in the editor also. It is easy onthe eyes to work in the dark background.Dr. Shavinder Singh 

1 1

Epidata Manager and Entry Client Parent child levels limits
by EpiData development and support 30 Apr '18

30 Apr '18

Dear Jens,We have a relaTional database  with 4 Parent child forms levels in theclassical Epidata as shown below. Family -- Eligible Couple -- Under5 Child-- Growth MonitoringWhen we import the database in EntryClient, Entry Client does not relate  beyond 3 forms. Is there any technical limitto number of child forms which can be related to parent form?Dr. Shavinder Singh

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 170, Issue 2
by EpiData development and support 15 Apr '18

15 Apr '18

Dear Jens and ream Thank you for the effort. I've got a request.. Could podcasts be made, so we can learn easily? I know it's a lot of work but it's a plea from novices including me Warm 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: Saturday, April 14, 2018 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 170, 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. Almost final pre-public Manager - EntryClient (and Analysis) (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 14 Apr 2018 18:29:44 +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] Almost final pre-public Manager - EntryClient (and Analysis) Message-ID: <798374ea-56eb-e9b0-ea5e-36f51a19cf4e(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Since the announcement last week we have not received any comments on the list or direct by mail. Neither have we found any (new) bugs, such that in the coming week we will release the next versions of Manager and EntryClient for public use. A major news item is also that we now consider the re-written Analysis ready for public use in terms of: - reading project files - data management - combination of files (merge, append) - saving, exporting and archiving data files (epx, dta, csv, ddi-3.1) including metadata - frequencies, count, means - documenting content of logging during entry Although it is a major drawback that one cannot create graphs or cross tables yet - we do think that the functionality now developed is sufficiently mature for release. Function is verified with the validation pgm's, which tests about 500 different aspects Therefore You may now find the pre-release versions for all three parts on http://www.epidata.dk/testing.php And once we have written a proper introduction document for the new analysis a public release version will be made available. Best wishes Jens Lauritsen and Torsten Bonde Christiansen EpiData Association Denmark ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 170, Issue 2 ********************************************

1 0

Almost final pre-public Manager - EntryClient (and Analysis)
by EpiData development and support 14 Apr '18

14 Apr '18

Since the announcement last week we have not received any comments on the list or direct by mail. Neither have we found any (new) bugs, such that in the coming week we will release the next versions of Manager and EntryClient for public use. A major news item is also that we now consider the re-written Analysis ready for public use in terms of: - reading project files - data management - combination of files (merge, append) - saving, exporting and archiving data files (epx, dta, csv, ddi-3.1) including metadata - frequencies, count, means - documenting content of logging during entry Although it is a major drawback that one cannot create graphs or cross tables yet - we do think that the functionality now developed is sufficiently mature for release. Function is verified with the validation pgm's, which tests about 500 different aspects Therefore You may now find the pre-release versions for all three parts on http://www.epidata.dk/testing.php And once we have written a proper introduction document for the new analysis a public release version will be made available. Best wishes Jens Lauritsen and Torsten Bonde Christiansen EpiData Association Denmark

1 0

Status - EpiData Software
by EpiData development and support 06 Apr '18

06 Apr '18

A brief status is: Manager and EntryClient: We do not expect addition of more functionality than found in the pre-release versions available this week. It is therefore very important that you report and discuss on this list (or add to Flyspray): a. Bugs in current functionality b. Any feature of high importance lacking in Manager or EntryClient (We are aware that scripting is not implemented, e.g. "before entry ...... after entry" blocks. ) Analysis: The Classic EpiData Analysis v2.2 - build 187 is the latest for production use. This will not be developed further, but will gradually be replaced by the new Analysis - which is still at the "experimental level". Major remaining aspects are: graphs, tables, dialog menu's collapsing/aggregating data, html formulation. Installation: We have decided to change the installation principles to a bundled package principle. The user will then only need to download one file, at least for Windows. The size of that single file will be larger, but still quite small (20-30Mb), which we hope pose no problem. The advantage is that in controlled environments only one file needs to be provided, e.g. here in the health region a new principle will only allow installation from a common system. EpiData has been accepted as part of that due to the inclusion of logging capabilities and we only need to deliver one package file for the health region. Question: Are all Linux users capable of working in 64 bit mode ? (Or do you have Linux installed on 32 bit computers) Open-Source release We are also working on aspects of release as open-source. This includes for example documentation of aspects of design and principles for other users to install and extend aspects on their own computers. More news on this later. The first test went well in the understanding that a power user (Jamie Hockin) in Canada could install all software and development tools, compile and also add to the main source code. Best wishes to all from Torsten Bonde Christiansen and I. Jens Lauritsen Initiator and Coordinator EpiData Association Denmark

1 0

Pre-public test of EpiData Manager and EntryClient - please test
by EpiData development and support 06 Apr '18

06 Apr '18

This week we have provided new versions on http://www.epidata.dk/testing.php: EpiData Manager Version 4.3.2.120 (pre-release) EpiData EntryClient Version 4.3.0.7 (pre-release) EpiData Analysis Version 0.9.3.7 (experimental test ) Manager and EntryClient will be released for production/public use in about a week - unless we find more bugs. Analysis is still experimental. The new features since v4.2 were announced on March 15th (see below). Since then we have removed several bugs, including a major bug in reading of projects and added a tool "archive". Before public release an "unarchive" tool will be provided also. With this you may encrypt any file or folder for archiving or mailing. This version applies stronger (SHA512) encryption and other internal changes to the xml structure. Therefore we kindly ask everyone to make a copy of their projects and then OPEN THE COPY with the versions mentioned above. This applies also to other projects without encryption. Should you find problems let us know on this list or by mail to info (at) epidata.dk . Jens Lauritsen/Torsten Bonde Christiansen EpiData Association Denmark Manager: * Jumps to fields can now also be key fields * Moved key selection from own windows to dataset properties * Added tools: Export Securitylog * Fixed several bugs in exporting to Stata 13+ EntryClient: * Bugfixes related to jump * Bugfixes related to logging with Extended Access * Added posibility to mark a record as Verified - observations that are "Marked for Deletion" cannot be directly marked as verified, but MUST be unmarked from deletion first. (under Extended Access this requires READ rights on the dataset) * Added additional information to the email body if the project is setup to create an email on close. Common: * Added "Days between password change" to Extended Access projects (and enforcement thereof) * Extended logging capabilities when using Extended Access * Better handling of recent files across Manager/Entryclient/Analysis * Updated cryptography of both Single Password and Extended Access from SHA1 to SHA512 Analysis: Consequential changes of the above to ensure reading and writing files accordingly.

1 0

Key from Image
by EpiData development and support 29 Mar '18

29 Mar '18

Does anyone have any information on using EpiData to key from image? The idea being one side of the users screen shows data entry fields while the other side of the screen shows an image that holds the data to be keyed. Once a user completes the data entry for an image, the next image is presented for keying a new record. Thanks, Brian

1 0

Appending memo and text fields, and better display for high dpi screen
by EpiData development and support 27 Mar '18

27 Mar '18

Hi All, Could I ask a couple of questions, please? (1) I have two epx files with the same variables, except that file A has a memo field and the corresponding field in file B is a string (as I imported file B from a stata dataset). How can I append these two files to have a memo field in my final file? (2) Is there a setting for a better display of the user interface on a high dpi screen? The texts on the manager and entry client look blurred at the moment. I am using these: Epidata manager version: 4.2.0.0 Epidata entry client version: 4.2.0.0 Mac OS High Sierra version 10.13.3 Thank you! Best wishes, Zaw Singapore

1 1

New testversions for EpiData Manager, EntryClient and Analysis
by EpiData development and support 15 Mar '18

15 Mar '18

We have just uploaded new testversions on: http://www.epidata.dk/testing.php Analysis: 0.9.3.6- EpiData EntryClient: 4.3.0.6- EpiData Manager: 4.3.1.119 We are still approaching public releases, but still lack some aspects. Remember to ALWAYS work on copies of data. In particular with this release if you use encryption since we have updated the strength of encryption to a stricter (modernized) level - SHA512. The following changes has been made in particular in relation to securing that we meet new demands for encryption and logging in relation to the regulatory requirements. During the coming week our inhouse complete test will be applied. But please do report any aspects you find problematic or strange. In manager we have done a bit of re-arrangement of the menu's, such that defining a "key" is now part of the properties for the datasets (dataforms). On the route to open-source we have done a test of having all source code installed in Canada by Jamie Hockin, who provided an updated "means" calculation in analysis, such that this should now be more precise. This was a promising test. A list of all changes is shown below. Best wishes Jens Lauritsen & Torsten Bonde Christiansen EpiData Association, Denmark. Manager: * Jumps to fields can now also be key fields * Moved key selection from own windows to dataset properties * Added tools: Export Securitylog * Fixed several bug in exporting to Stata 13+ EntryClient: * Bugfixes related to jump * Bugfixes related to logging with Extended Access * Added posibility to mark a record as Verified - observations that are "Marked for Deletion" cannot be directly marked as verified, but MUST be unmarked from deletion first. (under Extended Access this requires READ rights on the dataset) * Added additional information to the email body if the project is setup to create an email on close. Common: * Added "Days between password change" to Extended Access projects (and enforcement thereof) * Extended logging capabilities when using Extended Access * Better handling of recent files across Manager/Entryclient/Analysis * Updated cryptography of both Single Password and Extended Access from SHA1 to SHA512 Analysis: Consequential changes of the above to ensure reading and writing files accordingly.

1 0

time variable without seconds
by EpiData development and support 14 Mar '18

14 Mar '18

Is there any way to create a time variable in a dataform that does not require the seconds to be entered (ie would accept 08:15 instead of 08:15:00) Thank you ... Ian Dohoo -- Ian R. Dohoo DVM, PhD, FCAHS Professor Emeritus - Epidemiology U. of Prince Edward Island Charlottetown, PEI C1A 4P3 CANADA dohoo(a)upei.ca

1 1

new experimental build of analysis 0.9.3.0 released today
by EpiData development and support 09 Feb '18

09 Feb '18

From today v0.9.3.0 is released at the bottom of : Http://www.epidata.dk/testing.php Notice that the commands.html and the "how to adapt your pgm" help files found in the help menu of the main window. Please test and report to this list or in case of severe problems send an email to info at epidata.dk. We do hope that there are no more bugs in the released test version. But we do also encourage you to report such errors here. More info below Best wishes Jens Lauritsen , Torsten Bonde Christiansen EpiData Association Denmark ------------------------------------------------------------------------------------------------------------------- Example: read a file change value in a variable and display a browser before and after: // ----example: read "myfile.epx"; new variable v12 s; v12:= "unknown"; browse age v12 !caption:="Data before change"; v12 := iif( age[_n] > 18, "adult", "young"); browse age v12 !caption:=("Data after change" + now()); // ... end Here it would be natural to ask, why do I need the [-n]. This is a consequence of the way the internal machinery (parser) works. We will think over and attempt to see whether it is possible to leave out this, but until further notice you need that part. We have made it easy to add the [_n] - if you press alt+n with focus in the command prompt or in the editor the sequence "[_n]" will be added. Please do remember to work on copies of data. Real data should only be used in production release versions for actual data-analysis or data management Changes from last experimental version are: Documentation * fixed errors and inconsistencies in commands.html * fixed calling error - which would not open the commands.html in IE browser Adapted syntax * valuelabels: edit vl name <type> ( value, text) ( value, text) etc. Added functionality * automatic variables and memo fields may be created * list project * funtion user(), returning defined users in a project with extended access * Altered shortcuts on MAC (Editor) Bug fixes: * merge had several issues - and should now be complete, including documentation - could overwrite mergevar * editing of !related parameters !childobs and !afterobs * errors in certain variable expansion aspects and special combinations, e.g. save a project without variables * report validate, report cby , check relate could fail. * check relate -> would indicate incorrectly that a 1-many relation was not correct. * createtime(...) will return sysmis with illegal time value

1 0

new test version of EpiData Analysis released today 0.9.2.0
by EpiData development and support 23 Jan '18

23 Jan '18

We are rapidly approaching the first pre-public test version of the new analysis, but before getting to that stage. From today v0.9.2.0 is released at the bottom of : Http://www.epidata.dk/testing.php Changes from last experimental version are: * a unified and simplified option naming convention expected to be the final choice (many options are one or two letter only, not a long word, which may be misspelled) * You may set "mark for deletion" and "verified" at observation (record level) (and remove again) * Reorder ændrer ny på visuel struktur * reorder command will also change the sequence in a saved file * unification of the shortcuts and function. e.g. exit editor and exit browser * New reports: count by (variables, eg id visitdate) , validate double entry files) * The browser now shows observations marked for deletion or verification * new functions to summarize numerical data: sum(..) and strings: concat(..) * frequency command can show confidence intervals * common naming of result variables after running variables (try: list r) * renamed set options and added some for default browser, colours etc. (to see these, issue: set - or open editor and add set from edit menu) * commands to alter the structure of projects. e.g. "un-relate" a related project, append or merge whole projects or single datasets within a given project. * fix many minor bugs and error situations, which would give a strange error. * all errors are now shown regardless of setting of: set "echo" := "on/off"". They are only hidden if you issue the set "show error" := "off"; Notice that the commands.html and the "how to adapt your pgm" references are found via the help menu in either the main analysis form or the editor. But also that several browsers may be open . Please test and report to this list or in case of severe problems send an email to info at epidata.dk In particular test data management features and the ability of the software to read all files created (rec, dta, epx, csv) . Save them again after some data-management, e.g. summation or reordering, and see in Manager or EntryClient that it actually worked. Please do remember to work on copies of data. Real data should only be used in production release versions for actual data-analysis or data management Work now continues with the table command and other issues, e.g. ability to shift from txt to html output or simple encryption and decryption of projects. Notice that without the efforts from assisting other members of the list we could not have made the software to the current level. In particular thanks to Hans Rieder and Jamie Hockin for a lot of structured testing and feed-back. best wishes Jens Lauritsen , Torsten Christiansen EpiData Association Denmark

1 0

User manual and podcast
by EpiData development and support 01 Jan '18

01 Jan '18

Dear Jens Can we have a user manual and podcast on the new analysis software? Thanks 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: Friday, December 22, 2017 11:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 166, 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. Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) (EpiData development and support) 2. Re: Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) (EpiData development and support) 3. New experimental Analysis for testing released - v0.9.0.15 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: 22 Dec 2017 07:57:56 -0000 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) Message-ID: <20171222075756.22767.qmail(a)f4mail-235-247.rediffmail.com> Content-Type: text/plain; charset="UTF-8" Dear Hans,Sub - Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)Using Analysis for relating rec files is a good option.A PGM can easily save the updated rec files to epx files and relate also.I could save two related rec files to epx files.When I issued the Merge command,Read "D:\EpidataAnalysis0.9.0.0\FG\AgeSex2.epx";Merge FFNO !fn :="D:\EpidataAnalysis0.9.0.0\FG\FAMILY2.epx" !Table;Following  error message was dislayed; ERROR: External lookup table dataset "ds1" has a non-unique key combinationPlease use the integrity tool to get a complete list of non-unique valuesWhat is this integrity tool and how to get a complete list of non-unique values using this tool?.......................................................The following command is also not working.edit var sex !valuelabel := label_sex              !label : = "Examinee's sex";What is the need to edit Label option before conversion to epx files?Dr. Shavinder  ------------------------------ Message: 2 Date: Fri, 22 Dec 2017 09:04:26 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) Message-ID: <0df0bf45-05a5-21d4-9550-246df47e53f8(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Today we will give out a new experimental test version, where the check command (data integrity test) is very efficient, e.g. to find duplicates in a file check key v1 v2 v3; will tell which observations are duplicate in the combination of v1 v2 v3 In the new version colour of fonts and background is also working. Jens Lauritsen EpiData Association On 12/22/2017 08:57 AM, EpiData development and support wrote: > Dear Hans,Sub - Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)Using Analysis for relating rec files is a good option.A PGM can easily save the updated rec files to epx files and relate also.I could save two related rec files to epx files.When I issued the Merge command,Read "D:\EpidataAnalysis0.9.0.0\FG\AgeSex2.epx";Merge FFNO !fn :="D:\EpidataAnalysis0.9.0.0\FG\FAMILY2.epx" !Table;Following  error message was dislayed; ERROR: External lookup table dataset "ds1" has a non-unique key combinationPlease use the integrity tool to get a complete list of non-unique valuesWhat is this integrity tool and how to get a complete list of non-unique values using this tool?.......................................................The following command is also not working.edit var sex !valuelabel := label_sex              !label : > = "Examinee's sex";What is the need to edit Label option before conversion to epx files?Dr. Shavinder  > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list ------------------------------ Message: 3 Date: Fri, 22 Dec 2017 17:07:18 +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] New experimental Analysis for testing released - v0.9.0.15 Message-ID: <a4e6fab4-11e3-e70d-2680-c166752f1945(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Dear all users We have released next experimental version for testing, which you may find from the page: Http://www.epidata.dk/testing.php Many issues have been fixed since the latest public test in early december. A complete list is found at the bottom. In particular we have fixed and quality assured the data integrity command: check data, check key, check relate But also many other issues, e.g. colour control. These lines will turn output and command line into yellow on black background. set "COMMANDLINE BG COLOUR"?? := "#000000"; set "COMMANDLINE FONT COLOUR" := "#FFF000"; set "OUTPUT BG COLOUR"??????? := "#000000"; set "OUTPUT FONT COLOUR"????? := "#FFF000"; Many other aspects have been fixed, e.g. search and replace in editor in windows. Next in line is the implementation of tables command and a few more issues in relation to data-management, which will then be announced as a pre-public version. Please do some testing to ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 166, Issue 6 ********************************************

1 1

Merge command and rec to epx conversion
by EpiData development and support 23 Dec '17

23 Dec '17

Dear Jens,I have tested the recent experimental versionEpidataAnalysis0.9.1.5. (Windows version)GOOD PREGRESS -Colour commands for output and command lineis welcome addition. Please add similar commands for Editor also.As mentioned earlier, EpidataAnalysis0.9.1.5. is really fast. It canread files with more than 1,00,000 records easily.ISSUES REQUIRING ATTENTION -MERGE Command was tetsed with following PGM.Patient and visit epx files were used  from course of https://tbrieder.org/epidata/epidata.html//TRY.PGMcd "D:\EpidataAnalysis0.9.1.5\EX";close;read "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epx";merge idpat !fn := "d_ex01_patient" !table;save "combined10.epx" !replace;close;read "combined10.epx";  When this PGM is run it gets stuck at Merge Command. Following outputis obtained..cd "D:\EpidataAnalysis0.9.1.5\EX";D:\EpidataAnalysis0.9.1.5\EX.close;Project Closed!.read "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epx";Loaded file: D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epxCycle: 10 Datasets: 1 Modified: 10-11-2016 21:34:21.merge idpat !fn := "d_ex01_patient" !table;ERROR: Unable to open the file: D:\EpidataAnalysis0.9.1.5\EX\d_ex01_patientFile is corrupt or does not exist.Unable to open file "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_patient"ERROR: Error loading file:Same problem I was facing with my relational database files.Hence this command needs revision..........................When rec file is read in this software, the variables and data entered do not tally.Conversion from rec file to epx file results in variable with actual data appearingunder other variables..........................Since there is no check file, Hans suggested following commandedit var sex !valuelabel := label_sex              !label := "Examinee's sex";This command (edit) is also not working.It is hard work to write such software. Surely these issues will be addressedin future releases. Keep it up.I wish you and epidata team all success and happy new year 2018.With regards,Dr. Shavinder 

1 0

New experimental Analysis for testing released - v0.9.0.15
by EpiData development and support 22 Dec '17

22 Dec '17

Dear all users We have released next experimental version for testing, which you may find from the page: Http://www.epidata.dk/testing.php Many issues have been fixed since the latest public test in early december. A complete list is found at the bottom. In particular we have fixed and quality assured the data integrity command: check data, check key, check relate But also many other issues, e.g. colour control. These lines will turn output and command line into yellow on black background. set "COMMANDLINE BG COLOUR" := "#000000"; set "COMMANDLINE FONT COLOUR" := "#FFF000"; set "OUTPUT BG COLOUR" := "#000000"; set "OUTPUT FONT COLOUR" := "#FFF000"; Many other aspects have been fixed, e.g. search and replace in editor in windows. Next in line is the implementation of tables command and a few more issues in relation to data-management, which will then be announced as a pre-public version. Please do some testing in particular of saving files after changes to variables and structures, followed by entry in EntryClient and report to the list of your experiences. Best wishes for the coming end of year festivitas and a merry christmas for those who celebrate the christmas traditions. Jens Lauritsen and Torsten Christiansen EpiData Association Denmark. Complete list: * Removed the result variable $SYSTEMDIR and replaced with the function cwd() * Editor "open file" now opens in current directory * Options may now be a global that holds other options: - new global OPT s := "!cum !d0" - freq sex !OPT // this will effectively act as freq sex !cum !d0 * Fixed a number of bugs in "check relate" and "check key" * Added additional result variables to "check relate" and "check key" * Fixed bugs in relation to names already used in sections/headings * Editor: Inserting history/set-options * "list var" and variable information (F3) now shows variables that are part of key with a "*" * Added sub-command "edit data" with option !del -> marks all record in current select for deletion * Added command "report users" * Added option !del to "browse" and "list data" to show ONLY records marked for deletion * Browser: Added shortcut "CTRL + G" which shows a dialog for jump to observation * Added SET OPTIONS for COLOUR control og OUTPUT, COMMANDLINE and Browser * Added option !output [:= "html | text"] to "save" command. This saves the output buffer to text or html. * And many minor bug fixes.

1 0

Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)
by EpiData development and support 22 Dec '17

22 Dec '17

Dear Hans,Sub - Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)Using Analysis for relating rec files is a good option.A PGM can easily save the updated rec files to epx files and relate also.I could save two related rec files to epx files.When I issued the Merge command,Read "D:\EpidataAnalysis0.9.0.0\FG\AgeSex2.epx";Merge FFNO !fn :="D:\EpidataAnalysis0.9.0.0\FG\FAMILY2.epx" !Table;Following  error message was dislayed; ERROR: External lookup table dataset "ds1" has a non-unique key combinationPlease use the integrity tool to get a complete list of non-unique valuesWhat is this integrity tool and how to get a complete list of non-unique values using this tool?.......................................................The following command is also not working.edit var sex !valuelabel := label_sex              !label := "Examinee's sex";What is the need to edit Label option before conversion to epx files?Dr. Shavinder 

1 1

Fonts and backgrounds Epidata Analysis ver 0.9.0.0
by EpiData development and support 13 Dec '17

13 Dec '17

Dear Jens,Separate selection of Fonts in the Output, Command line and Editor isvery good feature. One can read rec file but cannot relate with other rec file.Merge command is not working with parent child rec files.Please retain the feature of choosing the background as black and white(as it was in Classical Epidata Analysis). Otherwise this feaure should change with  Windows colour scheme selection. Only white background results in lot of glare.Startup.pgm could not be located. It is faster than classical epidata analysis.It can read large data sets (more than 35,000) easily. Keep it up.With regards,Dr. Shavinder

1 2

New test release of EpiData Analysis v0.9.0.0 (experimental)
by EpiData development and support 11 Dec '17

11 Dec '17

Dear all users A test version of the new EpiData Analysis was released today. Get it from: Http://www.epidata.dk/testing.php All data management and check of data should now be ready and work similarly in EntryClient, Manager and New Analysis, e.g. help menu. Data management includes: Reading of files (rec, epx, stata, csv, clipboard), creation of new variables, labels, browsing, check data command, saving data in files (epx, stata, csv, copy to clipboard from browser), but also running pgm files with comprehensive loops etc. But since it is in development: MAKE SURE YOU WORK ON COPIES OF REAL DATA Extract the appropriate files (depending on Windows, Linux, Mac version) and make sure you maintain the folder structure. Then start epidataanalysis. The main changes since October 13th (v0.8.4.0) are: * Now all three Operating Systems are supported (Linux, Mac, Windows). * Hit F1 to get automatic search based on content (command line or editor) * observation identifier may be used, e.g. : new var id i := _n; * observations can be checked with the [_n] reference, e.g.: v1:= v1[_n-2] ; (add [_n] with alt+n in the editor or command line) * Browser shows a snapshot of data and you may open several browsers (after browse - use right click to copy or adapt data). * Complex formulations of command syntax allowed (References to variables, loops, expansions of variable names) * Font control (all windows) and custom startup.pgm for preferences * More set options to change aspects of the interface. Faster output. * Recent files are shared with Manager and EntryClient. * More commands, functions and options are added (Hit F1 to see these) example: erase "tempfile.epx" If you have not used the new analysis before, please start the software and look in the help menu (Tutorials local), where you find more explanatory files, including how to adapt old pgm files for the new syntax. To see more aspects, please see the mail from announcement of version (0.8.4.0) (http://lists.umanitoba.ca/pipermail/epidata-list/2017q4/002815.html) If problems arise please report to this list. But make sure you WORK on COPIES OF DATA until we have the first public release. It is of particular interest for us if you can challenge creation and modification of projects (epx files) with subsequent addition of data in EntryClient and view or change of structure in Manager. Our internal standard is about 500 automatic tests, but we cannot test how saved epx files work in EntryClient and Manager automatically. Best wishes Jens Lauritsen and Torsten Christiansen EpiData Association, Denmark The main changes to the command syntax are: 1. use ; at the end of each command in a pgm file 2. use := to give variables a new content . e.g. v1 := 10; 3. options are indicated with ! instead of /, e.g. freq v1 !cum ; means age !t; 4. filenames must contain extension, and enclosed in "projectmain.epx". 5. Similar aspects are grouped, e.g. list data; list variables; list datasets 6. Defining and editing variables have a common structure: new var; edit var; drop var; 7. Many additions allow comprehensive programming

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 166, Issue 1
by EpiData development and support 03 Dec '17

03 Dec '17

Dear Jens and team This is fantastic news Awaiting the stable version soon! sincerely 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: Saturday, December 2, 2017 11:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 166, 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. New test release of EpiData Analysis v0.9.0.0 (experimental) (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 2 Dec 2017 01:01:18 +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] New test release of EpiData Analysis v0.9.0.0 (experimental) Message-ID: <6dd70abc-84a1-bf22-aee6-104f0694f7c1(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Dear all users A test version of the new EpiData Analysis was released today. Get it from:? Http://www.epidata.dk/testing.php All data management and check of data should now be ready and work similarly in EntryClient, Manager and New Analysis, e.g. help menu. Data management includes: Reading of files (rec, epx, stata, csv, clipboard), creation of new variables, labels, browsing, check data command, saving data in files (epx, stata, csv, copy to clipboard from browser), but also running pgm files with comprehensive loops etc. But since it is in development: MAKE SURE YOU WORK ON COPIES OF REAL DATA Extract the appropriate files (depending on Windows, Linux, Mac version) and make sure you maintain the folder structure. Then start epidataanalysis. The main changes since October 13th (v0.8.4.0) are: * Now all three Operating Systems are supported (Linux, Mac, Windows). * Hit F1 to get automatic search based on content (command line or editor) * observation identifier may be used, e.g. : new var id i := _n; * observations can be checked with the [_n] reference, e.g.: v1:= v1[_n-2] ; ?? (add [_n] with alt+n in the editor or command line) * Browser shows a snapshot of data and you may open several browsers ??? (after browse - use right click to copy or adapt data). * Complex formulations of command syntax allowed (References to variables, loops, expansions of variable names) * Font control (all windows) and custom startup.pgm for preferences * More set options to change aspects of the interface. Faster output. * Recent files are shared with Manager and EntryClient. * More commands, functions and options are added (Hit F1 to see these) ?? example: erase "tempfile.epx" If you have not used the new analysis before, please start the software and look in the help menu (Tutorials local), where you find more explanatory files, including how to adapt old pgm files for the new syntax. To see more aspects, please see the mail from announcement of version (0.8.4.0) (http://lists.umanitoba.ca/pipermail/epidata-list/2017q4/002815.html) If problems arise please report to this list. But make sure you WORK on COPIES OF DATA until we have the first public release. It is of particular interest for us if you can challenge creation and modification of projects (epx files) with subsequent addition of data in EntryClient and view or change of structure in Manager. Our internal standard is about 500 automatic tests, but we cannot test how saved epx files work in EntryClient and Manager automatically. Best wishes Jens Lauritsen and Torsten Christiansen EpiData Association, Denmark The main changes to the command syntax are: ? 1. use ; at the end of each command in a pgm file ? 2. use := to give variables a new content????? . e.g. v1 := 10; ? 3. options are indicated with ! instead of /,? e.g. freq v1 !cum ; means age !t; ? 4. filenames must contain extension, and enclosed in "projectmain.epx". ? 5. Similar aspects are grouped, e.g. list data; list variables; list datasets ? 6. Defining and editing variables have a common structure: new var; edit var; drop var; ? 7. Many additions allow comprehensive programming ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 166, Issue 1 ********************************************

1 0

Mulitple Diagnosis
by EpiData development and support 26 Nov '17

26 Nov '17

Dear Jens and Jammy ,First example quantifies the total number of diagnosis which can besorted in descending order to see the magnitude.Second example actually adds all diagnosis in one defined variable (AllDiag).This can again be sorted in descending order (to see the magnitude) anddiagnosis grouping by sorting alphabetical. This data was actually entered inExcell sheet as numerically coded diagnosis. AllDiagnosis___________ resulted in sum of all the numberic data.Hence these codes were converted to actual diagnosis. This resulted inexcellent pattern of diagnostic combinations of all patients. Epidata Analysisis a marvellous software.Thank you for your prompt response and sustained effort to develop Epidata.Much appriciated.Dr Shavinder Singh

1 0

Multiple Diagnosis
by EpiData development and support 25 Nov '17

25 Nov '17

Dear Epidata Team,                   We have a patient's database. A patient can have multiplediagnosis. Hence these are the numerically coded variables defined for dataentry of ;Diag, Diag2, Diag3, Diag4, Diag5, Diag6. Of course one can FREQ theIndividual "diag" and see the individual diagnosis pattern. However if onewants to see the pattern of common diagnostic combinations observed inall the patients, is there any way out?  Dr. Shavinder Singh

1 3

Sorry for these extra characters in the post
by EpiData development and support 25 Nov '17

25 Nov '17

Dear Epidata Team,I aplogize for these strange extra characters appearing in the text file.This has been happening since last four posts to the list. I have sent thetext file this time. I cannot pin point the reason why this is happening.Please ignore these characters.Dr. Shavinder

1 0

EpiData EntryClient and Manager error: Control `DataviewerFrame’ has no parent window
by EpiData development and support 06 Nov '17

06 Nov '17

Hello: We (my admin and I) created a data base in EpiData Manager. Data has been entered. When I press Ctrl D, I can see the data entered nicely in column. I wanted to show my admin this functionality so that she can see how the data looks when entered. When we press Ctrl D (browse data) or use the menu on her computer we get this error (see below). Do you know how we could resolve this error: Control `DataviewerFrame’ has no parent window? IT has already uninstalled and installed both the Manager and the EntryClient. Any advice would be very much appreciated. [cid:image001.jpg@01D356DD.ADAB9260] Thanks, Renate

1 0

Re: [EpiData-list] Error in exporting .epx file to .dta
by EpiData development and support 24 Oct '17

24 Oct '17

The Stata versions we tried were 8, 9, 11 and 12 and SPSS version was 22. With regards to the query on whether to export the original missing values or as .a/.b, I feel it would be preferable to keep the original value. Thanks and Regards Dr. Divya Nair Assistant Professor | Dept. of Community Medicine Sri Venkateshwaraa Medical College Hospital & Research Centre Ariyur | Pondicherry 605 102. Mob: 8056748342 | Alternate email: divs87_nair(a)yahoo.co.in

1 0

Error in exporting .epx file to .dta
by EpiData development and support 23 Oct '17

23 Oct '17

Dear team members, I had entered data in an .epx file created using EpiData Manager v4.2.0.0 with jumps set for certain variables using the last defined and second last defined missing values. A unique identifier was also created for each record by combining two integer fields. On importing the data to stata for analysis, the following issues have been noted: 1. The unique id field remains empty in the stata file 2. Wherever, missing values were indicated in the .epx file, they appear as large random numbers in the stata file and not as the actual value that was entered. For example, age entered as 999 (missing) in the .epx file shows up as "32740" in the stata file. This happens only when the "missing" box is ticked while assigning value labels for categorical or continuous variables. This issue has been noted in the previous versions of epidata manager as well as while exporting to newer versions of stata and SPSS. I have attached the sample .epx file and the .dta file for your reference. Thanks and Regards Dr. Divya Nair

1 3

Re: [EpiData-list] EpiData-list Digest, Vol 164, Issue 2
by EpiData development and support 23 Oct '17

23 Oct '17

Thank you for the new version (0.804.0) od Epidata Analysis Two questions : - Is the command "Tables var1 var2" available ? - In the command "freq", spontaneously I would say that the percentages are in column (!c), and not in row (!r) Thanks for your activity. Bernard BRANGER 11 bis, rue Gabriel LUNEAU 44000 NANTES - FRANCE Mobile 06 32 70 33 80 Courriel : branger-bono(a)wanadoo.fr

1 0

EpiData & Windows 10
by EpiData development and support 17 Oct '17

17 Oct '17

Hi We use the Epidata v1.0 software on Windows 7 workstations. I see from your website that it is developed for windows 95/98/NT/2000/XP, but we use it on Windows 7 ok. I appreciate that it is freeware and is developed by a voluntary group. However can you please tell me if there are any plans to re-develop to ensure compatibility with Windows 10? Or, does it run ok on Windows 10? Kind regards Stephen Smith | Business Analyst | Waikato District Health Board Ryburn Lane | Hamilton 3240 p +64 7 839 8899 ext. 97045 | e Stephen.smith(a)waikatodhb.health.nz | w www.waikatodhb.health.nz/IS "Healthy People, Excellent Care " Please consider the environment before printing this e-mail This electronic message, together with any attachments is confidential and may be privileged. If you are not the intended recipient: 1.do not copy, disclose or use the contents in any way. 2.please let me know by return email immediately and then destroy the message. Waikato DHB is not responsible for any changes made to this message and/or any attachments after sending by Waikato DHB. Before opening or using attachments, check them for viruses and effects. Waikato DHB takes no responsibility for affected attachments. Click on link www.waikatodhb.health.nz/disclaimer to view the company policy website. If you are not redirected to the company policy website then copy and paste the URL into a new browser window. ______________________________________________________________________________ This email has been filtered by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

New (experimental) version of rewritten Analysis 0.8.4.0
by EpiData development and support 13 Oct '17

13 Oct '17

Today a public test version of rewritten Analysis was made available for Windows and Linux. (v0.8.4.0) Test versions are available as packed archives from: http://epidata.dk/testing.php (at the bottom) Extract the files provided and maintain the folder structure. We are rapidly approaching a version, which can be used in the management for real projects. But for a while still please only use for testing. Start epidataanalysis (exe) and see help menu "Commands Overview". The file shown is commands.html . Also study the "How_to_adapt_your_pgm_file_to_new_EpiData_Analysis_format.pdf" found in the docs folder. Our aim is to change as little as possible in the final syntax, but some changes are necessary due to demands when we write the software for more operating systems (currently Linux and Windows - Mac version will come). The main changes to the command syntax are: 1. use ; at the end of a command in a pgm file 2. use := to give variables a new content . e.g. v1 := 10; 3. options are indicated with ! instead of /, e.g. freq v1 !cum ; means age !t; 4. filenames must contain extension, and enclosed in "projectmain.epx". 5. Similar aspects are grouped, e.g. list data; list variables; list datasets 6. Defining and editing variables, labels etc have a common structure: new var; edit var; drop var; 7. Many additions allow comprehensive programming A major strength of the new analysis is that you may read and save datafiles in csv, dta (stata), epz and epx format directly. You may also read the classic rec files. All executed commands are saved in a pgm file defined by the user. Reading, editing and saving now supports encrypted data, user logged data and files containing related datasets . We know of some issues and bugs in the software released today, but decided to release at this point, since we need more input to remove all bugs at the detailed level. We have almost 300 validation tests and only one special error. Comparison with standard estimates show precision with difference from correct result at -2.06197786709744*E-12 . This is a very promising precision. Examples of known issues are that cycle is not corrected after modifying data, or errors in special types of "for ....to..." loops. If problems arise please report to this list. But make sure you WORK on COPIES OF DATA. Commands and statements added recently : * "append" and "merge" handles related datasets * "check" command with 4 sub commands: data, key, relate or study (document data content, e.g. "check key id visitdate" will tell if there is a unique key for id+visitdate) * "reorder" variables command * "reset" command * read and save files with extended login and user protection defined. * drop data , including remove records marked for deletion * control of fonts, including ability to set your own default by saving to "startup.pgm" * "set" options added recently: - EDITOR and OUTPUT FONT + SIZE: to adjust fonts and size - OUTPUT VIEWER: controls what type of output is generated. text or html is supported - INCLUDE DELETED: controls if records marked for deletion is part of the dataset - SET FORMAT VARIABLE LABEL and - SET FORMAT VALUELABEL: controls default option for value / variable text Many other issues managed: * enhanced and informative feedback in more situations (more indirect help) * run commands in "startup.pgm" on initiation of the program. (Placed in same folder) * Dragging files (data or .pgm) onto the program either opens the file or executes the .pgm * Variables can now be expanded using modifiers like "*", "?" or "-" , e.g. list variables v* * Extended editor with more functionality * F1....F12 function keys work as in Classic EpiData Analysis (except F2) Please test and challenge function. Jens Lauritsen and Torsten Christiansen EpiData Association Denmark

1 0

Difficulty in Importing Relational database of Classical epidata into Epidata Manager
by EpiData development and support 09 Oct '17

09 Oct '17

Dear Jens,                    I am trying to import Classical Epidata Relational File System of 8 tables into Epidata EntryClient.The structure is as follows;                 Family                                                Eligible Couple                                                                                                  Pregnant                                                                        Contra           Under five                             Agesex                                                                                                                Growth Monitoring                                                                            Tuberculosis                                     We  can import Family,  Eligible couple AgeSex and tuberculosis structure data files easily and link also .However the files linked to eligible couple ; Pregnant , Contra , Under five and Growth monitoring , only the structure of the file is imported, NOT DATA.  When we click the data check button in the Import Dialogue Box, it shows the following error .“Importing data is only impossible when the imported dataset has same variable (names +type) as  the defined variables!”That is already the case. The primary key between family and other  directly linked files is “FFNO” , a text variable . The primary key between Ecouple  and linked files is “FAMIDNUM”  a numeric  variable.  The primary key between Underfive and Growth monitoring files  is “Card2” , a numeric variable .  The number of records are in thousands.I am using the latest version of Epidata Manager and EntryClient.Why we are not able to import the data of Pregnant , contra , Under five and Growth monitoring files. Please guideDr. Shavinder Singh   

1 1

Epidata 3.1 and Windows 10
by EpiData development and support 23 Aug '17

23 Aug '17

Hello, My organization has been testing Epidata 3.1 for compatibility with Windows 10 before we upgrade our network OS, I encountered the following issue: if a change is made to an existing QES file, the process of revising the existing REC file stalls and can take 7-10 minutes to complete. This is very unusual since the process is virtually instantaneous in Windows 7 or previous OS versions. The IT staff haven't found a solution. I'm hoping someone here might have a suggestion (configuration, network setting?). Thanks Rod Rod Asplin, C.P.H.I. (C) Environmental Health Officer Communicable Disease Control Fraser Health Authority

1 0

Do not apply checks
by EpiData development and support 21 Aug '17

21 Aug '17

While I try to apply checks I got the following lines always appeared error Can any one tell me what is wrong with the following variable names Unknown label name or field name in line 24: COMMENT LEGAL USE label_cohort Unknown label name or field name in line 34: COMMENT LEGAL USE label_n102marita Unknown label name or field name in line 39: COMMENT LEGAL USE label_n103educat Thank You Very Much Fekadu

1 1

Problem with AUTOSEARCH
by EpiData development and support 20 Aug '17

20 Aug '17

Dear friends, When I enter a duplicate data in a field configured with autosearch, the dialog box displays three option buttons: YES, NO and CANCEL. When pressing the NO button, nothing happens but the other options work normally. The other dialog boxes similar to this one are working normally. Does anyone know if this is a bug in EpiData (Classic) Entry v3.1? How can I resolve this? I need to set up a variable like AUTOSEARCH varID varPERSON. Where varID is the identification variable and varPERSON is the number given to each person in the household. Grateful for attention! Márcia

1 0

Reg Epidata Manager 4.0.2.101
by EpiData development and support 03 Aug '17

03 Aug '17

This is a very basic question. 1) I am not able to automatically calculate the number of hours from the calculate option. I have input date and time and entered it into the calculate option but it is not giving me the correct answer. e.g. I have input date of injury and time of injury; and date of presentation and time of presentation. I need to calculate the number of hours of delay in presentation. I am not able to do that. 2) Is it possible to change the time option and exclude the seconds? Thank you, With regards, Madhurita

1 3

error message
by EpiData development and support 21 Jul '17

21 Jul '17

Dear all When comparing two datasets with Epidata Manager (double entry) I receive the error: "index out of bounds 108". Does somebody know what this means? Thank you very much, Nicole Dr. med. Nicole Bender Senior Research Fellow Evolutionary Morphology and Adaptation Group Institute of Evolutionary Medicine (IEM) University of Zurich Winterthurerstrasse 190 CH-8057 Zurich, Switzerland Office Y42 G86b Phone +41 44 635 05 31, Fax: +41 44 635 57 02 nicole.bender(a)iem.uzh.ch http://www.iem.uzh.ch/en/people/admin/Nicole-Bender.html

1 4

Read and Merge “rec” file commands and few suggestions in New Epidata Analysis (0.7.3.0)
by EpiData development and support 09 Jul '17

09 Jul '17

Dear Jens,                                     It is heartening to see the Epidata Analysis development progressing. Our favourite “qes/chk/rec” file  systm  seems fading  on the horizon. Our old applications are still functional in Classic Epidata Entry. It is comparatively easy to upgrade to the new”epx” file if one is using the FLAT file. However, the relational “rec” files cannot be upgraded to the new  ”epx” file. There was a line written in the mail that  one can read “rec” file but not write it in the new Epidata Analysis. Hence I request you to kindly preserve the read and merge (rec files) commands in the new Epidata Analysis.The Command and Function Reference Guide 2.1 is fairly exhaustive. Command “Merge” is perhaps not introduced in the prototype version, hence not mentioned in the Command and Function Reference Guide.It is possible to generate by the available Graphics in the Epidata Analysis ver 2.2.3 (build 187) by command syntax  generated by using  “Diaglogue boxes”.  Available options in the graphical output are excellent. However some tweaking is still required to get the final graph. PGMs is a wonderful feature with infinite possibilities. Gratitude to Epidata team for the sustained effort .With regards,Dr.  Shavinder Singh 

1 0

Test version of new EpiData Analysis released (v0.7.0.3) - please assist in testing.
by EpiData development and support 08 Jul '17

08 Jul '17

Exciting News Today we have released a test version of the rewritten analysis, which for the first time approaches functionality resembling the final first version to be released later. You may download the test version from http://www.epidata.dk/testing.php Please notice that it is still premature to use the new analysis for production every day use, but we urge users to challenge the new analysis. You could for instance replicate data-management procedures you do with ordinary Classic Analysis v2.2. rel 3 (Build 187) The intention is to release the new analysis for production when the following has been developed: A: all functionality for data management (new projects, new variables, labels and editing of these). B: append and merge. C: basic reporting - e.g. for logfile overview Already now you may test many of these aspects. After download and unzipping (files are provided in zipped archives) you will see the commands and syntax documentation. We attempt to maintain the same syntax that you know, but to allow for the modernization some changes are needed: e.g. read and write epx, csv and dta files ; work on all operating systems (Linux, Mac, Windows) ; accept UTF-8; extend with special functions; sort data; manage encrypted data. You can read rec files, but not write them. Use epx for saving data. We also aim for standardization across commands. E.g. number of decimals in output is always !Dx, where x is the number of decimals 0,1,2 etc. For data analysis these commands are implemented: count , means, freq, Some changes: use := instead of = . Put texts in " " . End all command lines with ;. Selection works on a single block. Options are mentioned with ! instead of /. Some enhancements: A copy of all executed commands is saved (commandlog.pgm). Recent pgm in editor filelist. Multiple pgm sorting ascending and descending and more. See datasets (F2) in a project. Open encrypted files. A frequency table of v17: freq v17 !vl !cum ; // would show labels and values plus cumulative percentage. To do the same table among those younger than 40 with no decimals. select (age < 40) do freq v17 !vl !d0; To remove all observations with age above 68. Use the command drop: select (age> 68) do drop data; A new construct is a loop, e.g. : new global integer i ; for i:=1 to 5 do ? "This is a number counting: " + i ; Which can be used to show means or frequencies for subgroups of another variable: new global integer i ; for i:= 1 to 5 do select (area = i) do means age !by:=sex !t; Please challenge function within WHAT is already implemented. Also notice that output format is still rather crude. Rest assured more will come during autumn. But do remember that you should NOT use production data - work on copies of real data. Please also discuss function and problems on this list. Best wishes for fruitful testing Torsten Christiansen Jens Lauritsen EpiData Association, Denmark

1 1

Updated versions of EntryClient and Manager (4.2.0.0)
by EpiData development and support 21 Jun '17

21 Jun '17

For all list users. We have released next versions of EpiData Manager and Entryclient: Major news: 1 Saving data is now per observation. The principle of writing data was changed completely. From this version onwards all changes to single observations (records) are saved after the user responds "Yes" to the question of saving of that observation on a given dataform. All saving to disk is performed in the background, such that entry can continue. But all data are still in memory, such that speed of browsing etc should be the same. A visual feedback button indicates current state: green = current state is saved correctly yellow = save in progress red = error in save. The user most intervene if this persists. The "red state" could occur if you loose connection to a network drive, e.g. due to time-out failure. In such cases the user can save a copy of the project with EntryClient ("save as" in the file menu). It is the responsibility of the user to secure proper handling afterwards, e.g. decide with a manager what should happen. To find out which project file is optimal for continued entry the "count observations/records by id" function in Manager - documentation, is a good way to get an overview. 2 Status bar have new common items. Make sure to get a new "default status bar" to see this. (default preferences) 3 Valuelabels are now possible for Date and Time variables. 4 A number of bugs have been fixed in relational data and other special situations. 5 Implementation of logging: extended access The content of the logfile system is now a standard dataform within the project. If a user have administrative rights the log file content can be seen in Manager, for all other users it is hidden. This allows analysis and export of the data in a logfile. All writing to the logfile is performed in the background, such that it does not interfere with ongoing entry. The logging function allows assessment of which users had access to data, at what time and see before/after values if an observation was edited after first save. For details, see the specific texts: Manager:http://epidata.dk/epidatamanager.changelog.txt EntryClient:http://epidata.dk/epidataentryclient.changelog.txt Common functions:http://epidata.dk/epidatacore.changelog.txt Unfortunately we have discovered a few bugs after the first (4.2.0.0) elease, so please make sure to download and install again if you have downloaded the new version before the 21st of June. Please verify that your changes to data are actually saved, We have obviously tested the new "save each observation" principle "in-house", but there could be examples in which this is not working correctly. Do not hesitate to report problems to this list or < info at epidata.dk > Development continues with re-writing analysis for complete data-management features. The new analysis can read the logfiles created with extended access. Expected to be available for all users in open testing within a few weeks. After that we will continue with implementation in EntryClient of extended scripting during entry. Please consider adding funding to cover development - e.g. at the level of what alternative software acquisitions would have cost. The funding principle continues as "attain funding-release without fee-release as open-source when we have completed development". Always acknowledge those giving funding (see http://www.epidata.dk/credit.htm and http://www.epidata.dk/funding.htm) We need help in creation of sample cases that could be used as part of the quality assurance programme. Currently the testing is thorough for Manager and Analysis, but still not sufficient for EntryClient. best wishes Jens Lauritsen & Torsten Christiansen EpiData Association Denmark

1 0

Make a Cascades and calculate some fields
by EpiData development and support 21 Jun '17

21 Jun '17

Dear All,I have 2 problems.1. Please somebody can help me to do a cascade in Epidata?My database have 4 levels (Region, District, Health Aeria and Village). I want to make a cascade model. So, when i select one region, i want to only have the district linked to the r?gion. The same for district and health aeria and village.2. How to have results with addition of some fields (Integer). In this Epidata version, we can calculate hours and concatenate. 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

Re: [EpiData-list] EpiData-list Digest, Vol 159, Issue 2 Message 1
by EpiData development and support 20 Jun '17

20 Jun '17

You can develop relational data form to have this kind of structure. Use "RELATE" command in EpiData entry. Here's a simple example on my blog. https://myominnoo.blogspot.com/2016/03/creating-relational-form-in-epidata-… You can also use EpiData Manager and EntryClient to have this kind. All the best -- *Myo Minn Oo* Operational Research Fellow *International Union Against Tuberculosis and Lung Disease (The Union)* 36, 27th Street, Between 72nd and 73rd Streets, Mandalay, Myanmar Tel: +95 11-201182, 2 71082 Fax: (+95) 2 71082 www.theunion.org worldlunghealth.org <http://www.worldlunghealth.org/> *Tel:* (+95) 99705 45333, 94513 35581 *Skype:* myoetc *Email:* myominnoo(a)theunionmyanmar.org, dr.myominnoo(a)gmail.com

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 159, Issue 2
by EpiData development and support 19 Jun '17

19 Jun '17

Dear All,Please somebody can help me to do a cascade in Epidata?My database have 4 levels (Region, District, Health Aeria and Village).I want to make a cascade model. When i select one region, i want to only have the district linked to the région. The same for district and health aeria and village.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 Le Vendredi 14 avril 2017 17h00, "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> a écrit : 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: Reg Epidata Manager 4.0.2.101 (EpiData development and support) 2. Re: Reg Epidata Manager 4.0.2.101 (EpiData development and support) 3. AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 18/04/2017) (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 13 Apr 2017 13:24:16 -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] Reg Epidata Manager 4.0.2.101 Message-ID: <6576F7E6-6E13-4FA0-AD4D-EF24A964BA2A(a)bell.net> Content-Type: text/plain; charset=utf-8 1) Can you wait and do this in Analysis or another software? Unless your data entry logic depends on this time difference, it should not be necessary to do the calculation in EntryClient. 2) It would be nice, but not in this version. You certainly don?t have to enter the seconds - they will always show up as 00. Jamie > On Apr 13, 2017, Madhurita wrote: > > 1) I am not able to automatically calculate the number of hours from the calculate option. I have input date and time and entered it into the calculate option but it is not giving me the correct answer. e.g. I have input date of injury and time of injury; and date of presentation and time of presentation. I need to calculate the number of hours of delay in presentation. I am not able to do that. > > > 2) Is it possible to change the time option and exclude the seconds? > ------------------------------ Message: 2 Date: Thu, 13 Apr 2017 19:26:49 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Reg Epidata Manager 4.0.2.101 Message-ID: <8C5A0DE3-7509-4108-9EE8-CFDC4C789894(a)epidata.dk> Content-Type: text/plain; charset=utf-8 Have you made the target variable a float? That is say length 6 and two or three decimals? Best wishes Jens Lauritsen On 13 April 2017 19:24:16 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: >1) Can you wait and do this in Analysis or another software? Unless >your data entry logic depends on this time difference, it should not be >necessary to do the calculation in EntryClient. > >2) It would be nice, but not in this version. You certainly don?t have >to enter the seconds - they will always show up as 00. > >Jamie > >> On Apr 13, 2017, Madhurita wrote: >> >> 1) I am not able to automatically calculate the number of hours from >the calculate option. I have input date and time and entered it into >the calculate option but it is not giving me the correct answer. e.g. I >have input date of injury and time of injury; and date of presentation >and time of presentation. I need to calculate the number of hours of >delay in presentation. I am not able to do that. >> >> >> 2) Is it possible to change the time option and exclude the seconds? >> > >_______________________________________________ >EpiData-list mailing list >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ------------------------------ Message: 3 Date: Thu, 13 Apr 2017 22:02:39 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 18/04/2017) Message-ID: <OF5889B08C.4B83D5E6-ON80258101.00739980-80258101.00739980(a)mailb.hse.ie> Content-Type: text/plain; charset="ISO-8859-1" I am out of the office until 18/04/2017. 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 159, Issue 1" sent on 13/04/2017 18:00:15. 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" *************************************************************************** ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 159, Issue 2 ********************************************

1 0

Re: [EpiData-list] Problem defining the key variable for a relational
by EpiData development and support 25 May '17

25 May '17

Thank you Jamie, that would appear to be the problem. I'll try to redo the structure from scratch. -Ruwan -----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, May 24, 2017 1:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 160, 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 https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.umanitoba.ca_mail… 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. Problem defining the key variable for a relational database (EpiData development and support) 2. Re: Problem defining the key variable for a relational database (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 May 2017 21:10:26 +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] Problem defining the key variable for a relational database Message-ID: <MWHPR1201MB01589C72CC80AFF050E2F45696F90(a)MWHPR1201MB0158.namprd12.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi there, I have a relational database with three key variables (district_id; health facility_id; patient_id). It is relational as there are three forms: Patient Demographics, Patient Progress, Laboratory. For the Progress form, for some reason, when try to enter the variables in the key (Right click form>Define key), I cannot add anything more than the patient_ID. The other options are greyed out. For all other forms, entering multiple variables in the key is no problem. I'd appreciate some advice on what (obvious) option I am missing. Thank you! Ruwan ------------------------------ Message: 2 Date: Wed, 24 May 2017 11:35:46 -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] Problem defining the key variable for a relational database Message-ID: <89B424E3-7B17-4F75-8E4B-8106D0CD3AD1(a)bell.net> Content-Type: text/plain; charset=utf-8 I assume that your structure is like this: Demographics form \?> Progress form (1-many) \?> Laboratory form (1-many) Once you define a key(s) in demographics, it automatically defined for the child forms because it(they) define the relation. When you define a new key in progress, they key or keys you defined for Progress show, but are greyed out because you cannot remove them. So in progress, you can add a new key, which will be automatically defined for laboratory. You MUST know what your relationships and keys are before you start. Once you have created a subform, you cannot change the keys in the parent form. I find it best to set up the data forms with just the keys and maybe a couple of other fields first, to make sure the structure works for you. You can defined the type of relationship (1-1 or 1-many) and try out the flow of data entry from one form to another and back again. Then add in the rest of the fields. Jamie > On May 23, 2017, at 17:10, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: > > I have a relational database with three key variables (district_id; health facility_id; patient_id). It is relational as there are three forms: Patient Demographics, Patient Progress, Laboratory. > > For the Progress form, for some reason, when try to enter the variables in the key (Right click form>Define key), I cannot add anything more than the patient_ID. The other options are greyed out. For all other forms, entering multiple variables in the key is no problem. > > I'd appreciate some advice on what (obvious) option I am missing. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.umanitoba.ca_mail… End of EpiData-list Digest, Vol 160, Issue 1 ********************************************

1 0

Problem defining the key variable for a relational database
by EpiData development and support 24 May '17

24 May '17

Hi there, I have a relational database with three key variables (district_id; health facility_id; patient_id). It is relational as there are three forms: Patient Demographics, Patient Progress, Laboratory. For the Progress form, for some reason, when try to enter the variables in the key (Right click form>Define key), I cannot add anything more than the patient_ID. The other options are greyed out. For all other forms, entering multiple variables in the key is no problem. I'd appreciate some advice on what (obvious) option I am missing. Thank you! Ruwan

1 1

indexing records in epidatastat and retrieving values
by EpiData development and support 14 Apr '17

14 Apr '17

Dear Sir, I am trying to retrieve value of variables based on other variables. Example: a dataset with 3 observations: # region_code ill 1 21 4 2 30 10 3 40 6 i have tried the following: sort region_code gen i s =_n @ill[1] but i am getting the result of the last observation and not the first. I will be thankful if you advise on how to retrieve the value of a variable based on record indexing. Sincerely Nada -- Nada Ghosn, MD Head, Epidemiology Surveillance Program (Esumoh) Ministry of Public Health Beirut, Museum square Lebanon Tel +961.1.614194 Fax +961.1.610920 Email esumohleb(a)gmail.com, esumoh(a)moph.gov.lb Website www.moph.gov.lb

1 1

AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 18/04/2017)
by EpiData development and support 13 Apr '17

13 Apr '17

I am out of the office until 18/04/2017. 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 159, Issue 1" sent on 13/04/2017 18:00:15. 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, Append Records
by EpiData development and support 14 Mar '17

14 Mar '17

Hello, This is in reference to using EpiData Manager and trying to append records using the Tools > Append option, for a Project that has 2 dataforms. When the Append Project window appears, the fields available are only from the 1st dataform. After successfully appending, the dataset for the 1st form is complete, and the 2nd form appears to have the correct number of records, but when viewing the data, or exporting, all rows for the appended records are null. This is the same case with a Project with a parent and child forms. The data is complete for the Parent form, but the Child form has rows with null values for all appended records. EpiData Manager: (2017/03/14 - 10:05:27) Program Version: 4.0.2.101 r1409 Core version: 4.0.0.0 r1373 FPC Version: 3.0.0 Platform: x86_64-Win64 XML Version: 4 Dataforms Count: 2 Please let me know if you need additional information. Kind regards, Claudia Hansen | Data Systems Programmer, Data Management, GHR-GHPN 359 Blackwell Street, Suite 200 | Durham, NC 27701 O: 919.544.7040 ext. 11718 | chansen(a)fhi360.org | www.fhi360.org<http://www.fhi360.org/> | FHI 360 Facebook<https://www.facebook.com/fhi360> [Description: Description: Description: fhi 360 email.jpg]

1 0

EpiData Manager (v4.0.2.101) and EntryClient (v4.0.2.49) released
by EpiData development and support 03 Mar '17

03 Mar '17

Dear List. Today we have released a minor update for EpiData Manager (v4.0.2.101) and EntryClient (v4.0.2.49) with the following changes: *Manager* * Fixed a bug where starting with -i commandline, but with no arguments, which caused A/V * On Variable properties - moved EntryMode to basic pane. * Grouped Value Labels and Ranges together * Removed variable property "Show Value Label Notes" - was not used * Fixed bug were it was posible to try import data to valuelabels with unsuppported variables selected. * Rename "max missing value" and "2nd max..." to "last missing value" and "2nd last..." as it is actualle the order of missing values that matters *EntryClient* * Changed the behaviour and text for the dialog when an existing index/key is found * Fixed a bug where the program would crash on close if preferences were opened with a project opened * All hints (including error hints) now follow the timing set in preferences. * Fixed a bug where the default font on windows might not have been present on all operating systems The new version is as always available from the download page: http://www.epidata.dk/download.php Kind regards Torsten Bonde Christiansen EpiData

1 0

Suggestions for Epidata Manager
by EpiData development and support 17 Feb '17

17 Feb '17

Dear Sir, I have been using Epidata Manager, EntryClient for past one year. I like it's simple and user friendly features. With my recent use I have few suggestions: 1. In variable properties>Calculate, please provide option to calculate using any mathematical operation sign (+, -,÷,×) between atleast four variables. 2. For jump rules, if it should be allowed to set the values of the questions jumped as per the value of jump. For eg. If there are variables A, B, C and D. If Code 1 is selected in A then jump to D and put the code 2 in B and C. If Code 2 in a selected in A then jump to C and put the code 1 in B. 3. In date variables an option of automatic date and time capture which is once captured and doesn't not change if the same form opened next time. This will help if we have multiple sections for data entry in single form which will be entered at different time intervals. 4. In browse data, it will be helpful if we can select and see any particular data entry in columns. Warm regards, Peeyush peeyush1902(a)gmail.com

1 1

Updated EpiData Manager v4.0.1.97
by EpiData development and support 16 Feb '17

16 Feb '17

Dear List Today we have released a minor update to EpiData Manager (v4.0.1.97) with the following changes: * If a variable is marked as "no-enter" it is displayed with the default "in-active" colour of the operating system. * Fixed a bug where importing CSV files under special circumstances did not work. * Added a better visual feedback for errors when importing/loading all file types. The new version is as always available from the download page: http://www.epidata.dk/download.php Kind regards Torsten Bonde Christiansen EpiData

1 0

Updates to .qes and .rec files without changing .chk
by EpiData development and support 07 Feb '17

07 Feb '17

Good morning, I have a quick, and hopefully simply question. I am trying to revise some of the wording in a single question on the .qes file of a database that has been in use for several years. The labels would NOT change and I don't need any of the coding in the .chk file to change. I understand that I will have to revise the .rec file in order to make this change visible to the users when they go to fill out the data form. However, anytime I try to make the simple wording change in the .qes file, then select "revise data file" in the tools menu, I receive a message saying that ALL the coding in my .chk file will be lost and I would have to re-enter all of it. I don't want to make any changes to the .chk file, only the wording in a single question on my data form! Is there a way to revise the wording of one of my questions without the need to re-do all the coding in my .chk file? Any help would be appreciated, Thanks, Lesley McLeod, MSc, CIC Infection Control Coordinator (North) Cell: 306-290-8746 Street Address: 3472 Elder Grove Regina, SK S4V 2V3 lesley.mcleod(a)pophealthnorthsask.ca<mailto:lesley.mcleod@pophealthnorthsask.ca> www.pophealthnorthsask.ca<http://www.pophealthnorthsask.ca/> Mamawetan Churchill River Health Region, Keewatin Yatthé Health Region & Athabasca Health Authority Confidentiality Notice: This email, including attachments, may contain confidential information. If you have received this email in error, please notify me immediately by return email, and delete this message. Thank you.

1 2

EpiDat EntryClient update v4.0.1.44
by EpiData development and support 07 Feb '17

07 Feb '17

Dear List Due to a reported bug in EpiData EntryClient 4.0.0.43 we have uploaded a new version today. This version fixes a bug where automatic variables (Date, Time and Autoincrement) were not correctly updated when creating a new observation. The new update is available from our download page here: http://www.epidata.dk/download.php Kind regards Torsten Bonde Christiansen EpiData

1 0

epidata v4.0
by EpiData development and support 01 Feb '17

01 Feb '17

Hello, Thanks very much for this great job! I downloaded the last test version and I noticed several problems - manager: the section name is never saved (when changed, the name is reset to section1 2,... on reload of the project). It is the same thing in version 2.x - entry: I experienced a non-reproducible crash during data entry after playing with the "Browse all data" window - entry : I noticed the problem already encountered about expansion of the first column of the "browse all data" - manager: there is an overlap of radio buttons in the "Entry Mode" panel of the "Extended" tab of the "field properties" window. - manager: overlap of radio buttons ine the "Update Mode" panel of the "Basic" panle of the "field properties" window for auto date and auto time fields - manager: the "field properties" window has been enlarged and I cannot reduce it. A request for the data entry manager about jumps: would it be possible to reset the value to of fields to a numeric or text value. I'd like to be able to do so in the following case for example: "Does the patient have a surgical history? YES/NO" If "yes" there is a serie of yes/no questions about specific surgeries. If the response of the main question is NO I would like to be able to reset the list of following questions to NO. It was possible to do it with epidata 3. For your information, I'm currently using the 64bit version under windows 7 pro. Best regards --------------- Jean-marie Chrétien. CHU Angers - DRCI Message court envoyé depuis un mobile.

1 2

Updated EpiData Analysis
by EpiData development and support 30 Jan '17

30 Jan '17

Dear all. Today we have release a new version of EpiData Analysis (v 2.2.2.186). This update for supporting the new epx format that was part of EpiData Manager and EntryClient 4.0 As with the previous release password protected and the "extended access" feature is not supported. The new version is available from the download page: http://epidata.dk/download.php Kind regards, Torsten Bonde Christiansen EpiData

1 0

Updated EpiData Manager and EntryClient v4
by EpiData development and support 30 Jan '17

30 Jan '17

Dear all. A few visual bug were indentified in the last week that have been corrected in todays update: * A panel with a beta warning was incorrectly shown in both programs after closing an open project. * Both programs incorrectly had "[TRUNK]" in the title bar. The new versions are available from the download page: http://epidata.dk/download.php Kind regards, Torsten Bonde Christiansen EpiData

1 0

Export data from Epidata Manager to SPSS
by EpiData development and support 26 Jan '17

26 Jan '17

Hello, I have 3 datasets in Epidata Manager that once exported to SPSS mix records. I am using Epidata Manager 2.0.0.25 and SPSS version 20. Kindly assist soonest. *Regards,* *Shakur Ndolo* *0728037673/ 0728321251* *P. O. Box 29944-00100 GPO, Nairobi*

1 1

How to read epx files created with most recent (v4) project files in Analysis ?
by EpiData development and support 26 Jan '17

26 Jan '17

Every time we add new functionality to Manager and EntryClient the underlying structure of the epx file has to change. An example of this is the latest addition of entry control at user level and logging of what the user does if you have added extended access control to the project. A consequence of this is that the standard analysis software (v2.2.2.b185) must also be updated, we have not YET done so. Therefore if you read a epx project file created with the most recent public version (v4) of Manager and EntryClient it will seem as if you have no data in the file, which is obviously not true. We will update Analysis (v2.2.2.b185) to accomodate reading of the new files. If all goes well this will be ready next week. Until this is done you may follow these steps to read your recently created or updated epx file: a. work in manager and entryclient as you have done already (make sure it is the public release from <Http://www.epidata.dk/download.php>) b. if you wish to look at the data, you may do so from EntryClient or Manager "browse data" (Ctrl+D) c. If you use Stata or other statistics software for analysis, then export to that dataformat, else: d. to do e.g. a frequency table or means of some entered data do this: d1: Get a copy of the prototype new analysis from: <http://www.epidata.dk/testing.php> d2: make a copy of the epx file (say mycopy.epx) - standard file copying on your system. d3: read the copy (say mycopy.epx) into the prototype of analysis (v0.06) d4: The syntax of the new analysis is somewhat different from old analysis. (see in the help menu), e.g. close; read "mycopy.epx" ; // notice that comments are now started with double // // for a frequency table with percentage and one decimal of variable v2, you would type : freq v2 !R !D1 // for means of age you would type: means alder !t !by:=meldetype ; The ; at the end will be added automatically if you write the command in the command prompt, but if you write the commands in the editor, you will have to add them on each line. The reason for copying the file (mycopy.epx) is that you must NEVER use production data in the test versions of the software. Test software is always found on <http://www.epidata.dk/testing.php> When we have fixed reading the new epx files for b185, you may again read the file into standard analysis. best wishes Jens Lauritsen EpiData Association

1 0

Version 4 released: EpiData Manager and EntryClient (individual user access)
by EpiData development and support 17 Jan '17

17 Jan '17

Dear all users. Version 4 of Manager and EntryClient have passed our in-house tests, which are found in "Validation of function in EpiData Manager and EpiData EntryClient" on the documentation page: http://www.epidata.dk/documentation.php. <http://www.epidata.dk/documentation.php> And we have fixed reported bugs. Therefore we have released public version to V4 on the download page. The main new aspects are: Memo text variables (long texts are shown in rectangles on screen) User adaptation of status bar during entry, including referring to other dataforms Defining individual user access at various roles and details. "fields" are now called "variables", "records" called "observations" if you have not worked with defining user access you may read the document here: <http://epidata.dk/php/downloadc.php?file=ExtendedAccess.pdf> This is a major step forward in the overall development plan for EpiData Software. The next steps of development will contain the following elements: 1. No difference btw. upper/lower case naming of variables etc. 2. Adaptation of the logfile format contained when you have logging in a project, such that analysis is easier. 3. Further implementation of aspects of Analysis. Feedback on the use of logging and user access control is highly welcomed with general comments and obviously also if you have specific problems or run into bugs. See the suggested strategy below. The reason for using V4 as the upgraded version from v2 is to avoid confusion with EpiData Classic, which was not developed since v3.1 released in 2008. Please note that from next versions all of EpiData Software will NOT be case sensitive in relation to naming of variables, headers etc. So please start adaptation of your projects to conform to this. E.g. you cannot use "v1" and "V1" or "Age" and "AGE" in the same project best wishes Jens Lauritsen EpiData Association, Denmark ------------------------------------------------------------------------------------------------------------------------ Our suggestion is to use this strategy if you wish to introduce user access control: 1. Create your project as always. 2. Make sure it works to all detail WITHOUT user access control. (test with a number of observations covering the whole range of the composition of the study base) 3. Make a copy of the database (just like if you defined double entry). Add extended user access control to the copy and experiment with the definitions until you are re-assured that this will work. That is the number of user roles (managers, who can change passwords, who can enter which data) etc. Enter e.g. 10 % of the data you already entered in number 2 and verify that it went ok.

1 0

EpiData EntryClient and Manager - next public release expected January 15th
by EpiData development and support 05 Jan '17

05 Jan '17

Manager and EntryClient were uploaded as release candidates on December 16th. Although downloads are about 250-300 we have not received any notice of problems or bugs. In our in-house quality assurance test we only found a Mac implementation issue (known problem - Drag and drop variables and titles is not consistent). The in-house quality assurance tests are found in "Validation of function in EpiData Manager and EpiData EntryClient" on the documentation page: <http://www.epidata.dk/documentation.php> The main new aspects are: Memo text variables (long texts are shown in rectangles on screen) User adaptation of status bar during entry Defining individual user access at various roles and details. if you have not worked with defining user access you may read the document here: <http://epidata.dk/php/downloadc.php?file=ExtendedAccess.pdf> The plan is to release the current pre-release as public version approximately 15th of January - provided no major issue shows up. Before public release we will implement: 1 A new report showing an overview of users, groups, and logfile content for projects with extended access option. In this option project access is defined at user level for each dataform. 2 Adaptation of help texts, screen menu text etc to conform to the new definitions (variables, dataset, etc) Best wishes Jens Lauritsen Initiator and Coordinator EpiData AssociationDenmark

1 0

Analysis
by EpiData development and support 04 Jan '17

04 Jan '17

Hello, First good year with a new version of EpiData Analysis. Thank you for your work. I tested some commands from the first test version: - I guess ": =" instead of "=" is because of the Mac or Linux? In any case, it is complicated to teach (less intuitive). Except for the equivalences (like Stata with the "=" and the "==" ... - Same for "!" instead "/" ? - Please use both upper and lower case for commands and variable names - After the "freq" command, the percentages are written in the vertical form and should be followed by "! c" instead of "! r" - Some personal demands for pedagogical purposes: = The "means"! t "command should show the result of the" t "test in case of two averages, and the result of ANOVA in case of more than two averages. I know that que le "F" est the square of the "t" for comparison of two averages. = Provide a complement to the "regress" command to get the regression line (as in the old Epi-Info "(eg"! Line ") = For the comparison of percentages, in case of insufficient calculated numbers (Ncell <5), do not calculate the chi-square and the "p" of the chi-square, and present the Fisher test for two percentages (the software "R" also presents the Fisher test for more than two percentages). Good luck. Thank you to excuse my bad english.... Bernard BRANGER 11 bis, rue Gabriel LUNEAU 44000 NANTES FRANCE Mobile 33 (0)6 32 70 33 80 Courriel : branger-bono(a)wanadoo.fr

1 3

v4 testing
by EpiData development and support 02 Jan '17

02 Jan '17

I played a bit with v4 apps today (on Elementary linux distro) and most things worked as expected. I used: EpiData Manager: (2017/01/01 - 16:08:45) Program Version: 4.0.0.94 [RC1] r1364 Core version: 4.0.0.0 r1337 FPC Version: 3.0.0 Platform: x86_64-Linux EpiData Analysis: (2017/01/01 - 16:07:11) Program Version: 0.6.0.0 [PROTOTYPE] r? Core version: 2.1.0.0 r1335 FPC Version: 3.0.0 Platform: x86_64-Linux The only problem encountered so far: Manager & EntryClient: the browse columns get larger when repeatedly clicking on the button to show values/labels. This is not the case with Analysis. Analysis: thanks for the short intro file that shows what is available in this version. I was annoyed that I got errors when there was no data because of select, but played with the syntax and did this as a workaround. I'm showing this just because the syntax works quite well. new global i i; for i := 1 to 3 do begin select gender = i count; if $count>0 then freq age; end; Having FOR and BEGIN blocks means we can use some sophisticated command syntax. Jamie

1 0

Epidata Development and Happy New Year
by EpiData development and support 31 Dec '16

31 Dec '16

Dear Jens and Epidata Team,                                                     I was a past user of EPI6 and shifted to Epidata Entry in 2000. Classical Epidata evolved with time and became very solid software capable of performing all the functionalities of EPI6 and much more. With additional functionalities and cross platform compatibilities, Epidata Manager and Epidata EntryClient are evolving at a rapid pace. I am yet to test the new version of Epidata Analysis. It requires tremendous perseverance to initiate, develop and maintain the software with limited resources. You have accomplished this mountainous task all these 16 years. Graphic documentation requires input in the manual. I had posted brief preliminary draft of options (off the list) to generate a particular graph long back.  I will continue to use and contribute to the user manual whatever possible. I congratulate you and entire Epidata team for this marvelous endeavor and wish happy New Year 2017.With regards,Dr Shavinder Singh 

1 0

Status and a new EpiData test: First prototype rewritten Analysis -
by EpiData development and support 27 Dec '16

27 Dec '16

Overview and status at new year 2016/2017 EpiData Software consists of three parts which are in development and maintained: 1. EpiData Manager (Linux, Windows, Mac) - create new projects for data entry - import data (csv, rec, stata) for documentation and entry - manage entered/imported data (pack, adapt structure) - define control of data (range, legal, jumps, conditional rules...) - document data project data (Dublin Core standard) - document quality and consistency - export data for external analysis (csv, stata, spss) - export data for long term archiving (ddi standard) 2. EpiData EntryClient (Linux, Windows, Mac) - Efficient data entry (shortcuts, date completions ....) - Effective control of legal values 3. EpiData Analysis a. Classic version v2.x (Windows) - Tables and graphs from dialogs - Estimation of confidence intervals and life tables - Efficient condensed tables for outbreak analysis - Extended SPC (Statistical Process Control graphs) - Extensive data management (functions and variables) - User written commands - Documentation focused (save commands in pgm files) - file format : rec + chk file b. New rewritten version in development (Linux, Windows, Mac) Will gradually replace 3a above and will have the same function. First prototype v0.6.0.0 is ready for testing now. See below. Read files: epx, stata, rec, csv or from clipboard Save with value labels: epx, stata. Data only: csv 4. Additionally we have EpiData Classic (v3.1) developed from 1999-2005 and a few utility tools. These are no longer maintained We are quite far with the rewriting Manager and EntryClient to a common base and we have just released the first prototype of Analysis. Gradually the rewritten software will have full function to the level that we can accomplish within the funding available based on many personal efforts from the core group and inspiration from users. All software is released in two different places: a. For production use get it from: www.epidata.dk/download.php b. During development get test versions from: www.epidata.dk/testing.php (and do not use these for "real" projects) Currently you can get this for testing: Release Candidate (almost ready for release): Manager and EntryClient Experimental prototype: Analysis From next test versions we expect that variable naming will again be "non-case sensitive" in all EpiData software. Currently it is case sensitive (except for classic analysis and classic epidata v3.1). The new analysis has partially a new syntax, but if you open it and press F1 there is a short explanation on differences and changes to the syntax. From the help menu you may also open the commands.html overview in your standard browser. The main difference in syntax is: use ":=" instead of "=" , select only works on one command at a time, new begin .... end block, commands in a pgm must end with ";", you can have more than one command on a line, separated by ";" . We wish all users a happy new year and hope You will enjoy the use of EpiData Software in 2017. We do also hope that some of you will spend some time testing and commenting. I do hope that all of You recognize that without the skilled implementation and software design by Torsten Christiansen, the support from funding bodies and discussions with the core group of "Friends of EpiData" I could not have continued to secure release of the EpiData Software suite in the framework and scope which binds such an effort. Jens Lauritsen Initiator and coordinator EpiData Association, Denmark

1 0

Pre-release testing of Manager and EntryClient (v4)
by EpiData development and support 16 Dec '16

16 Dec '16

A new step in development of EpiData Software has been reached now. Therefore we have placed for generel testing pre-release version four copies of EpiData EntryClient EpiData Manager on the testing page of EpiData: <http://www.epidata.dk/testing.php> Since the versions are for testing only, please DO NOT use for any production data. The files have passed our internal testing routines, but are not ready for general use yet, Following the external tests all of you contribute and subsequent changes we expect to release the version 4 for production in mid January. The new aspects are: a. Addition of a memo variable type (more than one line in texts) b. A new statusbar - which can be configured by the user, including adding names of variables from all forms c. A unified naming structure, which will be used in all coming software d. Addition of definition of user roles in projects. That is one can allow some users to define structure or change texts and others can only do entry. If you download the zipped files from you will find instructions on the new user role definitions in a pdf file. We have decided to call this updated version number 4 to avoid confusion with EpiData Classic which then will be the only v3.1 . Some of the documentation refers to v2.2, but disregard such comments. Best wishes Jens Lauritsen EpiData Association, Odense, Denmark

1 0

Reorder fields
by EpiData development and support 14 Dec '16

14 Dec '16

You can drag the fields around using the mouse. The order is top-to-bottom and then left-to-right for fields in exactly the same vertical position. > > I created a form from a stata file but the order of variables in the epidata file is different for some reason and the flow of the data entry is wrong - it does not match the order of variables in the stata file OR the physical position (left-right, up-down). > Can you please tell me how I can fix the variable order to fix the flow? > thanks > Sarah

1 1

Re: [EpiData-list] EpiDatamanager version with SAS support (EpiData-list Digest, Vol 154, Issue 9)
by EpiData development and support 18 Nov '16

18 Nov '16

Hello! I think both SPSS and SAS are able to read/import Stata data files. I have used this for importing data to SPSS. Best regards Jonas 2016-11-18 19:00 skrev epidata-list-request(a)lists.umanitoba.ca: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Looking for EpiDatamanager version with SAS support > (EpiData development and support) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 17 Nov 2016 12:02:19 +0100 > 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] Looking for EpiDatamanager version with SAS > support > Message-ID: > <D159CEE915BB9443937841D16D4B333DEE89385D89(a)PHOCEO09.aphm.ap-hm.fr> > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > Since SAS is not supported anymore by EpiDataManager, i would need to get the 2.9 version where it was still supported OR I would know if it is possible to get a .rec file from the .epx as we have a utility to convert from .rec to .sas > > Could you send me a link with the corresponding version? > > BTW, I understand the decision of saying goodbye to SAS and SPSS but wouldn't that close too many doors for the project? Everyone is not using Stata. > > Cheers, > Alex > > CPCET > Assistance Publique H?pitaux de Marseille > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > End of EpiData-list Digest, Vol 154, Issue 9 > ********************************************

1 0

Looking for EpiDatamanager version with SAS support
by EpiData development and support 17 Nov '16

17 Nov '16

Hello, Since SAS is not supported anymore by EpiDataManager, i would need to get the 2.9 version where it was still supported OR I would know if it is possible to get a .rec file from the .epx as we have a utility to convert from .rec to .sas Could you send me a link with the corresponding version? BTW, I understand the decision of saying goodbye to SAS and SPSS but wouldn't that close too many doors for the project? Everyone is not using Stata. Cheers, Alex CPCET Assistance Publique Hôpitaux de Marseille

1 0

Epidata in mobile devices
by EpiData development and support 14 Nov '16

14 Nov '16

Dear Epidata Team, I was wondering if epidata entry can be used in mobile devices like ipad or android tablets. I noticed someone asked about this in 2012, but i couldn't find an answer for that subject. Is it possible? Thank you very much for all your work. DD Doris Durán Santiago, Chile

1 0

problem with XML version 4
by EpiData development and support 12 Nov '16

12 Nov '16

Dear Epidata team! I tried to open a project in manager but got this error message: "PROJECT HAS INCORRECT XML VERSION! MAX SUPPORTED XML VERSION:3 PROJECT XML VERSION 4" I then looked at the file in an XML editor, the header indicated version 4: <?XML VERSION="1.0" ENCODING="UTF-8"?> <EPIDATA XMLNS="HTTP://WWW.EPIDATA.DK/XML/2.1" XMLNS:XSI="HTTP://WWW.W3.ORG/2001/XMLSCHEMA-INSTANCE" XSI:SCHEMALOCATION="HTTP://WWW.EPIDATA.DK/XML/2.1 HTTP://WWW.EPIDATA.DK/XML/2.1/EPX.XSD" VERSION="4" XML:LANG="EN" DATESEPARATOR="/" DECIMALSEPARATOR="," TIMESEPARATOR="." CYCLE="56"> I tried the change the header to this (taken from an earlier version of the project which was working): <?XML VERSION="1.0" ENCODING="UTF-8"?> <EPIDATA XMLNS="HTTP://WWW.EPIDATA.DK/XML/2.0" XMLNS:XSI="HTTP://WWW.W3.ORG/2001/XMLSCHEMA-INSTANCE" XSI:SCHEMALOCATION="HTTP://WWW.EPIDATA.DK/XML/2.0 HTTP://WWW.EPIDATA.DK/XML/2.0/EPX.XSD" VERSION="3" XML:LANG="EN" CYCLE="56"> This resulted in a new error, although I managed to open the project. But the project did not contain all CRFs and no data... New error message: "LIST INDEX (0) OUT OF BOUNDS.PRESS OK TO IGNORE AND RISK DATA CORRUPTION [....]" As this is a real lifr project and I had to be able to carry on, I solved the problem by copying the records from the bad file back into an previous project file by using an XML editor. It then worked fine. I noticed only one difference at the end of the bad file, some log lines. Hope this can help the project. I am using the 2.0.13.64 64 bit Win version of Manager and 2.0.10.26 of the Client. We had the same problem on the Mac Version Best regards Jonas Malmstedt -- ------------------------- Jonas Malmstedt Överläkare, M.D, Ph.D. - Consultant vascular surgeon Section for vascular surgery, - Department of Surgery Södersjukhuset - 118 83 Stockholm - Sweden ORCID ID [1] http://ki.se/en/kisos/sosvasc [2] http://ki.se/people/jonmal [3] Phone: 0046 (0)8 616 2893 email: jonas.malmstedt(a)sll.se Links: ------ [1] http://orcid.org/0000-0002-2758-9623 [2] http://ki.se/en/kisos/sosvasc [3] http://ki.se/people/jonmal

1 1

Problem with change of name of valuelabel and valuelabels for type
by EpiData development and support 10 Nov '16

10 Nov '16

Dear Epi-Data team! If you intend to change to a new Valuelabel (eg change name of the valuelabel and add a new value) in manager and do this via "Edit" and changes the name of the old label and add a value, then all variabels in the project get the new valuelabel. You have to do like this: "Edit", choose "none", then "Apply". Then choose "New" and make the new valuelabel. But when doing this I get "Access violation" error message. I think the access violation error is a problem with the type UPPERCASE which do not allow that you create valuelabels. Best regards Jonas -- ------------------------- Jonas Malmstedt Överläkare, M.D, Ph.D. - Consultant vascular surgeon Section for vascular surgery, - Department of Surgery Södersjukhuset - 118 83 Stockholm - Sweden ORCID ID [1] http://ki.se/en/kisos/sosvasc [2] http://ki.se/people/jonmal [3] Links: ------ [1] http://orcid.org/0000-0002-2758-9623 [2] http://ki.se/en/kisos/sosvasc [3] http://ki.se/people/jonmal

1 0

If-then skip function
by EpiData development and support 10 Nov '16

10 Nov '16

Dear Epidata users, Apologies if this has been asked before but I could not find the answer in the archive. I knew how to do an IF and THEN command in the old version of Epidata. I am now using version 2.0.8.56 and am stuck. I can perform a skip based on the field I am on (in 'field 'properties' in the 'jump' tab). But how do I do a skip based on a previous field? i.e. at the end of a section entering personal information I want to skip to one of several subsequent sections depending on what was entered in one of the early fields of personal information, not the last one in the section. I hope my query is clear. Thanks, Suzanne

1 1

An issue of lower vs. UPPER case naming, terminology change warning and other plans of implementation
by EpiData development and support 02 Nov '16

02 Nov '16

Dear All In the decisions of development we need to focus at all times to : a. simplify interface, b. create structured and easily understandable terminology c. adaptation to many combinations of users, computers and local language implementations of texts etc. In order to do so we will attempt to be more precise in terminology 1. We plan to use these definitions: project: all information contained in a given epx file dataset: contains all variables in a single entry form observation: is the data unit observed (formerly called a record) variable: contains a single data entity (formerly sometimes called a field) variable label: the descriptive text for a variable value labels:define legal values and gives a text for each value Any legal value can be given the "missing" status and exported as such If you have related data (e.g. house -> person -> visit) each of these will be a dataset containing a number of observations recorded in those variables present in a given dataset. 2 We will implement a "non case sensitive" principle. That is v1 and quest1 will be the same variables as V1 and QUEST1. H1 and h1 as a header text will be the same. But obviously the variable labels and header text can contain as well local language characters and any upper/lower case text. 3 EntryClient will get a "save as" possibility in the file menu, since sometimes we have experienced that a network drive was lost during entry, e.g. Z drive: - then any changes was lost since last save because there would also be no timed backup residing on that drive. 4 We will consider whether to implement a timed backup up principle in manager, just like there is one now in entryclient. If connection to the network is lost or the software brakes down, the timed backup file can be used after restarting Manager. 5 We will implement a missing value definition for dates and jumps based on date values. Please comment on the these aspects if you have ideas, suggestions, find the terminology confusing or have other examples of different terminology across Analysis, EntryClient and Manager. regards Jens Lauritsen EpiData Association, Denmark

1 0

New Manager Version (2.0.13.64) due to blocking bug -
by EpiData development and support 02 Nov '16

02 Nov '16

Unfortunately the version (2.0.13.63) of Manager had a bug in Windows, which we did not catch before release. Therefore please download and install the version 2.0.13.64, which was just uploaded. We will gradually be more strict in applying quality assurances before release, but sometimes this could result in 1-2 weeks delay of a bug fix version due to limited staff. Users who wish to assist in the quality assurance release program can send us an e-mail on info at epidata.dk We apologize for the inconvenience incurred by this and thank Mr Thambo for the reporting. Regards Jens Lauritsen EpiData Association, Denmark

1 0

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

EpiData-list Digest, Vol 151, Issue 1 - Bug to define Valuelabel (2)
by EpiData development and support 07 Jul '16

07 Jul '16

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

1 2

The old version Epidata - Control Function
by EpiData development and support 01 Jul '16

01 Jul '16

Dear Epidata Developers I use Epidata in a long time. There was the control function that allowed for a lot. There was a * .chk file in which you could write a basic useful language. I am trying to design an input mask, but now I seek the equivalent of this function, I can not find. Has it been removed? If there is how to use it? 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

Re: [EpiData-list] EpiData-list Digest, Vol 150, Issue 8
by EpiData development and support 30 Jun '16

30 Jun '16

Dear Jens and T.Christiansen, Many many thanks, from me and a grateful user community best 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: Thursday, June 30, 2016 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 150, 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. The old version Epidata - Control Function (EpiData development and support) 2. New public release EpiData Manager v 2.0.10.59 (EpiData development and support) 3. New experimental release of EpiData Manager and EpiData EntryClient (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 30 Jun 2016 10:01:36 +0000 (UTC) From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: Epidata <epidata-list(a)lists.umanitoba.ca>, "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Subject: [EpiData-list] The old version Epidata - Control Function Message-ID: <9169254.6772797.1467280896435.JavaMail.yahoo(a)mail.yahoo.com> Content-Type: text/plain; charset=UTF-8 Dear Epidata Developers I use Epidata in a long time. There was the control function that allowed for a lot. There was a * .chk file in which you could write a basic useful language. I am trying to design an input mask, but now I seek the equivalent of this function, I can not find. Has it been removed? If there is how to use it? 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 ------------------------------ Message: 2 Date: Thu, 30 Jun 2016 14:12:42 +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] New public release EpiData Manager v 2.0.10.59 Message-ID: <1467288762402.55581.73100@webmail3> Content-Type: text/plain; charset=UTF-8 Dear all The following changes have implemented in the Manager version 2.0.10.59, which replaces ALL previous versions: 2.0.10.59: * Fixed bug where rightclicking the designer, while editing a dataform caption would CAUSE a program crash. * Removed SAS Export as announced earlier (SPSS/PSPP is still there) * Visual change: All must-enter fields are now painted red, as in EntryClient. All changes with version can be seen here: <http://epidata.dk/epidatamanager.changelog.txt> For those who experienced problems with running 64bit versions on Windows and changed to Windows 32bit, please try the new replaced version. Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. Warm regards Jens Lauritsen EpiData Association Denmark > > ------------------------------ Message: 3 Date: Thu, 30 Jun 2016 16:32:06 +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] New experimental release of EpiData Manager and EpiData EntryClient Message-ID: <1467297126440.119863.7904@webmail6> Content-Type: text/plain; charset=UTF-8 Dear all A short while ago I announced the public release of version 2.0 for general production use. Production versions are available from <http://epidata.dk/download.php> During development we prepare test and experimental versions. These are made with new features and therefore the epx files are of a different structure. This is why we urge You NOT to use them for real projects, but only for testing. From this version and unwards test and experimental versions will only be supplied in the form of downloadable zipped/tar archives, which you MUST extract before use. (see pps) The purpose of open testing is to allow users to comment and aid in the development direction. As you know this is a small project in budget compared to large software systems, such that we are depending on the help of users in the tests. A new experimental version has just been uploaded to the page : http://epidata.dk/testing.php <http://epidata.dk/download.php> I do hope that users will challenge the new features, which in short are: 1 User logging and control: Many places now require logging of entry and access to data (e.g. who entered which data on which days for GCP monitoring). Please read the document on how to define extended user access. The document is not a teaching guide for setup of user access principles in general, but a description of the specific implementation we have made. The document explains how user rights are defined in a project and how you can separate entryrights from password changing rights or other aspects of extended data control. See: <http://epidata.dk/php/downloadc.php?file=ExtendedAccess.pdf> and should be included with the software. 2 E-mail after entry of data: As part of the project properties you may define, that the epz backup file can be mailed to a given mail. The software does NOT send the message but gives the standard mail and name of the file to your own email client. This can be useful if you have many remote entry places and a central analysis office. In such cases ALWAYS add encrypted status to your project. 3 Content in statusbar: In particular when you have long or related dataforms it can be instructive to know values of fields in the Statusbar. This is now a feature of the dataform. Known previously as "type statusbar" in EpiData Classic. We will provide more information within the next week, but after that next development sequence starts in August. Such that comments and test results should be sent to us at the latest around August 1st. At that point we will plan in more detail for the autumn. As always - do report to this list of your comments and results. Al types of comments are welcomed including as well enthusiastic and critical comments on design choices on our part. Warm regards again Jens Lauritsen EpiData Association Denmark PS - as mentioned previously: Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. pps: If for some reason you need an installation version we can inform you how to get that - at least for the current test - it is a safety measure not to deliver installation versions, since a number of users previously installed the test version over the public release version - and had severe problems of project data that could no longer be used (without efforts that only few know of). Do also remember that we have NO WAY of regaining data if you forget a password. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 150, Issue 8 ********************************************

1 0

New experimental release of EpiData Manager and EpiData EntryClient
by EpiData development and support 30 Jun '16

30 Jun '16

Dear all A short while ago I announced the public release of version 2.0 for general production use. Production versions are available from <http://epidata.dk/download.php> During development we prepare test and experimental versions. These are made with new features and therefore the epx files are of a different structure. This is why we urge You NOT to use them for real projects, but only for testing. From this version and unwards test and experimental versions will only be supplied in the form of downloadable zipped/tar archives, which you MUST extract before use. (see pps) The purpose of open testing is to allow users to comment and aid in the development direction. As you know this is a small project in budget compared to large software systems, such that we are depending on the help of users in the tests. A new experimental version has just been uploaded to the page : http://epidata.dk/testing.php <http://epidata.dk/download.php> I do hope that users will challenge the new features, which in short are: 1 User logging and control: Many places now require logging of entry and access to data (e.g. who entered which data on which days for GCP monitoring). Please read the document on how to define extended user access. The document is not a teaching guide for setup of user access principles in general, but a description of the specific implementation we have made. The document explains how user rights are defined in a project and how you can separate entryrights from password changing rights or other aspects of extended data control. See: <http://epidata.dk/php/downloadc.php?file=ExtendedAccess.pdf> and should be included with the software. 2 E-mail after entry of data: As part of the project properties you may define, that the epz backup file can be mailed to a given mail. The software does NOT send the message but gives the standard mail and name of the file to your own email client. This can be useful if you have many remote entry places and a central analysis office. In such cases ALWAYS add encrypted status to your project. 3 Content in statusbar: In particular when you have long or related dataforms it can be instructive to know values of fields in the Statusbar. This is now a feature of the dataform. Known previously as "type statusbar" in EpiData Classic. We will provide more information within the next week, but after that next development sequence starts in August. Such that comments and test results should be sent to us at the latest around August 1st. At that point we will plan in more detail for the autumn. As always - do report to this list of your comments and results. Al types of comments are welcomed including as well enthusiastic and critical comments on design choices on our part. Warm regards again Jens Lauritsen EpiData Association Denmark PS - as mentioned previously: Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. pps: If for some reason you need an installation version we can inform you how to get that - at least for the current test - it is a safety measure not to deliver installation versions, since a number of users previously installed the test version over the public release version - and had severe problems of project data that could no longer be used (without efforts that only few know of). Do also remember that we have NO WAY of regaining data if you forget a password.

1 0

New public release EpiData Manager v 2.0.10.59
by EpiData development and support 30 Jun '16

30 Jun '16

Dear all The following changes have implemented in the Manager version 2.0.10.59, which replaces ALL previous versions: 2.0.10.59: * Fixed bug where rightclicking the designer, while editing a dataform caption would CAUSE a program crash. * Removed SAS Export as announced earlier (SPSS/PSPP is still there) * Visual change: All must-enter fields are now painted red, as in EntryClient. All changes with version can be seen here: <http://epidata.dk/epidatamanager.changelog.txt> For those who experienced problems with running 64bit versions on Windows and changed to Windows 32bit, please try the new replaced version. Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. Warm regards Jens Lauritsen EpiData Association Denmark > >

1 0

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

22 Jun '16

Dear Jens Many of us use PSPP (free, legal and excellent) which requires export to SPSS sav style. This is because we cannot afford SPSS or STATA in many parts of dev world I know its more work that i cannot help with but if at all posible could the export to SPSS style be continued? sincerely 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: Tuesday, June 21, 2016 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 150, 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. Status of EpiData Development and a few questions (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Jun 2016 14:05: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: [EpiData-list] Status of EpiData Development and a few questions Message-ID: <1466510717716.8748.10152@webmail9> Content-Type: text/plain; charset=UTF-8 During this week our nights will again be longer and days shorter as a signal of change of season. Just now in Denmark sun is up at 04:39 and down at 22:05, further north even more bright hours. It is customary to make a status before summer vacation and the status for EpiData Development and maintenance is in short: Analysis: The first pre-prototype of a rewritten Analysis is the main development task just now. Core functionality of internal routines is in focus (e.g. how should the software read a command, how to add options etc). There is nothing to test for users until some months from now, but it is progressing as planned. The aim of the rewriting will be to recreate current EpiData Analysis commands, but with a slight modernisation and unification of approach and commands - more on that later. The EpiData List A few weeks back the list was not available, but this should have been fixed again, such that new list users can add themselves. First time you send a mail to the list we have to authorize it to secure against spam. Remember that files should be small and formatted as text (not html). EntryClient and Manager: The public versions are working efficiently with very few bugs, which we attempt to remove quickly. Recently errors in export of dates to Stata version 14 was fixed. There has been an issue when opening files with the 64 bit windows version, but this can be remedied by using the 32 bit version. Development versions of Manager and EntryClient: 1 Logging of user actions and control is in an in-house test. (e.g. someone can define dataforms and others only enter data). An issue of speed and actual control of what to add to logging is under consideration. 2 Configuration of Statusbar with contents of variables is working 3 Ability of automatic sending of backup file via email after entry is in test. The plan is to issue a new test version with this functionality within 2 weeks. I expect that we will no longer support export to SPSS and SAS since the maintenance of these two is cumbersome. The reason is that Stata format is fully documented and therefore easy to work with and R also reads Stata files. Therefore apart from the epx format - we will most likely restrict import and export with variable and value labels to Stata (dta) and without labels to csv (separated). Some users might find that restrictive, but in view of the overall size of the EpiData project priority must be given to secure sustainability. Such choices could lead to discussions on this list - which is highly welcomed. warm regards to all Jens Lauritsen Coordinator and Initiator of the Epidata Project ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 150, Issue 6 ********************************************

1 0

Status of EpiData Development and a few questions
by EpiData development and support 21 Jun '16

21 Jun '16

During this week our nights will again be longer and days shorter as a signal of change of season. Just now in Denmark sun is up at 04:39 and down at 22:05, further north even more bright hours. It is customary to make a status before summer vacation and the status for EpiData Development and maintenance is in short: Analysis: The first pre-prototype of a rewritten Analysis is the main development task just now. Core functionality of internal routines is in focus (e.g. how should the software read a command, how to add options etc). There is nothing to test for users until some months from now, but it is progressing as planned. The aim of the rewriting will be to recreate current EpiData Analysis commands, but with a slight modernisation and unification of approach and commands - more on that later. The EpiData List A few weeks back the list was not available, but this should have been fixed again, such that new list users can add themselves. First time you send a mail to the list we have to authorize it to secure against spam. Remember that files should be small and formatted as text (not html). EntryClient and Manager: The public versions are working efficiently with very few bugs, which we attempt to remove quickly. Recently errors in export of dates to Stata version 14 was fixed. There has been an issue when opening files with the 64 bit windows version, but this can be remedied by using the 32 bit version. Development versions of Manager and EntryClient: 1 Logging of user actions and control is in an in-house test. (e.g. someone can define dataforms and others only enter data). An issue of speed and actual control of what to add to logging is under consideration. 2 Configuration of Statusbar with contents of variables is working 3 Ability of automatic sending of backup file via email after entry is in test. The plan is to issue a new test version with this functionality within 2 weeks. I expect that we will no longer support export to SPSS and SAS since the maintenance of these two is cumbersome. The reason is that Stata format is fully documented and therefore easy to work with and R also reads Stata files. Therefore apart from the epx format - we will most likely restrict import and export with variable and value labels to Stata (dta) and without labels to csv (separated). Some users might find that restrictive, but in view of the overall size of the EpiData project priority must be given to secure sustainability. Such choices could lead to discussions on this list - which is highly welcomed. warm regards to all Jens Lauritsen Coordinator and Initiator of the Epidata Project

1 1

"hybrid" COMMENT LEGAL or RANGE
by EpiData development and support 17 Jun '16

17 Jun '16

Can I define in my chk file legal values like this, (for a field describing the number of housing units in a building): RANGE 1 7 COMMENT LEGAL 1 2 3 4 5 6 7 "more than 6" Thanks. --Chris Ryan

1 1

AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 04/07/2016)
by EpiData development and support 16 Jun '16

16 Jun '16

I am out of the office until 04/07/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 150, Issue 4" sent on 16/06/2016 18:00:25. 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

nested RELATES?
by EpiData development and support 13 Jun '16

13 Jun '16

I'm using Epidata 3.1 on Windows 7. Can RELATES be nested? By that I mean, can data entry form A relate one-to-many with data entry form B, and some of the records in B relate one-to-one to data entry forms C? Specifically, I have a qes/rec/chk setup for households. within households, there will be several people, each of whose data is entered in qes/rec/chk B some (not all) of the people will have asthma. For the asthmatics, I want to, conditional on their asthma status, jump to a third qes/rec/chk setup for data on the asthmatics. Thanks. --Chris Ryan Broome County Health Department, Binghamton, NY, US

1 1

List archives
by EpiData development and support 07 Jun '16

07 Jun '16

Have the EpiData List Archives changed accessibility rules? Clicking on any link ([1]http://lists.umanitoba.ca/pipermail/epidata-list/) from the EpiData web site to the Archives gives: "You don't have permission to access /pipermail/epidata-list/ on this server" Hans L Rieder, MD, MPH References 1. http://lists.umanitoba.ca/pipermail/epidata-list/

1 0

XML error while exporting
by EpiData development and support 06 Jun '16

06 Jun '16

Hello, I have encountered a problem with exporting an Epidata file ending epx. When trying to export, I receive the following message and the export won't go through: Project has incorrect XML version! Max supported XML Version: 3 Project XML Version: 4 Does anyone have a solution for this problem? I have downloaded the latest version of Epidata Manager on my MAC. Med venlig hilsen Antonio Sylvester E-mail: antonio(a)au.dk AU IT, Health Vennelyst Boulevard 9 Bygning 1610-1.97 8000 Århus C Tlf: (+45) 871 50922 E-mail: health.it(a)au.dk http://www.au.dk/it

1 1

Issues when exporting into Stata 13
by EpiData development and support 26 May '16

26 May '16

Hi - two things that I've become aware of when exporting data into Stata 13 using EpiData Manager:- 1) My interview dates have all had 60 years added to them, so instead of my interviews being recorded as taking place in 2016 they are recorded as happening in 2076. The day and month are correct. 2) I've exported my value labels, but only the first letter of these is displaying in the browse mode in Stata (though if I tabulate a variable the value labels do show in full in the table). Is there any way of correcting these problems from within EpiData, rather than from within Stata? Thanks Keith

1 0

EpiData Manager closing without warning when trying to set up double-data entry
by EpiData development and support 26 May '16

26 May '16

Hi - has anyone else run into this problem? I have created a project in EpiData Manager, and have created a duplicate project for double data-entry using Tools>Prepare Double Entry. I have entered some data into the duplicate project and now I want to compare the two. I open EpiData Manager again, open my first project, and then go to Document>Compare Duplicate Files. I get the double-entry validation screen from which I use the 'Add Files' button to add my second project. But before I can even do that EpiData Manager closes without warning. I have tried rebooting my computer, reinstalling epidata manager and removing the password which I had put on the original project, but nothing seems to solve this problem. Before setting up the duplicate project I did move the original project to a new location and rename it. I wonder if this could, somehow, be part of the problem? Any help very gratefully received, as we are planning to introduce the new version of EpiData for teaching this year. All the best Keith Keith Tomlin Lecturer in Epidemiology Department of Disease Control and Department of Population Health London School of Hygiene & Tropical Medicine Room 445, Keppel Street, London, WC1E 7HT, UK +44 (0)207 927 2716 ( tel:02079272257)

1 0