EpiData-list October 2017

epidata-list@lists.umanitoba.ca

1 participants
6 discussions

Re: [EpiData-list] Error in exporting .epx file to .dta

by EpiData development and support

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

5 years, 11 months

Error in exporting .epx file to .dta

by EpiData development and support

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

5 years, 11 months

Re: [EpiData-list] EpiData-list Digest, Vol 164, Issue 2

by EpiData development and support

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

5 years, 11 months

EpiData & Windows 10

by EpiData development and support

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

5 years, 11 months

New (experimental) version of rewritten Analysis 0.8.4.0

by EpiData development and support

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

5 years, 11 months

Difficulty in Importing Relational database of Classical epidata into Epidata Manager

by EpiData development and support

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

5 years, 11 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list October 2017