EpiData-list January 2007

epidata-list@lists.umanitoba.ca

1 participants
24 discussions

by epidata-list＠lists.umanitoba.ca

Hello, For French users Je n'ai pas eu beaucoup de chances avec mon precedent mail, proposant une eventuelle mutualisation des personnes pour la realisation de guides d'aide a l'utilisation de EPIDATA. J'ai finalement realise trois guides : - Un 8-pages de prise en main rapide - Un guide pour l'analyse seule - Un guide pour le controle des donnees avec un mot sur les fichiers relationnels Ces trois documents ne peuvent être joints a ce mail (taille bornee). Vous pourrez les trouver sur le site internet du Reseau Securite-Naissance des Pays de la Loire www.reseau-naissance.fr Je reste a votre disposition Bernard Branger branger-bono(a)wanadoo.fr Message redige sans accent

17 years, 3 months

[EpiData-list] Importing other file formats (eg SPSS) to create REC, CHK and QES files

by epidata-list＠lists.umanitoba.ca

Hello, I know that EpiData has the ability to output data in SPSS format (a TXT file and an SPS file which can be run to create a SAV file) - is it possible to reverse this process and either use a SAV file or a SPS/TXT combination to create REC and CHK files (and ideally even the QES file to go with them)? I'm also interested if I could generate REC/CHK files from other file formats, such as Triple-S (and output to this too) - what options are there currently for doing this. If nothing, are any being worked on or considered for implementation in future versions? I would be interested in helping with developing these things if that is possible or would help also. Thanks, Charity

17 years, 3 months

command labelvalue in analysis

by epidata-list＠lists.umanitoba.ca

A user wrote: "I discovered this link http://www.epidata.dk/downloads/docs/commands.htm" The link is outdated and has been deleted today. The overview of the latest commands in most recent development versions can always be found at "http://www.epidata.dk/commands.htm" However the release of next version of analysis will not take place until I find it sufficiently stable for general testing and usage. At that point you will find a copy on the testing page: http://www.epidata.dk/testing.php I reject telling when a given release is going to be made - since this is basically unknown. Unfortunately I am somewhat naive in this respect, since severe problems have been showing up during the major rewrite ongoing since release of v1.0 build 68. The list will be informed when the release is ready. The same answer applies to the other question: > When I calculate proportions, how to have Interval of confaince? > In Epiinfo, the command is Freq "Var"/C!! > Speed of development can usually be increased by confirmed donations to the EpiData Association. At this moment the latest donations have been given by the World Lung Foundation and the Swiss MPH education organisation. Thanks for the donations. Regards Jens Lauritsen EpiData Association

17 years, 3 months

Bug of Unique Key Field

by epidata-list＠lists.umanitoba.ca

Dear Epidata Team Friends, We have a unique field known as RECNO. We enter the number manually by looking at the latest RECORD NUMBER displayed at the bottom of the screen. When we enter the RECNO equal to the RECORD NUMBER. Displayed on the screen, a warning Dialogue box is displayed. Warning Duplicate Key in RECNO Value already entered in Record Number #4284 Go to Record #4284? Yes No When I press the yes button, Record Number is 4284 not 4285 as shown in the warning dialogue box. When I tested higher numbers, same warning message is displayed? Is it a bug or some solution is possible ? Please help us as we are waiting. Dr. Shavinder Singh

17 years, 3 months

Interval of Confiance

by epidata-list＠lists.umanitoba.ca

Hello, When I calculate proportions, how to have Interval of confaince? In Epiinfo, the command is Freq "Var"/C!! Thanks ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

17 years, 3 months

Command labelvalue

by epidata-list＠lists.umanitoba.ca

Hi, I looked on the site of epidata, in the section Documentation and on Commands and Functions in EpiData Analysis, i discovered this link http://www.epidata.dk/downloads/docs/commands.htm So in label Dates, there is labelvalue and missingvalue (new). I tried to carry out these orders here is the message which is displayed "Unknown Command". Then what is to be done? Thanks ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

17 years, 3 months

RE: AW: [EpiData-list] chk file size

by epidata-list＠lists.umanitoba.ca

In my experience the .chk files do get truncated at 64 kb when used with the .qes file, even when it was larger. My work-around is in my opinion not very elegant but it works: I split up the .qes and .chk files in two and have them linked by RELATE. Henriette Jansen -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: 18 January 2007 22:52 To: epidata-list(a)lists.umanitoba.ca Subject: Re: AW: [EpiData-list] chk file size My understanding from Jens is that the limitation had to do with using the internal editor. My .chk files often are a good deal longer than 64kb and I don't use the internal editor. But as always, testing is always the best advice. Richard NIMH epidata-list(a)lists.umanitoba.ca wrote: I think there is an issue whether EpiData , once it applies the *.chk file, truncates the *.chk file at 64Kb even if it was larger (because it was written in an other editor ). I am unsure whether it truncates or not. You should test it before relying on writing a longer one. marcel -----Ursprüngliche Nachricht----- Von: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Gesendet: Donnerstag, 18. Januar 2007 11:15 An: epidata-list(a)lists.umanitoba.ca Cc: Kristine Hopkins Betreff: RE: [EpiData-list] chk file size Hi; CHK files can be edited with any text editor, provided the syntax is respected. I'm using metapad (freeware, can be download at http://www.liquidninja.com/metapad/). It's small and very powerful. Gilles Delmas -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : mercredi 17 janvier 2007 03:15 À : epidata-list(a)lists.umanitoba.ca Cc : Kristine Hopkins Objet : [EpiData-list] chk file size Hello, I have encountered a problem with the size of my check file. I need to exceed the limit of 64Kb to include all the checks I want. Is there a way to get around this limitation? The manual says that "File size for CHK or QES files cannot exceed 64Kb in size if you work in the editor with that file." Is there another place to work in other then the editor? Any help is appreciated! Cate McNamee _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list --------------------------------- Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.

17 years, 3 months

chk file size

by epidata-list＠lists.umanitoba.ca

Hello, I have encountered a problem with the size of my check file. I need to exceed the limit of 64Kb to include all the checks I want. Is there a way to get around this limitation? The manual says that "File size for CHK or QES files cannot exceed 64Kb in size if you work in the editor with that file." Is there another place to work in other then the editor? Any help is appreciated! Cate McNamee

17 years, 3 months

How to - analysis: Routine reporting (Check if count is larger than 0)

by epidata-list＠lists.umanitoba.ca

When doing routine reporting we never know in advance if there are some observations for a given table in analysis. Therefore: read rawfile_from_patientsystem.csv /close means y sex would stop if no persons had any data in variable y The technique in analysis to control this is: read rawfile_from_patientsystem.csv /close * first count the number (with /q the result is not shown) count if y <> . /q imif $count > 0 then means y sex else type "No data in y or sex" endif Another useful technique is to find the period in the data. By sorting on the date variable and save the result as a constant this can be used in a "report". read rawfile_from_patientsystem.csv * sort on a given variable containing date: sort entrydate define first ________________ global define last ________________ global first = string(vmeb001[1]) count last = string(vmeb001[$count]) type "test - @first - @last" /h3 If one adds then "cls" to clear the screen or "set echo = off", then only the result of the type command is shown. But only do this when it is all working. I am writing on a manual of "how to write menusystems" for release later this year. The techniques above will be part of that. Jens Lauritsen EpiData Association

17 years, 3 months

Reading and closing files with EpiData

by epidata-list＠lists.umanitoba.ca

Dear Marc, > Also, I did not follow why the Read opened this file, and then I could > not close it? > > read "c:\epi_info\hosp\hsample.mdb > malformed string > . read "c:\epi_info\hosp\hsample.mdb" > No, data will be lost - Close first > . close read "c:\epi_info\hosp\hsample.mdb" > Syntax error It seems to me that you are triying to open an ACCESS file using EPiData. EpiData does not read ACCESS files. Still it trys, and the consequence is this: malformed string message. Once you have open a data set, Epidata does not allow you to open another without closing the first. This is because EpiData trys to prevent you of losing any changes you have done in your first data set. Only if you activily close you first data set you can open a second. The reason for the third message: Syntax error is that the syntax for closing a data set is just CLOSE. I hope it helps. Pedro Arias EpiData Translator > Thanks > Marc > L.A. > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 39, Issue 9 > *******************************************

17 years, 3 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 January 2007