EpiData-list

epidata-list@lists.umanitoba.ca

1828 discussions

Analysing Epidata rec file in epi 2002

by epidata-list＠lists.umanitoba.ca

Hello there list users I have a problem when I use Epi2002 to analyse data created through epidata. The problem is that the command freq * causes an error that means you have to close down. The same files are OK to analyse in Epi 6.04 and there is no problem with the FREQ * command. I wonder if the problem could be that I set up my . qes files without a label. I always used to do this in Epi6 and thought it would be OK in Epidata as I kept the variables to 10 letters or less as below. SEX # AGE ## M1HAM <Y> Has anyone had a similar problem? OR does anyone have a comment about creating .qes files with just variables and no labels? thank you Christine +++The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you.+++ Disclaimer added by HVDHB

20 years, 2 months

appreciate

by epidata-list＠lists.umanitoba.ca

20 years, 5 months

Vedr.: [Epidata-list] "file corrupted" message

by epidata-list＠lists.umanitoba.ca

A type of error like this is very difficult to find since it can be due to many factors. e.g. network failure, network cache failure, disk occupied failures etc. But to minimise this type of error the principle of saving files was changed with version 2.1 to eliminate that error. And from v2.1b that type of error has only until now been reported from two instances in Kenya and China from situations where the computer lost power while entering data. The cause of the error was in both cases that the operating system (not epidata) were handling open files at power breakdown in a way where end of file markers were faulty. Even if the error still occurs only in rare cases we will consider a tool to "repair corrupt files" as part of the tool. The idea being to 1. read the file structure. 2. read the records from the start of the file and write them to a new file. 3. If a record was not of correct length, then tell the user how many records were retrieved. regards Jens Lauritsen >>> <epidata-list(a)lists.umanitoba.ca> 24-11-03 16:08 >>> Hi - Periodically (perhaps every few months) I am not able to open a .rec file, and get the message that "one or more files are corrupted". Our IT person will find that the end of the file marker has to be reset, and once that is done, we're able to use the file again. We're now using EpiData2.1b, although this has been happening for probably about a year, with previous versions. I'm wondering if there is anything we can do to prevent this "file corruption" from happening. I'm wondering if this problem could be related to my editing records in EpiInfo that have been originally entered in EpiData. thanks, Elise Elise Lennon, RN, MPH Research Analyst Massachusetts Rural Domestic Violence and Child Victimization Project Massachusetts Department of Public Health Western Regional Office 23 Service Center Northampton, MA 01060 _______________________________________________ Epidata-list mailing list Epidata-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

20 years, 5 months

"file corrupted" message

by epidata-list＠lists.umanitoba.ca

Hi - Periodically (perhaps every few months) I am not able to open a .rec file, and get the message that "one or more files are corrupted". Our IT person will find that the end of the file marker has to be reset, and once that is done, we're able to use the file again. We're now using EpiData2.1b, although this has been happening for probably about a year, with previous versions. I'm wondering if there is anything we can do to prevent this "file corruption" from happening. I'm wondering if this problem could be related to my editing records in EpiInfo that have been originally entered in EpiData. thanks, Elise Elise Lennon, RN, MPH Research Analyst Massachusetts Rural Domestic Violence and Child Victimization Project Massachusetts Department of Public Health Western Regional Office 23 Service Center Northampton, MA 01060

20 years, 5 months

Re: How to tell which field made a relate ?

by epidata-list＠lists.umanitoba.ca

Piotr's followup: >But I don't realised that I can't open the related file twice. >When I open file with first command "relate", the same file couldn't be >opened in the next part of form. >Am I right? You have to experiment a bit. Actually I am not sure, what I scheduled was a principle. If one cannot have the same relate more than once, just save the fieldname after entry and perform relate in a third field: Principle: v1 set variable to "v1" and jump to v30 v2 set variable to "v2" and jump to v30 v3 ,,,,,....... etc v30 perform relate here regards Jens M. Lauritsen, Consultant,MD. PhD. The EpiData Association, (EpiData Foreningen) Enghavevej 34, DK5230 Odense M. Denmark e-mail: info(a)epidata.dk For E-mail news on EpiData: Http://www.epidata.dk/php/maillist.php EpiData is freeware

20 years, 6 months

How to tell which field made a relate ?

by epidata-list＠lists.umanitoba.ca

Piotr asked: My next problem is: if there is some way to get the name of field in calculation. I mean, I 'd like to set comment legal in relational file depended on reference which field was called from. i.e.: main file has question: Which medicine have you used for last 12 month? And there is multiply response so I'd like to use relational file. But the next quetion is: Which medicine ...ever used? And my problem is to have ONE file with the medicine, and in this file I should have an information about respondent, and form WHICH FIELD was calling. ------------------------------------------------------------------ Something along this line where you combine a global variable with a comment legal depending on its value should work, some experimentation needed: chk file: before file * note the global define fieldname ____________ global end id mustenter key unique end v1 after entry fieldname = "v1" relate id otherfile 1 end end v2 after entry fieldname = "v2" relate id otherfile end end otherfile's chk file: before file * note you can repeat a define to be able to use the file alone define fieldname _________ global end id key mustenter end moreinfo before entry comment legal 10 "no answer" 11 otherfiled end if fieldname = "v1" then comment legal 1 yes 2 no end endif if fieldname = "v2" then comment legal 11 yes 12 no end endif end end regards Jens Lauritsen Jens M. Lauritsen, Consultant,MD. PhD. The EpiData Association, (EpiData Foreningen) Enghavevej 34, DK5230 Odense M. Denmark e-mail: info(a)epidata.dk For E-mail news on EpiData: Http://www.epidata.dk/php/maillist.php EpiData is freeware

20 years, 6 months

Problem with division by zero

by epidata-list＠lists.umanitoba.ca

Hello! I have a problem with all known example "first", and BMI calculation. When I left blank field in "high" the warning "division by zero" is shown. The "ignoremissing" command is not included. The second question is why EpiData writes in check file command "missingvalue all [same name of labelblock]". It happens when I'm working "manually" with check and then I open check editor. My build is: 040903 Regards, Piotr -- Piotr Kołodziejczyk tel: +48604512362 e-mail: admiralek(a)o2.pl

20 years, 6 months

Email based list for EpiData support and user discussions

by epidata-list＠lists.umanitoba.ca

It is with great pleasure that I welcome the addition of an e-mail based list for communication among users of Epidata. The initiation of such a list is yet another indication that the EpiData initiative has gained acceptance around the world. The aim of the list is to aid users and development in terms of : - mutual exchange of ideas and solutions - receive comments on problems and features desired - receive active input at times of release of new versions Thanks to the University of Mannitoba, Canada for hosting the list and to Chris Green Canada for the offer of moderating the list. With proper and positive use of the list it is my expectation that the moderation job for Chris will be very small. Regards Jens Lauritsen Initiator of the EpiData Development project WWW.EpiData.dk

20 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list