EpiData-list November 2016

epidata-list@lists.umanitoba.ca

1 participants
9 discussions

Re: [EpiData-list] EpiDatamanager version with SAS support (EpiData-list Digest, Vol 154, Issue 9)

by EpiData development and support

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

7 years, 5 months

Looking for EpiDatamanager version with SAS support

by EpiData development and support

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

7 years, 5 months

Epidata in mobile devices

by EpiData development and support

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

7 years, 5 months

problem with XML version 4

by EpiData development and support

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

7 years, 5 months

Problem with change of name of valuelabel and valuelabels for type

by EpiData development and support

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

7 years, 5 months

If-then skip function

by EpiData development and support

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

7 years, 5 months

An issue of lower vs. UPPER case naming, terminology change warning and other plans of implementation

by EpiData development and support

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

7 years, 6 months

New Manager Version (2.0.13.64) due to blocking bug -

by EpiData development and support

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

7 years, 6 months

Minor fix to EpiData Manager

by EpiData development and support

Dear List. A new version of EpiData Manager (2.0.13.63) has been released for public use. The new version contains a fix only related to linux, where moving fields no longer worked correctly. Hence if you are using EpiData Manager on Windows or Mac, there is no need for updating if you have the previous version (2.0.12.62) installed. The updated version can as always be downloaded from our website: http://www.epidata.dk/download.php <http://epidata.dk/download.php> Kind regards Torsten Bonde Christiansen EpiData Association

7 years, 6 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list November 2016