- EpiData-list - University of Manitoba Mailing Lists

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 14 Jan '21

14 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