- EpiData-list - University of Manitoba Mailing Lists

Website down
by EpiData support and user community 14 Feb '26

14 Feb '26

Hello, I am getting started with epidata and trying to download a copy of epidata. However all of the website pages at epidata.dk redirect to https://www.webhosting.dk/DKK/mustcontactus.php?domain=epidata.dk& . Is there any alternative way to download epidata? Best Patrick

1 2

select command in EpiData Analysis 3.3.0.0 r617
by EpiData support and user community 02 Feb '26

02 Feb '26

Caution! This message was sent from outside the University of Manitoba. Di 01 fév 2026 Bonsoir, I need to understand how to use the select command in EpiData Analysis 3.3.0.0 r617; I tried the following: .select Sexe<>"Inconnu" do; Selecting, please wait... (25951 of 26097 selected) Then: .freq Sexe; Sexe ──────────────── N ──────────────── Féminin 11973 Inconnu 146 Masculin 13978 ──────────────── Total 26097 ──────────────── The selection doesn’t apply to the database, even if the previous message said so; it’s unfortunate because further analysis of the data should apply to the selected records. I didn’t find explanations about select in the help file (how to apply it and how to cancel it); do you have some answers about this? Cordialement, Réjean Réjean Dion, M.D. Médecin-conseil en santé publique (maladies infectieuses) Laboratoire de santé publique du Québec (LSPQ), Institut national de santé publique du Québec (INSPQ) 20045, chemin Sainte-Marie, Sainte-Anne-de-Bellevue (Québec) H9X 3R5 INSPQ Centre d'expertise et de référence en santé publique URL: http://www.inspq.qc.ca/ Professeur adjoint de clinique Département de médecine sociale et préventive (DMSP), École de santé publique de l’Université de Montréal (ESPUM) Membre actif Département de médecine préventive et de santé publique (DMPSP), Centre hospitalier de l’Université de Montréal (CHUM) Tél.: 514-457-2070 poste 2325 Fax: 514-457-6346 Courriel: rejean.dion(a)inspq.qc.ca

1 1

New Epidata Analysis 3.3.0 for Linux does not work on the two Linux diatros
by EpiData support and user community 21 Jan '26

21 Jan '26

Caution! This message was sent from outside the University of Manitoba. Dear Jens, New Epidata Analysis 3.3.0 for Linux does not work on the following two Linux diatros. Linux Lite 6.4 BOSS 10 Linux. After going through a “Mandatory” tutorial, it get stuck. Following error is diplayed. An unhandled error occurred in the program! Please verify that the error can be reproduced. Report to the: EpiData-list (mail.....) and mail to info(a)epidata.dk<javascript:void(0);> Include most recent 5-10 lines of history in your report. I wish, if we can have a look at this issue. After hard work put in by Epidata Team for making this useful linux software, it should work. With regards, Dr. Shavinder Singh

1 1

is there a way I can contribute money toward EpiData?
by EpiData support and user community 31 Dec '25

31 Dec '25

Caution! This message was sent from outside the University of Manitoba. Hello. I'm not much of a programmer. Would a donation of funds help this excellect project along? Thanks. --Chris Ryan

1 0

Happy New Year 2026 to Epidata Team
by EpiData support and user community 31 Dec '25

31 Dec '25

Caution! This message was sent from outside the University of Manitoba. Dear Jens and Epidata Team, I hope you all are fine and enthusiastic for Epidata development. Wish you bright new year 2026 full of healthy vibes, energy and wellbeing. With best wishes, Shavinder Singh

1 0

what are the command-line capabilities of the latest version of EpiData?
by EpiData support and user community 02 Nov '25

02 Nov '25

Caution! This message was sent from outside the University of Manitoba. On the website is read about EpiC, but I get the sense that applies only to Classic, although perhaps I misunderstand. Using the epx-based modern version, can I write code or issue commands that will, e.g., export, import, append, and so on? Thanks. --Chris Ryan

1 0

heading colors chosen in Manager do not cascade to Entry screens
by EpiData support and user community 02 Nov '25

02 Nov '25

Caution! This message was sent from outside the University of Manitoba. When I set colors for Heading1, Heading2, etc, I expected those headings in Entry to appear in those colors. They did not. The color setting in Manager only changes the colors one sees when working in Manager? The font choices in Manager do seem to cascade to the Entry screens, as near as I can tell so far. --Chris Ryan

1 0

make the picklist of value labels and their values appear upon request?
by EpiData support and user community 02 Nov '25

02 Nov '25

Caution! This message was sent from outside the University of Manitoba. I see the checkbox option in Manager to "always show" the picklist for a particular variable during data entry. Can I leave that box unchecked yet still make it possible for a user to open the list at will, i.e. once in a while they forget what allowable values are? Thanks, --Chris

1 2

is there a way to design a project, or any part(s) of one, outside of Manager?
by EpiData support and user community 02 Nov '25

02 Nov '25

Caution! This message was sent from outside the University of Manitoba. I'm starting to experiment with creating my first EpiData project, with the latest (non-classic) version of the software. I've encountered a few questions/issues, which I'll post in separate email messages, for clarity in threads on the List. First, is there a way to design a project, or any part(s) of one, outside of Manager? From what I've read, there was an intent to make project design more of a GUI, point-and-click activity. But for programmers, writing a text file in an editor is more efficient. If not designing the whole project, then, for example, defining sets of value labels? Thanks. --Chris Ryan

1 2

place for data entry notes?
by EpiData support and user community 02 Nov '25

02 Nov '25

Caution! This message was sent from outside the University of Manitoba. As I recall, in Classic there was the ability for a user to enter "notes" about the data entry experience. F5? F9? I forget the exact keystrokes. At any rate it was a place for user to write things like "the scribbles on the paper survey form were hard to decipher; I took my best shot" or "the power went out while I was doing this record" Thanks. --Chris

1 0

in the latest (non-classic) version, can legal values of a variable depend on the value of an earlier variable?
by EpiData support and user community 01 Nov '25

01 Nov '25

Caution! This message was sent from outside the University of Manitoba. Say for example I have 2 variables, V1 and V2. If V1 = "dog", I want the choices in the pick list (what classic EpiData would call LEGAL values) for V2 to be "beagle", "collie", and "mutt" But if V1 = "cat", I want the choices in the pick list (what classic EpiData would call LEGAL values) for V2 to be "tabby", "siamese", "calico" (I'm not even sure if Classic could do that; I can't remember, it's been a while) Thanks. --Chris Ryan

1 0

simultaneous data entry in the same file
by EpiData support and user community 14 Oct '25

14 Oct '25

Caution! This message was sent from outside the University of Manitoba. Hello. I'm contemplating Epidata as a tool for an ongoing project of operational data entry (monthly volumes/census of different types of clinic visits at a facility) in which several different staff members would be entering the data relevant to their section of the clinic (TB, STD, etc.) The facility does not have an electronic medical record, or any other platform from which these data could be extracted in automated fashion. Currently each staff member is typing numbers into a massive shared spreadsheet on their networK (ugh!). If I set up a single, shared, Epidata .rec file in that same network location, could several staff members be editing it (adding records) simultaneously? It would be rare by sheer chance, but it could happen. No two staffers would ever be editing the same existing record. Alternatively, if each staffer had their own .rec file pertaining to their activities, I suppose I could, each month, APPEND them into my "working" total file, from which I would derive my summaries (probably by exporting and running some R code)? Advice and suggestions welcome. Thanks. --Chris Ryan Binghamton, NY, US

1 3

/Save command error solution
by EpiData support and user community 08 Oct '25

08 Oct '25

Caution! This message was sent from outside the University of Manitoba. Thank Jamie for the response. It was a part of long command given below. BAR V10a /By=v3 /PCT /Legend /Frame /Hgrid /Vgrid /SizeX=1200 /SizeY=900 /Ti="" /Sub="" /Fn="" /Xtext="Association of Overweight and obesity among Female adolescents with Mother's Literacy Status" /Ytext="Percents" /Fontsize=14 /Edit /save /Replace It worked today. The version on the download page is V2.2 Rel. 3 (Build 187) You have mentioned Epidata Analysis version 2.2.3.237 Is it a new a new build of Classical Epidata Analysis? Is Classical Epidata Analysis development still going on? Please repond whenver you can. With regards, Shavinder Singh version 2.2.3.237

1 1

/save command in Classical Epidata Analysis ver 2.2.2.187 displays error message,
by EpiData support and user community 03 Oct '25

03 Oct '25

Caution! This message was sent from outside the University of Manitoba. Dear Epidata Team, When I use “/save” command to save the graph produced in Classical Epidata Analysis ver 2.2.2.187, e.g. /save=”MyGraph.wmf” The following error message is displayed; save : Unknown Command Any solution ! Dr. Shavinder Singh

1 1

Difficulty downloading EpiData
by EpiData support and user community 26 Aug '25

26 Aug '25

Caution! This message was sent from outside the University of Manitoba. Hi, A colleague and I want to use EpiData but we are having trouble downloading from the website, on both Mac and PC. Has anyone else had trouble? Thanks! Katie Edler

1 4

Unable to export stata files from the epidata manager
by EpiData support and user community 10 Jul '25

10 Jul '25

I am using Epidata manager version 4.7.0.0 on a windows 11 laptop. I have been unable to export stata files from the manager for the past 2 weeks. When I try the program crashes and has to be closed down via task manager. Hope there are some good solutions for that?

1 2

Writing .PGM files for New EpiDataanalysis?
by EpiData support and user community 15 Feb '25

15 Feb '25

Caution! This message was sent from outside the University of Manitoba. Dear list, I am experiencing a fairly steep learning curve trying to write quite basic .pgm script files for the new post-2018 EpiData Analysis guided by the introductory text on the epidata website and the commands.html reference. I have searched the web for relevant tutorials, courses or examples, but cannot find any. Could anybody on the list be willing to share some programming examples for example on the examples page on Epidata.dk (or elsewhere)? BTW: Does the new Analysis allow for a parallel to the user input command in Classic: globalvariable=trim("?Input value?") Thanks for any hints or links. Regards, Vegard Hoegli MD, MPH

1 6

PGM-file with date formulas crashes
by EpiData support and user community 07 Feb '25

07 Feb '25

Caution! This message was sent from outside the University of Manitoba. Dear list, 4 years ago I made a menu-driven activity monitoring system for a community health center based on the menu system designed by Jens Lauritsenand Hans Rieder with additional help from Jamie Hockin. Thank you for your generous help! The system has been in stable production at 2 sites in Norway since then, with very little need for support. Now, however, reports (.pgm-files) which includes date functions suddenly crash with this output: Invalid argument/mathematical expression PGM Error: Operation aborted One of the actual commands : Select year(startdate)= @rappaar On experimenting with different functions, it seems like the function no longer accepts date values. The EntryClient display dates in the format: dd.mm.yyyy, while Analysis displays dd/mm/yyyy, but this does not seem to be a problem. The report ran smoothly with data up to 2023, the same .epx datafile updated with 2024-data (about 3200 records) fails. Dataentry works fine, using EntryClient v 4.6.0.2, Menu shell and analysis runs EpiDatstat Classic 2.2.3.187 Since the problem arises in a file that used to work fine, I suspected that there must be a registration error. However,I have browsed and searched the dataset for missing or unexpected input but cannot find anything. If any of you have a hint where to look (or suggest a work-around, I would be grateful. Thank you in advance! Vegard Hoegli MD, MPH

1 3

join
by EpiData support and user community 05 Feb '25

05 Feb '25

Caution! This message was sent from outside the University of Manitoba.

1 0

Bonne année 2025 and follow-up on EpiData developments
by EpiData support and user community 08 Jan '25

08 Jan '25

Caution! This message was sent from outside the University of Manitoba. Je 02 jan 2025 Bonjour et bonne année 2025 à l'équipe d'EpiData. I hope Jens and Jamie still remember me; I have very nice memories of them. I used a lot the classic EpiData softwares (Entry and Analysis) before their new developments (Manager, EntryClient and Analysis); I had many difficulties with the test of the new versions years ago, so I decided to wait and to return to Epi Info 7 (ei7), for which I acquired a quite advance level, however, ei7 evolution didn't follow and I learned that the CDC won't support it anymore after next September. So, after all those years, I will need to return to EpiData. I asked to our information technology department to install the new EpiData on my computer, but I guess I'll need some support and more recent and detailed documentations that the ones that are available on the website (URL: https://epidata.dk/documentation.php); perhaps, if Jamie is available to give me a tour about EpiData, it would be a good start and accelerate my learning curve. Cordialement, Réjean Réjean Dion, M.D. Médecin-conseil en santé publique (maladies infectieuses) Laboratoire de santé publique du Québec (LSPQ) Institut national de santé publique du Québec (INSPQ) 20045, chemin Sainte-Marie, Sainte-Anne-de-Bellevue (Québec) H9X 3R5 INSPQ Centre d'expertise et de référence en santé publique URL: http://www.inspq.qc.ca/ Professeur adjoint de clinique Département de médecine sociale et préventive (DMSP) École de santé publique de l'Université de Montréal (ESPUM) Tél.: 514-457-2070 poste 2325 Fax: 514-457-6346 Courriel: rejean.dion(a)inspq.qc.ca

1 4

Happy New Year 2025 to the Jens and Epidata Team
by EpiData support and user community 01 Jan '25

01 Jan '25

Caution! This message was sent from outside the University of Manitoba. Happy New Year 2025 to the Jens and Epidata Team. Epidata Team has shown perseverance and resolve to continue the Epidata development. Keep it up. With regards and best wishes, Dr. Shavinder Singh

1 1

EpiData freq and means, compared to SAS
by EpiData support and user community 16 Jul '24

16 Jul '24

Caution! This message was sent from outside the University of Manitoba. Hi all I have a project where I compare results of statistical analysis of free to use, easy to use (menu driven) statistical analysis programs. Free To Use Statistical Software: Comparing Statistical Analyses<https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4105959> I did comparison of a little results from EpiData, comparing frequency and means to results from SAS. I'm happy to say EpiData results and SAS results are the same. I usually also compare results from correlation and regression. The help file in the downloaded program says regression is, at present, only in Analysis classic? The commands.htm file on the epidata website also lists correlation. I'm not clear if correlation is available in the all in one install? I can't seem to get a correlate command to run. correlate :=PctBelowPov =BirthRate =Services results in ERROR: Identifier "correlate" not found! Thanks Gene

1 2

EpiData, analysis, means /by
by EpiData support and user community 15 Jul '24

15 Jul '24

Caution! This message was sent from outside the University of Manitoba. Hi all I hope this is something simple. I'm reading in this data set, the one I mentioned before. ShortDataSet.csv<https://drive.google.com/file/d/11WIET3s4eMHsB6JQ6hOQBx0SKquGRKKw/view?usp=…> I can get a frequency for AreaRegion, using both the drop down menu system and by typing in "freq AreaRegion" (without the quotes) and I can get a means in both the drop down menu system and by typing in "means population I can't seem to get means by population, in the line at the bottom of the analysis system where we can type in commands. I went to the list of commands http://www.epidata.dk/commands.htm where it says this: means variable1 [/by=variable2] [/T] [/q] basic descriptive statistics for numeric variable1, optionally stratified by variable2 Options: /by=variable2 : Stratify by this variable I typed in " means population /by=AreaRegion" (without the quotes) and got this .means population /by AreaRegion; ERROR: Line 1: Syntax error at pos 18: / Expected: "-", "!", "(", ")", ":=", ";", "@", "[", "else", "Identifier", "in", "to" I also tried a couple of variations, like "means population [/by=AreaRegion]" and means population (/by=AreaRegion) and got similar error lines. Any help with this? By the way, on the commands.htm web page above, in the first column, it looks like you can click on the command and it's supposed to go to another web page, for example, means<http://www.epidata.dk/means.htm> is supposed to lead to http://www.epidata.dk/means.htm but that results in not found. And again, I greatly appreciate all the work that folks put into EpiData and all the accompanying web pages, help pages, documentation, etc. It's a lot of work and your work is appreciated. Thanks Gene

1 2

about epi data analysis, email list
by EpiData support and user community 15 Jul '24

15 Jul '24

Caution! This message was sent from outside the University of Manitoba. Hi I think I mentioned a couple of places on the epi data website where the email list website needs to be updated. Also, when you open epi data analysis, and click on help and about, it says the epi data email list is here http://lists.umanitoba.ca/mailman/listinfo/epidata-list but that clicks onto 'page not found'. Thanks Gene Gene Shackman Albany NY 12203 Applied Sociologist

1 0

EpiData, means, difficult data set
by EpiData support and user community 12 Jul '24

12 Jul '24

Caution! This message was sent from outside the University of Manitoba. Hi all First, thanks to everyone involved in EpiData. It's a lot of work and I appreciate it. I list EpiData in my list of free to use stat software https://sites.google.com/site/gsocialchange/statsoft I have a data set that's probably difficult. ShortDataSet.csv<https://drive.google.com/file/d/11WIET3s4eMHsB6JQ6hOQBx0SKquGRKKw/view?usp=…> I can do some analysis, such as frequency, and a scatter graph, but I'm having problems with means. Using the menu drop downs, I tried to get a means for population and got this outcome .means population !vla !l; ERROR: Unknown option/variable: vla Actually, I get the same error if I try to get means for pctbelowpov, and gdppercap too. I -can- use population in a scatter plot, for example, population by gdppercap, or population by pctbelowpov. I can also use "describe" on a set of variables, for example, pctbelowpov to population. Just can't get means to work. Any help is greatly appreciated. Thanks Gene Gene Shackman Albany NY Applied Sociologist https://sites.google.com/site/gsocialchange/global-social-change-research-p…

1 6

Release of latest versions Analysis: v3.3.0.0, Manager and EntryClient: 4.7.0.0
by EpiData support and user community 26 May '24

26 May '24

Caution! This message was sent from outside the University of Manitoba. Dear Jens and Team, Congratulations for carrying on the Epidata development. The latest versions Analysis: v3.3.0.0, Manager and EntryClient: 4.7.0.0 are more stable. After going through the details, will get back. With regards, Dr. Shavinder Singh

1 0

New versions out on epidata.dk
by EpiData support support and user community 23 Apr '24

23 Apr '24

Caution! This message was sent from outside the University of Manitoba. Dear all It has been a while since new updates were available to all. Yesterday all new compiled versions are there for you on http://www.epidata.dk/ in the downloads page The main changes since last version and last update is: Analysis: v3.3.0.0 Manager and EntryClient: 4.7.0.0 If you test with "check version online" in help menu, the above will be shown after download. But will say an earlier version as "public". But the new versions should be safe for general use. But as always be sure to test before changing that all works as expected. Changes: Files on the website with "latest changes" will be updated soon. But the changes are: All: due to problems of invisibility on windows all software now starts at a default position, which should work. Then move to where you prefer after each start. Coordinates saved earlier were not consistent and lead to invisibility of the software. Analysis: a. Analysis has now an added graphs menu part with several graph types General a. All software was moved to a new GIT hub based account - allowing for conversion to open source developments and maintenance. More news on this later. b. All software was updated to latest version of FreePascal compiler and Lazarus . For more information on these two tools, see https://www.lazarus-ide.org/ Without the efforts of Jamie Hockin and Torsten B. Christiansen the update would not have been possible. Any comments appreciated. -- Jens Lauritsen Founder and Coordinator EpiData Association Denmark

1 2

Epidata manager and Windows 11
by EpiData support support and user community 27 Jun '23

27 Jun '23

Dear Jens Was running a workshop on research methods The epidata session we found many with windows 11 unable to install epidata manager Is there any way to overcome this? With regards Thambu CMC Vellore ________________________________ From: epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Sent: Sunday, February 26, 2023 6:04 PM To: epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca> Subject: EpiData-list Digest, Vol 210, Issue 1 CAUTION: This email originated from outside of CMC. Do not click links or open attachments unless you recognize the sender and know the content is safe. Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe 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 -- epidata-list(a)lists.umanitoba.ca ___________________________________ Today's Topics: 1. Re: Re Installation of EpiData Manager on Windows 11 - The Libeay32.dll issue (EpiData support support and user community) 2. Re: Re Installation of EpiData Manager on Windows 11 - The Libeay32.dll issue (EpiData support support and user community) 3. Re: Re Installation of EpiData Manager on Windows 11 - The Libeay32.dll issue (EpiData support support and user community) ---------------------------------------------------------------------- Message: 1 Date: Thu, 23 Feb 2023 16:44:09 -0500 From: EpiData support support and user community <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Re: Re Installation of EpiData Manager on Windows 11 - The Libeay32.dll issue To: EpiData support support and user community <epidata-list(a)lists.umanitoba.ca> Message-ID: <167718835436.2910.17237443081117514713(a)vpl-mailman01.ad.umanitoba.ca> Content-Type: text/plain; charset=utf-8 I can’t help with the .dll issue as I’m a Mac user. In principle, you should only install EpiData once on any computer, or at least only once for any one user. As with most software these days, EpiData stores some settings in a standard location separate from the data directory. You can create shortcuts to the software in multiple directories that include a parameter pointing to the startup settings (startup.pgm) you want to use. That’s an advanced procedure, though. Jamie > PS: I organize my project as separate installations where both data and > executables are kept in their own folder structure. Is this a problem - > maybe a wrong instance of the library is executed? DS ------------------------------ Message: 2 Date: Sun, 26 Feb 2023 10:19:43 +0100 From: EpiData support support and user community <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Re: Re Installation of EpiData Manager on Windows 11 - The Libeay32.dll issue To: EpiData support support and user community <epidata-list(a)lists.umanitoba.ca> Message-ID: <167740318785.2910.11155511378007643836(a)vpl-mailman01.ad.umanitoba.ca> Content-Type: text/plain; charset=UTF-8 In a recent course 3 of 5 pc's all with the full suite installed showed a strange behaviour of EntryClient and Manager. The exe apparently started and was running, but not to be found on the screen. I suspected a wrong position failure, but could not access the place where the ini file is placed. What we did then was to copy only the exe file to another folder, eg a subfolder of the desktop. And then it worked. I am annoyed by not knowing the mechanism behind. The analysis did not show the same problem. We will discuss in the core group what to do. Maybe a completely different dll and place of ini on startup could be a solution to implement and test in the coming release. How important is it for users that we have user defined place on screen at startup. If we had a default startup in the middle of the screen some problems would be avoided. E.g. when you sometimes use two external screens and forget to move to screen 1 on a laptop . Any idea or consideration is welcomed. ⁣Jens Lauritsen EpiData Association, Denmark Coordinator & initiator of the EpiData Project Den 23. feb. 2023 21.56, fra 21.56, EpiData support support and user community <epidata-list(a)lists.umanitoba.ca> skrev: >Dear list, >I have also had problems starting Manager and Entryclient. Thank you >for >pointing at the Libeay32.dll. I am not an expert on this, and need some >advice: > >The file is part of any EpiData installation. Renaming it to something >else >makes the application start as a first time execution, and I am asked >to >select a working directory etc, and after that is done once, the >program >seems to work normally. > >However, there are other application folders that contain the same >library. >When I copied one of these files into the EpiData directory as >suggested in >a former post, the ssleay32.dll file reported an error. > >I would therefore highly appreciate advice on how to correctly deal >with >this issue. > >PS: I organize my project as separate installations where both data and >executables are kept in their own folder structure. Is this a problem - >maybe a wrong instance of the library is executed? DS > >Best wishes. >Vegard Høgli >MD, MPH, Norway >_______________________________________________ >EpiData-list mailing list -- epidata-list(a)lists.umanitoba.ca >To unsubscribe send an email to epidata-list-leave(a)lists.umanitoba.ca ------------------------------ Message: 3 Date: Sun, 26 Feb 2023 07:39:15 -0500 From: EpiData support support and user community <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Re: Re Installation of EpiData Manager on Windows 11 - The Libeay32.dll issue To: EpiData support support and user community <epidata-list(a)lists.umanitoba.ca> Message-ID: <167741485127.2910.12252475536043175381(a)vpl-mailman01.ad.umanitoba.ca> Content-Type: text/plain; charset=utf-8 Two suggestions. 1. For Windows and Linux, a startup parameter to reset the screen position would be useful. It’s possible with Mac, but a bit problematic for many to use the command line. 2. My preferred: define a key combination that resets the screen position to some default, like mid-screen, as you suggest, Jens. This would work on all platforms. Something like <shift><ctrl>W? Jamie > In a recent course 3 of 5 pc's all with the full suite installed showed a strange behaviour of EntryClient and Manager. The exe apparently started and was running, but not to be found on the screen. I suspected a wrong position failure, but could not access the place where the ini file is placed. > > What we did then was to copy only the exe file to another folder, eg a subfolder of the desktop. And then it worked. I am annoyed by not knowing the mechanism behind. The analysis did not show the same problem. > > We will discuss in the core group what to do. Maybe a completely different dll and place of ini on startup could be a solution to implement and test in the coming release. > > How important is it for users that we have user defined place on screen at startup. If we had a default startup in the middle of the screen some problems would be avoided. E.g. when you sometimes use two external screens and forget to move to screen 1 on a laptop . > > Any idea or consideration is welcomed. > > ⁣Jens Lauritsen > EpiData Association, Denmark > Coordinator & initiator of the EpiData Project ------------------------------ Subject: Digest Footer ________________________________________ To unsubscribe send an email to epidata-list-leave(a)lists.umanitoba.ca ------------------------------ End of EpiData-list Digest, Vol 210, Issue 1 ********************************************

1 1

Windows 11 - Yhe Libeay32.dll issue
by EpiData support support and user community 01 Mar '23

01 Mar '23

Dear Jamie and Jens, thank you for replying, I have made different menu-driven systems where files are stored in relative subfolders. I include the program files so the user can run it from a USB stick or a Citrix share without additional installation procedure. I have found that removing or renaming the Libeay32.dll file in the corresponding program directory, the program asks for default directory etc on first execution. Later on, Manager and Entryclient runs without difficulty. I am not sure if that may cause other problems, though. best wishes Vegard

1 1

Re Installation of EpiData Manager on Windows 11 - The Libeay32.dll issue
by EpiData support support and user community 01 Mar '23

01 Mar '23

Dear list, I have also had problems starting Manager and Entryclient. Thank you for pointing at the Libeay32.dll. I am not an expert on this, and need some advice: The file is part of any EpiData installation. Renaming it to something else makes the application start as a first time execution, and I am asked to select a working directory etc, and after that is done once, the program seems to work normally. However, there are other application folders that contain the same library. When I copied one of these files into the EpiData directory as suggested in a former post, the ssleay32.dll file reported an error. I would therefore highly appreciate advice on how to correctly deal with this issue. PS: I organize my project as separate installations where both data and executables are kept in their own folder structure. Is this a problem - maybe a wrong instance of the library is executed? DS Best wishes. Vegard Høgli MD, MPH, Norway

1 5

Re: Installation of Epidata Manager on Windows 11
by EpiData support support and user community 31 Dec '22

31 Dec '22

1 0

Re: Installation of Epidata Manager on Windows 11
by EpiData support support and user community 31 Dec '22

31 Dec '22

1 0

Re: Installation of Epidata Manager on Windows 11
by EpiData development and support 29 Dec '22

29 Dec '22

Dear Epidata team I have been trying to use Epidata Manager v4.6.0.6, EntryClient v4.6.0.6 and Analysis v3.2.0.0 on my 64 bit Windows 11 laptop. The software do not open by simply clicking on the exe files, nor does it open if we install the packages using admin access. Other colleagues are also facing similar issues. Please suggest possible solutions. Regards Divya

2 3

Current status of Epidata Manger, EntryClient and New Analysis
by EpiData development and support 30 Nov '22

30 Nov '22

Dear Jens and Team, I hope you all are happy everything is fine at your end. The list os off. What is the current status of Epidata Manger, EntryClient and New Analysis? Please respond. There is no way to know as epidata list is not there. With regards, Dr. Shavinder Singh  

1 1

calculating intervals between 2 pregnancie
by EpiData development and support 28 Nov '22

28 Nov '22

I want to calculate intervals between 2 different pregnancies. In my .chk, I have put this command: BEFORE FILE TYPE COMMENT ALLFIELDS RED END INTERVALLE AFTER ENTRY INTERVALLE=((DATE - DATE1)/ 30) END END And IT DOES NOT WORK I you can help. Thanks Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion _____ From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Mon, 03 Jan 2022 22:00:18 +0400 Subject: EpiData-list Digest, Vol 202, 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. BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support) 2. Re: BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Mon, 03 Jan 2022 13:19:13 +0400 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: <20220103091913.c8c2eafa(a)smail.chu-reunion.fr> Content-Type: text/plain; charset="UTF-8" We are changing year, so I am creating a "RU22.REC" with the root RU21.QES file (to replace the RU21.REC one) 1) The other years I went in RU21.CHK and renamed it RU22.CHK and it worked When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK BUT IT GIVES ME A VERTICAL QUESTIONNAIRE LIKE A VERY LONG SNAKE, VERY BAD TO MAKE A DATA RECORD HOW COULD I THROUGH THE "SAVEDATA" PROCEDURE HAVE AN HORIZONTAL (NORMAL) QUESTIONNAIRE Thank you very much for your help ALSO: HAPPY NEW YEAR 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 ------------------------------ Message: 2 Date: Mon, 3 Jan 2022 08:58:42 -0500 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] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: <28A45B95-FE40-4966-A975-72FCCD1A533D(a)bell.net> Content-Type: text/plain; charset=us-ascii Have you tried using the .REC file from 1) with the .CHK file from 2)? Normally, I would have done pretty much the same as you, but like this: Use the windows command line to copy files, in this order. copy ru21.qes ru22.qes Run EpiData to create ru22.rec from ru22.qes copy ru21.chk ru22.chk Jamie > On Jan 3, 2022, at 4:19 AM, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: > > 1) The other years I went in RU21.CHK and renamed it RU22.CHK and it worked > When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct > > > > > 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure > SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 202, Issue 1 ********************************************

1 2

Error message while wrting rec file from excell file
by EpiData development and support 06 Aug '22

06 Aug '22

Dear Epidata Team,                                   I was trying to copy two columns of Excell to import into Classical Epidata Analysis, to write a .rec file. I am getting this error message in red colour. "Separators: (tab: 38)(semicolon: 0)(comma: 0)(space: 31) Lines: 39" What does this message mean and how to fix it. With regards, Dr. Shavinder Singh

1 0

PROBLEM: HOW TO CONNECT OVERTIME RECORDS. MESSAGE FOR JAMIE
by EpiData development and support 27 Jul '22

27 Jul '22

Dear Jamie, Thank you for your answer but I failed See below all the commands I tried Subject: [EpiData-list] PROBLEM: HOW TO CONNECT OVERTIME RECORDS PLEASE Message-ID: <20220724052114.e51cdb84(a)smail.chu-reunion.fr> Content-Type: text/plain; charset="UTF-8" ORIGINAL QUESTION SAY: you have women all identified by a personal number When you chose a number, you have all the babies she had over time e.g. a woman had her first child in 2007, the second one in 2009, the third in 2014 and the last one in 2020 If I want to calculate the intervals between pregnancies (and compare with a risk, preeclampsia for example) - What variable should I create? - What command should I do to find: in 2009 the interval with the preceding pregnancy was 21 months, in 2014 the interval with the preceding was 51 months etc.... JAMIE’S ANSWER You can do this in Analysis. My example is for the new EpiData Analysis. Similar commands work in classic analysis. First create your time difference variable new v mois i; // integer variable called MOIS Then sort the data by subject ID and delivery date sort sujetid accouchment; Then calculate the time difference between records, but only when the subject ID is the same as in the previous record mois := iif(sujetid = sujetid[_n - 1], (accouchment - accouchment[_n - 1]) DIV 30, 0); Dividing the delivery dates by 30 gives approximate months. Dividing by 30.417 and rounding off is more accurate, but I?d go with the integers. Jamie DIEFERENT COMMANDS I TRIED TO DO : ALWAYS « UNKNOWN IDENTIFYER » define interv ### let interv = (numero = numero [_ n-1], dn - dn [_n-1]) div 30.41; intervl = if (numero = numero [_ n-1], dn - dn [_n-1]) div 30.41; interv = iif (numero = numero [_ n-1], dn - dn [_n-1]) div 30.41; if (numero = numero [_ n-1] ) then interv = ( dn - dn [_n-1]) / 30.41;You can do this in Analysis. My example is for the new EpiData Analysis. Similar commands work in classic analysis. First create your time difference variable new v mois i; // integer variable called MOIS Then sort the data by subject ID and delivery date sort sujetid accouchment; Then calculate the time difference between records, but only when the subject ID is the same as in the previous record mois := iif(sujetid = sujetid[_n - 1], (accouchment - accouchment[_n - 1]) DIV 30, 0); Dividing the delivery dates by 30 gives approximate months. Dividing by 30.417 and rounding off is more accurate, but I?d go with the integers. Jamie 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: Sun, 24 Jul 2022 16:05:18 +0400 Subject: EpiData-list Digest, Vol 206, 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. PROBLEM: HOW TO CONNECT OVERTIME RECORDS PLEASE (EpiData development and support) 2. Re: PROBLEM: HOW TO CONNECT OVERTIME RECORDS PLEASE (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sun, 24 Jul 2022 09:21:14 +0400 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] PROBLEM: HOW TO CONNECT OVERTIME RECORDS PLEASE Message-ID: <20220724052114.e51cdb84(a)smail.chu-reunion.fr> Content-Type: text/plain; charset="UTF-8" SAY: you have women all identified by a personal number When you chose a number, you have all the babies she had over time e.g. a woman had her first child in 2007, the second one in 2009, the third in 2014 and the last one in 2020 If I want to calculate the intervals between pregnancies (and compare with a risk, preeclampsia for example) - What variable should I create? - What command should I do to find: in 2009 the interval with the preceding pregnancy was 21 months, in 2014 the interval with the preceding was 51 months etc.... THANK YOU IF CAN HELP Best 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: Mon, 03 Jan 2022 22:00:18 +0400 Subject: EpiData-list Digest, Vol 202, 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. BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support) 2. Re: BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Mon, 03 Jan 2022 13:19:13 +0400 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: <20220103091913.c8c2eafa(a)smail.chu-reunion.fr> Content-Type: text/plain; charset="UTF-8" We are changing year, so I am creating a "RU22.REC" with the root RU21.QES file (to replace the RU21.REC one) 1) The other years I went in RU21.CHK and renamed it RU22.CHK and it worked When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK BUT IT GIVES ME A VERTICAL QUESTIONNAIRE LIKE A VERY LONG SNAKE, VERY BAD TO MAKE A DATA RECORD HOW COULD I THROUGH THE "SAVEDATA" PROCEDURE HAVE AN HORIZONTAL (NORMAL) QUESTIONNAIRE Thank you very much for your help ALSO: HAPPY NEW YEAR 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 ------------------------------ Message: 2 Date: Mon, 3 Jan 2022 08:58:42 -0500 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] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: <28A45B95-FE40-4966-A975-72FCCD1A533D(a)bell.net> Content-Type: text/plain; charset=us-ascii Have you tried using the .REC file from 1) with the .CHK file from 2)? Normally, I would have done pretty much the same as you, but like this: Use the windows command line to copy files, in this order. copy ru21.qes ru22.qes Run EpiData to create ru22.rec from ru22.qes copy ru21.chk ru22.chk Jamie > On Jan 3, 2022, at 4:19 AM, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: > > 1) The other years I went in RU21.CHK and renamed it RU22.CHK and it worked > When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct > > > > > 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure > SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 202, Issue 1 ******************************************** ------------------------------ Message: 2 Date: Sun, 24 Jul 2022 08:04:29 -0400 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] PROBLEM: HOW TO CONNECT OVERTIME RECORDS PLEASE Message-ID: <848EE055-EC37-44A4-87C6-29EBA5918FC9(a)bell.net> Content-Type: text/plain; charset=utf-8 You can do this in Analysis. My example is for the new EpiData Analysis. Similar commands work in classic analysis. First create your time difference variable new v mois i; // integer variable called MOIS Then sort the data by subject ID and delivery date sort sujetid accouchment; Then calculate the time difference between records, but only when the subject ID is the same as in the previous record mois := iif(sujetid = sujetid[_n - 1], (accouchment - accouchment[_n - 1]) DIV 30, 0); Dividing the delivery dates by 30 gives approximate months. Dividing by 30.417 and rounding off is more accurate, but I?d go with the integers. Jamie > > ?SAY: you have women all identified by a personal number > > > When you chose a number, you have all the babies she had over time > e.g. a woman had her first child in 2007, the second one in 2009, the third in 2014 and the last one in 2020 > > > If I want to calculate the intervals between pregnancies (and compare with a risk, preeclampsia for example) > - What variable should I create? > - What command should I do to find: in 2009 the interval with the preceding pregnancy was 21 months, in 2014 the interval with the preceding was 51 months etc.... > > > THANK YOU IF CAN HELP > Best > > Dr Pierre-Yves Robillard > R?animation n?onatale et pediatrique, n?onatologie > Centre Hospitalier R?gional ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 206, Issue 1 ********************************************

1 1

PROBLEM: HOW TO CONNECT OVERTIME RECORDS PLEASE
by EpiData development and support 24 Jul '22

24 Jul '22

SAY: you have women all identified by a personal number When you chose a number, you have all the babies she had over time e.g. a woman had her first child in 2007, the second one in 2009, the third in 2014 and the last one in 2020 If I want to calculate the intervals between pregnancies (and compare with a risk, preeclampsia for example) - What variable should I create? - What command should I do to find: in 2009 the interval with the preceding pregnancy was 21 months, in 2014 the interval with the preceding was 51 months etc.... THANK YOU IF CAN HELP Best 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: Mon, 03 Jan 2022 22:00:18 +0400 Subject: EpiData-list Digest, Vol 202, 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. BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support) 2. Re: BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Mon, 03 Jan 2022 13:19:13 +0400 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: <20220103091913.c8c2eafa(a)smail.chu-reunion.fr> Content-Type: text/plain; charset="UTF-8" We are changing year, so I am creating a "RU22.REC" with the root RU21.QES file (to replace the RU21.REC one) 1) The other years I went in RU21.CHK and renamed it RU22.CHK and it worked When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK BUT IT GIVES ME A VERTICAL QUESTIONNAIRE LIKE A VERY LONG SNAKE, VERY BAD TO MAKE A DATA RECORD HOW COULD I THROUGH THE "SAVEDATA" PROCEDURE HAVE AN HORIZONTAL (NORMAL) QUESTIONNAIRE Thank you very much for your help ALSO: HAPPY NEW YEAR 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 ------------------------------ Message: 2 Date: Mon, 3 Jan 2022 08:58:42 -0500 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] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: <28A45B95-FE40-4966-A975-72FCCD1A533D(a)bell.net> Content-Type: text/plain; charset=us-ascii Have you tried using the .REC file from 1) with the .CHK file from 2)? Normally, I would have done pretty much the same as you, but like this: Use the windows command line to copy files, in this order. copy ru21.qes ru22.qes Run EpiData to create ru22.rec from ru22.qes copy ru21.chk ru22.chk Jamie > On Jan 3, 2022, at 4:19 AM, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: > > 1) The other years I went in RU21.CHK and renamed it RU22.CHK and it worked > When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct > > > > > 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure > SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 202, Issue 1 ********************************************

1 1

EpiData and Monterey 12.2.1
by EpiData development and support 28 Jun '22

28 Jun '22

Good day, I have encountered problems when trying to install EpiData on my new Apple Mac. The OS is Monterey 12.2.1 I get a message to contact the developers and ask them to update the software so that it can be installed if one has Monterey OS. I am teaching an online course at the University of Pretoria, that includes EpiData, starting in 10 days time. There are 1600 students enrolled and almost certainly there will be some with the Monterey latest OS. Regards Brendan Brendan Girdler-Brown +27 (0) 66 077 1295

1 9

Unsuscribe
by EpiData development and support 14 Mar '22

14 Mar '22

-- Christoph Napierala Glärnischstrasse 1 CH-8608 Bubikon mobile:+41 796893932 mail:christoph.napierala@gmail.com

1 0

Help with Boolean
by EpiData development and support 14 Mar '22

14 Mar '22

Hello, New EpiData user here. I set up a form with some of my variables as Boolean. Entered my data using 0/1 for those variables. My issue is that all of them are now showing as N. Isn’t it N for 0 and Y for 1 ? Didn’t notice the issue until exporting my data. Is there anything I can do now about that ? Thanks.

1 6

BIG PROBLEMS TO UPDATE A CHK FILE
by EpiData development and support 03 Jan '22

03 Jan '22

We are changing year, so I am creating a "RU22.REC" with the root RU21.QES file (to replace the RU21.REC one) 1) The other years I went in RU21.CHK and renamed it RU22.CHK and it worked When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK BUT IT GIVES ME A VERTICAL QUESTIONNAIRE LIKE A VERY LONG SNAKE, VERY BAD TO MAKE A DATA RECORD HOW COULD I THROUGH THE "SAVEDATA" PROCEDURE HAVE AN HORIZONTAL (NORMAL) QUESTIONNAIRE Thank you very much for your help ALSO: HAPPY NEW YEAR 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

1 1

Delete all records at once or a DataSet
by EpiData development and support 30 Nov '21

30 Nov '21

Hello together, I am using the "new" EpiData on Linux. I know how to delete one record/entry/observation/row in the EpiDataEntry. But I do not find a way to delete all records at once. Is there a function for this? My current workaround is simplye remove the <records> section from the xml file. Kind Christian

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 200, Issue 3
by EpiData development and support 30 Nov '21

30 Nov '21

Dear Jens I am not familiar with exporting files from epidata or epidata manager to R or versions of software base on R Is there some guidance on the same? Sorry if this has been asked/ answered earlier with regards Thambu

1 1

Re: [EpiData-list] Problems installing v 4.6.0.6 on Mac Also
by EpiData development and support 12 Jul '21

12 Jul '21

This is normal macOS behavior when first trying to run software that does not come from the app store. You must right click (or ctrl-click) on the app icon and choose open. You may have to do this twice for each app. Jamie

1 1

Problems installing v 4.6.0.6 on Mac Also
by EpiData development and support 07 Jul '21

07 Jul '21

When trying to install new version on MacOC Catalina (10.15.7) fails too. "EpiDataAnalysis App cannot be installed because the Developer cannot be confirmed. MacOS cannot ensure that the program does not contain Malware" This happens both to Manager and Analysis installers (haven´t checked Entry Client) Same result regardless program security unlocked in settings. Regards, vegard Hogli

1 0

Re: [EpiData-list] Problems installing Epidata 4.6.0.6 on Windows 10 Home
by EpiData development and support 05 Jul '21

05 Jul '21

Hi, Thanks for your reply! Unfortunately, I receive the same error message in the Event viewer when I download the zip-file, unzip it to a folder and then click the exe file. Best wishes, Johanna Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

1 0

Problems installing Epidata 4.6.0.6 on Windows 10 Home
by EpiData development and support 03 Jul '21

03 Jul '21

Hi, I’m having trouble installing and opening EpiData Manager and EntryClient 4.6.0.6 on a brand new Windows 10 Home laptop. After completing the ‘All in one installer’ process, double clicking the shortcut icons does not open any application. On checking the Windows Application Logs, I see the following error message for both Manager and Client: Faulting application name: epidatamanager.exe, version: 4.6.0.6, time stamp: 0x00000000 Faulting module name: libeay32.dll, version: 1.0.2.5, time stamp: 0x56618848 Exception code: 0xc0000005 Fault offset: 0x000000000000ca23 Faulting process ID: 0x2584 Faulting application start time: 0x01d7686c70eb6c7f Faulting application path: C:\Program Files\EpiData\epidatamanager.exe Faulting module path: C:\Program Files\EpiData\libeay32.dll Report ID: 5ea1974a-9f7a-435c-90ac-006cc7a19264 Faulting package full name: Faulting package-relative application ID: I have switched off all anti-virus software but this also didn’t fix the problem. Has anyone else encountered this problem? Does anyone have any suggestions on how to fix this problem? Thanks so much in advance! Regards, Johanna Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

1 1

EpiData support
by EpiData development and support 26 Jun '21

26 Jun '21

I would like to thank Jens, Torsten and Jamie for their stirling work. I am facilitator of an online module (part of the PGDPH) at the University of Pretoria in South Africa. We have about 750 students enrolled for the module (620 just completed and 130 will be starting on Monday in a second offering) and we decided to use EpiData as the software of choice for data entry and management for all the good reasons that people know about. Many of the students use Apple Mac computers and, of these, an increasing number are using Catalina or Big Sur as their OS. When our first module started 8 weeks ago several students using Catalina really struggled to install and use EpiData; most had to then borrow or buy a Windows computer to do the 1 week modulette on EpiData. I contacted Jens, about ten days ago, and two days ago I received a reply that he would be upgrading the current public release to assist our students. This adds an enormous amount of value as more and more students in Africa are working with Apple Mac computers, and it is reassuring for us that EpiData will continue to be developed and upgraded for the benefit of these students. Many thanks gentlemen! Brendan Girdler-Brown +27 (0)11 477 7865 +27 (0) 66 077 1295

1 1

New Epidata Analysis 3.2.0.0 Dark Editor Background
by EpiData development and support 23 Jun '21

23 Jun '21

Dear Jens and Team, Congratulations Great release (RC1) We devote lot of time in Editor also for meaningful output. Please incorporate the function of “Adjust the colour of the Editor background also”. e.g. #000000 is black. Regards, Shavinder Singh

1 1

New versions of Manager, EntryClient and Analysis
by EpiData development and support 23 Jun '21

23 Jun '21

Dear all From today you will find on the website at http://www.epidata.dk/download.php The new public release versions are: EpiData Manager and EntryClient version 4.6.0.6 EpiData Analysis version 3.2.0.0 The main new aspect is that Analysis now has a dialogue as an assisting tool for creating analysis commands with most options for frequencies, tables, describe and ctable. Find this in the menu point "Analysis". In addition the whole principle of development is in re-design, such that future updates should be easier to manage within the project. You should notice that the current release versions will be the final ones for 32 bit systems (older computers). The reason is that the maintenance of all possible aspects for as well 32 and 64 bit versions for as well Windows, Linux and Mac OS has become too cumbersome. The 32 bit versions (4.6.0.6 or 3.2.0.0) will remain downloadable from the page: http://www.epidata.dk/download32.php In short time the main download page will be adapted to contain only 64 bit versions and links to Classic EpiData and the 32 bit versions. The adaptation will also complete updating of other aspects, e.g. content of "latest changes" files. Thanks to the implementation and development of principles by Torsten Christiansen and Jamie Hockin (struggling with Mac aspects), plus guidance from Hans Rieder and coordination/managing efforts by myself the project continues. Without the continued comments and downloads that we can see from all users we would not be motivated to continue, so thanks for that. The current aim is to include all functions available in classic EpiData.(whether to include "before/after blocks" will be decided later). After our summer period here (july-august) development will continue with graphs in analysis and other aspects. best wishes Jens Lauritsen Initiator and Coordinator of EpiData Software Denmark

1 0

EpiData and Apple Mac
by EpiData development and support 22 Jun '21

22 Jun '21

Good day, In our University we run a course on-line and students learn how to use EpiData as well as Stata during the course. We encountered a problem with the students who use Apple Mac computers and who are using Catalina OS. It appears that EpiData does not run properly in Catalina environment. They can download and install a beta version but that does not allow saving, for example, or export to Stata; so they are unable to submit assignments requiring the preparation of questionnaires, data entry or export to Stata. It affects about 20 of our 600 students. Does anyone have any solution to suggest?

1 4

New test version of EpiData Software (Mac working and dialogs in Analysis)
by EpiData development and support 26 Apr '21

26 Apr '21

Dear all A new test release has been placed on www.epidata.dk/testing.php The changes will be released as public version after implementation of a few more changes and tests. Users are invited to test the following new features and improvements: - but remember as always to work on test data and copies of projects. Major new feature in Analysis: Dialogs for statistics A visual form which will create the command - like in Analysis ClassicSpeed of reading projects has been improved EntryClient, Manager and Analysis work in Mac (64 bit - latest OS) A number of bug-fixes and internal clarifications to manage definitions of missing data and tables have been implemented. Most of this is important improvements, but should not be visible to the user, apart from reading of files being much faster. One of the difficulties is to ensure correct implementation of procedures for encryption, user control of entry (logging) and the way the operating systems control access to the encryption libraries. Increasingly in many organizations user have only restricted access to their own computer making it difficult to write software - without paying licenses to e.g. Microsoft and Apple. The test versions are provided as zip/tgz compressed files. Make sure that you unzip all content with maintained folder/directory structure Please comment on the list if you have problems/suggestions or experiences with the updated versions. One note is that after unzipping and opening you should resize the dialogs in Analysis if you have a Mac computer. Otherwise some of the content is not sufficiently intuitive to use (we are working on that). As always the changes were made in a collaborative effort of Torsten B.Christiansen, Jamie Hockin , Hans Rieder and I. Torsten does the main software desing and programming and Jamie added important aspects of Mac function and dialog implementation. best wishes Jens Lauritsen EpiData Association Denmark

1 1

EpiData on MAC
by EpiData development and support 24 Apr '21

24 Apr '21

Dear EpiData List Would anyone know how to run EpiData Entry on a Mac Computer. When I try to download, I get the message: Epidataentry needs to be updated. (To the current version of MAC). Kind regards, Jannie ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).

1 0

Child form unicity bug
by EpiData development and support 13 Mar '21

13 Mar '21

Hello, First, I would to thanks the Epidata team for the great job done so far. Recently, in a database with a main form and several child forms (single or repeated), we observed at the end of the study several duplicate forms for several patients. This can happen on a 1 to 1 relationship or on a 1 to many relationships. We checked the properties of all datasets. They have been properly established to ensure that each record is unique. We have performed some tests to reproduce the issue and found that the issue occurs when a key field is exited with the mouse, or when a form is exited using the mouse to choose a new form to fill in the left panel of the screen instead of leaving the form with the last filled field. When this happens, the user can browse the forms and enter a duplicate visits without warning. Under these circumstances, the "Save Form" dialog box appeared twice. These bugs can be reproduced with the child-bug.epx (joined file) database using the following procedure: Add a new patient Fill out the main form with a new patient: Patient n ° 45 Age: 2 years Height: 90 (do not use Enter key) After typing 90 on the keyboard, use the mouse to select the inclusion data form. After this action, the "Save Record" dialog box appears twice instead of once when the Height field is exited with the Enter key. Once the focus is on the inclusion form, enter today's date and weight e.g. 12 kg (do not use the enter key). After typing 12 on the keyboard, use the mouse to select the Visits form. Once the visit form is displayed, select the inclusion form again. Instead of displaying the data entered previously, the form is empty and the completed forms counter is zero, add the current date and a weight. If you repeat this operation several times, you can complete more than one form. The number of child forms filled is only "correctly" displayed when the patient is exited and selected again. I hope these information will help to solve the problem. Best regards _________________________ Jean-Marie Chrétien CHU Angers - DRCi – Responsable de la Cellule Gestion des Données et Evaluation CIL adjoint pour la recherche 02.413.55976 06.65.80.71.15

1 0

Online Training in epidata anlayisis
by EpiData development and support 08 Feb '21

08 Feb '21

Dear Jens A request. Could you or any of the resource people make a short podcast on the use of the updated epidata analysis? Or are there any resources available for this online i/ we can access Thanks in advance Thambu

1 1

Command Select
by EpiData development and support 08 Feb '21

08 Feb '21

Thank you for your response. Example with my own file. .freq castem; castem ----------- N ----------- 1 153 2 150 3 632 ----------- Total 935 ----------- .select castem<>3 do; Selecting, please wait... (303 of 935 selected) .begin; ==> No operative (idem begin without < ; >) ERROR: Line 1: Syntax error at pos 7: ERROR: Unexpected end of line! Perhaps a ";" is missing? .freq castem; ==> no selection... castem ----------- N ----------- 1 153 2 150 3 632 ----------- Total 935 ----------- .select castem=1 do drop data; ==> objective : keep codage 1 Selecting, please wait... (153 of 935 selected) (153 observations dropped) .freq castem; ==> Selection code<> 1 (link avec drop data ?) castem ----------- N ----------- 2 150 3 632 ----------- Total 782 ----------- And an another (and last) question : how to delete the current selection? Thank you. Bernard Branger, Nantes, France

1 1

New analysis
by EpiData development and support 06 Feb '21

06 Feb '21

Hello, For training, I'm trying to understand the new version of "Analysis". A few comments : - The command "freq var ! r;" (as shown in the guide) doesn't work, but "freq var ! pr" is OK. Strictly speaking and on the educational plan, the percentages presented with "freq" are in columns : "freq var ! c;" or "freq var ! pc;" would be more logical. - To select a part of the file, I noted, (as an example for a frequency) the command "select (var1 <3) do freq var2 ! pr;". Should we repeat with each command "select (var1 <3) do"? Is there a way, like the old "select", to select part of the file for further commands? - The command (example) "select (var1 = 3) do var1: = 2;" is quite complicated compared to that "if ... then ...." - How to create a new numeric variable with 3 digits and 2 decimal places? As in the old "define var ###. ##"? - When will the "regress" commands and the graph commands (including scatter with a regression line as in the old "Epi-Info" ...? Thank you for your help. Bernard BRANGER - 44000 NANTES - France

1 1

Happy (belated) New Year 2021
by EpiData development and support 15 Jan '21

15 Jan '21

Happy (belated) New Year 2021 Dear Jens and Epidata Team,                         There is absolute silence on the list. I hope Covid 19 impact is waning away and New Epidata Analysis development is in progress. Any news!! Shavinder Singh  

1 0

Re: [EpiData-list] Epidata 4.6.0.4 SPSS-Export
by EpiData development and support 15 Dec '20

15 Dec '20

Dear Michael, thank you for this hint! That makes things much easier. If someone nevertheless needs it, I attach a spss syntax, that produces a list of string variables in the datafile and than deletes all leading and ending quotation marks (the first and the last character) in these string variables. It can be included in the spss import syntax. Best Regards, Juergen Am 15.12.2020 um 10:32 schrieb EpiData development and support: > Dear Juergen, > this is right, the SPSS-Export doesn't work right. The used SPSS- > Command "data list" is a lit bit out of date and could not handle > qualifiers for Textvariables. > > This is a workaround: > Do the SPSS-Export. > Afterwards do a second export, the "CSV-Export", and overwrite the > existing file. > In the Specifications for the CSV-Export you can disable/delete the > Quote Character. > Greetings > Michael > > Am 15.12.2020 10:08 schrieb EpiData development and support: >> Dear all, >> >> I have a little problem with the SPSS-Export of the Epidata-Files. >> When you export string variables, you can specify the variable >> delimiter (e.g. "|") but not the text delimiter. The result is a csv >> file, that is imported in SPSS with quotation marks at the start and >> the end of every string variable, even if the variable is empty. I >> found no way to delete these quotation marks during the spss import >> process except with a quite complicated macro. >> >> Is it possible to change the SPSS export? >> >> Kind Regards, >> >> Juergen Spiegel >> >> >> -- >> *********************************************************** >> Freiburger Institut fuer angewandte Sozialwissenschaft e.V. >> FIFAS >> Erasmusstr. 16, D-79098 Freiburg >> >> Telefon: +49-761-288364 >> Fax: +49-761-2927493 >> Web: http://www.fifas.de >> E-Mail: info(a)fifas.de >> >> _______________________________________________ >> 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 -- *********************************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: +49-761-288364 Fax: +49-761-2927493 Web: http://www.fifas.de E-Mail: info(a)fifas.de

1 1

Epidata 4.6.0.4 SPSS-Export
by EpiData development and support 15 Dec '20

15 Dec '20

Dear all, I have a little problem with the SPSS-Export of the Epidata-Files. When you export string variables, you can specify the variable delimiter (e.g. "|") but not the text delimiter. The result is a csv file, that is imported in SPSS with quotation marks at the start and the end of every string variable, even if the variable is empty. I found no way to delete these quotation marks during the spss import process except with a quite complicated macro. Is it possible to change the SPSS export? Kind Regards, Juergen Spiegel -- *********************************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: +49-761-288364 Fax: +49-761-2927493 Web: http://www.fifas.de E-Mail: info(a)fifas.de

1 1

Issue with upwards shifting variables working from different computers
by EpiData development and support 16 Oct '20

16 Oct '20

Dear all, Could someone help us out with an issue regarding the change of layout of an EpiData file every time we open in EpiData manager/EntryClient on different computers? This issue occurs every time we edit the file in a different computer, as we are two persons working on the same file/project on different computer. More specifically, we noticed that the layout shifts upwards when you open the same file in on another computer. These upwards shifts of variables results in the (visual or complete?) loss of the created variables. This also makes the input of data through EntryClient challenging (because you don’t see all the variables anymore). Has this issue been encountered before? And would someone have a solution? All help would be much appreciated! Many thanks

1 1

Update of most recent public version of Analysis (due to error in the editor)
by EpiData development and support 03 Jul '20

03 Jul '20

Dear All Unfortunately there was an undisclosed bug in the public version released last week of new Analysis. One could exit Analysis without being asked to save an unsaved pgm file in the editor. This is now fixed. The most recent public version is therefore: _Manager_ *v4.6.0.2* _EntryClient_ *v4.6.0.2* _Analysis_ *v3.0.0.1* And the combined one for Windows: setup.all-in-one.4.6.0.5.exe The lacking finding of the error has been added to the pre-test for coming analysis. best wishes and apologies. Jens Lauritsen EpiData Association, Denmark

1 0

SPSS Export
by EpiData development and support 03 Jul '20

03 Jul '20

Dear Torsten, dear Jens, Epidata-Manager does the SPSS-Export in a indirect way. A SPSS-Syntax-File and a CSV-Data-File are created. You have to run the Syntax in SPSS to create a SPSS-Datafile. This is the current proceeding. For this proceeding I have some questions: - Is it very hard to create a SPSS-Datafile at once? - Why is the SPSS-CSV-Data-Export-File different to a direct CSV-Data-Export-File? The Structure is different. In my opinion it will be easier and a clear way to have ONE (adjustible) CSV-Data-Export-File. For that I recommend to replace the second Tab in " Tools/Export.../Type: SPSS 'SPSS-Options' " with the 'CSV-Options' (except for "Export Value Labels" because this is a great advantage of EpiData! Perhaps this Item stands better one the first Tab.) - Is it possible to change the default given SPSS-Syntax? The "Data List"-Command still works, but it is a little bit out of date. It does not work with the qualifier for Textvariables. So you have to edit the csv-File or have to write a new Syntax. "GET DATA" is the current Command. With kind regards Michael

1 1

Epidata 3.1 - Not Showing Correct Date
by EpiData development and support 02 Jul '20

02 Jul '20

Good morning. I received a ticket from one of our Epidata users. The user is using Epidata 3.1. According to her, the data entry sheets usually self-populate with the correct date. However, it seems to be stuck on 20/04/2020. Please see attached. Troubleshooting done: 1. Clear personalization and profile. 2. Re-install the software. Info: 1. There are 2 users of Epidata in this department. The 2 of them are experiencing this. 2. They are using VDI pool to access Epidata. What do you think is the problem and how it can be resolved. Thank you. Noel Bermejo Technical Analyst - Information Technology Yorkton Regional Health Centre - Yorkton Saskatchewan Health Authority | 306-786-0159 This email message may contain confidential and/or privileged information. It is intended only for the addressee(s). Any unauthorized disclosure is strictly prohibited. If you are not a named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.

1 1

Epidata Analysis 3.00 and background colour
by EpiData development and support 28 Jun '20

28 Jun '20

Dear Jens and Team,                    Congratulations for this next step of Epidata Analysis 3.00 development. You have very kindly added the functionality of;Output background colour,Command background colour from Edit -- Colour pull down menu.I am not technically sure of the difficulties involved in adding "Editor background colour" option also in the software with cross platform compatibility.However if possible, please try to add that also in the next development release.Our rock solid Classical Epidata Analysis 2.2 ver was developed after year of hard work by Epidata Team. Replicating all those and additional functionalities in the new Epidata Analysis is a daunting task. However Epidata team has shown real perseverance .With regards and best wishes,Shavinder Singh   

1 0

Almost releasable new pre-public version of Analysis (please test)
by EpiData development and support 25 Jun '20

25 Jun '20

Dear list-readers A new updated version of EpiData Analysis (v1.7.99.1) has been placed for your testing on http://epidata.dk/testing.php Please find below a summary of the changes. In particular notice that the requirement of [_n] in pgm's has been removed, unless you refer to a given observation. I expect the release as public in the coming week or the week after. Please test and report to this list. As part of my job as a clinical epidemiologist and professor at the Odense University Hospital here in Denmark I have extensively tested the software during the last three months. We now use the pre-public version on a daily basis. Now we have a running system in new EpiData Analysis. It is run by secretaries, who have no experience in programming. They just click an icon to accomplish: a.import a csv file saved daily from our main IT-patient registration system (EpiData Analysis) b. merge with previously controlled observations to evaluate only new observations (EpiData Analysis) c. quality securing coding in the patient journal. (EpiData EntryClient) d. create SPC graphs in classic analysis (EpiData Analysis Classic) e. create lists for audit of patients where the quality standards were not met. To run the system in the revised new analysis we only lack possibility of creating graphs, which I expect to include in the coming months, if all goes well ready by the end of this year. One other aspect we need to tackle is the increasing demand for safety certificates and documentation in relation to secure systems. If any of you are experienced in this area please write me an e-mail (jl at epidata.dk) . Without the efforts of Torsten Bonde Christiansen (Software design and programming), Jamie Hockin (testing, programming, Mac adaptation) and Hans L. Rieder (testing, approving solutions) the software would not continue to develop. Please look into the website for inspiration: https://tbrieder.org/epidata/epidata.html Best wishes Jens Lauritsen, coordinator and initiator. EpiData Association, Denmark -------------------------------------------------------------------------------------------------------------------------------- Changes since v1.6.0.0 Major improvement: - [_n] is no longer needed, except when desired. - editor: Completely new. Many aspects improved. Works better in MacOs - new !output option with save command - allows saving output content as html - new "set" option to control format of saved output html|txt - new "set" option allows user definition of css styles in saved html output - new "set" option defines internal css or external reference to css file in html output - extended fast createdate function allows conversion of date strings with named months. - extended createdate function allows use of national month naming defined in set Other new aspects: - mergevar added as the last in a merged dataset - default dataset used after merge is the merged one - keyboard shortcuts unified and simplified. - main window opens immediately if started with a pgm - many commands: unified option naming, e.g. !l is labels Bug fixes: - all solved - keep : if used in a "for loop" errors could occur - Assignment: incorrect control of missing in string variables - validate duplicate : error if a variable was missing - many minor other bugs or inconsistencies Bug fixes: - partially solved - errors in calculations when dividing by zero. fixed in Linux and MacOS, but not in windows always. Known issues at this point: - Analysis does NOT handle header "variables" at all (except keeping defined ones). - Sometimes windows 10 gives a "list - index out of bounds" error in particular when running a selected block from the editor or when running several pgm files within a pgm.

1 1

Screen backgrounds
by EpiData development and support 14 Jun '20

14 Jun '20

Dear Jens,                  Great work is being carried out of developing New Epidata Analysis. I was just exploring new release ver 1.7.99.1  One suggestion as request;                 We had relatively simple system of changing background to either black or white from pull down menu (Screen Font Option from window pull down menu ) in Classical Epidata Analysis.Tweaking Start.pgm is not everyone’s cup of tea. We work in the main output screen and Editor screen for long time. Dark (black) background are not stressful to the eyes while white background are. If possible please retain that feature  (of changing background to either black or white from pull down menu) in New Epidata Analysis also.With regards,Shavinder Singh 

1 0

New version
by EpiData development and support 12 Jun '20

12 Jun '20

Dear Jens Thank you. Are there any simple podcasts you could do perhaps 5 mins each explaining the new features? Much obliged Thambu David

1 1

Remote storage/access to data collected in EpiData
by EpiData development and support 03 Jun '20

03 Jun '20

Dear EpiData users, I have designed a relational data system for a nutritional cohort study in Nigeria and was wondering if anyone on this forum has any tips or recommendations for how best to establish a server/cloud based back up of the system so that the PI's can have remote access to do additional data quality assurance. More specifically, are there freely accessible or at least affordable secure servers or data storage facilities that you would recommend if neither ourselves or implementing partner have that facility in place? With kind regards, Edna Ogada

1 2

HELP ON EPPIDATA ENTRY
by EpiData development and support 10 May '20

10 May '20

Sir/Madam I am Ibrahim from Ghana. I face a challenge while developing a data base with epidata entry. I have different regions and each region has a number of different districts under it. I want to link the each region to the specific districts under it so that at data entry mode, when a particular region is selected, only the districts under it will appear at the districts field for selection. I will really appreciate a support from anyone on this issue. I don't mind calling for more information if a phone number is provided for me. Thank you

1 1

EpiData classic v3.1 in 2020? Under 64bit?
by EpiData development and support 07 May '20

07 May '20

Dear EpiData list members, Use EpiData classic v3.1 in 2020? (last release in 2008) YES - that's what I have just been doing, based on good experience a decade ago under Windows 7 pro 32bit, and on guidance found regarding EpiData v4.6 versus v3.1 on <http://www.epidata.dk/download.php> (see below). HOWEVER, one important feature no longer seemed to be working under Windows 7 pro 64bit: DEFINEd variables were only locally available (i.e. in the same record), but not GLOBALly (i.e. across RELATEd tables). Question: Is anything known about this problem, or even a work-around? This would be important, because: 1- EpiData v3.1 uses a parsimonious language easy to retain e.g. for researchers who only occasionally are in the situation to program themselves a data entry tool (but then typically like to get it working quickly w/o learning new software); 2- According to http://www.epidata.dk/download.php (accessed today), "In special situations or when a given function is not yet developed in Manager, EntryClient and Analysis you could need ... EpiData (Classic) Entry v3.1 (get it here) (only for programmed checks, before/after end blocks)". HOWEVER, MANY will find essential what can be done with BEFORE/AFTER FILE/RECORD/(field) blocks and apparently can not (yet?) be done with v4.6; 3- The feature "DEFINE variable GLOBAL" is necessary for multiple-level hierarchies and longitudinal databases (and it proved feasible and effective when I did it 10 years ago under Windows 7 pro 32bit, communicating only by email between North-America and sub-Saharan Africa). Thanks in advance Rolf

1 1

Defining Entry Rights EpiData Manager v4.6.0.2
by EpiData development and support 10 Mar '20

10 Mar '20

Hello, I am testing the EpiData system as a possible solution for data management for a nutrition cohort study. I have been able to set up a dataform and create groups and users using the Extended Access capabilities. I am however unable to define entry rights (CTRL E) on the my test data form, when I click on it using the point click option or control E absolutely nothing happens and the window I expect to show up as shown in the page 4 (Step 3) of attached PDF does not appear. Anyone else experienced this problem? Or am I missing something? Edna

1 5

Export to R from epidata
by EpiData development and support 11 Jan '20

11 Jan '20

Dear Jens Is it possible to export the data in epidata to R data? Perhaps it can but i am not sure how Please could you advice again, much appreciate your teams tremendous works new year greetings Thambu

1 1

Re: [EpiData-list] Export to R from epidata (EpiData development and support)
by EpiData development and support 11 Jan '20

11 Jan '20

I have exported from EpiData to R successfully. I used both Stata-files to preserve value labels and CSV files. Work fine. Kind Regards Henning Langen Stokmo Consultant (Nuclear Medicine) // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital Radiology Resident // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital PhD-student // Department of Nuclear Medicine, Oslo University Hospital | Oslo University Functional and Molecular Imaging Research Group ( https://www.ous-research.no/revheim/) ResearchGate: https://www.researchgate.net/profile/Henning_Langen_Stokmo On 11 January 2020 at 19:01:02, epidata-list-request(a)lists.umanitoba.ca ( epidata-list-request(a)lists.umanitoba.ca) wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Export to R from epidata (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 11 Jan 2020 04:51:46 +0000 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Subject: [EpiData-list] Export to R from epidata > Message-ID: <1578718346010.92724(a)cmcvellore.ac.in> > Content-Type: text/plain; charset="iso-8859-1" > > Dear Jens > Is it possible to export the data in epidata to R data? > Perhaps it can but i am not sure how > Please could you advice > again, much appreciate your teams tremendous works > new year greetings > Thambu > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 188, Issue 2 > ******************************************** >

1 0

new public release of Analysis, Manager and EntryClient released
by EpiData development and support 09 Jan '20

09 Jan '20

Dear all Yesterday we moved the "pre-release" version announced on December 31st 2019 to the official public download page. You may review the changes in the announcement on that day. So from now please install and use the updated versions. Some important errors have been identified in previous versions of EntryClient, so you should update. You may always test which version you have in the help menu "check version online". EpiData Analysis: 1.6.0.0 EpiData EntryClient: 4.6.0.2 EpiData Manager: 4.6.0.2 You might have to contact a central IT office if there are restrictions on installation and use of software. E.g. in our hospital I have to install from a local network drive while having a local administrator right for 30 minutes. We have not had any major issues reported - but a few minor aspects were identified in-house and fixed. E.g. A lacking !label abbreviation in a command and a change when importing csv files (string variables identified shorter than about 70 characters will now be string and not memo). Four observations that you should know of: 1 In analysis the command keys have been changed a bit. Check the "window" menu and notice that in the editor "ctrl+a" will run all commands and "ctrl+d" will execute the current command or a block if you have selected a block of commands. 2 If in new analysis you wish to create a memo or upper variable these are found as options to the "new variable" command as options (!memo !Upper): e.g. new variable txt string !memo. 3 If you are creating password protection in Analysis, this is done at the project level, not at the variable or dataset level. An example of this is shown below. 4 Currently I am doing many SPC (Statistical Process Control) graphs in my work at the hospital for hip fracture patient quality assurance. The way this is done is that we extract from the main hospital registration system a number of variables for all hip fracture patients. This is saved once a day on a central server as a csv file. Then I import this file with the new analysis and save it for table analysis in new analysis with many variables including time and memo variables (analysisNew.epx). But when I need to do the SPC graphs in Classic Analysis the epx file is not read, since Classic Analysis cannot read this type of variable. The remedy is to save a separate epx file (analysisClassic.epx) and use that for the graphs. Then I can just copy the graphs to a common folder and an html file shows the current results. The principle is an extension of a system developed with Norwegian Colleagues recording data for local municipal reporting from health centers (Thanks Vegard Högli). best wishes to all Jens Lauritsen EpiData Association Denmark new p !l:="test project" !size:=100; New project created: test project .... (output omitted - project with 1 dataset and 100 observations created) // to add a password encryption on all data: edit p !pw:="test"; // to verify this : list p; (output omitted - exect for info on "encryption"): Project Encryption: simple password (data only); // to remove a password: edit p !pw:=""; list p; (output omitted - exect for info on "encryption"): Project Encryption: none

1 0

New test versions and a warning on time and memo variables
by EpiData development and support 31 Dec '19

31 Dec '19

Dear all users of EpiData As quite many of you have already experienced, we have placed new test versions of EpiData EntryClient, Manager and Analysis on the http://epidata.dk/testing.php page on December 18th. The changes implemented in the test versions are documented in detail in the "change lists" found under each software on the "public release page, http://epidata.dk/download.php. Current public release versions are 4.6.0 for EntryClient and Manager and 1.4.0 for Analysis. As the the updated test versions are numbered: 4.6.0.2 for EntryClient and Manager and 1.6.0 for Analysis the major changes are in Analysis, where we are preparing for introduction of graphs and other lacking functionality. 1.6.0.0 of analysis * new command: Recode - very strong including formation of labels and other documentation * See Commands.html for details (press F1) of changes to options and the other new commands: keep and version * Variable list, History, Project overview and Command tree have been moved to seperate windows * Revised shortcuts and option names, e.g. unification of label as !l * !h option works for all commands and prints a simple list of supported options for a given command. * Table may be used for only one variable (with options for frequencies) And many Many minor bugfixes, mostly involving statistic calculation and special cases (eg. 0 data) If no major problems are identified the current "test versions" on the testing page will be "public release versions" in early January. Warning: As a side-effect of the new variable types (memo and time) variable, you should notice that if you want to read epx datafiles into classic analysis, then in the new analysis change those variables to another form, e.g. one or more string variables. At this end of our year I wish to express my thanks to all who supported EpiData Software over the years, including anonymous donors in the recent year, but also in particular the core group of Torsten Christiansen, Jamie Hockin and Hans L. Rieder. I wish all a happy new year and do hope that You will welcome the new and coming further structured development. Without all of your support and ideas the project could not continue. Best wishes Jens Lauritsen EpiData Association

1 0

NEUTRALZING A RECORD
by EpiData development and support 19 Dec '19

19 Dec '19

Dear all, How can you neutralize a record in a data set (duplicate or else)? In Epi-Info, you just needed to do F6 on the data sheet It should have a possibility with Epidata Thanks Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion _____ From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 18 Dec 2019 22:01:08 +0400 Subject: EpiData-list Digest, Vol 187, 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. 64-bit version / MacOS Catalina (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Dec 2019 07:11:00 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] 64-bit version / MacOS Catalina Message-ID: <trinity-9c54c698-20c3-48e6-a35f-c400c76e47b2-1576563060099@3c-app-webde-bap14> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: <http://lists.umanitoba.ca/pipermail/epidata-list/attachments/20191217/ca53a…> ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 187, Issue 1 ********************************************

1 2

News on software upgrades and EpiData software on Mac Catalina ?
by EpiData development and support 18 Dec '19

18 Dec '19

Dear all Within short time new "pre-public" versions of EpiData Software (Manager, EntryClient and Analysis) will appear on the testing.php page of EpiData. Apart from bug fixes the main upgrading is in Analysis. A dedicated mail will be posted once the updates are placed there. Another issue is that a few users have asked when EpiData software will be available for the MacOS Catalina. This is not to easy to answer since it seems that Apple has applied further special restrictions. In short we can guide you with this (unfortunated) message: Mac users of Epidata software should not upgrade their operating system to MacOS Catalina. Current Mac versions of Epidata will not run under this most recent version of MacOS because of restrictions Apple has put into the operating system. We are working on 64-bit Mac versions of the software that can be installed on MacOS Catalina and will advise users when these are ready. More news on this later when the tests are more extensive and time has permitted the development. Best wishes to all Jens Lauritsen EpiData Association Denmark

1 0

64-bit version / MacOS Catalina
by EpiData development and support 17 Dec '19

17 Dec '19

1 0

Unable to import .qes & .chk in iOS version?
by EpiData development and support 19 Nov '19

19 Nov '19

Dears, I work with local colleagues on TB mortality issues. I imported .rec from Windows version but can't for .chk and .qes Is this "normal", as mentionned in last thread related to iOS version of Epidata or do I miss something ? Thanks ! Gaël Claquin Tél Bénin: +229 99 00 37 17

1 1

Update of EpiData to work with MacOS Catalina
by EpiData development and support 18 Oct '19

18 Oct '19

Hi, When is an update for EpiData Manager and - Entry Client planned for it to work with MacOS Catalina? Current versions are incompatible. Kind Regards Henning Langen Stokmo Consultant (Nuclear Medicine) // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital Radiology Resident // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital PhD-student // Department of Nuclear Medicine, Oslo University Hospital | Oslo University Functional and Molecular Imaging Research Group ( https://www.ous-research.no/revheim/) ResearchGate: https://www.researchgate.net/profile/Henning_Langen_Stokmo

1 1

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 02 Sep '19

02 Sep '19

Dear, Hans Thank you for this solution, but my goal is not to use R for the statistics. I will be using Python for all my statistics and graphs. The error with the missing values is not a dealbraker as I can recode the values in Python. But I would rather not have to. Kind Regards Henning Langen Stokmo Twitter: @helangen Keybase: @helangen PGP fingerprint: 9C50 5F2D BDB7 F13A

1 0

Re: [EpiData-list] Missing data values when exporting to Stata (EpiData development and support)
by EpiData development and support 27 Aug '19

27 Aug '19

Hi, Exporting the .dta file from Analysis throws the same error in Python as the Stata 14-file from EpiData Manager. Unsure if this is a Python error or Stata-export error. I have used all versions earlier in R so probably something to do with Python Pandas read_stata-function. Kind Regards Henning

1 1

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 26 Aug '19

26 Aug '19

Hi, again I tried exporting to Stata v13 and v14 from EpiData Manager (same version av before), but Python throws an error when reading both files. Unsure what the errors are. I can’t find where to export in EpiData Analysis v1.4.0.0. I tried “File -> Save” as .dta, but the file is not a Stata-file. I tried looking in the documentation for an export command, but can’t find one. What am I missing? Kind Regards Henning

1 1

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 23 Aug '19

23 Aug '19

I will download the Analysis app and try that. I will also try to export to Stata 14 as the Stata version does not matter with regards to Python. Thanks Kind Regards Henning Langen Stokmo Consultant (Nuclear Medicine) // Department of Nuclear Medicine, Oslo University Hospital Radiology Resident // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital PhD-student // Department of Nuclear Medicine, Oslo University Hospital | Oslo University Functional and Molecular Imaging Research Group (https://www.ous-research.no/revheim/) ResearchGate: https://www.researchgate.net/profile/Henning_Langen_Stokmo Sent from Canary (https://canarymail.io/) > On Friday, Aug 23, 2019 at 7:00 PM, <epidata-list-request(a)lists.umanitoba.ca (mailto:epidata-list-request@lists.umanitoba.ca)> wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Re: Missing data values when exporting to Stata > (EpiData development and support) > 2. Re: Missing data values when exporting to Stata > (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 22 Aug 2019 23:40:02 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Missing data values when exporting to > Stata > Message-ID: <041A2CAB-A14A-4F26-8389-3410D8489A76(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > Sorry for not giving any information about the versions and system I use. > > I use EpiData Manager v4.4.2.1 on a MacBook Pro 13? (2018) running Mojave 10.14.6 to export. The exported files are to Stata v12. > The .dta files are opened in Python v3.6.8 via PyCharm IDE CE 2019.2 and imported to a Panda dataframe with the command ?pd.read_stata(<filename>). The empty lines in the Stata-file gets correctly set as ?NaN? in Pandas, but the value label for the missing category is set to ?100.0? instead of ?NaN? as I expect it should be after coding this in EpiData. > > Kind Regards > Henning L. Stokmo > Phd-Student, Oslo University Hospital > > > > On 22 Aug 2019, at 19:00, epidata-list-request(a)lists.umanitoba.ca wrote: > > > > Send EpiData-list mailing list submissions to > > epidata-list(a)lists.umanitoba.ca > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > or, via email, send a message with subject or body 'help' to > > epidata-list-request(a)lists.umanitoba.ca > > > > You can reach the person managing the list at > > epidata-list-owner(a)lists.umanitoba.ca > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of EpiData-list digest..." > > > > > > EpiData-list mailing list > > ___________________________________ > > > > Today's Topics: > > > > 1. Re: Missing data values when exporting to Stata > > (EpiData development and support) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Wed, 21 Aug 2019 21:43:41 +0200 > > From: EpiData development and support > > <epidata-list(a)lists.umanitoba.ca> > > To: epidata-list(a)lists.umanitoba.ca > > Subject: Re: [EpiData-list] Missing data values when exporting to > > Stata > > Message-ID: <CE3439F1-72F7-4F8A-90F1-313DF876BD64(a)epidata.dk> > > Content-Type: text/plain; charset=utf-8 > > > > As I remember the Stata value should be > > .a > > But please specify which version of Stata and if you are using Manager export or the new analysis, which may directly save the file in Stata format. > > > > Best wishes > > Jens Lauritsen > > EpiData Association > > Denmark > > > > Den 21. august 2019 14.04.31 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> skrev: > > > Hi, > > > > > > I have some missing data that is encoded as ?9? in the database and in > > > the value label list it is flagged as missing. When exporting to CSV > > > the value is obviously set as ?9? as expected. > > > > > > When I export it as Stata I assume this value ?9? gets encoded to > > > Stata? definition of a missing value, but when I read the data in > > > Python with the ?pd.read_stata?-function it defines the category value > > > ?9? as 100.0 and not as missing data (NaN) like the blanks in EpiData. > > > > > > Eksample > > > One column has 80 values. 19 of these are encoded as ?9? (missing), 58 > > > of these are blank, and 3 are coded as ?1? (Yes) in EpiData. After > > > exporting to Stata and reading in Python I get > > > > > > 19 values in category ?100? > > > 3 values in category ?Yes? > > > 58 values NaN (i.e. missing) > > > > > > Why aren?t the ?9? category correctly coded as missing when exporting > > > to Stata, or am I missing something here? > > > > > > Kind Regards > > > Henning > > > _______________________________________________ > > > 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. > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 183, Issue 2 > > ******************************************** > > > > ------------------------------ > > Message: 2 > Date: Fri, 23 Aug 2019 11:21:07 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Missing data values when exporting to > Stata > Message-ID: <C7C018D0-96BA-45C8-8AFF-7F9FC92D31AF(a)epidata.dk> > Content-Type: text/plain; charset=utf-8 > > You spotted an error in export to Stata 12. > > If you export to Stata 14 it works as desired. > > A easier way is to use the new Analysis for export, Analysis has options for choice of Stata version a d works on a Mac. > > Can the python use Stata 14? > > Best wishes > Jens Lauritsen > EpiData Association > Denmark > > > > > Den 22. august 2019 23.40.02 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> skrev: > > Sorry for not giving any information about the versions and system I > > use. > > > > I use EpiData Manager v4.4.2.1 on a MacBook Pro 13? (2018) running > > Mojave 10.14.6 to export. The exported files are to Stata v12. > > The .dta files are opened in Python v3.6.8 via PyCharm IDE CE 2019.2 > > and imported to a Panda dataframe with the command > > ?pd.read_stata(<filename>). The empty lines in the Stata-file gets > > correctly set as ?NaN? in Pandas, but the value label for the missing > > category is set to ?100.0? instead of ?NaN? as I expect it should be > > after coding this in EpiData. > > > > Kind Regards > > Henning L. Stokmo > > Phd-Student, Oslo University Hospital > > > > > > > On 22 Aug 2019, at 19:00, epidata-list-request(a)lists.umanitoba.ca > > wrote: > > > > > > Send EpiData-list mailing list submissions to > > > epidata-list(a)lists.umanitoba.ca > > > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > or, via email, send a message with subject or body 'help' to > > > epidata-list-request(a)lists.umanitoba.ca > > > > > > You can reach the person managing the list at > > > epidata-list-owner(a)lists.umanitoba.ca > > > > > > When replying, please edit your Subject line so it is more specific > > > than "Re: Contents of EpiData-list digest..." > > > > > > > > > EpiData-list mailing list > > > ___________________________________ > > > > > > Today's Topics: > > > > > > 1. Re: Missing data values when exporting to Stata > > > (EpiData development and support) > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Wed, 21 Aug 2019 21:43:41 +0200 > > > From: EpiData development and support > > > <epidata-list(a)lists.umanitoba.ca> > > > To: epidata-list(a)lists.umanitoba.ca > > > Subject: Re: [EpiData-list] Missing data values when exporting to > > > Stata > > > Message-ID: <CE3439F1-72F7-4F8A-90F1-313DF876BD64(a)epidata.dk> > > > Content-Type: text/plain; charset=utf-8 > > > > > > As I remember the Stata value should be > > > .a > > > But please specify which version of Stata and if you are using > > Manager export or the new analysis, which may directly save the file in > > Stata format. > > > > > > Best wishes > > > Jens Lauritsen > > > EpiData Association > > > Denmark > > > > > > Den 21. august 2019 14.04.31 CEST, EpiData development and support > > <epidata-list(a)lists.umanitoba.ca> skrev: > > > > Hi, > > > > > > > > I have some missing data that is encoded as ?9? in the database and > > in > > > > the value label list it is flagged as missing. When exporting to CSV > > > > the value is obviously set as ?9? as expected. > > > > > > > > When I export it as Stata I assume this value ?9? gets encoded to > > > > Stata? definition of a missing value, but when I read the data in > > > > Python with the ?pd.read_stata?-function it defines the category > > value > > > > ?9? as 100.0 and not as missing data (NaN) like the blanks in > > EpiData. > > > > > > > > Eksample > > > > One column has 80 values. 19 of these are encoded as ?9? (missing), > > 58 > > > > of these are blank, and 3 are coded as ?1? (Yes) in EpiData. After > > > > exporting to Stata and reading in Python I get > > > > > > > > 19 values in category ?100? > > > > 3 values in category ?Yes? > > > > 58 values NaN (i.e. missing) > > > > > > > > Why aren?t the ?9? category correctly coded as missing when > > exporting > > > > to Stata, or am I missing something here? > > > > > > > > Kind Regards > > > > Henning > > > > _______________________________________________ > > > > 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. > > > > > > ------------------------------ > > > > > > ________________________________________ > > > EpiData-list(a)lists.umanitoba.ca > > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > > > > End of EpiData-list Digest, Vol 183, Issue 2 > > > ******************************************** > > > > _______________________________________________ > > 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. > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 183, Issue 3 > ********************************************

1 0

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 23 Aug '19

23 Aug '19

Sorry for not giving any information about the versions and system I use. I use EpiData Manager v4.4.2.1 on a MacBook Pro 13” (2018) running Mojave 10.14.6 to export. The exported files are to Stata v12. The .dta files are opened in Python v3.6.8 via PyCharm IDE CE 2019.2 and imported to a Panda dataframe with the command “pd.read_stata(<filename>). The empty lines in the Stata-file gets correctly set as “NaN” in Pandas, but the value label for the missing category is set to “100.0” instead of “NaN” as I expect it should be after coding this in EpiData. Kind Regards Henning L. Stokmo Phd-Student, Oslo University Hospital > On 22 Aug 2019, at 19:00, epidata-list-request(a)lists.umanitoba.ca wrote: > > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Re: Missing data values when exporting to Stata > (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 21 Aug 2019 21:43:41 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Missing data values when exporting to > Stata > Message-ID: <CE3439F1-72F7-4F8A-90F1-313DF876BD64(a)epidata.dk> > Content-Type: text/plain; charset=utf-8 > > As I remember the Stata value should be > .a > But please specify which version of Stata and if you are using Manager export or the new analysis, which may directly save the file in Stata format. > > Best wishes > Jens Lauritsen > EpiData Association > Denmark > > Den 21. august 2019 14.04.31 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> skrev: >> Hi, >> >> I have some missing data that is encoded as ?9? in the database and in >> the value label list it is flagged as missing. When exporting to CSV >> the value is obviously set as ?9? as expected. >> >> When I export it as Stata I assume this value ?9? gets encoded to >> Stata? definition of a missing value, but when I read the data in >> Python with the ?pd.read_stata?-function it defines the category value >> ?9? as 100.0 and not as missing data (NaN) like the blanks in EpiData. >> >> Eksample >> One column has 80 values. 19 of these are encoded as ?9? (missing), 58 >> of these are blank, and 3 are coded as ?1? (Yes) in EpiData. After >> exporting to Stata and reading in Python I get >> >> 19 values in category ?100? >> 3 values in category ?Yes? >> 58 values NaN (i.e. missing) >> >> Why aren?t the ?9? category correctly coded as missing when exporting >> to Stata, or am I missing something here? >> >> Kind Regards >> Henning >> _______________________________________________ >> 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. > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 183, Issue 2 > ********************************************

1 1

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 21 Aug '19

21 Aug '19

Hi, I have some missing data that is encoded as ‘9’ in the database and in the value label list it is flagged as missing. When exporting to CSV the value is obviously set as ‘9’ as expected. When I export it as Stata I assume this value ‘9’ gets encoded to Stata’ definition of a missing value, but when I read the data in Python with the ‘pd.read_stata’-function it defines the category value ‘9’ as 100.0 and not as missing data (NaN) like the blanks in EpiData. Eksample One column has 80 values. 19 of these are encoded as ‘9’ (missing), 58 of these are blank, and 3 are coded as ‘1’ (Yes) in EpiData. After exporting to Stata and reading in Python I get 19 values in category ‘100’ 3 values in category ‘Yes’ 58 values NaN (i.e. missing) Why aren’t the ‘9’ category correctly coded as missing when exporting to Stata, or am I missing something here? Kind Regards Henning

1 1

New versions available as pre-release. (Manager V4.6.0.0 , Entryclient V4.6.0.0, Analysis V1.4.0.0)
by EpiData development and support 16 May '19

16 May '19

Dear users New versions have been placed as "pre-release" on: http://epidata.dk/testing.php (Manager V4.6.0.0 , Entryclient V4.6.0.0, Analysis V1.4.0.0) You will find new commands e.g. compact tables in analysis and bugs removed. The major changes are in analysis. All changes will be documented in a few days - and at that point a new mail will be sent to all on this list. Please remember, that as long as the software is placed on the testing.php page DO NOT use on routine data. Make a copy of your data and test function with the new software. Best wishes Torsten Bonde Christiansen and Jens Lauritsen EpiData Association Denmark

1 2

Re: [EpiData-list] EpiData-list Digest, Vol 181, Issue 7
by EpiData development and support 29 Apr '19

29 Apr '19

THANK YOUUUU!!!!!!! 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: Sun, 28 Apr 2019 21:00:14 +0400 Subject: EpiData-list Digest, Vol 181, Issue 7 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Re: HELP! HOW DO WE CREATE A SMALLEST DATAFIL.REC? (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 27 Apr 2019 20:40:13 +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] HELP! HOW DO WE CREATE A SMALLEST DATAFIL.REC? Message-ID: <5c7a4cb2-0714-13d8-5b23-bfbbb9f03ca4(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Pierre-Yves: Explicitly, you would have - example - a data set that you read and manipulate in EpiData Analysis [classic] as follows: cls close read "original.rec" * Contains variables VAR01, VAR02, .... , VAR19, VAR20 * Has 1200 records * 1) Reduce number of variables * => keep only some variables to your choice: keep var01 var03 var05 var10 var11 var16 * if the converse gives less to write, use: * drop var02 var04 var06 var07 etc * 2) Reduce number of records [assuming sorted by your preference] * Select only the first 500 records: select recnumber<501 * Save the new data set: savedata "reduced_set.rec" /replace * Use the new set: cls close read "reduced_set.rec" * All this is in the superb help file which you get with F1 in EpiData Analysis V2.2.3.187 Best regards, Hans On Apr 26, 2019, at 01:55, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: >> Dear all, >> >> I need to create a smallest datafile to work on it for logistic regression >> In EPIINFO6 it was very easy. the command was: >> >> >> route c:\data\preclog.rec >> >> write recfile chgt multi capot diaf foam withdraw cream depo rythm pil iud \ >> >> precl \ >> >> >> >> For epidata it is logopen "c:\data\preclog.rec" >> >> but after, write recfile does nor work in Epidata >> >> What is the process please? >> >> Thanks >> >> Dr Pierre-Yves Robillard -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 181, Issue 7 ********************************************

1 0

HELP! HOW DO WE CREATE A SMALLEST DATAFIL.REC?
by EpiData development and support 27 Apr '19

27 Apr '19

Dear all, I need to create a smallest datafile to work on it for logistic regression In EPIINFO6 it was very easy. the command was: route c:\data\preclog.rec write recfile chgt multi capot diaf foam withdraw cream depo rythm pil iud \ precl \ For epidata it is logopen "c:\data\preclog.rec" but after, write recfile does nor work in Epidata What is the process please? Thanks Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion _____ From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Fri, 12 Apr 2019 21:00:30 +0400 Subject: EpiData-list Digest, Vol 181, Issue 4 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Re: Problems appending files (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Apr 2019 19:09:30 +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] Problems appending files Message-ID: <1c40e7a2-df66-7ec2-3a02-ec373ce19e14(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Omar Bautista: In the new analysis, this would be the grammar if you would wish to append the four files a.epx, b.epx, c.epx, d.epx and to sa ve them to a new file abcd.epx that you can then use henceforth: cls; read "a.epx"; append !fn := "b.epx"; append !fn := "c.epx"; append !fn := "d.epx"; save "abcd.epx" !replace; Best regards, Hans On 10-Apr-19 20:20, EpiData development and support wrote: > ?Thanks! Very well explained. > > I'm now exporting the data from EpiData using STATA format, on > separate files. And then handling some merge-append functions within > R. I will record the commands to run them as a little R script to make > it more automatic. At least, this is working. But it would be great, > in a near future, to learn how to solve this automatic id problem > within EpiData. > > Cheers, -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 181, Issue 4 ********************************************

1 3

Problems appending files
by EpiData development and support 11 Apr '19

11 Apr '19

Hello Jens and EpiData users! I trying to append some EpiData files. But I'm having a problem... I tried the same steps that are illustrated in this video: https://www.youtube.com/watch?v=BY6nZ0-k2Bs But I'm having an error that is shown in the attached file. Please, help me! -- Omar Bautista González Colaborador en autogestión comunitaria desde República Dominicana Docente de la Universidad Autónoma de Santo Domingo

1 7

Thank you for answer to: Is there a Road Map for the test version (V4.4.2.1) and other questions
by EpiData development and support 21 Mar '19

21 Mar '19

Dear Jens Lauritsen, I just want to thank you for your answers to all of our questions. We really appreciate it! Best regards, Leticia Grize Leticia Grize PhD Biostatistics Unit Department of Epidemiology and Public Health Swiss Tropical and Public Health Institute Office address: Eulerstrasse 77, Basel Phone: +41-(0)61-284-87-12 Fax: +41-(0)61-284-81-01 Email: leticia.grize(a)swisstph.ch Postal address: Swiss TPH / P.O. Box / CH-4002 Basel / Switzerland STPH website: http://www.Swisstph.ch -------------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately by reply e-mail and delete this message from your system. --------------------------------------------------------------------------

1 0

Is there a Road Map for the test version (V4.4.2.1) and other questions
by EpiData development and support 20 Mar '19

20 Mar '19

Dear EpiData Association team / epidata-list, I work at a non-profit organization conducting studies in different parts of the world. Several of these studies at our institute are still using EpiData v3.1. At the moment all collaborators of our institute are being migrated from Windows 7 to Windows 10. Our IT department has included EpiData Manager V4.4.2.1 in the software package being installed in our new computers since it is the 'newest' version (a test version but not the current version!) . Since several studies are in the process of entering data using V3.1 we encountered the fact that the entry mask does not work on the newer version (as expected). Using V4.4.2.1 means for us the re-design of the masks, which we have tried but encounter difficulties with the part of the '.chk' e.g no conditional jumps can be applied and calculations can be cumbersome, etc... We would rather work with V3.1 but out IT department would like to know the following to go back to EpiData V3.1: 1.) Which is your 'Road Map' for the development of V4.4.2.1 from 'test' to a 'current' version? Would you have an estimate of the date of availability of the V4.4.2.1 as a current version? 2.) They asked if V3.1 was designed for Win 10, but I rather ask: are there known errors in the use of V3.1 when running under Win10? 3.) Would you have 'security' updates for V3.1? Since it is an old software, the IT team is refusing to install V3.1 because if could introduce 'insecurity' in the Institute's system. - If we were forced to use the test version, is there an easy way to implement the check files from V3.1? - Would you have a manual for the users? We are in the middle of several studies going on and we would like to have reassurance that things are done properly. I would really appreciate your help! Best regards and thank you, Leticia Grize Leticia Grize PhD Biostatistics Unit Department of Epidemiology and Public Health Swiss Tropical and Public Health Institute Office address: Eulerstrasse 77, Basel Phone: +41-(0)61-284-87-12 Fax: +41-(0)61-284-81-01 Email: leticia.grize(a)swisstph.ch Postal address: Swiss TPH / P.O. Box / CH-4002 Basel / Switzerland STPH website: http://www.Swisstph.ch -------------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately by reply e-mail and delete this message from your system. --------------------------------------------------------------------------

1 1

RE - A question on size of downloads - what is acceptable for EpiData Software ?
by EpiData development and support 11 Feb '19

11 Feb '19

 Dear Jens,All in one" bundle is suitable and time saving in Windows software. Classical EpidataEntry and Analysis are still popular and stable. Please retain these as long aspossible. It will require time and effort to preserve the range of functionalities of  Classical Epidata Entry and Analysis in the new versions as well as add new features.Keep up this good contribution  for public health.With regards,Dr. Shavinder Singh  

1 0

A question on size of downloads - what is acceptable for EpiData Software ?
by EpiData development and support 08 Feb '19

08 Feb '19

Please consider if a change in download principles is acceptable. All maintained software could be released in two forms: 1 As an installation "all in one" bundle for (4 different bundles): a1: Linux 32 bit (Manager, EntryClient, New Analysis) b1: Linux 64 bit (Manager, EntryClient, New Analysis) c1: Mac OS (Standard Intel) : (Manager, EntryClient, New Analysis) d1: Windows (common routine for 32 and 64 bit): (Manager, EntryClient, New Analysis, Analysis Classic) 2 As zipped packages with all software in one zip file (4 different bundles): a2: Linux 32 bit (Manager, EntryClient, New Analysis) b2: Linux 64 bit (Manager, EntryClient, New Analysis) c2: Mac OS (Standard Intel) : (Manager, EntryClient, New Analysis) d2: Windows (all in one for 32 and 64 bit): (Manager, EntryClient, New Analysis, Analysis Classic) The download size will be up to about 10 Mb per package/bundle. With the above we add Analysis Classic to the current windows packages. The reason is that it will take quite a while before remaining functionality (graphs, survival analysis etc) will be added to the rewritten Analysis. Analysis Classic will remain as it is in the latest version (v2.2 rel 3, build 187). The webpage will also provide access to the current Classic Entry v3.1. Please comment here or by mail to info (at) epidata.dk Best wishes Jens Lauritsen EpiData Association Denmark

1 0

Is there a way to get an older version of the software ?
by EpiData development and support 30 Jan '19

30 Jan '19

We do NOT recommend that users continue with old versions of EntryClient, Manager og Analysis. During development the following occurs: a. We fix bugs which have been identified. b. Functionality is added according to the development plan c. Sometimes fixing a bug or adding new functionality extends the structure of the project epx files. The new version will read ALL old version and update the project. But old versions cannot read the updated project file. In experimental and development versions found on the test page we might experiment with new structure of the project files. THEREFORE NEVER use your production files with test versions. ! Since bugs are resolved in new versions always specify precisely which version and which operating system (windows, linux, mac) your are using when errors occur. Therefore the help menu has a function "copy version info", which may then easily be added to a mail to this list. Example: EpiData Manager: (2019/01/30 - 11:30:31) Program Version: 4.4.2.1 r1493 Core version: 4.4.0.0 r1490 FPC Version: 3.0.0 Platform: x86_64-Linux In the help menu "Check Version Online" will compare and report against current public and experimental versions if you have internet access. An issue may arise if a workplace (e.g. a hospital) does not allow the users to add new versions. For instance there was a report that one health region only updates software once every six months. On your own responsibility you may then get the old version again (which some users wished for home use), by manually entering in a browser the complete file name with the old version numbers. e.g. to get version 4.2.0.0 of Manager for Mac you would like to get this file: setup.epidatamanager.4.2.0.0.i386.darwin.dmg You add that name to the archive folder name: www.epidata.dk/downloads/OldFiles/ and specify it with an http:// in front. But a much better option is to always work with the latest version. A resolved bug could for instance solving a "save data problem". All web pages for the EpiData project will be replaced when time permits this. Once that is done we will have a policy of access to older versions. best wishes Jens Lauritsen EpiData Association

1 0

Dialogue Window "Define Entry Rights" does not appear
by EpiData development and support 30 Jan '19

30 Jan '19

Hello List, hello Mr. Lauritzen, in a subproject a local Admin is defining Groups and Users. After that she wants to define the Entry Rights, but the window doesn't appear. She tested it on 4 different PC (WIN 10/newest EpiData Version) with no success. With me on my Installation it works (Win 10 and newest ED too). I wonder how I could help her. Are there some tipps how to find out what kind of problem exists? Perhaps a workaround? Kind regards Michael

1 0

Bug in 64-bit Linux package for epidataanalysis
by EpiData development and support 14 Jan '19

14 Jan '19

Hello, there is a bug in the 64-bit Linux package for `epidataanalysis` that causes a failure when trying to launch the program via the application menu. It's a missing letter "a" in the `epidataanalysis.desktop` file. I've attached a patch. Kind regards Daniel -- Give a man a fish, and you feed him for a day. Teach a man to fish, and you feed him for a lifetime. www.gemeinsam-gegen-armut.org

1 0

version trouble
by EpiData development and support 04 Jan '19

04 Jan '19

Hi, I am new to Epidata. I have spent many hours in writing forms for my study in the Epidata version 4.4 downloaded recently. When now testing it on my hospital where I will use it for registering data it tursn out that the hospital is running an earlier version 4.2 in which I cannot open the file from 4.4. My hospital will wait til this summer to install a new version. Does anyone have any suggestions on how to solve this without having to construct it all over again? Thanks, Ulf Ljungblad, Norway

1 2