- EpiData-list - University of Manitoba Mailing Lists

Command labelvalue
by epidata-list＠lists.umanitoba.ca 21 Jan '07

21 Jan '07

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

1 0

RE: AW: [EpiData-list] chk file size
by epidata-list＠lists.umanitoba.ca 19 Jan '07

19 Jan '07

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.

1 0

chk file size
by epidata-list＠lists.umanitoba.ca 18 Jan '07

18 Jan '07

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

1 4

How to - analysis: Routine reporting (Check if count is larger than 0)
by epidata-list＠lists.umanitoba.ca 17 Jan '07

17 Jan '07

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

1 0

Reading and closing files with EpiData
by epidata-list＠lists.umanitoba.ca 14 Jan '07

14 Jan '07

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 > *******************************************

1 0

Read files
by epidata-list＠lists.umanitoba.ca 14 Jan '07

14 Jan '07

EpiData Analysis does not read Access files, export it into a format that can be read (REC, CSV, DBF) Hans 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 Thanks Marc L.A. -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

quesitons re Browse and Read/Close
by epidata-list＠lists.umanitoba.ca 13 Jan '07

13 Jan '07

I just started using Epidata. In my first Browse I could not move the screen completely to the right to see the command. Is there a limit to the number of characters the screen can display on any given line? 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 Thanks Marc L.A.

1 0

Regarding automatically filling of fields
by epidata-list＠lists.umanitoba.ca 13 Jan '07

13 Jan '07

Just a comment to MUSTENTER and NOENTER MUSTENTER prevents people from skipping inadvertently a field NOENTER prevents people from getting into the field and inadvertently change it (The role of the command MUSTENTER and NOENTER is not fully clear to me, = However, they have to be included in this fashion) To Jamie, Jens Lauritsen, Hans and all of you that follow this thread = and came with many helpful suggestions 'Thanks'. Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

Re: Regarding automatically filling of fields and colloborative efforts
by epidata-list＠lists.umanitoba.ca 13 Jan '07

13 Jan '07

1. Regarding automatically filling of fields > After trying different models, I managed to create a Syntax that allow me to enter data in one field and get automatically related data filled up in two other fields. I had to split the helping REC file into two files. The Key variable in the first file was the brand (say Aspirin) and the second variable was the Generic name (say ASA), and in the second file the Key variable was the generic name and the second variable the ATC code. > This is a very good example of how "good examples" develop with assistance. Please wrap up this example and send for inclusion as a worked example for placement on www.epidata.dk/examples.php E.g. just a zip file with the qes, chk and rec files and a pdf file showing the screen. Much like the "Yves" example, a good example was created. By combining efforts in this way many people learn and gets inspiration. Another way of giving inspiration is to work out "flyers" in collaboration with me, such as http://www.epidata.dk/php/downloadc.php?file=epidataflyer_general.pdf Projects or institutions having examples or ideas are much welcomed to suggest this. Best by writing to "info at epidata.dk " I hope during the 2007 it will be possible to get a WIKI started with mutual responsibility among users. Some aspects of this has been started, but the whole organisation is not ready for general use yet. A WIKI is an open editing system based on contributions from a broad base of users. Examples are: www.wikipedia.org, http://www.freepascal.org/wiki or https://wiki.ubuntu.com/. An example for use in EpiData would be introduction texts developed in local language, such as the one announced earlier on epidata-list by Bernard Branger and located at http://www.reseau-naissance.fr/medias/epidata_guide_2006.pdf and http://www.reseau-naissance.fr/medias/epidata_guide_controle.pdf which could be kept locally and then with a link in the wiki or added as text to the wiki. The difference from text on the EpiData main site is that the editing and placement on the WIKI needs no work from my part. In contrast to the main site where I (or another dedicated person) have to do something to add texts. Kind regards Jens Lauritsen EpiData Association

1 0

Regarding automatically filling of fields
by epidata-list＠lists.umanitoba.ca 12 Jan '07

12 Jan '07

To Jamie, Jens Lauritsen, Hans and all of you that follow this thread and came with many helpful suggestions 'Thanks'. After trying different models, I managed to create a Syntax that allow me to enter data in one field and get automatically related data filled up in two other fields. I had to split the helping REC file into two files. The Key variable in the first file was the brand (say Aspirin) and the second variable was the Generic name (say ASA), and in the second file the Key variable was the generic name and the second variable the ATC code. If somebody may give a feed back, I will appreciate it. The two 'Helping files' look like this: Brand-Generic (MedGen.REC) MedNvn Aspirin MedGen acetylic salicylic acid MedNvn Beuron MedGen acetaminophen MedNvn Efferalgan MedGen acetaminophen MedNvn Panadol MedGen acetaminophen MedNvn Paralen MedGen acetaminophen MedNvn Tyelenol MedGen acetaminophen Generic-ATC (MedATC.REC) MedGen acetylic salicylic acid MedATC n02ba01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 The CHK file of my qustionnaire (MedicineQues.CHK): MedNvn MUSTENTER COMMENT LEGAL MedGen.rec Show TYPE COMMENT MedGen END MedGen COMMENT LEGAL MedATC.rec Show TYPE COMMENT MedATC END MedATC NOENTER End (The role of the command MUSTENTER and NOENTER is not fully clear to me, However, they have to be included in this fashion) The CHK file of the Brand-Generic database (MedGen.CHK): MedNvn KEY 1 END MedGen KEY 2 END The CHK file of the Generic-ATC database (MedATC.CHK): MedNvn KEY 1 END MedATC KEY 2 END My QESTIONNAIRE file (MedicineQues.QES): MedNvn the name of the Drug ___________________ MedGen The Generic name ___________________ MedATC The ATC code _____________ AnyFild Any field # *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 0