- EpiData-list - University of Manitoba Mailing Lists

Changing Confidence Intervals on EpiData Analysis
by epidata-list＠lists.umanitoba.ca 29 Mar '07

29 Mar '07

Hi, I would like the stats I get when doing an epitable to to reflect a 90% CI, instead of the default 95%. Is it possible to do so, and if yes, how? Thanks! REgards Juanette John Natural Resources & the Environment - CSIR PO Box 395 Pretoria 0001 South Africa jjohn(a)csir.co.za Tel 27 12 841 4189 (mornings only) Cell 083 4100 444 Fax 27 12 841 4257/086 6180084 CSIR: "our future through Science" http://www.csir.co.za -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to CallCentre(a)csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Using Notes for long text fields
by epidata-list＠lists.umanitoba.ca 15 Mar '07

15 Mar '07

Hi Pedro, that's a good point. I'll try to figure that out. It seems to me that Epidata was not really developed for dealing with long text fields. Nevertheless, many questionnaires have such questions, e.g. a concluding question in which the respondent can comment on the contents of the questionnaire and this often leads to long and very interesting comments. It would ofcourse be nice if such and other long text answers could simply be processed with Epidatal. Maybe this will become more easy in a future release? Who knows. Bye and thanks, Ben.

1 1

long text fields
by epidata-list＠lists.umanitoba.ca 15 Mar '07

15 Mar '07

Hi Jamie, thanks a lot , I going to try that Notes screen, Ben.

1 0

Long texts in EpiData Entry
by epidata-list＠lists.umanitoba.ca 14 Mar '07

14 Mar '07

Regarding Jamie 2nd option (see below), one thing we have to be aware is the problem of file size that the Epidat Editor can manage. If i am not wrong there is a limitation on that side. So check if that limitations is going to be a problem when entering your comments. > 2) Capture the text using the data notes capability. Just hit <F5> when > in a field and EpiData opens the Notes screen. You can type all you want > in here. EpiData puts in the record number, field name and current > field contents, so you may want to add to a BEFORE ENTRY block for this > field: > > BEFORE ENTRY > WRITENOTE "Notes for patient @patidnum, visit number @visitnum" > END > > This a very powerful feature of EpiData that is missing from most other > software. > You don't have any means of manipulating the data, but they are captured > and can be reviewed and edited in any text/word processor. > > Jamie Pedro Arias

1 0

Mapulation dates & Hour
by epidata-list＠lists.umanitoba.ca 14 Mar '07

14 Mar '07

Thank you Charity I know this command and I have already used it when I even I drove the management of data since the beginning. But we are in front of this problem when someone give you this kind of data base. Then I would especially like to draw the attention of the designers of software so that this module can be introduced. Thank all ___________________________________________ 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

long text fields
by epidata-list＠lists.umanitoba.ca 14 Mar '07

14 Mar '07

Hi all, Is there a nice way in Epidata to deal with long text fields of 300 positions? I'm working with a questionnaire with open-end questions. The answers are not longer than about 300 characters. The qes files now has four text fields, each covering 80 positions which is the maximum. Though this works, it is e.g. not easy to make corrections in the text, since the four fields are handled separately by Epidata; inserting a word that I forgot to enter in the first field implies that all remaining fields have to be adjusted as well, since the text does not scroll over all five fields at the same time. Also, instead of showing 80 positions, only 64 are visible at a time, in each field. Does anyone have an idea or tip what I could do, staying with Epidata that is. (Of course, I could also type the text in notepad or whatever, but it's much nicer to keep all data together.) Thanks for any advice, Ben.

1 1

Manipulation of Date and hour
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

I would like to know how to manipulate dates and hours at the same time. I have a data base which I seized under Epidata Entry and who understand variables dates and the hour of entrance for the delivery and date and the hour for the delivery. The hour I made two numeric variables, the hour and minutes. Now how to make to have the difference in the hour or in minutes? The problem does not settlewhen the delivery with place the same day. But the problem when there is gap For example: DAR Date of arrival <10/01/2007> HAR Arrival time 13 MAR Minute of arrival 45 DAC Dates delivery <12/01/2007> HAC Hour of delivery 02 MAC Minutes of delivery 34 Under SPSS, the manipulation is easy, I would like to know if under Epidata Analysis we can do the same with these temporal data. Should the opposite occur it would be necessary to think of introducing this module into the final version of this magnificent software. ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Mardi, 13 Mars 2007, 18h10mn 43s Objet : EpiData-list Digest, Vol 41, Issue 7 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. deleted and excluded records (epidata-list(a)lists.umanitoba.ca) 2. Re: deleted and excluded records (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 13 Mar 2007 08:16:27 +0100 (CET) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] deleted and excluded records To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <52289.130.226.78.129.1173770187.squirrel(a)webmail.webhosting.dk> Content-Type: text/plain; charset=iso-8859-1 Continued discussion on this topic: The suggested solution I gave could be clarified: 1. Dates before year approx. 1700-1800 give problems in Analysis now, but obviously should not. Although as everyone probably know there is a shift around 15xx (I do not remember the exact year). 2. The suggestion: "SUGGESTION: Would it not be possible for Analysis to assign a standard valid value (e.g. 01/01/1900) to any invalid dates it comes across during the read process. " Will be used in the next build of analysis, since it is very easy to implement. Obviously with a message to the user. I think this can be done in 5 minutes of work time in the programming, whereas the optimal solution of showing variable/field name and record is a large job - could be 1-2 days of work, since the function controlling the date value is not knowing neither the name of the field nor the record. But I will add the issue to the work plan for a solution at some point. Regarding the "excluded" versus "deleted" is also easy. The user can control whether records deleted are read or not by: set read deleted=on set read deleted=off The change works only when reading the file, so if you change re-read the file again. e.g. set read deleted = off read myfile describe age set read deleted = on read myfile /close describe age // here records marked for deletion are included. off is default. There is an error in v1 b68 in relation to this setting, such that if you read the file with "set read deleted=off" and then do an "update", you will see the records marked for deletion. The error has been found and a solution will be shown in next test release. regards Jens Lauritsen ------------------------------ Message: 2 Date: Tue, 13 Mar 2007 09:43:23 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] deleted and excluded records To: epidata-list(a)lists.umanitoba.ca Message-ID: <44e66f9b0703130043t1911363ev728eaea2e245ef85(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Thanks for the quick response to my email. I would just like to clarify my suggestion re "excluded" and "deleted" records. The issue is not about whether one can control reading deleted records or not (as Jens' response implies). My point was that if one is not aware that records have been deleted, it would be more informative on reading the dataset in Analysis if the message specifically states that x records have been deleted (and are therefore excluded). Using the word "excluded" suggests that Analysis has a problem with some values and therefore has excluded the records. One could spend quite some time trying to identify the problem before realising that these are merely records that have been deleted. On the point of deleted records, is there some way in Analysis of identifying records which had been deleted (but which one has chosen to include in the analysis). In EpiInfo, there was a system variable RECDELETED. Also, in browse/update mode, deleted records were identifiable by an asterisk. This was very useful in trying to sort out why records had been deleted. Thanks again, Annemieke van Middelkoop ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 41, Issue 7 ******************************************* ___________________________________________________________________________ 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 1

Manipulation of Date end hour
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

I would like to know how to treat(manipulate) dates and hours at the same time. I have a data base which I seized under Epidata Entry and who understand variables dates and the hour of entrance for the delivery and date and the hour for the delivery. The hour I made two numeric variables, the hour and minutes. Now how to make to have the difference in the hour or in minutes? The problem does not settlewhen the delivery with place the same day. But the problem when there is gap For example: DAR Date of arrival <10/01/2007> HAR Arrival time 13 MAR Minute of arrival 45 DAC Dates delivery <12/01/2007> HAC Hour of delivery 02 MAC Minutes of delivery 34 Under SPSS, the manipulation is easy, I would like to know if under Epidata Analysis we can do the same with these temporal data. Should the opposite occur it would be necessary to think of introducing this module into the final version of this magnificent software. ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Mardi, 13 Mars 2007, 18h10mn 43s Objet : EpiData-list Digest, Vol 41, Issue 7 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. deleted and excluded records (epidata-list(a)lists.umanitoba.ca) 2. Re: deleted and excluded records (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 13 Mar 2007 08:16:27 +0100 (CET) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] deleted and excluded records To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <52289.130.226.78.129.1173770187.squirrel(a)webmail.webhosting.dk> Content-Type: text/plain; charset=iso-8859-1 Continued discussion on this topic: The suggested solution I gave could be clarified: 1. Dates before year approx. 1700-1800 give problems in Analysis now, but obviously should not. Although as everyone probably know there is a shift around 15xx (I do not remember the exact year). 2. The suggestion: "SUGGESTION: Would it not be possible for Analysis to assign a standard valid value (e.g. 01/01/1900) to any invalid dates it comes across during the read process. " Will be used in the next build of analysis, since it is very easy to implement. Obviously with a message to the user. I think this can be done in 5 minutes of work time in the programming, whereas the optimal solution of showing variable/field name and record is a large job - could be 1-2 days of work, since the function controlling the date value is not knowing neither the name of the field nor the record. But I will add the issue to the work plan for a solution at some point. Regarding the "excluded" versus "deleted" is also easy. The user can control whether records deleted are read or not by: set read deleted=on set read deleted=off The change works only when reading the file, so if you change re-read the file again. e.g. set read deleted = off read myfile describe age set read deleted = on read myfile /close describe age // here records marked for deletion are included. off is default. There is an error in v1 b68 in relation to this setting, such that if you read the file with "set read deleted=off" and then do an "update", you will see the records marked for deletion. The error has been found and a solution will be shown in next test release. regards Jens Lauritsen ------------------------------ Message: 2 Date: Tue, 13 Mar 2007 09:43:23 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] deleted and excluded records To: epidata-list(a)lists.umanitoba.ca Message-ID: <44e66f9b0703130043t1911363ev728eaea2e245ef85(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Thanks for the quick response to my email. I would just like to clarify my suggestion re "excluded" and "deleted" records. The issue is not about whether one can control reading deleted records or not (as Jens' response implies). My point was that if one is not aware that records have been deleted, it would be more informative on reading the dataset in Analysis if the message specifically states that x records have been deleted (and are therefore excluded). Using the word "excluded" suggests that Analysis has a problem with some values and therefore has excluded the records. One could spend quite some time trying to identify the problem before realising that these are merely records that have been deleted. On the point of deleted records, is there some way in Analysis of identifying records which had been deleted (but which one has chosen to include in the analysis). In EpiInfo, there was a system variable RECDELETED. Also, in browse/update mode, deleted records were identifiable by an asterisk. This was very useful in trying to sort out why records had been deleted. Thanks again, Annemieke van Middelkoop ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 41, Issue 7 ******************************************* ___________________________________________________________________________ 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 1

deleted and excluded records and dates
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

Hi all, Interesting disccussion here. > 2. The suggestion: > "SUGGESTION: Would it not be possible for Analysis to assign a standard > valid value (e.g. 01/01/1900) to any invalid dates it comes across > during the read process. " > > Will be used in the next build of analysis, since it is very easy to > implement. Obviously with a message to the user. I think this can be > done in 5 minutes of work time in the programming, whereas the optimal > solution of showing variable/field name and record is a large job - > could be 1-2 days of work, since the function controlling the date value > is not knowing neither the name of the field nor the record. But I will > add the issue to the work plan for a solution at some point. In my view the problem with that solution is that if Analysis automatically changes all "invalid" dates to any standard missing value, it can be a problem if the user saves the changes in a new data file and deletes the old one. The message for the users should be VERY CLEAR. > I would just like to clarify my suggestion re "excluded" and "deleted" > records. The issue is not about whether one can control reading > deleted records or not (as Jens' response implies). My point was that > if one is not aware that records have been deleted, it would be more > informative on reading the dataset in Analysis if the message > specifically states that x records have been deleted (and are > therefore excluded). Using the word "excluded" suggests that Analysis > has a problem with some values and therefore has excluded the records. > One could spend quite some time trying to identify the problem before > realising that these are merely records that have been deleted. Maybe we can use a text similar to the one used by EpiInfo for Windows: "#### records loaded (deleted records excluded/included)" Still it makes no senese to display 100 times the same message saying that a record was excluded because of an invalide date if the user can not do anything. In my view one solution can be display, in adition to the previous message, another message saying: "#### records excluded because of quality checking with dates(or other reasons). TIP: sort ascending your data in any date variable and browse them to detect the problems" Pedro Arias

1 0

deleted and excluded records
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

Continued discussion on this topic: The suggested solution I gave could be clarified: 1. Dates before year approx. 1700-1800 give problems in Analysis now, but obviously should not. Although as everyone probably know there is a shift around 15xx (I do not remember the exact year). 2. The suggestion: "SUGGESTION: Would it not be possible for Analysis to assign a standard valid value (e.g. 01/01/1900) to any invalid dates it comes across during the read process. " Will be used in the next build of analysis, since it is very easy to implement. Obviously with a message to the user. I think this can be done in 5 minutes of work time in the programming, whereas the optimal solution of showing variable/field name and record is a large job - could be 1-2 days of work, since the function controlling the date value is not knowing neither the name of the field nor the record. But I will add the issue to the work plan for a solution at some point. Regarding the "excluded" versus "deleted" is also easy. The user can control whether records deleted are read or not by: set read deleted=on set read deleted=off The change works only when reading the file, so if you change re-read the file again. e.g. set read deleted = off read myfile describe age set read deleted = on read myfile /close describe age // here records marked for deletion are included. off is default. There is an error in v1 b68 in relation to this setting, such that if you read the file with "set read deleted=off" and then do an "update", you will see the records marked for deletion. The error has been found and a solution will be shown in next test release. regards Jens Lauritsen

1 1

READ statement / Invalid dates / How to handle dates in analysis
by epidata-list＠lists.umanitoba.ca 12 Mar '07

12 Mar '07

READ statement / Invalid dates / How to handle dates in analysis 1. I submitted my previous email concerning the READ statement because: - on reading a particular file, a list of some 20+ invalid dates was produced - followed by a message that there were x valid records and 10 records excluded from analysis. I assumed that the 10 records were excluded because of the invalid dates. Subsequently, I have discovered that there was no connection between the invalid dates and the excluded records! In fact, the invalid records were records which had been deleted. SUGGESTION: When records are excluded because they are deleted records, could the message use the words "Deleted records" rather than "Excluded records". Just to avoid any confusion! 2. To respond to Jamie's email (Invalid dates), some of the invalid dates had been entered by EpiInfo, but about half had been entered using EpiData. EpiData Entry has no problems accepting a date such as 12/03/206. (I have also tried 12/03/0206 which just immediately reverts to 12/03/206). Yet EpiData Analysis sees such a date as invalid. SUGGESTION: EpiData Entry and Analysis should be consistent with their interpretation of invalid dates. 3. To respond to Jens' email (How to handle dates in analysis), illegal dates are not the issue I am addressing. Illegal dates are not accepted by EpiData and will therefore not be an issue in Analysis. I am addressing legal dates which may have been entered incorrectly, e.g. 12/03/2006 inadvertently entered as 12/03/206. EpiData accepts this date. But Analysis does not accept it as a valid date. 4. Once the dataset with invalid dates has been read in Analysis, it is not possible to carry out any commands which might include such dates. BROWSE, LIST, SAVEDATA for example will not operate (unless one specifies variables excluding those which have invalid values). SUGGESTION: Would it not be possible for Analysis to assign a standard valid value (e.g. 01/01/1900) to any invalid dates it comes across during the read process. A message to this effect could be added to the list of invalid dates (with their variable names and record numbers). It is then up to the user to edit the invalid dates. But then at least Analysis will be able to carry out all commands. Many thanks, Annemieke van Middelkoop Pretoria, South Africa

1 0

How to handle dates in analysis
by epidata-list＠lists.umanitoba.ca 11 Mar '07

11 Mar '07

Clarification: Neither EpiData Entry nor EpiData Analysis can have date fields with illegal dates. E.g. February 29th is only allowed in leap years. Epi6 could save illegal dates and never controlled the data while reading for correct content. >From the beginning of EpiData all date fields were included as "true dates", meaning that there cannot be a date value which does not exist in the past or future. (dates before year 1600 can give problems) For EpiData Analysis this has given some users problems since it was difficult to see in which records the date problems were located if some dates were rejected. Also some old dates before year 1800 have not been accomodated fully in analysis, but this should be a minor problem, since we never or very rarely have data from that period. And if we do one could split the dates into day month and year parts as three variables, although this would remove the automatic validation of the content of the data. I suggest that we look at the possibility of implementing: > c. That, if neither a. nor b. is an option, more detail about the > 'invalid' dates (record number, variable name) is provided so that > they can be edited. since we cannot use an illegal date for anything. Analysis with incorrect dates makes no sense. Once we find a workable principle for this the same technical principle and list can include also names of variables/fields, which will be in conflict with internal functions, e.g. year, date or tab. -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Learning material in Portuguese
by epidata-list＠lists.umanitoba.ca 10 Mar '07

10 Mar '07

I added a link to the learning material in Portuguese on the Download page (www.epidata.dk/download.php) - thanks to the group in Rio Janeiro. It is good if users start experimenting with development of "WIKI" based notes and materials. You can do so by at the address www.epidata.org/wiki After some experimentation period and establishment of a responsible group for the Wiki a separation can be made btw. "official" materials and materials at the responsibility of users. regards Jens Lauritsen EpiData Association

1 0

INVALID dates
by epidata-list＠lists.umanitoba.ca 10 Mar '07

10 Mar '07

Dear Friend, Epi Analysis is a sensitive tool to detect the invalid dates that can be corrected. Of course these invalid dated can be prevented altogether by inserting date ranges in the check files also before data entry. Epi Analysis also detects the corrupted records in the file while READing it, which EPI6 was not able to do. Hence screening of dataset while loading is an important for data cleaning also and should be retained. I fully endorse the option c. suggested by you. Just like providing record numbers of corrupted records, the record with invalid dates should be listed with record number and if possible the date variable name also. With regards, Dr. Shavinder Singh

1 0

Re: [EpiData-list] invalid dates
by epidata-list＠lists.umanitoba.ca 09 Mar '07

09 Mar '07

While a solution that flags dates as invalid/missing will be useful, another strategy for dealing with the invalid dates is to import them as text and use the built-in functions to convert valid ones to dates. There is still a potential problem with finding the invalid date records, but you have an opportunity to do this on your own terms. I assume that the dates were imported somehow into a .rec file, as entry would not allow such dates. I don't recall whether import checks date validity, but it does other field types. The invalid dates can readily be checked using the validation capacity of EpiData Entry and .chk files. This may be the best way to do this, as a detailed report of errors is produced. I have run into this type of error importing EpiInfo files and reading .dbf files, but not working with .rec files that I had control over. Jamie > > I have several concerns about this approach. > 1. Most important, records with 'invalid' dates are excluded from > analysis (10 in this example). The fact that the 'invalid' dates are > likely to be incorrect is no reason to not be able to analyse the > records. > 2. READing a large dataset with many dates can be a very slow process. > 3. The output given by Analysis (as shown above) is not very useful. > Neither record numbers nor variable names are identified. > > I would like to suggest: > a. That dates are not checked at all during the READ process. The > analyst can look for incorrect dates in Analysis, relevant to the > content of the data. > OR > b. That the user can specify whether to check the dates or not on > READing a dataset. > OR > c. That, if neither a. nor b. is an option, more detail about the > 'invalid' dates (record number, variable name) is provided so that > they can be edited. > > Annemieke van Middelkoop > Pretoria, South Africa >

1 0

Learning material
by epidata-list＠lists.umanitoba.ca 09 Mar '07

09 Mar '07

Hello all, Sometime a go, I tried to find out some learning/teaching material for EpiData entry in portuguese. Unfortunately, I didnt find any. Since this year is the first year that I'll teach a class about computer program for clinical research to pos-graduation students, I decided to make a small material in portuguese. A sort of introductory step by step guide for beginners and some little more complex examples. If any would like to take a look, it is available at : http://www.ipec.fiocruz.br/materialdidatico/Aplicativos_pesquisa/2007/EpiDa… By -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

RE: EpiData-list Digest, Vol 41, Issue 2
by epidata-list＠lists.umanitoba.ca 09 Mar '07

09 Mar '07

I agree with the approach of Annenmieke van Middelkoop about 'invalid' records after "Read". Bernard Branger, Nantes, France __________________________________________________________________________ I have several concerns about this approach. 1. Most important, records with 'invalid' dates are excluded from analysis (10 in this example). The fact that the 'invalid' dates are likely to be incorrect is no reason to not be able to analyse the records. 2. READing a large dataset with many dates can be a very slow process. 3. The output given by Analysis (as shown above) is not very useful. Neither record numbers nor variable names are identified. I would like to suggest: a. That dates are not checked at all during the READ process. The analyst can look for incorrect dates in Analysis, relevant to the content of the data. OR b. That the user can specify whether to check the dates or not on READing a dataset. OR c. That, if neither a. nor b. is an option, more detail about the 'invalid' dates (record number, variable name) is provided so that they can be edited. Annemieke van Middelkoop Pretoria, South Africa ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 41, Issue 2 *******************************************

1 0

READ statement
by epidata-list＠lists.umanitoba.ca 07 Mar '07

07 Mar '07

When READing a dataset in Analysis, the program checks all dates in the dataset for 'valid' dates. For example, on reading a dataset DATA.REC, the following message is displayed: . Read Loading data C:\TEST\DATA.REC, please wait.. invalid year 1000, month 1, day 17 Error field DLOPV record: 1401 invalid year 5001, month 6, day 18 invalid year 200, month 1, day 16 invalid year 199, month 8, day 8 invalid year 200, month 2, day 2 invalid year 2200, month 12, day 3 invalid year 202, month 12, day 10 invalid year 202, month 12, day 10 invalid year 200, month 12, day 4 invalid year 200, month 12, day 4 invalid year 202, month 12, day 19 invalid year 603, month 5, day 24 invalid year 603, month 6, day 24 invalid year 199, month 1, day 15 invalid year 203, month 8, day 23 invalid year 203, month 8, day 23 invalid year 993, month 1, day 1 invalid year 199, month 9, day 19 invalid year 802, month 1, day 17 invalid year 199, month 4, day 18 invalid year 996, month 7, day 17 invalid year 206, month 7, day 31 invalid year 200, month 5, day 11 Errors reading data File name : C:\TEST\DATA.REC Fields: 222 Total records: 10460 Valid records: 10450 Excluded records: 10 I have several concerns about this approach. 1. Most important, records with 'invalid' dates are excluded from analysis (10 in this example). The fact that the 'invalid' dates are likely to be incorrect is no reason to not be able to analyse the records. 2. READing a large dataset with many dates can be a very slow process. 3. The output given by Analysis (as shown above) is not very useful. Neither record numbers nor variable names are identified. I would like to suggest: a. That dates are not checked at all during the READ process. The analyst can look for incorrect dates in Analysis, relevant to the content of the data. OR b. That the user can specify whether to check the dates or not on READing a dataset. OR c. That, if neither a. nor b. is an option, more detail about the 'invalid' dates (record number, variable name) is provided so that they can be edited. Annemieke van Middelkoop Pretoria, South Africa

1 0

Re: [EpiData-list] Entering time and date for outbreaks
by epidata-list＠lists.umanitoba.ca 28 Feb '07

28 Feb '07

Hi Charity Thanks very much for your formula. Its sounds really good. I had a go at putting it in a check file. Following through your example below 'Diatime' is my 'vtime2' and 'diadate' is my vdate2. I thought I would start off slowly by seeing if I coudl calculate Vhours2. I created a new field called Vhours2 in my rec file and then I put the following code into the check file. DIATIME AFTER ENTRY LET VHOURS2=INT(DIATIME)+(FRAC(DIATIME)/0.6)+(DIADATE*24) END END Epi accepted the code but nothing appears in the vhours2 field when I enter information in the diadate and diatime fields. Can you see what I am doing wrong? thanks Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 26/02/2007 7:24 p.m. >>> Hello Chrsitine, I prefer to enter times as a decimal field, i.e. ##.##. I can then put checks in place to make sure the minutes are in correct time format e.g. IF Frac(vtime) > 0.59 THEN .... Based on this decimal 24 hour time format, I have a formula which you can use to calculate the difference in hours between two time and date combinations. Assume that your first time and date are vtime1 and vdate1, and your second time and date are vtime2 and vdate2: First calculate the number of hours (since 31st December 1899) for both time and date combinations (store them as vhours1 and vhours2) using the following formulae: vhours2=Int(vtime2) + (Frac(vtime2)/0.6) + (vdate2*24) vhours1=Int(vtime1) + (Frac(vtime1)/0.6) + (vdate1*24) And then you can just calculate the time difference /incubation period into a different variable! timediff=vhours2-vhours1 You could also have done something similar and perhaps simpler using EpiData's Time2Num function which will convert a decimal time into a number between 0 and 1 representing a fraction of a day - I just prefer to work with hours. To explain the hours calculation formula for you (only need to read below if you care how the formula works): Int(vtime) takes the integer part of the time, and Frac(vtime) takes the fractional part of the time. These are separated so Frac(vtime) alone can be converted from minutes into fraction of an hour (e.g. from 0.30 to 0.50). The date integer (representing the number of days since 31 Dec 1899) is then multiplied by 24 to get the number of hours since 31 Dec 1899. This 1899 date is relevant only because it is how EpiData stores the date as an integer - we do not have to worry about this because we only care about the difference between the two dates. Hope this helps! Charity Charity Jenkins Data Processing Officer Centre for Behavioural Research in Cancer The Cancer Council Victoria http://www.cancervic.org.au/cbrc<https://webmail.accv.org.au/exchweb/bin/redir.asp?URL=http://www.cancervic.…> On 2/26/07, epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca> wrote: > > Hello everyone > > I am after advice about the best way to record time and date > information when collecting information about food poisoning outbreaks, > given epidata does not have a time/date field. We want this information > to estimate incubation periods, in order to get clues about the likely > illness. > > Incubation > Incubation = time from when someone is exposed to the time they become > unwell. > For example someone may eat a buffet meal at 7pm on 21 February and > become unwell at 1am on 22 February = incubation of 6 hours. > > Current method > At the moment we: > a) enter information in two fields. OnsetDay is recorded in a date > field, and onsettime in a numeric field (####) > b) list the two fields (using epi info) to view the information > c) calculate incubation manually. > > Is there a better/easier way to do this? Also what is the recommended > way for entering 24 clock time - should 7.30pm be 1930 or 19.30 > > thanks very much > > Christine > > > > Christine Roseveare > Analyst > Regional Public Health > 570 9194 > 027 495 9671 > > > > > -- > 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 ** > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > -- 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 **

1 4

work-arounds for data entry on more than one computer
by epidata-list＠lists.umanitoba.ca 28 Feb '07

28 Feb '07

Epi-Data users: What strategies have you used to get around the limitation of only being able to input the data on one computer? We are thinking of splitting the file into two - with Type A respondents in one file/on one computer and Type B respondents in another file/on a different computer and then combining the resulting datasets in Stata. Will this work? Are there other/better strategies? Thanks, Kristine Hopkins khopkins(a)prc.utexas.edu

1 3

Re: [EpiData-list] Entering time and date for outbreaks
by epidata-list＠lists.umanitoba.ca 27 Feb '07

27 Feb '07

Hi Charity I have tried adapting that check code to my file, just changing the field names as necessary, and it worked perfectly. How exciting to see my incubation times popping up effortlessly! Thanks very much for that. Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 27/02/2007 12:24 p.m. >>> Hi Christine, I think I forgot to mention that for vhours to be a field it needs to be fairly large as the number of hours since 1899 is a big number. Also it needs to have two decimal places. I used a nine digit number plus two decimals when I tried it. Once you know you have it working you could calculate the difference directly into the timediff field (which also needs two decimal places but does not need to be nearly as large) without having to store it in vhours1 and vhours2 first, to save having meaningless numbers lying about. Also, I didn't use the word "LET" - not sure if this makes any difference. And the number will not calculate until all the fields in the formula are filled, i.e. if you put the code in the time field but do not yet have anything in the date field, it will not work. I put the full calculation in all fields so that any time a field was updated the difference would update also. I will paste what I did below and hopefully it will clear anything else up I've forgotten to mention! Let me know how you go. Thanks, Charity Below is the text from the qes file I used to test my formulae. vtime1 ##.## vdate1 <dd/mm/yyyy> vhours1 #########.## vtime2 ##.## vdate2 <dd/mm/yyyy> vhours2 #########.## timediff ####.## And the code I used in my chk file (for the second time and date only, to save space): vtime2 MUSTENTER AFTER ENTRY IF (vtime2 < 0) OR (vtime2 > 23.59) OR (Frac(vtime2) > 0.59) THEN HELP "Enter a valid time" GOTO vtime2 ENDIF vhours2=Int(vtime2) + (Frac(vtime2)/0.6) + (vdate2*24) vhours1=Int(vtime1) + (Frac(vtime1)/0.6) + (vdate1*24) timediff=vhours2-vhours1 END END vdate2 MUSTENTER AFTER ENTRY vhours2=Int(vtime2) + (Frac(vtime2)/0.6) + (vdate2*24) vhours1=Int(vtime1) + (Frac(vtime1)/0.6) + (vdate1*24) timediff=vhours2-vhours1 END END vhours2 NOENTER END Charity Jenkins Data Processing Officer Centre for Behavioural Research in Cancer The Cancer Council Victoria http://www.cancervic.org.au/cbrc<https://webmail.accv.org.au/exchweb/bin/redir.asp?URL=http://www.cancervic.…> On 2/27/07, epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca > wrote: > > Hi Charity > > Thanks very much for your formula. Its sounds really good. I had a go > at putting it in a check file. Following through your example below > 'Diatime' is my 'vtime2' and 'diadate' is my vdate2. I thought I would > start off slowly by seeing if I coudl calculate Vhours2. I created a new > field called Vhours2 in my rec file and then I put the following code > into the check file. > > > DIATIME > AFTER ENTRY > LET VHOURS2=INT(DIATIME)+(FRAC(DIATIME)/0.6)+(DIADATE*24) > END > END > > Epi accepted the code but nothing appears in the vhours2 field when I > enter information in the diadate and diatime fields. Can you see what I > am doing wrong? > > > thanks > > Christine Roseveare > Analyst > Regional Public Health > 570 9194 > 027 495 9671 > > -- 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 **

1 0

date time difference and age calculation
by epidata-list＠lists.umanitoba.ca 26 Feb '07

26 Feb '07

In writing documentation, help file, how to's, faq solutions etc. the problem is not so much to give solutions, but how to write solutions in a way where users actually find them. For the age calculation if you look in EpiData Entry file under "time functions" you will see: ................... LET INT1=(ROUND(INT((TODAY-D1)/365.25)) Calculates the age of a person whose date of birth was entered in D1. Round is needed to convert the result of the calculation from a real number to a integer number. ................... and if you look in the help file for entry under "time functions" or "time about" or "Age on specific date" one example clearly shows how to do the calculations questioned on the list recently. The time example is also included with the installation of the Entry programme. I am not saying this to "point fingers" at the recent questioning on this list, but to underline that despite the amount of documentation, field notes, help files etc. it is my firm conviction that there is a definite need for a lively help line. For users following the Stata list or having used the very large volume of documentation and help facilities for Stata (www.stata.com) you will notice that also on that list questions shows up on issues actually explained but users not finding them. In other words: We can and should include obvious "often asked issues" in documentation, but even if we do, there will be someone not finding this information. Which is exactly why a large user base where someone find and take the time to answer these questions on the EpiData list is very important. Regards Jens Lauritsen EpiData Association

1 0

Entering time and date for outbreaks
by epidata-list＠lists.umanitoba.ca 26 Feb '07

26 Feb '07

Hello everyone I am after advice about the best way to record time and date information when collecting information about food poisoning outbreaks, given epidata does not have a time/date field. We want this information to estimate incubation periods, in order to get clues about the likely illness. Incubation Incubation = time from when someone is exposed to the time they become unwell. For example someone may eat a buffet meal at 7pm on 21 February and become unwell at 1am on 22 February = incubation of 6 hours. Current method At the moment we: a) enter information in two fields. OnsetDay is recorded in a date field, and onsettime in a numeric field (####) b) list the two fields (using epi info) to view the information c) calculate incubation manually. Is there a better/easier way to do this? Also what is the recommended way for entering 24 clock time - should 7.30pm be 1930 or 19.30 thanks very much Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- 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 **

1 1

Current age calculation
by epidata-list＠lists.umanitoba.ca 25 Feb '07

25 Feb '07

Thank you Jamie for today mornings message. I was confused by the complex syntax of American date selection This solution was also obtained over the week end while working on a Fedora Linux machine on which Epidata entry and Analysis latest versions were installed.. Simple formulas, which produced wonders, are given below; define interval ### let interval=wdate - dbirth *calculate the interval in days using American dates. define interval ### let interval=(wdate dbirth)30.44 results in a error Data type mismatch define interval ###.# let interval=(wdate dbirth)/30.44 calculates the interval months using American dates. Epi Analysis accepts float type variables as suggested by Gillis Delmas. However round or integer prefix do not help. The output is produced in decimals and not rounded to the nearest figure. I wanted to obtain the current age hence did not include this formula in Epidata Entry as suggested by Pedro Emmanuel Brasil One request to Jens; Such examples should be included in the help file in the form of simple FAQs, which can save hours or even days of Epi Analysis Users (beginner and even experienced!!). Thank you friends for your timely help Much appreciated Dr. Shavinder Singh

1 0

Age Calculation
by epidata-list＠lists.umanitoba.ca 24 Feb '07

24 Feb '07

Dear Friends, Thanks for your time and effort. I tried in so many many ways. Nothing is working. I am attching a sample file with following PGM. The error message obtained are shown in the next line beginning with "*" Kindly help. With regards, Dr. Shavinder Singh *Try.pgm cls close set echo=off set replace logfile=on read "d:\work\amdate.rec" define wdateu <DD/MM/YYYY> LET wdateu=wdate define dbirthU <DD/MM/YYYY> LET dbirthU=dbirth logopen "TRY.PGM OUTPUT FILE" /CLOSE define interval ### let interval=date("wdateu","dmy")- date("dbirthu","dmy") list Interval *Error message - (NO RESPONSE) define interval2 ### let interval2=Integer(date("wdate" - "dbirth")) list Interval2 *Error message Access violation at address 006C91D6 in module 'EPIDATASTAT.EXE'. Read of address FFFFFFFF define interval3 ### let interval3=Integer(date("wdate") - date("dbirth")) list Interval3 *Error message - (NO RESPONSE) define interval4 ### let interval4=Integer(round(date("wdate","mdy")- date("dbirth","mdy"))) list Interval4 *Error message -(NO RESPONSE) close

1 1

<IDNUM> in statusbar!!
by epidata-list＠lists.umanitoba.ca 24 Feb '07

24 Feb '07

Hi Jamie, thanks for helping me out with the <IDNUM> problem! You also answered my other question about how to show the <IDNUM> in the statusbar. Bye, Ben.

1 0

showing <IDNUM> in statusbar
by epidata-list＠lists.umanitoba.ca 23 Feb '07

23 Feb '07

Hi all, Thanks Juergen for your valuable tip to use respnumber TYPE SATUSBAR end to show the value of field 'respnumber' in the statusbar during data entry! I'm quite unexperienced in using epidata and didn't know of this nice feature. Still I have a question. Is it also possible to show the value of the automatic IDNUM field in the statusbar? The reason for this question is that I do not want to enter the respondent number myself, but would like to use the automatically generated IDNUM instead. More or less related is the next question. If one uses the following two lines (look quite meaningless, I agree) <IDNUM> <IDNUM> in the QES file, then why does, during data entry, the first <IDNUM> always stay 1 - even after entering the second, third etc. case - while the second <IDNUM> is adjusted to the correct case number, i.e., the one who's data are currently being entered? Bye and thanks for any help, Ben.

1 0

Showing IDNUM at top of 2 or more entry screens
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 of the screen, 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

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

EpiData-List: List index out of bounds
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

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.

1 0

BUG REPORT : minus sign for MISSINGVALUE with more
by epidata-list＠lists.umanitoba.ca 15 Feb '07

15 Feb '07

It is not a bug, DATE is a reserved name, you cannot use it as a field name. Furthermore, there is nothing like "## ## ###" for a field definition, the definition for dates is <dd/mm/yyyy> (if you choose European date format) Regards, Hans Hello, I noticed a strang bug in Epidata Entry when I use the '-' sign to input=20 a MISSINGVALUE in a field. I created three fields on one line to enter a date with incomplete value = : Date ## ## #### Age ## Sexe # In the check file I used the following DATE MISSINGVALUE 99 END DATE1 MISSINGVALUE 99 END DATE2 MISSINGVALUE 9999 END -- 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

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

14 Feb '07

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

1 0

BUG REPORT : minus sign for MISSINGVALUE with more than one field on the same line
by epidata-list＠lists.umanitoba.ca 14 Feb '07

14 Feb '07

Hello, I noticed a strang bug in Epidata Entry when I use the '-' sign to input a MISSINGVALUE in a field. I created three fields on one line to enter a date with incomplete value : Date ## ## #### Age ## Sexe # In the check file I used the following DATE MISSINGVALUE 99 END DATE1 MISSINGVALUE 99 END DATE2 MISSINGVALUE 9999 END When I type a '-' followed by enter or tab in the field - DATE, the focus goes to DATE2. - DATE1, the focus goes to the field AGE - DATE2, the focus goes to the field SEXE This only happens when I use the minus sign and when there are several fields on the same line. -- Jean-Marie Chrétien CHU d'Angers - Centre de Recherche Clinique 4 rue Larrey 49933 ANGERS Cedex 9 Tel : 02.41.35.59.76 Fax : 02.41.35.59.68

1 0

��dryangyun��
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

where is your master websites,thank you

1 0

sorting rec file
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

"Is there any possibility to sort the file without exporting the data?" Within EpiData Entry: Define the ID field as a key ID key unique end then after entering all data, export data (#6 in toolbar) to EpiData file and mark "use index as sort order" In EpiData Analysis read myfile sort id savedata newfile copyfile myfile.chk newfile.chk Regards Jens Lauritsen EpiData Association

1 0

Sorting of rec File ?
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

Dear all, Because of our study design and the randomization procedure in our trial the ID can not be entered in the correct order. Later on it would be more convenient to enter data in the order of the ID. Is there any possibility to sort the file without exporting the data? Thanks in advance, Markus

1 0

QES with two colmns?
by epidata-list＠lists.umanitoba.ca 12 Feb '07

12 Feb '07

Hello all, As times goes by, Im getting the idea that data entry is an art more then a science. Many ptojects have to keep a lot of fields in the paper form and at the end the paper is not big enough to have them all. The consequence is that the QES file should be as similar as possible with paper forms. These last couple weeks Im tryin to make a QES file with tow columns but I cant get to straight up the second column in the REC file. When I make the QES I line up the second by hand, since menu EDIT\line field comand seems to work fine only with one column. But whe the REC file generated the variables, labels and filds of the second column are not align as the QES file (sometimes the labels are uncomplete). Exemple: QES p71 RECUPRACAO # p72 SEQUELA # p73 OBITO# p74 CAUSA MORTIS <A > p75 NECESSITOU INTERNACAO # p76 PROLONGOU A INTERNACAO # p77 MEDICAMENTO SUSPENSO # p78 HOUVE MELHORA # p79 POSOLOGIA ALTERADA # p710 NECESSITOU TRATAMENTO ADICIONAL # p711 HOUVE REEXPOSICAO # p712 REACAO REAPARECEU # p713 PRIMEIRA NOTIFICACAO # p714 NOTIFICADO PARA INDUSTRIA # -- Exemple of resulting REC. p71 RECUPRACAO # p72 SEQUELA # p73 OBITO# p74 AUS<A > p75 NECESSITOU INTERNACAO # p76 PROLON# p77 MEDICAMENTO SUSPENSO # p78 HOUVE MELHORA # p79 POSOLOGIA ALTERADA # p710 NECESSITOU TRATAMENTO ADICIONAL # p711 HOUVE REEXPOSICAO # p712 REACAO REAPARECEU # p713 PRIMEIRA NOTIFICACAO # p714 NOTIFICADO PAR # The most amazing to me is that I´ve worked on some QES files with tow columns before and sometimes it works fine and sometimes it just does not work. At this file for example, a few segments work fine and some dont. Any tip to work around this matter? Thank you, Pedro Emmanuel Brasil Abraço forte e que a força esteja com você, Pedro Emmanuel

1 2

Web Site problem corrected. - new graph command ready v2 b106 analysis
by epidata-list＠lists.umanitoba.ca 08 Feb '07

08 Feb '07

There has been a problem with the website download principle on www.epidata.dk during the last 24 hours. The problem has been resolved, but affected downloads as well as the "Mantis" documentation system. In the latest test build for analysis (b106) a new graph type was included, called "dplot" This will plot a cumulative frequency curve for a given variable. Example of usage: * Show a cumulated frequency percent plot for a variable (here height): dplot height dplot height /yline=50 - the values contained are the same as those showed at : freq height /CP * With option /P: Show a probit plot. * If the data are distributed as Gaussian (Normal) then a probit plot will show data on a straight line. X axis: Midpoints of all data. (e.g. if x = 1 3 ...., then first observation is at x=(1+(3-1)/2)=2 Y axis: The cumulated percentage is converted to probability and graphed as the inverse normal probability dplot height /P There is an unresolved issue with small numbers (incorrect showing) Regards Jens Lauritsen

1 0

How to edit a graph and set further options
by epidata-list＠lists.umanitoba.ca 07 Feb '07

07 Feb '07

Gilles responded correctly on the question of further defining graph options: Try the command: SET GRAPH EDIT = ON which will work in v1 of analysis In the test version v2.0 the "set graph edit" is not allowed. Instead you have to add /edit to any graph command. e.g. scatter v1 v2 /edit But many users will (I assume) use the dialogs from the workprocess toolbar. And in these the /edit is by default added to all graph commands. Regards Jens Lauritsen EpiData Association

1 2

Editing graphs using Epidata analysis
by epidata-list＠lists.umanitoba.ca 06 Feb '07

06 Feb '07

Hallo, I downloaded the test version of the latest Epidata analysis sofware.My problem is;How do I edit a graph so that the percentages appear in each bar or in pie chart. I think I have communicated. Thanks Caleb Ouma Ongong'a +254721-953790, +254733890191 P.O Box 756556-00200 Nairobi-Kenya "Remember that happiness doesn't depend on what you are or on what you possess, but only on how you think." --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar.

1 1

Today autofield
by epidata-list＠lists.umanitoba.ca 05 Feb '07

05 Feb '07

Hello all, I have been reading the epidata list for while but never tryed to send anything so far. It has been a while that I cant get the field <d/m/y-today> work at enter data. I´ve tryed other today autofields but none have worked so far. When I edit chek, this field appears to be working because the today date is there and field is not open for edition. However, when I open the enterdata, the field is always empty and, of course, I cant enter the date in there. My work around, although not as efficient, is to use the <dd/mm/yyyy> with the REPEAT comand in the check file. Is it some sort of bug or Im doing something wrong? Best regards, may the FORCE be with you all, Pedro Brasil Instituto de Pesquisa Clinica Evandro Chagas Fundação Oswaldo Cruz Av. Brasil 4365, Rio de Janeiro, Brasil -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 1

How to get test version of EpiData Analysis v2
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Point your browser to : Http://www.epidata.dk/testing.php and click on: "Complete Setup" or click directly on this link: http://www.epidata.dk/php/downloadc.php?file=setupepidatastattest.exe Notice that test versions should always be used with caution until they are released from the official download page at http://www.epidata.dk/download.php Kind regards Jens Lauritsen EpiData Association

1 0

Re: [EpiData-list] Validation duplicate files
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Hi Charity and Lars: There are two ways for duplicate data entry: 1) independent of sequence 2) dependent on sequence 1) If you use a field with unique identifier, you can enter the data independently of sequence twice, and then compare the two files later on that unique identifier. In this instance two data entry groups can enter add the same time part A and part B and then switch for second entry. 2) You can use the "Tools" "Prepare Double Entry Verification". If you do not tick and choose the option "Match records by field" (and choose the Unique identifier), then the second entry will by default follow the record number, and thus sequence matters. If you choose that option, the first data entry group will still have to await completion by the first data entry group. As Charity says, it is critical in any case to have a truly unique identifier which can by assured by KEY UNIQUE. Seemingly, Lars, you did not have that. You must thus identify the records with duplicate identifiers and or missing identifiers in both files, mark them for deletion (but not packing" and then compare. You deal then separately with the problematic records in both files, most simply perhaps by reentering them properly and independently in both files. Regards, Hans Hello Lars, I just did a small test of this to make sure, and the ordering/sequence of IDs in the two files does not make a difference when Validating Duplicate Files. What will cause a problem is if there is a duplicated ID in one of your two files - are you sure that the Case IDs are unique? You should have "KEY UNIQUE 1" included in your .chk file for the ID variable to ensure this. Kind regards, Charity On 2/1/07, epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca> wrote: Dear Epidata_list, I'm a new member of this list and a fairly new user of the Epidata software. In attempting to validate duplicate files not entered in same sequence by two observers I have difficulty in performing the test under documebt/validate duplicate files. Attempting to perfom the test with a selected key field of case-id an error is given; "Duplicate keys found" and the validation is terminated. Is it possible to perform a comparison of the two datasets despite the fact that the registrations are not performed in same sequence with regard to registration of the observations? Siincerely, Lars -- 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

Testing Epidata Analysis V2.0
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Hi, How can i have an Epidata Analysis V2.0 for make some testing? 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 ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Jeudi, 1 Février 2007, 19h15mn 13s Objet : EpiData-list Digest, Vol 40, Issue 1 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. Tables in 2.0 R. 1 Build 104 of Epidata Analysis (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Thu, 1 Feb 2007 08:04:10 -0800 (PST) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Tables in 2.0 R. 1 Build 104 of Epidata Analysis To: epidata-list(a)lists.umanitoba.ca Message-ID: <398980.61861.qm(a)web32105.mail.mud.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Hi, Thank you for introducing the test version of Epidata Analysis V2.0. I tried to do some tables using it but no infrential statistics is performed. Just an r*c table is shown. Even for "Means" command, just descriptive statistics is shown. Thanks Reza ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 40, Issue 1 ******************************************* ___________________________________________________________________________ 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

Validation duplicate files
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

Dear Epidata_list, I'm a new member of this list and a fairly new user of the Epidata software. In attempting to validate duplicate files not entered in same sequence by two observers I have difficulty in performing the test under documebt/validate duplicate files. Attempting to perfom the test with a selected key field of case-id an error is given; "Duplicate keys found" and the validation is terminated. Is it possible to perform a comparison of the two datasets despite the fact that the registrations are not performed in same sequence with regard to registration of the observations? Siincerely, Lars

1 1

Re: Release of EpiData Analysis v2.0 for testing
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

As announced a short while back the module is now available for testing. A short example should help users getting started on the test. 1. Expect that some/many set commands have changed. E.g. Obsolete ones in version 2: Set statistics, set percentages, set table reverse etc 2. You only get what you ask for. e.g.: tables v1 v2 // will only give the counts tables v1 v2 /R // will give row percentages (column:/C, total: /T) tables v1 v2 /T /EX // will give a chi square test and with /EX also exact tests for 2x2 tables tables v1 v2 v3 /T /EX // will do a stratified analysis with overall exact testing as well. tables v1 v2 v3 v4 /OA //will make a condensed outbreak analysis table tables v1 v2 /SD // will sort descending instead of the default ascending sort on row and column tables v1 v2 /SRAT // will sort ascending on the row total /SRDT would be descending 3. replacement for epitables or etab will be typically (to have highest value as case and exposure): tables v1 v2 v3 /sd /t Many aspects are not final yet - notice it is a test build, e.g. some issues remain on medians in SPC graphs. Therefore the front page also states: Notice - this is a premature test build - only for experienced test persons ! regards Jens Lauritsen EpiData Association

1 0

EpiData Analysis: testing of version 2.0.1.104
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

Public testing of version 2 of EpiData Analysis can now begin. A lot of work has been done to reshape internal parts of EpiData Analysis. All users are now encouraged to participate in the testing. A system of comparing estimates, counting with results of Stata or Epi6 is applied. Currently the system contains around 1000 different tests. But maybe the system is not taking care of all problems, therefore user tests are also important. A complete list of changes is shown at http://www.epidata.dk/analysisversioninfo.htm. Main points are: Output is simplified. You only get what you ask for. To get more add options (e.g. /T) to the command Tables Extended (sorting, percentages, weights, outbreak) Metadata commands: missingvalue, labelvalue, rename Outbreak analysis: "tab outcome exposure variables /oa" "epicurve datevar outcome group" The test version is placed at: Http://www.epidata.dk/testing.php Please discuss the new version on this list. If you find definite bugs report to http://www.epidata.dk/php/mantis, where all development is documented. .............................................................. Regarding the discussion last week of differences btw. open-source and free software. As announced earlier a "master plan" for rewriting all EpiData Software to Open-Source as well as platform independence is part of the general development plan for EpiData. Releasing software as open-source makes no sense if the structure and content of the product is not sufficiently modular to allow for several independent development lines. Someone might disagree with me on this, but knowing how fragile software development is and seing the increased requirements for documentation and quality assurance I am assured that a controlled situation is preferable at this point in time. For almost all end users having a stable, quality assured software line is more important than having access to independent and possibly confusing development. But there should be no doubt that the aim is at an appropriate time to release the product source-code as open-source. Should anyone have a lot of energy or time to add to the project there are many issues needing assistance, e.g. answering questions on the epidata-list, assisting in sorting incoming mails to the help line, releasing mails for the epidata-list coming from un-subscribed persons, creating a FAQ collection such as that running for Stata at http://www.stata.com/support/faqs/ or joining a group running a wiki for EpiData, which could contain the FAQ. A start of this can be seen at www.epidata.org/wiki, but will not be announced before such a group has been established (A coordinator has been found). Notice also that for EpiData Entry users can develop their own CHK file commands. Modules for doing so (source code and examples) are found on http://www.epidata.dk/documentation.php .............................................................. Kind regards Jens Lauritsen EpiData Association

1 0

Tables in 2.0 R. 1 Build 104 of Epidata Analysis
by epidata-list＠lists.umanitoba.ca 01 Feb '07

01 Feb '07

Hi, Thank you for introducing the test version of Epidata Analysis V2.0. I tried to do some tables using it but no infrential statistics is performed. Just an r*c table is shown. Even for "Means" command, just descriptive statistics is shown. Thanks Reza ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/

1 0

EpiData-list
by epidata-list＠lists.umanitoba.ca 24 Jan '07

24 Jan '07

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

1 0

[EpiData-list] Importing other file formats (eg SPSS) to create REC, CHK and QES files
by epidata-list＠lists.umanitoba.ca 23 Jan '07

23 Jan '07

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

1 6

command labelvalue in analysis
by epidata-list＠lists.umanitoba.ca 22 Jan '07

22 Jan '07

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

1 0

Bug of Unique Key Field
by epidata-list＠lists.umanitoba.ca 22 Jan '07

22 Jan '07

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

1 0

Interval of Confiance
by epidata-list＠lists.umanitoba.ca 22 Jan '07

22 Jan '07

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

1 0

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

String functions
by epidata-list＠lists.umanitoba.ca 11 Jan '07

11 Jan '07

Hello Epidata Listers. My colleague and I are new to the data entry development game and can't figure out the string functions. Our study id is a combination of one letter and 3 numbers. I'd like for the letter to always be capitalized. It seems that the following might be appropriate somehow: function Upper(S: string): string Returns a string containing the same text as S, but with all letters converted to upper case. but I don't understand how it works. Where do I put the function? Do I replace "S" with the variable name "id"? I've tried several variations but since I don't understand the logic, I don't know how to debug my syntax errors. I'd appreciate any help you could give! Thanks, Kristine ------------------------------------- Kristine Hopkins, Ph.D. Population Research Center 1 University Station, G1800 Austin, TX 78712 ph: 512.471.8313 fax: 512.471.4886

1 1

(sin asunto)
by epidata-list＠lists.umanitoba.ca 10 Jan '07

10 Jan '07

1 0

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

09 Jan '07

Once again This syntax work when data entered to one field and a second field being automaticaly filled up. What is the syntax for a following third field (ATC code) to be filled after the entering into the first field??? The CHK file of my qustionnaire (MedicineQues.CHK): MedNvn MUSTENTER COMMENT LEGAL MedGenATC.rec SHOW TYPE COMMENT MedGen END MedGen NOENTER END The CHK file of the Brand-Generic-ATC database (MedGenATC.CHK): MedNvn KEY 1 END MedGen KEY 2 END My QES file (MedicineQues.QES): MedNvn the name of the Drug ___________________ MedGen The Generic name ___________________ MedATC The ATC code _____________ AnyFild Any field # and my REC of the Brand-Generic-ATC database (MedGenATC.REC): (I took only 6 cases for illustration) MedNvn Aspirin MedGen acetylic salicylic acid n02ba01 MedNvn Beuron MedGen acetaminophen n02be01 MedNvn Efferalgan MedGen acetaminophen n02be01 MedNvn Panadol MedGen acetaminophen n02be01 MedNvn Paralen MedGen acetaminophen n02be01 MedNvn Tyelenol MedGen acetaminophen n02be01 *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 2

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

08 Jan '07

The CHK file of my qustionnaire (MedicineQues.CHK): MedNvn MUSTENTER COMMENT LEGAL MedGenATC.rec SHOW TYPE COMMENT MedGen END MedGen NOENTER END The CHK file of the Brand-Generic-ATC database (MedGenATC.CHK): MedNvn KEY 1 END MedGen KEY 2 END My QES file (MedicineQues.QES): MedNvn the name of the Drug ___________________ MedGen The Generic name ___________________ MedATC The ATC code _____________ AnyFild Any field # and my REC of the Brand-Generic-ATC database (MedGenATC.REC): (I took only 6 cases for illustration) MedNvn Aspirin MedGen acetylic salicylic acid n02ba01 MedNvn Beuron MedGen acetaminophen n02be01 MedNvn Efferalgan MedGen acetaminophen n02be01 MedNvn Panadol MedGen acetaminophen n02be01 MedNvn Paralen MedGen acetaminophen n02be01 MedNvn Tyelenol MedGen acetaminophen n02be01 *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 0

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

07 Jan '07

*** *** *** Comments to the suggested procedures: Regarding Jens Lauritsens' comment- I am working with a great number of 'brand names' of about 3.000. It will be a very big CHK file and a lot of work to do to arrange the file. I did not tried the model. As to Hans' comment- I tried the model and used the following syntax in the MedicineQues.CHK file: MEDNVN MUSTENTER COMMENT LEGAL AutoFillMedGenATC.rec SHOW TYPE COMMENT MedGen END MedGen NOENTER END My NameGenericATC.CHK looked like this: MedNvn KEY 1 END GenNvn KEY 2 END My MedicineQues.QES file looked like this: MedNvn the name of the Drug ___________________ MedGen The Generic name ___________________ MedATC The ATC code _____________ and my NameGenericATC.REC looked like this: MedNvn Aspirin MedGen acetylic salicylic acid n02ba01 MedNvn Beuron MedGen acetaminophen n02be01 MedNvn Efferalgan MedGen acetaminophen n02be01 MedNvn Panadol MedGen acetaminophen n02be01 MedNvn Paralen MedGen acetaminophen n02be01 MedNvn Tyelenol MedGen acetaminophen n02be01 However, I could not find out to get the ATC codes to appear on the MedATC field.

1 1

Generic and brand names
by epidata-list＠lists.umanitoba.ca 03 Jan '07

03 Jan '07

Make a QES files with three fields: brandname ___________ genername ___________ otherfield _ Make your CHK file: brandname MUSTENTER COMMENT LEGAL brandgeneric.rec SHOW TYPE COMMENT genername END genername NOENTER END otherfield MUSTENTER END In the field "brandname" you refer to another REC file "brandgeneric.rec". This latter REC files has 2 fields: brand ________ generic ________ and the BRANDGENERIC.CHK file must be: brand KEY 1 END generic KEY 2 END This presumes that you have imported the list of brandnames with the corresponding generic name into the BRANDGENERIC.REC file, e.g. brand Aspirin generic acetylic salicylic acid brand Beuron generic acetaminophen brand Efferalgan generic acetaminophen brand Panadol generic acetaminophen brand Paralen generic acetaminophen brand Tyelenol generic acetaminophen If the data entry person starts entering, the list will show as a labelblock and starting writing will go to the brandname, once reached, ENTER suffices, the brandname is entered into the field BRANDNAME and the field GENERNAME is automatically completed. Hope this helps, Hans Just arrived on the list. I am about to construct a questionnaire on Epi-Data. Never worked with = it before, but it seems to be quite straight forward simple, as long as = the requirements are simple However, for some years ago I was constructing similar questionnaire on = the Paradox DB. It was possible to simplify the type work by cross = tabulating. e.g. Instead of typing the patients address, telephone number, and so = forth, these data was auto-filled in the database that was linked to = another database with the mentioned informations. I create a medication questionnaire. As the patients normally knows the = 'trade names', and I am interested in the 'generic names' (as many of = you knows e.g. one of the most used pain killers acetaminophen exists as = multiple brands). I have a database consisting of these two variables.=20 It will be 100.000 times easier for the persons typing the = questionnaires to type one of the brand names of acetaminophen and the = generic name automatically will be filled. Is it possible to create this lin on the Epi-data?? -- 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

looking up information based on entry in a field
by epidata-list＠lists.umanitoba.ca 03 Jan '07

03 Jan '07

It is quite easy to set up a system where information is converted based on input in a field Look in the help file for EpiData Entry under "comment legal". e.g. qes: v1 entered information _______________________ v2 converted information ________________________________ chk file: v1 comment legal AMA "Aminoacetophen" ABA "Aminoacetophen" PC "Penicillin A" PC1 "Penicillin A" end type comment v2 end v2 noenter end if you enter "AMA" or "ABA" in v1 then the equivalent "AminoAcetophen" will be copied into field v2. Kind regards and happy new year to all Jens Lauritsen EpiData Association

1 0

Cross tabulating
by epidata-list＠lists.umanitoba.ca 02 Jan '07

02 Jan '07

Just arrived on the list. I am about to construct a questionnaire on Epi-Data. Never worked with it before, but it seems to be quite straight forward simple, as long as the requirements are simple. However, for some years ago I was constructing similar questionnaire on the Paradox DB. It was possible to simplify the type work by cross tabulating. e.g. Instead of typing the patients address, telephone number, and so forth, these data was auto-filled in the database that was linked to another database with the mentioned informations. I create a medication questionnaire. As the patients normally knows the 'trade names', and I am interested in the 'generic names' (as many of you knows e.g. one of the most used pain killers acetaminophen exists as multiple brands). I have a database consisting of these two variables. It will be 100.000 times easier for the persons typing the questionnaires to type one of the brand names of acetaminophen and the generic name automatically will be filled. Is it possible to create this lin on the Epi-data?? Thanks *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 0

Cross tabulating
by epidata-list＠lists.umanitoba.ca 01 Jan '07

01 Jan '07

Just arrived on the list. I am about to construct a questionnaire on Epi-Data. Never worked with it before, but it seems to be quite straight forward simple, as long as the requirements are simple. However, for some years ago I was constructing similar questionnaire on the Paradox DB. It was possible to simplify the type work by cross tabulating. e.g. Instead of typing the patients address, telephone number, and so forth, these data was auto-filled in the database that was linked to another database with the mentioned informations. I create a medication questionnaire. As the patients normally knows the 'trade names', and I am interested in the 'generic names' (as many of you knows e.g. one of the most used pain killers acetaminophen exists as multiple brands). I have a database consisting of these two variables. It will be 100.000 times easier for the persons typing the questionnaires to type one of the brand names of acetaminophen and the generic name automatically will be filled. Is it possible to create this lin on the Epi-data?? Thanks *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 0

Error opening newly created recfile
by epidata-list＠lists.umanitoba.ca 27 Dec '06

27 Dec '06

Hi all, After entering data using the data entry module of epidata, I open the recfile (file1.rec) with the stat module, sorted it on some numeric variable and then saved it with the "savedata" command to another recfile (file2.rec). Then I try to open the newly created and sorted file with the dataentry module, but this causes ane error, saying "List index out of bounds (9)". I have to most recent version of the epidata dataentry module installed. What could be wong? Ben.

1 0

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 23 Dec '06

23 Dec '06

I will be out of the office starting 12/23/2006 and will not return until 01/02/2007. If you require immediate assistance, please contact Rachel McCormick at extension 5829 or Lewinda Knowles at extension 5167. Happy Holidays!

1 0

French users - Guide
by epidata-list＠lists.umanitoba.ca 23 Dec '06

23 Dec '06

Hello, For the French users. A l'occasion de cours, j'ai réalisé deux documents en Français sur l'utilisation de Epi-Data. L'un, de 8 pages, sur la saisie et l'analyse (brève), et l'autre, plus complet de 12 pages, sur l'analyse seule. Ces deux guides sont disponibles sur le site du Réseau "Sécurité Naissance" des Pays de la Loire au www.reseau-naissance.fr Rubrique Epidemio-Stats. Si des personnes pouvaient compléter ces guides directement ou en créer d'autres (par exemple une partie "Contrôle" ou une partie "Fichiers relationnels"), ce serait sympathique, histoire de mutualiser les ressources (selon le même format). A en discuter. Bon Noël à tous et toutes. Bernard Branger Médecin coordinateur Réseau Sécurité Naissance 1, allée Baco 44000 NANTES Tel 02 40 48 55 81

1 0

Creating MS Access-style menus in epidata
by epidata-list＠lists.umanitoba.ca 21 Dec '06

21 Dec '06

Is it possible to create menus for series of linked Epidata screens like in MS Access? Thanks Martin Adjuik Statistician Navrongo Health Research Centre P. O. Box 114, Navrongo UER, Ghana Tel: +233 742 22310 Fax:+233 742 22496

1 0

relate and showing dates
by epidata-list＠lists.umanitoba.ca 13 Dec '06

13 Dec '06

I would experiment with autosearch and autosearch list Let us know how your experiments turn out. Jens Lauritsen EpiData Association

1 0

help with relate
by epidata-list＠lists.umanitoba.ca 12 Dec '06

12 Dec '06

Hello, I have a database with people and for each a set of visits (v1,v2,... v10). I used the RELATE command to open the visits database and it works well. But i don't know how to open a specific visit (i.e. v8) directly from the record of a person. I'd like to use a list to select the visit I want to see. Is it possible and how ? Thanks by advance for your advice. Jean-Marie

1 0

Value Label
by epidata-list＠lists.umanitoba.ca 29 Nov '06

29 Nov '06

Hello to All, I would like to give names to dichotomisées variables. I make him(it) well under SPSS. It is a question " Been worth Label ". I do not know how to make. By example: I dichotomise the variable Q05 (Rate of Haemoglobin) in two cathégories; modQ05 (Class of Hb) 1=TxHb < 12 mg / dl, 2=TxHb > 12 mg / dl. Afterward, I would like to call 1 = "Anaemia 2" = "Hb Normale". So that when I make Freq modQ05, I obtain the distribution by looking directly Anaemia Hb Normale Thank you ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Samedi, 18 Novembre 2006, 19h00mn 47s Objet : EpiData-list Digest, Vol 37, 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. Create one variable from two or more variables (epidata-list(a)lists.umanitoba.ca) 2. Re: Create one variable from two or more variables (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Fri, 17 Nov 2006 12:59:22 -0800 (PST) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Create one variable from two or more variables To: epidata-list(a)lists.umanitoba.ca Message-ID: <160765.20031.qm(a)web60116.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Is there a way to automatically create a variable from 2-3 entered variables? For example: I have var1 ###### var2 ## var3 # I would like epidata entry to automatically populate a new variable for each case, where the value would be var1, var2, var3 appended with each other: var4 var1var2var3 I tried creating a data check command: ~~~~~~~~~~~~~~~~~~~~~~ var4 MUSTENTER AFTER ENTRY var4="var1" + string(var1) + "var2" + string(var2) + "var3" + string(var3) END END ~~~~~~~~~~~~~~~~~~~~~~~~~ But that did NOT work. Thanks so much J.H. ____________________________________________________________________________________ Sponsored Link Mortgage rates near 39yr lows. $510k for $1,698/mo. Calculate new payment! www.LowerMyBills.com/lre ------------------------------ Message: 2 Date: Fri, 17 Nov 2006 21:51:05 +0000 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Create one variable from two or more variables To: epidata-list(a)lists.umanitoba.ca Message-ID: <455E2EC9.2050400(a)ird.bf> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello, It seems that several mis-specifications are made in your code: - first, why don't you declare initially the variables var1 to var3 as string variables? This would help to concatenate them. - second, if the variables v1-v3 have to be numericals, the creation of the var4 should be something like : var4 = string(var1)+string(var2)+string(var3) - third, to generate automatically v4 (defined as a string variable) I would have written the following code: var4 BEFORE ENTRY var4 = string(var1)+string(var2)+string(var3) GOTO var5 (if var5 is the next variable in the QES file) END END Please note that MUSTENTER may be not appropriate, unless you are sure that there will be no missing variables among v1-v3 Hope this helps Regards ------------------------------------------------------- Yves MARTIN-PREVEL, Epidemiologist, MD, MSc, PhD Nutrition Unit (WHO Collaborating Center for Nutrition) Institut de Recherche pour le Développement (IRD) 01 BP 182 - OUAGADOUGOU 01 - BURKINA FASO Tel: +226 50 30 67 37; Fax: +226 50 31 03 85 http://www.ird.bf/ epidata-list(a)lists.umanitoba.ca a écrit : > Is there a way to automatically create a variable from > 2-3 entered variables? > For example: I have > var1 ###### > var2 ## > var3 # > > I would like epidata entry to automatically populate a > new variable for each case, where the value would be > var1, var2, var3 appended with each other: > > var4 var1var2var3 > > I tried creating a data check command: > > ~~~~~~~~~~~~~~~~~~~~~~ > var4 > MUSTENTER > AFTER ENTRY > var4="var1" + string(var1) + "var2" + string(var2) > + "var3" + string(var3) > END > END > ~~~~~~~~~~~~~~~~~~~~~~~~~ > But that did NOT work. > Thanks so much > J.H. > > > > > > > ____________________________________________________________________________________ > Sponsored Link > > Mortgage rates near 39yr lows. > $510k for $1,698/mo. Calculate new payment! > www.LowerMyBills.com/lre > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 37, Issue 6 ******************************************* ___________________________________________________________________________ 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 2

Re : EpiData-list Digest, Vol 37, Issue 8
by epidata-list＠lists.umanitoba.ca 28 Nov '06

28 Nov '06

Bonjour, Merci de ne plus m'envoyer de messages!!! Cordialement ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Mardi, 28 Novembre 2006, 19h07mn 30s Objet : EpiData-list Digest, Vol 37, Issue 8 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. relational databases- using a mother file field in a check for a child file field (epidata-list(a)lists.umanitoba.ca) 2. Re: relational databases- using a mother file field in a check for a child file field (epidata-list(a)lists.umanitoba.ca) 3. Re: Value Label (epidata-list(a)lists.umanitoba.ca) 4. Re: relational databases- using a mother file field in a check for a child file field (epidata-list(a)lists.umanitoba.ca) 5. relational databases- using a mother file field in a check for a child file field (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Nov 2006 16:54:24 +1100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] relational databases- using a mother file field in a check for a child file field To: epidata-list(a)lists.umanitoba.ca Message-ID: <5.1.0.14.2.20061127165249.018c76c8(a)mail.mcri.edu.au> Content-Type: text/plain; charset="us-ascii"; format=flowed Dear listers, I have created a relational EpiData database where the value of a field called RECDATE is automatically passed from the mother file to the related child file. This works fine. I have a field in the child file called DATE and wish to ensure that DATE is always later than RECDATE. I have tried the following check: date AFTER ENTRY IF DATE< RECDATE THEN HELP "The date can't be earlier than the date of recruitment" TYPE=ERROR ENDIF END END And I get the following error: Error in IF expression: Invalid parameters to DATE. Does anyone have any advice on using automatically passed variables in checks? All help is much appreciated. In case it helps, here is the start of my child.chk file. BEFORE RECORD RECDATE=varRECDATE END id KEY 1 END recdate NOENTER END date RANGE 1/1/2006 31/12/2007 LEGAL 1/1/1800 1/1/1900 END AFTER ENTRY IF DATE< RECDATE THEN HELP "The date can't be earlier than the date of recruitment" TYPE=ERROR ENDIF END END Katherine Smith Research Assistant Clinical Epidemiology and Biostatistics Unit (CEBU) Murdoch Childrens Research Institute (03) 9345 7957 katherine.smith(a)mcri.edu.au ------------------------------ Message: 2 Date: Tue, 28 Nov 2006 12:08:49 +1100 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] relational databases- using a mother file field in a check for a child file field To: "epidata-list(a)lists.umanitoba.ca" <epidata-list(a)lists.umanitoba.ca> Message-ID: <525bc0510611271708q5b0863c8x25ba004ddd750fc0(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi Katherine, I have just had a similar problem - it seems to be with using the word "date" which is reserved as a function in Epidata. I don't know how to get around this (maybe someone else here does) so for my database I simply changed the name of the variable to something else (e.g. vdate). Charity On 11/27/06, epidata-list(a)lists.umanitoba.ca < epidata-list(a)lists.umanitoba.ca> wrote: > > > And I get the following error: > > Error in IF expression: Invalid parameters to DATE. > > ------------------------------ Message: 3 Date: Mon, 27 Nov 2006 17:52:12 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Value Label To: epidata-list(a)lists.umanitoba.ca Message-ID: <456B6C1C.90103(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed You could just recode q05 to a text variable: define modq05 __________ recode q05 to modq05 lo-2.0 = "Anaemia" 12.0-hi = "Hb Normale" When you do this, check to see where a value of exactly 12 is classified. If in the wrong category, then use recode q05 to modq05 12.0-hi = "Hb Normale" lo-12.0 = "Anaemia" That is, the final a-b=c is the one that counts for points at your dividing point between categories. In the latest (test) release of Analysis, you can add variable name and value labels, but this feature is not yet documented. Jamie Jean-Paul wrote: > Hello to All, > I would like to give names to dichotomisées variables. > By example: I dichotomise the variable Q05 (Rate of Haemoglobin) in two cathégories; modQ05 (Class of Hb) 1=TxHb < 12 mg / dl, 2=TxHb > 12 mg / dl. > Afterward, I would like to call 1 = "Anaemia 2" = "Hb Normale". > So that when I make Freq modQ05, I obtain the distribution by looking directly > Anaemia > Hb Normal ------------------------------ Message: 4 Date: Mon, 27 Nov 2006 17:29:21 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] relational databases- using a mother file field in a check for a child file field To: epidata-list(a)lists.umanitoba.ca Message-ID: <456B66C1.10406(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Do not make a variable with the name DATE. DATE is an EpiData function name. The general rule is that you should never create a variable with the same name as is used anywhere in EpiData's syntax. Change the variable name to DxDate or RxData or IntervDate. Jamie Katherine wrote: > Dear listers, > > I have created a relational EpiData database where the value of a > field called RECDATE is automatically passed from the mother file to > the related child file. This works fine. I have a field in the child > file called DATE and wish to ensure that DATE is always later than > RECDATE. I have tried the following check: > > date > AFTER ENTRY > IF DATE< RECDATE THEN > HELP "The date can't be earlier than the date of recruitment" > TYPE=ERROR > ENDIF > END > END > ------------------------------ Message: 5 Date: Tue, 28 Nov 2006 15:31:00 +1100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] relational databases- using a mother file field in a check for a child file field To: epidata-list(a)lists.umanitoba.ca Message-ID: <5.1.0.14.2.20061128152929.00c4f020(a)mail.mcri.edu.au> Content-Type: text/plain; charset="us-ascii"; format=flowed Dear Jamie and Charity, Thank you very much for your prompt replies. Changing the name of the field to something other than DATE solved the problem. Best wishes, Katherine Katherine Smith Research Assistant Clinical Epidemiology and Biostatistics Unit (CEBU) Murdoch Childrens Research Institute (03) 9345 7957 katherine.smith(a)mcri.edu.au ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 37, Issue 8 ******************************************* ___________________________________________________________________________ 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

relational databases- using a mother file field in a check for a child file field
by epidata-list＠lists.umanitoba.ca 27 Nov '06

27 Nov '06

Dear Jamie and Charity, Thank you very much for your prompt replies. Changing the name of the field to something other than DATE solved the problem. Best wishes, Katherine Katherine Smith Research Assistant Clinical Epidemiology and Biostatistics Unit (CEBU) Murdoch Childrens Research Institute (03) 9345 7957 katherine.smith(a)mcri.edu.au

1 0

relational databases- using a mother file field in a check for a child file field
by epidata-list＠lists.umanitoba.ca 27 Nov '06

27 Nov '06

Dear listers, I have created a relational EpiData database where the value of a field called RECDATE is automatically passed from the mother file to the related child file. This works fine. I have a field in the child file called DATE and wish to ensure that DATE is always later than RECDATE. I have tried the following check: date AFTER ENTRY IF DATE< RECDATE THEN HELP "The date can't be earlier than the date of recruitment" TYPE=ERROR ENDIF END END And I get the following error: Error in IF expression: Invalid parameters to DATE. Does anyone have any advice on using automatically passed variables in checks? All help is much appreciated. In case it helps, here is the start of my child.chk file. BEFORE RECORD RECDATE=varRECDATE END id KEY 1 END recdate NOENTER END date RANGE 1/1/2006 31/12/2007 LEGAL 1/1/1800 1/1/1900 END AFTER ENTRY IF DATE< RECDATE THEN HELP "The date can't be earlier than the date of recruitment" TYPE=ERROR ENDIF END END Katherine Smith Research Assistant Clinical Epidemiology and Biostatistics Unit (CEBU) Murdoch Childrens Research Institute (03) 9345 7957 katherine.smith(a)mcri.edu.au

1 2

Create one variable from two or more variables
by epidata-list＠lists.umanitoba.ca 17 Nov '06

17 Nov '06

Is there a way to automatically create a variable from 2-3 entered variables? For example: I have var1 ###### var2 ## var3 # I would like epidata entry to automatically populate a new variable for each case, where the value would be var1, var2, var3 appended with each other: var4 var1var2var3 I tried creating a data check command: ~~~~~~~~~~~~~~~~~~~~~~ var4 MUSTENTER AFTER ENTRY var4="var1" + string(var1) + "var2" + string(var2) + "var3" + string(var3) END END ~~~~~~~~~~~~~~~~~~~~~~~~~ But that did NOT work. Thanks so much J.H. ____________________________________________________________________________________ Sponsored Link Mortgage rates near 39yr lows. $510k for $1,698/mo. Calculate new payment! www.LowerMyBills.com/lre

1 1

Error in reading csv file
by epidata-list＠lists.umanitoba.ca 16 Nov '06

16 Nov '06

Keith had an error on reading csv file: "I am trying to read a .csv file using EpiData Analysis. The .csv file has 128 fields in it. The first row contains column headings (8 Chars Long). None of the fields contain data over 64 chars long." Please submit the file in a zip archive to the system mailbox at info at epidata.dk and we will use the file for further testing. Regards Jens Lauritsen EpiData Assocation

1 0

Question
by epidata-list＠lists.umanitoba.ca 16 Nov '06

16 Nov '06

EPIDATA ANALYSIS 1.1 (Build 68) This is the first time I have attempted to use this product. Any insight into the cause of this problem is much appreciated! I am trying to read a .csv file using EpiData Analysis. The .csv file has 128 fields in it. The first row contains column headings (8 Chars Long). None of the fields contain data over 64 chars long. When I click "Read Data" and select the .csv file to read, I get this error message... Data in field Hospital, record 206 exceed maximum length Access violation at address 00732A30 in module 'EpiDataStat.exe'. Read of address 0000000C Operation aborted The data in field Hospital, record 206 is only 36 characters. I have found that if I truncate that field to 18 characters, then EpiData Analysis will read that record successfully. I get the same error on other fields within my .csv file and again, if I truncate the data within those fields to 18 characters, then EpiData Analysis will read the entire file successfully. Thank you in advance for any assistance you can provide! Keith _____________________ Keith Higginbotham Computer Systems Center Alabama Dept of Public Health 334-206-7040

1 0

Error in export to Stata v8 from EpiC june 2006 (v3.1.1)
by epidata-list＠lists.umanitoba.ca 14 Nov '06

14 Nov '06

An error has been found in writing Stata files with EpiC from June 2006, v.3.1.1 It was the version on the testing page. An updated version of EpiC 3.1.2 has been placed on the testing page (see link at top of www.epidata.dk/download.php). Regards Jens Lauritsen EpiData Association

1 0

Double-entry problem
by epidata-list＠lists.umanitoba.ca 09 Nov '06

09 Nov '06

Hello all - I am collecting and entering data for a project with well over 700 variables. Of course, we are double entering roughly 20% of our data records to check for consistency and mistakes. I created a .dbl file from the .rec file to prepare for double entry as instructed in the EpiData manual. But it seems like there is a next step that I am missing. We've double-entered a few records and corrected a few mistakes. I was under the impression that the fields we corrected during double-entry would overwrite those fields and save to the original record. However, when I opened the records that had been double-entered and corrected the original responses were still there. All of the corrections we made were not there. What my next step in EpiData to accept the changes that were made during double entry for each of those records? Thanks a lot! Sarah McDougal Department of Aging & Mental Health 13301 Bruce B. Downs Blvd, MHC 1400 Tampa, FL 33612-3807 Phone: (813) 974-1975 Fax: (813) 974-1968

1 1

Which estimates to have as default in OUTBREAK ANALYSIS ?
by epidata-list＠lists.umanitoba.ca 07 Nov '06

07 Nov '06

> I prefer B of the two options. Add the /o option to provide a separate > table of odds ratios, or replace the RR with OR (I prefer the > replacement, since the user should know what the study design is). Add > the /ci option to provide CI for the attack rates (not something I > routinely look for). Add the /t option for chi-squared and p, Fisher > exact p. > > Jamie I agree option B is better. I wouldn't mix OR + Attack Rate, so if /o is added it should replace RR with OR and eliminate AR. /AF, can be useful to add Attributable Fraction (both in exposed and in population) Greetings, Pedro

1 0

Which estimates to have as default in OUTBREAK ANALYSIS ?
by epidata-list＠lists.umanitoba.ca 06 Nov '06

06 Nov '06

In version 2.0 a new /OA (Outbreak analysis) parameter will be added to analysis. The question is what should be shown as default (other aspects will come as further options): e.g.: . tab ill vanilla milk coffee /oa Would make a table for ill by all other variables, and then show what: A: N total number of observations for exposed and unexposed: Ill number of persons with outcome Attack Rate + CI (percent with outcome) Odds Ratios + CI B: N total number of observations for exposed and unexposed: Ill number of persons with outcome Attack Rate (percent with outcome) RR + CI Please discuss default and desired options Regards Jens Lauritsen EpiData Association

1 2

Help: copying graphs/tables from Epidata into word
by epidata-list＠lists.umanitoba.ca 25 Oct '06

25 Oct '06

hello I am sure this has a simple answr but its quite annoying. I cannot copy my tables from epidata into word How do i do this thanks Bankole Olatosi PhD(c), MS, MPHResearch Associate, South Carolina Rural Health Research Center,Columbia, SC Tel: 803-251-6317Fax: 803-251-6399 PhD Candidate Health Services Policy and Management,Norman Arnold School of Public Health,University of South Carolina _________________________________________________________________ Stay in touch with old friends and meet new ones with Windows Live Spaces http://spaces.live.com/signup.aspx

1 2

Mode of copying from output window
by epidata-list＠lists.umanitoba.ca 24 Oct '06

24 Oct '06

Help: copying graphs/tables from Epidata into word For graphs it is quite easy: After creating a graph a copy is always placed on the clipboard, so: 1. create a graph - and make sure it is visible in the output window (close edit graph if you requested edit). 2. start wordprocessor, drawing programme, presentation programme etc. 3. press ctrl+v - and the graph is copied into the current open programme. If your pc is not too old you can have EpiData Analysis and the word processor open at the same time and switch btw. them by pressing alt+tab keys. Regarding tables: Is the development now such that default copying (ctrl+c) should be html formatted rather than text formatted ? Now: Shift+Ctrl+C: html formatted. Ctrl+C: tab delimited copying. We are experimenting with a "mouse over" effect, such that if the mouse is over a table or graph in output, then it would be nice that "right-click" would enable "copy table" or "copy graph". regards Jens lauritsen EpiData Association

1 0