- EpiData-list - University of Manitoba Mailing Lists

Problem with change of name of valuelabel and valuelabels for type
by EpiData development and support 10 Nov '16

10 Nov '16

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

1 0

If-then skip function
by EpiData development and support 10 Nov '16

10 Nov '16

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

1 1

An issue of lower vs. UPPER case naming, terminology change warning and other plans of implementation
by EpiData development and support 02 Nov '16

02 Nov '16

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

1 0

New Manager Version (2.0.13.64) due to blocking bug -
by EpiData development and support 02 Nov '16

02 Nov '16

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

1 0

Minor fix to EpiData Manager
by EpiData development and support 01 Nov '16

01 Nov '16

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

1 0

Is there any file size limit in Epidata Analysis 2.2.2.183
by EpiData development and support 28 Oct '16

28 Oct '16

Dear Jens,                       Thanks for the quick response. It was heartening to know that Epidata development is progressing. Keep up this good work for the public health cause.Regarding the record limit issue;I tried correcting the wrong dates and that did not help. I tried reading the file without date variables, still the same problem persisted.  However, I extracted 3 variables of interest and wrote a separate file of 4.9 Mb. Original file size is 9.2 Mb. This extracted small file was easily read by Epidata Analysis.Just a small point about Epidata Analysis.If there is adequate RAM (4 Gb) and hard disk space (1 Tb) on the PC, does Epidata Analysis have any file size limitation? Can size of the rec file be the problem here?With regards,Dr. Shavinder

1 0

Status and strategic decisions for development of EpiData Software
by EpiData development and support 28 Oct '16

28 Oct '16

For all users of EpiData Software I am writing today to explain some changes you may notice in future list postings from me. Due to regulatory demands in Denmark there is a need to formalize some of the development strategies, including how the EpiData list is used to support development. Some of the emails from me will have a form where statements made are understood as accepted unless further debate gives reason for changes. Any comment or indication of opinion is welcomed at any time. If no major comments are given within 5 days the paragraphs will be formally understood as accepted by the user base. I want to reassure you that there will be NO information given to anyone regarding who is on the discussion list, anything you say here or otherwise express in relation to development or preference in strategy. In the formal constitution of the Association this is formulated as stated below my signature. There will be a continued division of decision making in EpiData development in which the roles are: a. this EpiData-List: discuss principles, decisions, practical implementation, bug removal, questions on specific aspects etc. b. the core group: Definite strategic decisions including those with financial implications are placed here. The core group is comprised of those giving major input to development. Names are indicated in the section "Particularly Active" in the "Friends of EpiData" section on the credit page of the main webpage. c. specific implementation: These are ultimately made by me and Torsten Christiansen, who is assuring sound software principles. At the final level I am legally responsible for all decisions taken, but it is important that the whole user base is informed of the principles. Best regards to all Jens Lauritsen, MD, Phd. Initiator and Coordinator EpiData Association, Denmark ------------------------------------------------------------------------------------------------------------------------ Formal extract: Decisions on dissemination and development strategies is taken in an open discussion on the EpiData list, which is open for all users. Specific power users from the user base will be added to a group of core decision makers (the board), who can sign account balance’s and grant signing rights to one or more persons in the core group in relation to payments and salaries. The board is guided in the larger decisions by the ”Friends of EpiData” – an international collection of experienced persons within EpiDemiology, Public Health and Community Medicine supporting the aim of the EpiData Association. Updated lists of names are shown at www.epidata.dk/credit.htm. To ensure broad support in development decisions and strategies all major directional plans will be made publicly available on the EpiData discussion group list, which is open to all users. Such plans will be clearly formulated as such with proper timelimits for commenting and possible changes.

1 0

Is there any record limit in Epidata Analysis 2.2.2 (ver 183)
by EpiData development and support 28 Oct '16

28 Oct '16

Dear  Jens and Epidata Team,                                                       There ia prolonged silence on the list. I hope everything is fine and development is progressing.I have a unique concern. There is a flat file of classical Epidata Entry 3.1. The number of records is 93425. I am using Epidata Analysis 2.2.2 (ver 183).  Epidata Analysis does not read this file.Only message I get is “Loading data D:\EpiData\PH\D.REC, please wait...The indicator below is green. When I convert this “rec file”  to  “dbase file” using classical Epidata Entry 3.1,  the converted dbase file is easily read by Epidata Analysis. (However it adds decimal and two zeroes to the numeric data.My question is; Is there any record limit in Epidata Analysis 2.2.2 (ver 183)?With regards,Dr Shavinder 

1 1

Serious bug identified (only in a special type of projects with related dataforms) - update to new EntryClient
by EpiData development and support 24 Aug '16

24 Aug '16

Yesterday - We have identified a bug which have created incorrect data in a certain situation . therefore - an updated EntryClient version has been uploaded (EntryClient 2.0.9.25) today. The change is due to a serious bug in RELATED dataforms. With single dataforms there is NO problem. For most projects with related dataforms the situation is: 1 New observations are added with unique key fields (say "project id"+"date of visit") 2 key values are never changed. Then you have NO problem and your data are correct. But if a project has: a. related set of dataforms (main + one or more child dataforms) b. the key contains MORE than ONE field. c. you have edited (changed) values in one of the key fields after entering records "above" a child form d. child records for more than one observation have the same value in a key field which was edited at a higher level AND you can say YES to all of a+b+c+d there is reason to check your data. If there is doubt for a given project you are welcome to contact us by mail at "info at epidata.dk" for further advice. The situation arose when we changed a flat file structure to a related structure. We split the flat file to four subfiles and imported the data into a related structure. As a first step gave one of three fields of the key the same value, whereas obviously the combination of three fields was unique. Following import this was correct, but after changing all 1000 records we realized the problem. We apologize very much for the inconvenience this might incur, but do hope that you will continue to report any strange behaviour. Only by meticulous observation can we find such unfortunate bugs. regards Jens Lauritsen EpiData Association, Denmark

1 0

AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 29/08/2016)
by EpiData development and support 17 Aug '16

17 Aug '16

I am out of the office until 29/08/2016. Please contact Tracey McCole on 071 9852900 if you require further assistance, otherwise I will attend to your email when I return Note: This is an automated response to your message "EpiData-list Digest, Vol 152, Issue 2" sent on 17/08/2016 18:00:19. This is the only notification you will receive while this person is away. *************************************************************************** "Tá an fhaisnéis sa ríomhphost seo (ceangaltáin san áireamh) faoi rún. Baineann sé leis an té ar seoladh chuige amháin agus tá sé ar intinn go bhfaighfidh siadsan amháin é agus gurb iadsan amháin a dhéanfaidh breithniú air. Más rud é nach tusa an duine ar leis é, tá cosc iomlán ar aon fhaisnéis atá ann, a úsáid, a chraobhscaoileadh, a scaipeadh, a nochtadh, a fhoilsiú, ná a chóipeáil . Seains gurb iad tuairimí pearsanta an údar atá san ríomhphost agus nach tuairimí FSS iad. Má fuair tú an ríomhphost seo trí dhearmad, bheadh muid buíoch dá gcuirfeá in iúil don.Deasc Seirbhísí ECT ar an nguthán ag +353 71 9820555 nó ar an ríomhphost chuig ICT.Helpdesk(a)hse.ie agus ansin glan an ríomhphost seo ded' chóras." *************************************************************************** "Information in this email (including attachments) is confidential. It is intended for receipt and consideration only by the intended recipient.If you are not an addressee or intended recipient, any use, dissemination,distribution, disclosure, publication or copying of information contained in this email is strictly prohibited..Opinions expressed in this email may be personal to the author and are not necessarily the opinions of the HSE. If this email has been received by you in error we would be grateful if you could immediately notify the ICT Service Desk by telephone at +353 71 9820555 or by email to ICT.Helpdesk(a)hse.ie and thereafter delete this e-mail from your system" ***************************************************************************

1 0