February 2007 - EpiData-list - University of Manitoba Mailing Lists

IDNUM at top of each data entry screen?
by epidata-list＠lists.umanitoba.ca 22 Feb '07

22 Feb '07

Hi all, With many fields to enter, the QES file of epidata can easily become very large and cover 2 (or even more) subsequent screens. While entering the data, after having filled in the last field of screen 1, there will be a continuous scrolling down after each next field is entered. To prevent this continuous scrolling, one can use the TOPOFSCREEN command in the CHK file, which places the field in question at the top of the second entry screen. This results in a more steady (over)view during data entry, which I think is preferable. Now to my question. At the top of the first screen I show the value of the automatic <IDNUM> field, which corresponds with the respondent number written on the questionnaires. Is there a way to have this <IDNUM> shown at the top of EACH new data entry screen? I've tried this by simply putting the text respondent: <IDNUM> at the top of each new screen. However, this didn't work well, since after the entry and saving of record 1, the next empty datarecord for case 2 is shown, but instead of showing respondent 2 it shows respondent 1 while at the second screen it shows respondent 2 Probably I'm doing something strange, with showing the IDNUM field more then one time in the same REC file. Does anyone know a method to manage this problem? Thanks, Ben.

1 1

Age calculation
by epidata-list＠lists.umanitoba.ca 21 Feb '07

21 Feb '07

Hi, Gilles assessment of the problem is rigth, the message you get is because the results of your calculation is real number and your defined variable is an integer. I think the best solution is: Let age=Integer(date("WDATE","mdy") - date("DOB","mdy"))/30.44) The INTEGER function converts and real number into an integer. I have tried with some records and it works. Regarding Pedro Emmanuel´s solution, I wouldn't do that except if you need the calculation during the data entry (for example to take decisions based on the age of the patient). Otherwise i wouldn't include the field in the QES in order to save room in the harddisk (I know it is not a big issue nowadays, but..) and to save room in the screen and also make it more clear. Hope it helps. Saludos, Pedro Arias > > > > 2007/2/20, epidata-list-rtequest(a)lists.umanitoba.ca < > epidata-list-request(a)lists.umanitoba.ca>: >> >> 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. Date range selection for age calculation >> (epidata-list(a)lists.umanitoba.ca) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: 20 Feb 2007 07:15:30 -0000 >> From: epidata-list(a)lists.umanitoba.ca >> Subject: [EpiData-list] Date range selection for age calculation To: >> epidata-list-request(a)lists.umanitoba.ca >> Cc: epidata-list(a)lists.umanitoba.ca >> Message-ID: <20070220071530.19938.qmail(a)webmail35.rediffmail.com> >> Content-Type: text/plain; charset=iso-8859-1 >> >> Dear Epidata team friends, >> I have two American date >> format variables. DOB is date of birth of baby and WDATE is date of >> weighing the baby for the growth monitoring. >> >> I used to write the following statement to calculate the age in months >> in EPI6 >> >> Define age ### >> Let age=(WDATE DOB)/30.44 >> >> That does not work in EPI ANALYSIS >> >> I tried the statement; >> Let age= (date("WDATE","mdy") - date("DOB","mdy"))/30.44 >> The error message was; >> Data type mismatch >> >> Please help. >> >> Shavinder Singh >> >> >> >> ------------------------------ >> >> ________________________________________ >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> >> End of EpiData-list Digest, Vol 40, Issue 15 >> ******************************************** >> > > > > -- > Abraço forte e que a força esteja com você, > Pedro Emmanuel > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 40, Issue 16 > ********************************************

1 0

Re: EpiData-list Digest, Vol 40, Issue 15
by epidata-list＠lists.umanitoba.ca 21 Feb '07

21 Feb '07

Dear Shavinder Singh, I did learn in the same as you, missing a lot first. Dont give up. My suggestion is to put this variable on the .QES that would be automatically calculate during entry. Usually the formula is LET variable_age=ROUND(INT((now_date - birth_date)/365.25)) Epidata does not round and transform the calculation automatically and this syntax is necessary every time you will do any calculation with dates. Good luck, Pedro Emmanuel Brasil 2007/2/20, epidata-list-request(a)lists.umanitoba.ca < epidata-list-request(a)lists.umanitoba.ca>: > > 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. Date range selection for age calculation > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: 20 Feb 2007 07:15:30 -0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Date range selection for age calculation > To: epidata-list-request(a)lists.umanitoba.ca > Cc: epidata-list(a)lists.umanitoba.ca > Message-ID: <20070220071530.19938.qmail(a)webmail35.rediffmail.com> > Content-Type: text/plain; charset=iso-8859-1 > > Dear Epidata team friends, > I have two American date > format variables. DOB is date of birth of baby and WDATE is date of weighing > the baby for the growth monitoring. > > I used to write the following statement to calculate the age in months in > EPI6 > > Define age ### > Let age=(WDATE – DOB)/30.44 > > That does not work in EPI ANALYSIS > > I tried the statement; > Let age= (date("WDATE","mdy") - date("DOB","mdy"))/30.44 > The error message was; > Data type mismatch > > Please help. > > Shavinder Singh > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 40, Issue 15 > ******************************************** > -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Date range selection for age calculation
by epidata-list＠lists.umanitoba.ca 21 Feb '07

21 Feb '07

Dear Epidata team friends, I have two American date format variables. DOB is date of birth of baby and WDATE is date of weighing the baby for the growth monitoring. I used to write the following statement to calculate the age in months in EPI6 Define age ### Let age=(WDATE DOB)/30.44 That does not work in EPI ANALYSIS I tried the statement; Let age= (date(WDATE,mdy) - date(DOB,mdy))/30.44 The error message was; Data type mismatch Please help. Shavinder Singh

1 1

Error when reading a rec file (list index out of bounds)
by epidata-list＠lists.umanitoba.ca 20 Feb '07

20 Feb '07

The user reporting on the 15th: When I try to open updated REC file, I get the message "List index out of out of bounds (420)" - How can I solve this problem? Thank you. We have seen the problem with earlier versions of EpiData Entry (v2.1), but as I remember not with 3.1. But I could be mistaken as I remember having seen it, but cannot reproduce the error with any data I have. A similar error was reported in February 2006, where the error was: In the chk file one of the fields had a wrong name. The very subtle error message does not give you a clue to this, but please check if this could be the cause. A good strategy is always to try to repeat the problem. What did you do since you could read the file last time. Then repeating the steps tells us where to look for a problem in the software and often also how to solve it. But your description does not help a lot, since we should know : 1. What did you do btw. the last time it worked and until it did not ? 2. Which versions of EpiData (Entry or Analysis) wrote the file (saved). If the file can be shown to others you can upload a small copy to the Mantis database, see the http://www.epidata.dk/testing.php with a description - but you must first register as a user there. An easier alternative for the user is to send the file directly to me at info at epidata.dk and we will look at it very soon. regards Jens Lauritsen EpiData Association

1 0

multiple response
by epidata-list＠lists.umanitoba.ca 20 Feb '07

20 Feb '07

The example prepared by Charity Jenkins on the multiple response issue discussed on Febr. 16th. has now been placed for download on http://www.epidata.dk/examples.php For the original description, you can see the text in the archives of the list on the 16th. http://lists.umanitoba.ca/mailman/listinfo/epidata-list Regards Jens Lauritsen EpiData Association

1 0

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 17 Feb '07

17 Feb '07

I will be out of the office starting 02/16/2007 and will not return until 02/26/2007. If you require immediate assistance, please contact Stephen Drew at extension 5330. Have a great day.

1 0

multiple response and example files
by epidata-list＠lists.umanitoba.ca 16 Feb '07

16 Feb '07

Charity offered: > I will put together an example of this as Epidata files - can I attach > this > to the list or somewhere else? > I have contacted Charity directly in the aim of adding the example for the website at www.epidata.dk/examples.php Information will be given to the list when it is ready. Some users have asked to the list for a copy. Please wait until it is ready there. Regards Jens Lauritsen EpiData Association

1 0

Multiple response questions
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

Dear Kristine: As one variable can take only one value, you must use as many variables as there are possible values. If you have 5 possible responses ("Do you have any of the following 5 symptoms?"), you need 5 variables, each with 3 possible values, "present", "absent", "unanswered". I don't see an easier way. Regards, Hans Dear Epi-data users: What is the best way to deal with multiple response questions? Thanks, Kristine Hopkins Population Research Center, University of Texas at Austin -- 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 1

Is there any possibility to sort the file without exporting the data?
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

Dear Mr Lauritsen, Thank you very much for your help, this was the hint I needed, works perfectly... Kind regards, Markus

1 0