- EpiData-list - University of Manitoba Mailing Lists

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 05 Aug '22

05 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