- EpiData-list - University of Manitoba Mailing Lists

how to sum numeric variables even if one of the variables is empty
by epidata-list＠lists.umanitoba.ca 06 Aug '07

06 Aug '07

Hello I would like to make an automatic sum (see: variable "daystotadm") of a series of variables (see: variable "daysadm1-2..."), but if only one of these variable is empty, the automatic calculation using the function SUM give a null result. Do anyone know a way to solve this problem without the need to enter a value for each variable. In my file I don not necessarily enter all the five lines and the number of days is already a calculated field? I attach the qes and the check files Thank you Francesco Grandesso QES FILE --------------------------------------------------------------------------------- Date of entry Date of exit Number of days -------------------------------------------- --------------- {dateentry1} <dd/mm/yyyy> {dateexit1} <dd/mm/yyyy> {daysadm1} ### {dateentry2} <dd/mm/yyyy> {dateexit2} <dd/mm/yyyy> {daysadm2} ### {dateentry3} <dd/mm/yyyy> {dateexit3} <dd/mm/yyyy> {daysadm3} ### {dateentry4} <dd/mm/yyyy> {dateexit4} <dd/mm/yyyy> {daysadm4} ### {dateentry5} <dd/mm/yyyy> {dateexit5} <dd/mm/yyyy> {daysadm5} ### -------------------------------------------- --------------- {daystotadm} Total days #### CHK FILE ---------------------------------------------------------------------------------- dateexit1 AFTER ENTRY daysadm1=(dateexit1-dateentry1) daystotadm=SUM(daysadm1,daysadm2,daysadm3,daysadm4,daysadm5) END END daysadm1 NOENTER END .................... and so on for each of the five dateexit* and daysadm* variables __________________________________________ Francesco Grandesso EPICENTRE 8, Rue Saint Sabin 75011 Paris, France tel +33 (0)1 4021 2847 fax +33 (0)1 4021 2803 email Francesco.GRANDESSO(a)epicentre.msf.org

1 1

Chris Sellers/FHS/ADPH is out of the office.
by epidata-list＠lists.umanitoba.ca 04 Aug '07

04 Aug '07

I will be out of the office starting 08/03/2007 and will not return until 08/09/2007. I will check emails periodically while I am away. If an issue needs immediate attention, please, contact Fred Grady at FredGrady(a)adph.state.al.us. Otherwise, I will respond to your email when I return.

1 0

Command Set replace logfile=on
by epidata-list＠lists.umanitoba.ca 04 Aug '07

04 Aug '07

Dear Epidata Team friends, I want to get the html file output form datafile by a PGM. I want to replace the previous output in the defined folder by the new output. The commands in my PGM are as follows; Set replace logfile=on Logopen The quarterly report file . 2007 /close Error message displayed is Replace Logfile not supported I change Set replace logfile=on to another command set replace datafile=on That also does not help. The help file about /close , /replace switches of Logopen command is not clear because it does not work as expected. If you close and reload Epidata Analysis, it works only once and displays error message when the PGM is run second time in the same session. What is the right command syntax? I am using trial version 2 (build 112). With regards, Shavinder Singh

1 0

Command Set replace logfile=on
by epidata-list＠lists.umanitoba.ca 03 Aug '07

03 Aug '07

Dear Epidata Team friends, I want to get the html file output form datafile by a PGM. I want to replace the previous output in the defined folder by the new output. The commands in my PGM are as follows; Set replace logfile=on Logopen The quarterly report file . 2007 /close Error message displayed is Replace Logfile not supported I change Set replace logfile=on to another command set replace datafile=on That also does not help. The help file about /close , /replace switches of Logopen command is not clear because it does not work as expected. If you close and reload Epidata Analysis, it works only once and displays error message when the PGM is run second time in the same session. What is the right command syntax? I am using trial version 2 (build 112). With regards, Shavinder Singh

1 0

Summing a number of variables
by epidata-list＠lists.umanitoba.ca 03 Aug '07

03 Aug '07

The easiest way of summing: > I would like to make an automatic sum (see: variable "daystotadm") of a > series of variables (see: variable "daysadm1-2..."), but if only one of > these variable is empty, the automatic calculation using the function SUM > give a null result. > What I would do is: dateexit1 AFTER ENTRY if dateexit1 = . then goto daysadm1 endif end end dateexit2 AFTER ENTRY if dateexit2 = . then goto daysadm endif end end etc for the other dateexit3 to 5. daysadm before entry * assume you have at least data in the first var: daysadm=(dateexit1-dateentry1) if dateexit2 <> . then daystotadm =(dateexit2-dataentry2) + daysadm endif if dateexit3 <> . then daystotadm =(dateexit3-dataentry3) + daysadm endif if dateexit4 <> . then daystotadm =(dateexit4-dataentry4) + daysadm endif if dateexit5 <> . then daystotadm =(dateexit5-dataentry5) + daysadm endif goto ... next variable end end In this way when the first dateexit is equal to ., the program jumps and no entry is needed in ... up to number 5 variable. (I hope the comparison of date variable with . works - did not test it). Regarding the other question from yesterday. Installation of EpiData software (entry and analysis) is always very "clean", meaning not disturbing the PC, so you can have many copies if you wish for various purposes. Just copy the exe file (plus help if needed). When testing I tend to create the default for testing as: c:\epidataanalysistest such that the test version of analysis does not interfere with the release version. regards jens lauritsen EpiData Association

1 0

"invalid floating pint" error with DESCRIBE in Analysis
by epidata-list＠lists.umanitoba.ca 02 Aug '07

02 Aug '07

I have a small data file, created in EpiData 3.1 on Windows XP. It consists of 7 records and 8 variables. I load the data into Analysis version 1.1 build 68. I use the command line editor to issue DESCRIBE * command, and I get descriptive summaries of all variables, including the variable called AMOUNT. But when I issue the command DESCRIBE AMOUNT, I get an error message: Invalid floating point operation See attached html file. Any suggestions how I could solve this problem? Thanks. -- Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 40 Arch Street, Johnson City, NY 13790 cryanatbinghamtondotedu PGP public keys available at http://home.stny.rr.com/ryancw/ "If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea." [Antoine de St. Exupery]

1 0

Data entry only setup for EpIData Entry
by epidata-list＠lists.umanitoba.ca 20 Jul '07

20 Jul '07

Re: Is it possible to start Epidata Entry with "Enter data" For a system like that I suggest to add to the chk file the following: after file backup ..... see below quit end with the above, EpiData Entry will quit completely after performing a backup. Further on the backup: (copied from the help file) The syntax of the backup command is: BACKUP distination-directory or BACKUP distination-directory [ZIP zip-file-name [DATE]] or BACKUP distination-directory [ENCRYPT name-of-encrypted-zip-file password [DATE]] I usually prefer BACKUP distination-directory ZIP zip-file-name DATE Regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 45, Issue 6
by epidata-list＠lists.umanitoba.ca 19 Jul '07

19 Jul '07

Thanks for the help Jamie, it works just fine; I like the notoolbars option. -----Original Message----- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 18 Jul 2007 7:01 pm Subject: EpiData-list Digest, Vol 45, Issue 6 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. Re: Is it possible to start Epidata Entry with "Enter data" (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Jul 2007 22:06:28 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Is it possible to start Epidata Entry with "Enter data" To: epidata-list(a)lists.umanitoba.ca Message-ID: <469D75A4.5020506(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed You can get most of this by doing the following: Make sure the Windows Toolbars option is to hide toolbars during entry (this is the default) Create a shortcut that has the command line "c:\program files\epidata\epidata.exe" "c:\data\file.rec" You can put "/notoolbars" on the end of that, but it may be better to set the options that way. Users can still turn on the other toolbars, but why would they? Everything needed for entry is there. Jamie > I would like to know if it is possible to force a data entry clerk to click on a short cut (which we can create and place on desktop) that would allow the user to only enter data without having access to the other data entry functions (e.g. check, data documentation, etc). This is to prevent the data entry person from chnaging anything with the data entry forms during the entry process. > > Shuaib > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 45, Issue 6 ******************************************* ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.

1 0

Is it possible to start Epidata Entry with "Enter data"
by epidata-list＠lists.umanitoba.ca 17 Jul '07

17 Jul '07

Dear Epidata Users, I would like to know if it is possible to force a data entry clerk to click on a short cut (which we can create and place on desktop) that would allow the user to only enter data without having access to the other data entry functions (e.g. check, data documentation, etc). This is to prevent the data entry person from chnaging anything with the data entry forms during the entry process. Many thanks Shuaib ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.

1 1

RR in TABLES command
by epidata-list＠lists.umanitoba.ca 12 Jul '07

12 Jul '07

Regarding Pedro Arias' question Couldn't the default display for TABLES VAR1 VAR2 be NN at the 'a' cell, and YY for TABLES VAR1 VAR2 /RR ? best regards, Fúlvio ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Quarta-feira, 11 de Julho de 2007 18:00:51 Assunto: EpiData-list Digest, Vol 45, Issue 3 Dear all, I have a general question regarding the layout for the output of the TABLES command. In version 2 (112) the default option for TABLES is sorted in ascending order. That means that when using boolean fields TABLES will display N,N in the top left cell of a 2 x 2 table, because internally NO=0 and Yes=1. (Jens, is that correct?) When asking for RR (TABLES VAR1 VAR2 /RR) what we get is the RR of being N in the outcome if you are N in the exposure. Which is clearly the inverse of what we usually are looking for. But because most of the statistical/epidemiological software dispay the table in the other way (Y,Y on the top left cell) EpiData can misslead the users with its results. (obviously users should read the table, but...). And we have /SD as option to change that My question is: Should EPiData follow the general rule of displaying YY in the too left cell?. (and therefore calculating the RR that usually we are interested in) Jens has a point saying that if we change that when we are not interested in RR but only in the numbers and %, most of the program follow the rule of sorting the values in ascending order and that if we want to follow this rule we will need an EPITABLE command (in version 2 he is trying to get ride of innecesary commands). I think we alreday have the EPITABLE command, it is TABLES V1 V2 /RR I would appreciate if can comment on that. Version 2 is almost ready, but i think this is an important issue. Hope my explantion and question is clear. Thanks a lot, Pedro Arias EpiData Spanish cotranslator I am checking the entry in some files using the double entry verification. The data are from a family study so the unique identifying information is a family ID (4 digits), an individual ID (2 digits), and informant ID (in some cases, people will be reporting on others. Each data record, then, is uniquely identified by these 8 digits. I created a key for the entry check file as follows: rhinf RANGE 1 99 MUSTENTER after entry rhukey=famid*10000+indid*100+rhinf end END rhukey noenter key unique end This works fine to prevent entering the same record twice. I'm trying to use the variable rhukey as the match variable in the double entry program. I have intentionally entered non-matching data, but Epidata doesn't recognize any discrepancies. Is there a problem with a key that is created in the dbl file as well as in the original file? Thanks. Richard Herrell NIMH --------------------------------- Shape Yahoo! in your own image. Join our Network Research Panel today! I prefer the current method as there is no doubt about what the syntax means (lower values in top left unless you specify /SD) and the /SD switch provides a means of inverting the order. Many people code variables as 1=Yes 2=No, which gives a proper RR without the /SD switch. Many others use 0=No 1=Yes, which requires /SD. Since EpiData internally treats Booleans False as 0 and True as 1, the current approach allows programming that does not require exceptions. User help and guides should point this out. The TAB output clearly identifies the meaning of the RR, which is something a number of us requested. This is something that came into later versions of EpiInfo to help the user avoid misunderstanding. So no need for EPITABLE - just use TAB OUTCOME EXPOSURE /RR /SD Jamie > My question is: Should EPiData follow the general rule of displaying YY in > the too left cell?. (and therefore calculating the RR that usually we are > interested in) > > Jens has a point saying that if we change that when we are not interested > in RR but only in the numbers and %, most of the program follow the rule > of sorting the values in ascending order and that if we want to follow > this rule we will need an EPITABLE command (in version 2 he is trying to > get ride of innecesary commands). I think we alreday have the EPITABLE > command, it is TABLES V1 V2 /RR > ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list ____________________________________________________________________________________ Novo Yahoo! Cadê? - Experimente uma nova busca. http://yahoo.com.br/oqueeuganhocomisso

1 0