- EpiData-list - University of Manitoba Mailing Lists

RE: [EpiData-list] Reserved words
by epidata-list＠lists.umanitoba.ca 04 Nov '05

04 Nov '05

there must be a misunderstanding. i said that when EpiAnalysis encountered the reserve word DATE in the .REC database there was no error message provided. all Analysis did was stop functioning properly. countless hours of searching for the problem and seeking assistance from others would have been avoided if Analysis had provided an error message about reserve words. thanks for the info on screen format. i eventually used the editor in EpiAnalysis and kept everything to the left of the shaded 80 column line provided....just another way. -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Fri 11/4/2005 2:23 AM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: [EpiData-list] Reserved words and a warning on using "if constructs" 1)A member commented on the use of date as a reserved word and the use of chk and dbf files. CHK files are only read with REC files. If you read CSV (delimited files) or DBF files no CHK file of the same name as the csv or dbf file will be used. If you wish to add labels (comment legal) for data in dbf or csv files then do: read myfile.dbf savedata xname * create a chk file with the name xname.chk read xname // obviously any name can be used xname is just an example On the topic of reserved names it is difficult because so many different languages exist. But in general do not use names of functions. E.g. avoid year, date and month use instead Y, d , m or vyear vdate vmonth 2. Using if the use of temporary select is a strong facility, e.g.: count if age > 50 tab sex agegrp if HbA1c > 6 tab sex agegrp if Country = 1 but currently DO NOT USE IF in combination with options for any command, e.g.: tab sex agegrp /Missing if Country = 1 this would be read as: tab sex agegrp /Missing Country = 1 meaning that all data was recoded for variable country. With next release this will be fixed. A new build is on the way fixing this and the other known (few) bugs. But I wish to finalize the aggregate (summary output statistics) command first. 3. Screen fonts in EpiData dataentry can be defined with options and a combination of the use of @ and blanks. See the help file. Screen fonts in analysis are defined with the "Set viewer font name", see the documentation on output formats installed with the programme. Regards Jens Lauritsen EpiData Association

1 0

Reserved words and a warning on using "if constructs"
by epidata-list＠lists.umanitoba.ca 04 Nov '05

04 Nov '05

1)A member commented on the use of date as a reserved word and the use of chk and dbf files. CHK files are only read with REC files. If you read CSV (delimited files) or DBF files no CHK file of the same name as the csv or dbf file will be used. If you wish to add labels (comment legal) for data in dbf or csv files then do: read myfile.dbf savedata xname * create a chk file with the name xname.chk read xname // obviously any name can be used xname is just an example On the topic of reserved names it is difficult because so many different languages exist. But in general do not use names of functions. E.g. avoid year, date and month use instead Y, d , m or vyear vdate vmonth 2. Using if the use of temporary select is a strong facility, e.g.: count if age > 50 tab sex agegrp if HbA1c > 6 tab sex agegrp if Country = 1 but currently DO NOT USE IF in combination with options for any command, e.g.: tab sex agegrp /Missing if Country = 1 this would be read as: tab sex agegrp /Missing Country = 1 meaning that all data was recoded for variable country. With next release this will be fixed. A new build is on the way fixing this and the other known (few) bugs. But I wish to finalize the aggregate (summary output statistics) command first. 3. Screen fonts in EpiData dataentry can be defined with options and a combination of the use of @ and blanks. See the help file. Screen fonts in analysis are defined with the "Set viewer font name", see the documentation on output formats installed with the programme. Regards Jens Lauritsen EpiData Association

1 0

EpiData editor, set tables
by epidata-list＠lists.umanitoba.ca 03 Nov '05

03 Nov '05

greetings. (1)the problem with the set command NOT working was because when the .DBF data set was imported and then saved as a .REC the 'new' data set contained the var. name DATE. EpiDataStat went crazy, sorta. no error message about reserved words or anything so helpful. so, it wasn't the .CHK constuct. (2) how does one control the EpiData editor? i spent considerable time creating a data collection instrument and the result was less than desirable when trying to print the form either at Data Entry or from the editor. so there must be something in the fine print which i haven't seen. how to get it to wrap at 80 cols., what about type size, etc. page length etc. thanks

1 0

set table value and label on/off and getting back to analysis output view
by epidata-list＠lists.umanitoba.ca 30 Oct '05

30 Oct '05

Set table value = off - and on Only works if the variables has a defined comment legal With the bromar.rec supplied with analysis: set table value = on tab sex sex No. % 1 Female 490 12.17 2 Male 3537 87.83 Total 4027 100% set table value = off tab sex sex No. % Female 490 12.17 Male 3537 87.83 Total 4027 100% set table label = off TABLE LABEL=OFF tab sex sex No. % 1 490 12.17 2 3537 87.83 Total 4027 100% (2) Analysis: when using Help: select (a) how to, (b) commands&func, (c) Intro when u select either of these u cannot get back to Analysis without first Quiting the program. To show output again Either: 1. Click on "Viewer" in tool bar and "Show Output" 2. Have your cursor active somewhere on the output (e.g. in the middle of help) and press ESC 3. Issue the command CLS (clear screen) and produce new output. The cls command is important every so often if you think the programme is slowing down. This is due to the way output is formed. regards Jens Lauritsen EpiData Association

1 0

How to: select with dates and an open question ? ?
by epidata-list＠lists.umanitoba.ca 30 Oct '05

30 Oct '05

This should work: * ---------------------------------------- DEFINE DATEMIN <dd/mm/yyyy> DEFINE DATEMAX <dd/mm/yyyy> LET DATEMIN = dmy(? First date: e.g. (02/12/1989) ?,"dmy") LET DATEMAX = ? Second date : e.g. (02/12/1999) ?,"dmy") SELECT (DATEADM <= DATEMIN) AND (DATEDIS >= DATEMAX) FREQ AGE ................................................................ or to select directly in comparison with a specific date using the dmy function: select date(? Write date, dd/mm/yyyy ?,"dmy") > dmy(10,02,1999) Jens Lauritsen EpiData Association

1 0

Analysis: Set, Help
by epidata-list＠lists.umanitoba.ca 30 Oct '05

30 Oct '05

greetings. (1)Analysis doc. says default value of SET TABLE VALUE = OFF My Experience is that the command does not work at all. It is ON all the time and cannot be turned OFF or ON using the set command. (2) Analysis: when using Help: select (a) how to, (b) commands&func, (c) Intro when u select either of these u cannot get back to Analysis without first Quiting the program. Suggest a CLOSE window, similar to Browse (unless i'm missing the return somewhere) -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Sat 10/29/2005 4:50 AM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: [EpiData-list] TABLES OUTPUT greetings. i was going to send 2 .doc files demonstrating the following 'problem' but, they were more than 25k. 1. have database using .chk which contains a LABELBLOCK the LABELBLOCK was constructed 1-16 with names assigned to each(of coourse) 2. ran Analysis and issued the command TABLES SEX SITECODE 3. result was what appeared to be a random display of SITECODE using the LABELs assigned 4. it turned out to be the problem with the number ordering 1 10 11 12 13 14 15 16 2 3 4 5 6 7 8 9 --so, i suggest either an alphabetc listing of labels or in order it was created 1-16 etc. --when i removed the LABELBLOCK the output was 1-16 and it should be. also, i noticed that another person is having the same issue with the FREQ resulting in error 'Too Many Catagories" thanks, kelly

1 0

Bed occupancy - problems with date calculation...
by epidata-list＠lists.umanitoba.ca 29 Oct '05

29 Oct '05

Hi. I am trying to write a PGM in order to calculate the bed occupancy in a defined period of time. As dates can be converted to sequential integer numbers, I wrote the following, considering DATEADM (admission date), DATEDIS (discharge date) and AGE as database variables: * ---------------------------------------- DEFINE DATEMIN <dd/mm/yyyy> DEFINE DATEMAX <dd/mm/yyyy> LET DATEMIN = ? First date : ? LET DATEMAX = ? Second date : ? SELECT (DATEADM <= DATEMIN) AND (DATEDIS >= DATEMAX) FREQ AGE *----------------------------- After typing first date: 15/10/2005 (even "15/10/2005"), I get the error message: "Data type mismatch". If I type 15102005, I get "Invalid date", what sounds reasonable. But I can only entry the desired date when I type 75162, what is NOT the respective sequential number of days since 31/12/1899 ("EpiData handles dates as float-type numbers counting the number of days since 31/12/1899" as can be read in EpiData Help) What am I doing wrong? Thank you in advance. MARCO MOURA ================================== Dr. MARCO Antonio MOURA Reis, MD, PhD Discipline of Medical Informatics Department of Medicine University of Region of Joinville - UNIVILLE Joinville (SC) - BRAZIL E-mail: mmoura(a)infomedica.com.br ==================================

1 0

How to: How is sort order of tables defined ? (get tables in right order)
by epidata-list＠lists.umanitoba.ca 29 Oct '05

29 Oct '05

One way of getting other people to see problems is to have analysis creating random data with a combination of the command generate (which produces an empty data file) and the random functions. Then we do not need the attached files. The reason for NOT allowing attachments is that this is a very good way of protecting all on the list from virus spreading E.g. for the question from today run these commands: First: create a chk file with the labels: ....................... t.chk ................ labelblock label s 1 "London" 2 "Copenhagen" 3 "Madrid" 4 "New Delhi" 5 "Madras" 6 "Pretoria" 7 "Kiev" 8 "Hong Kong" 9 "Melbourne" 10 "Sao Paolo" 11 "Santiago" 12 "Ottawa" 13 "New Orleans" 14 "Bangkok" 15 "Honolulu" 16 "Havana" 0 "Oslo" 17 "Odense" 18 "Paris" 19 "Budapest" end end sitecode comment legal use s end sex comment legal 0 male 1 female end end ..... save the text above as t.chk ........................ ............ Then create a pgm file: t.pgm: ................................ * Example file for creation of test data: close * create an empty data set with 1000 observations: generate 1000 define sex # define sitecode ## define sitecode2 ## * now assign values to the variables (random numbers) sex = ran(2) // sex will get numbers 0 and 1 sitecode = random(20) // sitecode will get numbers from 0 to 19 sitecode2 = sitecode savedata t * Now we have saved a data file with 1000 numbers, * but we need to read it again to get the labels read t /close * turn on labels, but turn off numbers for the tables: set table label = on set table value = off tab sex sitecode tab sex sitecode2 * notice that the order is the same as the numerical code for both variables * now we also turn on the numbers for the sitecode: set table value = on tab sex sitecode ................................ end t.pgm When you run the t.pgm you will notice that the first table of sex and sitecode shows this: SEX SITECODE male % female % Total % Oslo 25 {52.1} 23 {47.9} 48 {100.0} London 26 {48.1} 28 {51.9} 54 {100.0} .... snip ....................... Whereas the last with the values turned on shows: set table value = on tab sex sitecode SEX SITECODE 0 male % 1 female % Total % 0 Oslo 25 {52.1} 23 {47.9} 48 {100.0} 1 London 26 {48.1} 28 {51.9} 54 {100.0} 10 Sao Paolo 26 {47.3} 29 {52.7} Which means that for crosstables there is apparently a sorting going on on the first column. Notice that the two variables sitecode and sitecode2 are of type numerical. If we instead had used string variables: define v2 __ v2 = string(sitecode) tab v2 * then the order of v2 would be sorted meaning the "0 oslo - 1 london - 2 sao paolo" sequence * but without the text. To remedy this the trick would be to say: v2 = " " + v2 if length(trim(v2)) < 2 Then a new "tab v2" would show the correct table ------------------------------------------ Lesson: Obviously more user control of sort order of cross tables is on the wish list. But the feature is not part of the current most wanted list from my point of view. We have been experimenting a bit with sorting, but it is not all that easy. By converting btw. variable types and turning values and labels on and off you can get a lot of control as it is now. A feature which is expected to be available later this year is to be able to take the text label from a variable and save in a string variable, e.g. v2string = label(sitecode) or v2string = string(sitecode) + label(sitecode) (this is not implemented now) An undocumented sorting feature is available - but will not be documented until I am sure how to control sorting. Users are welcome to use it. The table will be sorted in reverse numerical order. But the problem with labels and values above persist. table sex v2 /rd or tab sex v2 /Rowdes Jens Lauritsen EpiData Association > 1. have database using .chk which contains a LABELBLOCK > the LABELBLOCK was constructed 1-16 with names assigned to each(of coourse) > 2. ran Analysis and issued the command TABLES SEX SITECODE > 3. result was what appeared to be a random display of SITECODE using the LABELs assigned > 4. it turned out to be the problem with the number ordering > 1 > 10 > 11 > 12 > 13 > 14 > 15 > 16 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > --so, i suggest either an alphabetc listing of labels or in order it was created 1-16 etc. > --when i removed the LABELBLOCK the output was 1-16 and it should be. also, i noticed that > another person is having the same issue with the FREQ resulting in error 'Too Many Catagories" > thanks, kelly > >

1 0

TABLES OUTPUT
by epidata-list＠lists.umanitoba.ca 29 Oct '05

29 Oct '05

greetings. i was going to send 2 .doc files demonstrating the following 'problem' but, they were more than 25k. 1. have database using .chk which contains a LABELBLOCK the LABELBLOCK was constructed 1-16 with names assigned to each(of coourse) 2. ran Analysis and issued the command TABLES SEX SITECODE 3. result was what appeared to be a random display of SITECODE using the LABELs assigned 4. it turned out to be the problem with the number ordering 1 10 11 12 13 14 15 16 2 3 4 5 6 7 8 9 --so, i suggest either an alphabetc listing of labels or in order it was created 1-16 etc. --when i removed the LABELBLOCK the output was 1-16 and it should be. also, i noticed that another person is having the same issue with the FREQ resulting in error 'Too Many Catagories" thanks, kelly

1 0

hi Jamie
by epidata-list＠lists.umanitoba.ca 29 Oct '05

29 Oct '05

please send email address.... keb1(a)cdc.gov -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Wed 10/26/2005 6:26 PM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: [EpiData-list] how do you get the file to test the problem? Use EpiData to archive the file - it will be a fraction of the original size. You an do this from the Tools menu. If still too large, then we'll have to exchange e-mail addresses off the list somehow Jamie Hockin Public Health Agency of Canada

1 0

Administrative comments on recent issues on EpiData-List
by epidata-list＠lists.umanitoba.ca 27 Oct '05

27 Oct '05

Good colleagues. A few administrative issues: 1. The list has been set up to enhance communication by e-mail and to limit size of each posting. For users with fast internet size of a mail is not a concern, but for people on slow modem lines large mails creates large problems. So as of now the following rules guide the list: a. Attachments must be small b. Text in e-mail must be small. A combined limit of 25kb has been defined. A few days back a user attached a rec file with the size of almost 1mb which is far exceeding this size. Individual users can exchange large attachments outside the list directly as suggested by Jamie Hockin. 2. Only certain attachments are allowed, e.g. small rec, chk and qes files. 3. Minimise the number of lines when you answer or comment on other mails. If a user asks a question - then on the reply only keep the minimal part indicating the topic of the question and reply. Otherwise the complete originating mail can be repeated several times. 4. Bouncing. When a person has an automatic mail saying e.g. "I am out of office please ....." then when a notice from the list comes to that person a message is sent to the person. The automatic message is sent back to the list, which then replies to the user etc. So if no mechanism controls several hundred mails can bounce back and forth. Therefore some users will experience to be automatically signed off the list. This is not a censorship or similar but a mechanism to avoid that everyone gets many "I am out of office..." messages. If you are excluded by "bounce-control" then just sign on to the list again when you are back from the leave. Or maybe create a different e-mail account which you use for receiving list messages. 5. Write in a specific and short manner and protect your e-mail adress You should be aware that messages you send to the list are: - distributed to all members (currently nearing 200) - is kept as part of the archive and is available for searching on internet. So to minimise the chance that your e-mail is trapped and used in a virus spread do not write it directly if you wish to receive personal mails, but write something like xxx at yyyy zz or similar. instead of xxx(a)yyyy.zz 6. Only users who are members of the list can submit messages. The first message by a new list member is sent to list administrators for approval. We could turn this off, but it will result in advertisements or spam messages every so often. I assume list members appreciate the principles above, but I am willing to discuss some of them. E.g. the size of allowed attachments and mails. Kind regards Jens Lauritsen EpiData Association

1 0

New version 1.0 celebrations and few suggestions
by epidata-list＠lists.umanitoba.ca 27 Oct '05

27 Oct '05

Dear Jens and other friends of Epidata Team, I have just joined the list last week. First of all congratulations for the excellent software developed maintaining the simplicity of EPI6. Good graphic are good addition to that simplicity. Fine controls of percents in the Tables command are just superb. The wishlist is long and it takes lot of effort to fulfil that. However few suggestions; a. Multiple Bar Charts which can depict gender comparisons of a variable in the same graph. b. Freq command with switches such as freq v1 sum=v2, /n /p etc. c. Combine command. d. Freq command requires some corrections as simple freq command of a variable gives an error message "Too many categories". e. In the long run 3D graphic for appropriate data. Please keep up this good work. Sincerely, Dr. Shavinder Singh Department of Community Medicine,

1 0

how do you get the file to test the problem?
by epidata-list＠lists.umanitoba.ca 26 Oct '05

26 Oct '05

Use EpiData to archive the file - it will be a fraction of the original size. You an do this from the Tools menu. If still too large, then we'll have to exchange e-mail addresses off the list somehow Jamie Hockin Public Health Agency of Canada

1 0

variables COMMAND in Analysis
by epidata-list＠lists.umanitoba.ca 26 Oct '05

26 Oct '05

greetings. i just used the variables command in Analysis and the output results were a little surprising. the Value Lable field display was as follows: 1 = a 10 = 25 11 = 26. 19 = 29 2 = b 20 = 30 The Freq or tables command had the same issue at one time. we had this discussion about why before. 1 2 3 4 etc. is a better output in the end. -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca Sent: Wed 10/26/2005 10:12 AM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: EpiData-list Digest, Vol 24, Issue 14 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..."

1 0

tried to send but Moderator said no files sze is to big(685KB). how do you get the file to test the problem?
by epidata-list＠lists.umanitoba.ca 26 Oct '05

26 Oct '05

-----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Wed 10/26/2005 9:21 AM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: [EpiData-list] Analysis read time and "too many catagories" greetings. i have atached a .rec file with 165,905 records, each 44 bytes. (1) it takes EpiAnalysis 10 seconds to open compared to instant availability in Epi6. why so slow? (2) using EpiAnalysis FREQ DATE resulted in error... "Too Many Catagories", no output. why??? (3) using Epi6 time for FREQ DATE was 1.9 seconds. slowness we can perhaps tolerate but no output on FREQ may be an issue. Or, it could be ther user. thank you and stay safe, kelly -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca Sent: Tue 10/25/2005 1:01 PM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: EpiData-list Digest, Vol 24, Issue 13 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..."

1 0

Analysis read time and "too many catagories"
by epidata-list＠lists.umanitoba.ca 26 Oct '05

26 Oct '05

greetings. i have atached a .rec file with 165,905 records, each 44 bytes. (1) it takes EpiAnalysis 10 seconds to open compared to instant availability in Epi6. why so slow? (2) using EpiAnalysis FREQ DATE resulted in error... "Too Many Catagories", no output. why??? (3) using Epi6 time for FREQ DATE was 1.9 seconds. slowness we can perhaps tolerate but no output on FREQ may be an issue. Or, it could be ther user. thank you and stay safe, kelly -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca Sent: Tue 10/25/2005 1:01 PM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: EpiData-list Digest, Vol 24, Issue 13 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..."

1 0

Using Epidata for a central server
by epidata-list＠lists.umanitoba.ca 26 Oct '05

26 Oct '05

Hello 1.About having a central server, please refer to the website and read the limitation of Epidata. 2.Well you can use the qes for data management or also use the option of preparing one data screen(rec file)and use the option of copy structure which is located at the tools menu.The advantage is that; 1. It is fast 2. There is no need to prepare another check. With these option, data entry staff can entry data for you and you have to merge them to have a collective data either at epidata or using spss. Using text fields.It is possible to enter open-ended questions and narrative with Epidata but it limitatiton is that it takes up to 80 characters whilst that of spss DE takes about 256 characters SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Homepage http://rastafarionline.com/rasbesa Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Tue, 25 Oct 2005 12:01:20 -0500 (CDT) Subject: EpiData-list Digest, Vol 24, Issue 13 > 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..." ------- End of Original Message -------

1 1

External reference for data entry: length limitation
by epidata-list＠lists.umanitoba.ca 25 Oct '05

25 Oct '05

Dear friends. Using COMMENT LEGAL function in order to select strings and get their respective codes from a separate REC file, I wanted to get CID10 codes and their respective Descriptions during data entry. In my parent CHK file you can see: DISEASE COMMENT LEGAL CID10.REC SHOW TYPE COMMENT CIDCODE END CIDCODE NOENTER END In my reference CHK file you'd read: DISEASE KEY 1 END CID10 KEY UNIQUE 2 END It's working fine, except that, in the pop-up window of reference the description of DISEASE is shown length limited to 30 characters, despite of my reference REC file showing 70. Any clue? Thanks in advance. MARCO MOURA ================================== Dr. MARCO Antonio MOURA Reis, MD, PhD Discipline of Medical Informatics Department of Medicine University of Region of Joinville - UNIVILLE Joinville (SC) - BRAZIL E-mail: mmoura(a)infomedica.com.br ==================================

1 0

Re: Multiple locations input
by epidata-list＠lists.umanitoba.ca 25 Oct '05

25 Oct '05

Well, Megan. As I know, simultaneous entries are not possible. I have been using EpiData in clinical research and constantly dealing with multiple users input. Right now I am creating a set of files to be used for a multicenter study about Neonatal Care Units (up to 50). What I do is to distribute sets of REC/CHK files (named specifically after each center) and recover the filled REC files through the use of a Web based free, but access-limited Group (like Yahoo Groups), what turns to be a additional backup system for my precious files. Having different files make it possible to first check the adequacy of each file before combining them. Combine files is quite fast and easy. Hope it helps. MARCO MOURA ================================== Dr. MARCO Antonio MOURA Reis, MD, PhD Discipline of Medical Informatics Department of Medicine University of Region of Joinville - UNIVILLE Joinville (SC) - BRAZIL E-mail: mmoura(a)infomedica.com.br ==================================

1 0

Multiple users - question by Megan Reif
by epidata-list＠lists.umanitoba.ca 25 Oct '05

25 Oct '05

Dear Megan: I can tell you a bit about our experience with multiple users in different countries we have had. We use one original set: original.qes original.rec original.chk Once this is definitively agreed upon, we use Copy structure (including the check file) to get: a.rec a.chk b.rec b.chk .. as many as we need and give one pair to each user (actually in duplicate for double entry). They enter the data at their leisure and then email the validated *.rec files. Because these files are so small, this can be done from even the slowest email connection (which matters to us as we work in some of the poorest countries). In EpiData Analysis, we simply do: close erase "abcd.rec" read "a.rec" append "b.rec" append "c.rec" append "d.rec" savedata "abcd.rec" close read "abcd.rec" People in the periphery simply continue to enter data into a.rec or b.rec and send so and so often the updated file, and the coordinator runs the append.pgm again. We did this with 30 locations in Zimbabwe collaborating with 31 locations in Mongolia, with a similar set-up for Moldowa collaborating with Uganda, and we never had a need for a central server. Email did just fine. A file with 58,000 records and and 9 fields took just 2 MB. I hope this helps a bit with that part of your question. Regards, Hans Rieder

1 0

Remote Entry, Multiple Users, Long Text Fields
by epidata-list＠lists.umanitoba.ca 24 Oct '05

24 Oct '05

Hello, I am a political scientists but used to work with public health people at The Carter Center. I am comparing EpiData, SPSS Data Entry Builder, and File Maker Pro as options for entering media incident reports of election violence. I am interested in "epidemiology of political violence" and eventually plan to map incidents. I am leaning toward Epi because it is freeware and many other great qualities, but a couple of questions remain: (1) I would like to have people entering data at the same time from multiple locations. Is it possible to have a remote and immediate data deposit on a central server via the web using EpiData? If not, how have people handled data management when field staff enter data? Do they just use the same .qes and then send the .rec files periodically, which are appended. Are there any problems with this method? I was thinking of setting up a web site where people could upload their files, then I would combine them. (2) I am a bit confused about text fields. Is it possible to enter open-ended questions and narratives (paragraph length)? This is what is attractive to me about SPSS DEB. They have remote entry as well as long text fields. If anyone has considered these issues I would welcome assistance. Best wishes, Megan Reif Megan E. Reif Department of Political Science University of Michigan 5700 Haven Hall 505 S. State Street Ann Arbor, MI 48109-1045 Mobile: 734.730.6024 Home: 734.763.6916 Fax: 734.764.3522 reifm(a)umich.edu -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.4/146 - Release Date: 10/21/2005

1 0

How to: relate files - how can I get only one record in sub files for each main record ?
by epidata-list＠lists.umanitoba.ca 22 Oct '05

22 Oct '05

Ziad asked: How to go for new record if you have two parts in EpiData? > I have database made of two parts. When we finish data entry in "part 2", > instead of moving to new record file, and we expect to see part 1, we get > new record file in part 2. > I assume the situation is this: a. enter data into file A b. at latest field in file A perform a relate to file B based on unique ID c. continue with more data in B d. at last field in file B you wish to continue with next record in file A. IF you specify in file A last field: after entry relate id fileB end Then after entering last field in file B you will have a new record in file B, but if you instead: after entry relate id fileB 1 end then only one record will be entered in file B and you will return to file A Example: qes files: file a: id <IDNUM> v1 first field # v2 date <dd/mm/yyyy> v3 relate # file b: id ##### v1 first field # v2 date <dd/mm/yyyy> v3 relate # Chk files: file a: id KEY UNIQUE 1 END v3 AFTER ENTRY RELATE id fileb 1 END END file b: id KEY UNIQUE 1 END Kind regards Jens Lauritsen EpiData Association

1 0

Atttach data file to the request
by epidata-list＠lists.umanitoba.ca 21 Oct '05

21 Oct '05

Hello All! Describing your problem, mighty be easy to you but to the one who is suppose to fix it up difficult.It will be appropriate if you add the data to the problem description for one to fix it up and send it you. I suggest you include the data screen for any of us to figured out the solution. Regards SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Homepage http://rastafarionline.com/rasbesa Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Fri, 21 Oct 2005 12:01:05 -0500 (CDT) Subject: EpiData-list Digest, Vol 24, Issue 11 > 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..." ------- End of Original Message -------

1 0

How to go for new record if you have two parts in EpiData?
by epidata-list＠lists.umanitoba.ca 21 Oct '05

21 Oct '05

Hello! I have database made of two parts. When we finish data entry in "part 2", instead of moving to new record file, and we expect to see part 1, we get new record file in part 2. Example: when we enter questionnaire number 1-part 1. Then part 2 opens for the same questionnaire 1. At the end of part 2, instead of moving to questionnaire 2 to start doing data entry, it gives us new record file under part 2 for questionnaire 1. Any advice(s)? Thank you in advance! Best regards! /Ziad -- Centre for Studies of Complementary Medicine Karolinska Institutet Stockholm

1 0

Re: Double Entry Error and @ when exporting to SPSS
by epidata-list＠lists.umanitoba.ca 14 Oct '05

14 Oct '05

I have a problem with results of calculation during double entry. During > double entry, all calculations give same results as first entry except only > for few subjects. Mystery sometimes happen - I am not sure what the problem is here. But we are just now working on different aspects of double entry verification. With the next build of EpiData Entry these errors should be fixed. For the finding of errors it would be very good if users could supply us with the rec+chk files giving problems. If someone as indicated on the list recently have examples creating problems please provide them for us for testing. The known issues to settle are: 1. Sometimes the double entry verification does not move on to the next record (problem with range definition in last field) 2. The calculation error indicated today. Send the files as zipped files (e.g. with few records, say 2-5) to info @ epidata.dk with a clear subject indicating that this is not spam, e.g EpiData test case for finding double entry problem. 2. Exporting to SPSS from old to new version of EpiData. The EpiData file format has not changed apart from the addition of encrypted fields and <yyyy/mm/dd> fields What most likely cause your problems is that the setting of "variable name" as first word or automatic was different on the two computers. Also for export to SPSS you do not need the QES file, but the chk file (definition of value labels and missing data) + the rec file (definition of fields, variable labels and all of the data). regards Jens Lauritsen EpiData Association

1 0

problems with calculations during double entry
by epidata-list＠lists.umanitoba.ca 14 Oct '05

14 Oct '05

Hi, I have a problem with results of calculation during double entry. During double entry, all calculations give same results as first entry except only for few subjects. I checked my formulae with other software and they look OK. This bug is not systematic thats why I have difficulties finding errors. I dont understand why this bug appears only for few subjects. They have not the same characteristics. Who can tell me what king of error it could be, because I dont know anymore what to looking for? Below, calculations : pspef AFTER ENTRY IF (sex = 1) and (height < 162.6) THEN pspdpef=(height * 0.073) - 5.98 ENDIF IF (sex = 1) and (height > 162.5) THEN pspdpef=(height * 0.125) - 13.14 ENDIF IF (sex = 0) and (height < 152.6) THEN pspdpef=(height * 0.079) - 6.79 ENDIF IF (sex = 0) and (height > 152.5) THEN pspdpef=(height * 0.064) - 3.94 ENDIF IF (sex = 1) THEN pssdcpef=(pspef - pspdpef) / (pspdpef * 0.18) ENDIF IF (sex = 0) THEN pssdcpef=(pspef - pspdpef) / (pspdpef * 0.2) ENDIF psppef=(pspef/pspdpef)*100 END END pspdpef NOENTER END pssdcpef NOENTER END psppef NOENTER END Example : sex = 1 , height = 132.8, pspef = 4.90 First entry (good results) pspdpef = 3.71 pssdcpef = 1.78 psppef = 132.1 Double entry pspdpef = 3.71 pssdcpef = -1.15 psppef = 79.2 Thank you in advance for your help. Marie-Pierre Strippoli Marie-Pierre Institut of social and preventive medicine Department of Epidemiology and Biostatistic Paediatric Epidemiology Finkenhubelweg 11 3012 Bern Tel: +41 (0)31 631 35 07 Fax: +41 (0)31 631 35 20 http://www.ispm.unibe.ch

1 0

Re:
by epidata-list＠lists.umanitoba.ca 13 Oct '05

13 Oct '05

"Brigitte Löwe" <b-loewe(a)web.de> schrieb am 13.10.05 13:56:01: > > > We have a problem and maybe you can help us: > We exported data from an old version of epidata(2003; operating system Windows NT servicepack 5) to a new one (3.1; operating system Windows XP Professional). Now there are in the qes.file many, many @ signs and they also appear when we export our data into SPSS (in the variable labels). If we skip the signs, in some cases variable labels in SPSS don´t exist anymore. > What can we do to have a qes.file without @ signs but get all variable labels in SPSS? > > Thank you for your help! ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

1 0

RE: EpiData-list Digest, Vol 24, Issue 7
by epidata-list＠lists.umanitoba.ca 13 Oct '05

13 Oct '05

REG MAAK DAN 2-3 -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 12 October 2005 19:01 To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 24, 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..."

1 0

Have you used EpiData guideline?
by epidata-list＠lists.umanitoba.ca 13 Oct '05

13 Oct '05

Hello! I sent last year information about an introductory guideline about EpiData. I wonder if anyone has used it? It used to be under EpiData page for a while, and now it is under my university link: http://onkpat.ki.se/1?node=47234 In case you have used it, can you please write me back your feedback about it? I am intending to develop further versions of how to use EpiData, and need feedback to support my case for funds. Best regards! /Ziad Email: Ziad.El-Khatib(a)ki.se -- Ziad El-Khatib Division of International Health Care (IHCAR) Department of Public Health Sciences Karolinska Institutet Norrbacka 2nd Floor SE-171 76 Stockholm, Sweden Tel: +46 (0)8 51770185 Mobile: +46 (0) 73 776 48 59 Fax: +46 (0)8 311590

1 0

Using stattransfer to solve corrupted file
by epidata-list＠lists.umanitoba.ca 12 Oct '05

12 Oct '05

Another form of solving a corrupted file is to use statransfer(a statistical software that enhance file transfer from one format to other eg. from spss file to rec or any other file)with this software you transfer the file back to rec and it will solve your problem. SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Homepage http://rastafarionline.com/rasbesa Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 12 Oct 2005 12:00:37 -0500 (CDT) Subject: EpiData-list Digest, Vol 24, 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..." ------- End of Original Message -------

1 0

How to: Recapture a corrupted file
by epidata-list＠lists.umanitoba.ca 12 Oct '05

12 Oct '05

In some versions of some computers open files can get "messed" up if power is suddenly lost. Over the years we have strengthened EpiData Entry with several alternative mechanisms to try to avoid problems in this situation (e.g. only one record at a time is in memory. The rest is on the harddisk or floppy.). But despite this the error have been reported at rare instances. Also over the years I have seen files from this situation which was a combination of a rec datafile, a word document and a presentation or drawing. In other words this is part of a operating system problem. How to resolve ? If a corrupted file message is given you can do the following: Manual repair of corrupt files: 1 Make a second copy of your REC and CHK files and do the following (MAKE SURE IT IS A COPY !!!): 2. Verify that YOU HAVE THE ORIGINAL CORRUPTED file in a separate place. 3 Open the extra copy of the REC file in any ascii editor (e.g. notepad.exe). 4 Make sure you are using a fixed font. 5 Look for records with strange or odd formatted records and delete the complete record (Make a note of which one such that you can re-enter it later in EpiData) 6 Delete the parts with a strange format. 7 Pay particular notion to length of lines. All records should show same pattern. 8 Save the file and try to open in EpiData. If you think the above is hopeless - then try to regain other documents or files that were also open at the time, e.g a spreadsheet, a text document or a database from another programme than EpiData. The above is a modifed version of a user supplied explanation earlier. Regards Jens Lauritsen EpiData Association

1 0

New user find Help !
by epidata-list＠lists.umanitoba.ca 11 Oct '05

11 Oct '05

Hi, I´am a new user, I need some help, and my english is a bit poor. Anyone can help me in spanish ? Thanks in advance, Bernardo Ramazzi ( from Uruguay )

1 0

How to: Recover "epidata rec files" or get sufficient help from others.
by epidata-list＠lists.umanitoba.ca 11 Oct '05

11 Oct '05

A good recovery strategy when something goes wrong is: 1. Ask yourself "When was I in control the last time" 2. What did I do since I was in control of the situation. 3. What might I have done wrong since the control. 4. What was I intending to do at the time when I felt no longer in control of the situation. 5. Do I think the "loss of control" is due to a software error, a hardware (e.g. harddisk broken) error or a user error ? 6. How much work should I repeat to continue working from my last backup of all data (I assume you do have a copy somewhere). 7. Can I repeat the steps from the "in control situation" to the "out of control situation" and the same thing happens every time. If you can answer these questions you have a very good clue for the solution or the appropriate information to tell someone who can assist you - e.g. other users on this list. Regards Jens Lauritsen EpiData Association

1 0

How to recover files .rec in epidata
by epidata-list＠lists.umanitoba.ca 11 Oct '05

11 Oct '05

Please, I desperately need to know how to recover .rec files in epidata. Thank you --------------------------------------------------------------- Universia Brasil. Em todas as fases da vida acadêmica. Acesse o portal e confira nossos serviços e benefícios: http://www.universia.com.br/

1 0

Re: EpiData-list Digest, Vol 24, Issue 5
by epidata-list＠lists.umanitoba.ca 10 Oct '05

10 Oct '05

1 0

EpiData-list Digest, Vol 24, Issue 5
by epidata-list＠lists.umanitoba.ca 10 Oct '05

10 Oct '05

Hello to everybody the Lovers of Free We are anxious to congratulate all the EPIDATA's team for this 1000 users. In Côte d'Ivoire, I am one of the pioneers with EPIDATA, and every day I make effort to reveal it around me. It is a very simple software of use. And I think that all the institutions of search have to contribute to the development by gifts(donations). Thank you Dr KONAN DIBY Jean-Paul Médecin Santé Publique Service Biostatistique Epidémiologie Institut National Santé Publique BPV 47 Abidjan Cél: +225 05 994 326 --------------------------------- Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez le ici !

1 0

Re: EpiData-list Digest, Vol 24, Issue 5
by epidata-list＠lists.umanitoba.ca 10 Oct '05

10 Oct '05

It is such great and useful tool indeed! Keep the work up!! Best regards! /Ziad -- Ziad El-Khatib Division of International Health Care (IHCAR) Department of Public Health Sciences Karolinska Institutet Norrbacka 2nd Floor SE-171 76 Stockholm, Sweden Tel: +46 (0)8 51770185 Mobile: +46 (0) 73 776 48 59 Fax: +46 (0)8 311590 On 10/10/05, epidata-list-request(a)lists.umanitoba.ca < epidata-list-request(a)lists.umanitoba.ca> wrote: > > 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. 1000 downloads (epidata-list(a)lists.umanitoba.ca) > > > MIME-version: 1.0 > Content-type: message/rfc822 > > Date: Mon, 10 Oct 2005 14:08:49 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] 1000 downloads > In-reply-to: <200510081700.j98H0LbJ011518(a)electra.cc.umanitoba.ca> > To: epidata-list(a)lists.umanitoba.ca > Message-id: <20051010130237.M17632(a)ug.edu.gh> > MIME-version: 1.0 > Content-type: text/plain; charset=iso-8859-1 > Content-transfer-encoding: 7BIT > Precedence: list > Message: 1 > References: <200510081700.j98H0LbJ011518(a)electra.cc.umanitoba.ca> > > Dear All! > As we celebrate the 1000 downloads,we apreciate the effort of the free > sharing of the softwares and kudos to the programmers and the entire > team.In > Ghana, everyone that is introduce to this software is amaze but the > problem > is that it does not work as a database software as compare to EpInfo 3** > (windows version).In view of this i appeal to anyone to help the Epidata > team to develop this to higher version. > > SEDZRO KOJO MENSAH > P.O.Box AS 387 > Ashaiman -Tema > Ghana > House : +233-22-300789 > MOBILE : +233-244-458788 > Homepage http://rastafarionline.com/rasbesa > > Open WebMail Project (http://openwebmail.org) > > > ---------- Original Message ----------- > From: epidata-list-request(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Sent: Sat, 8 Oct 2005 12:00:55 -0500 (CDT) > Subject: EpiData-list Digest, Vol 24, Issue 4 > > > 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..." > ------- End of Original Message ------- > > > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > >

1 0

1000 downloads
by epidata-list＠lists.umanitoba.ca 10 Oct '05

10 Oct '05

Dear All! As we celebrate the 1000 downloads,we apreciate the effort of the free sharing of the softwares and kudos to the programmers and the entire team.In Ghana, everyone that is introduce to this software is amaze but the problem is that it does not work as a database software as compare to EpInfo 3** (windows version).In view of this i appeal to anyone to help the Epidata team to develop this to higher version. SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Homepage http://rastafarionline.com/rasbesa Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Sat, 8 Oct 2005 12:00:55 -0500 (CDT) Subject: EpiData-list Digest, Vol 24, Issue 4 > 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..." ------- End of Original Message -------

1 0

Celebration - 1000 downloads of EpiData Analysis
by epidata-list＠lists.umanitoba.ca 07 Oct '05

07 Oct '05

Good Colleagues Although I did not manage to catch who downloaded the number 1000 of analysis after release of v1.0 I think it is worth mentioning. It seems like the product is being received quite well. Regards Jens Lauritsen EpiData Association

1 0

How to: What do I do when Installation says "Unknown Publisher"
by epidata-list＠lists.umanitoba.ca 06 Oct '05

06 Oct '05

With Windows XP a new system has been invoked where software developers can add certificates to the software making sure from where a certain software comes. To get such a certificate for EpiData costs some funding. Maybe it is worthwhile paying and maybe not. Another "running cost" without other aspect than having an external certification office, e.g. verisign telling that software from http://www.epidata.dk is certified to come from epidata.dk is maybe not needed. What users can do to certify that there is no problem in installing EpiData software and be sure that there is no problem with this is: 1. Always get copies of software directly from Http://www.epidata.dk 2. Add "Http://www.epidata.dk" to "trusted websites" in 2a - firewall 2b - instllation policy of the individual user PC 2c - installation and software policy of the institution. Until someone finds a "software publisher certificate" essential and wishes to fund the issuing of a certificate I think funding is better spent on development. So in short: When the installation message says "Unknown publisher" - if you downloaded the software from Http://www.epidata.dk/download.php you can say yes to the install. If your system prevents this, then follow the advice points 2a-2c and try again. Kind regards Jens Lauritsen EpiData Association ps. Very few bugs have been documented in analysis. In the solving of those present undocumented updated versions for testing will be available as www.epidata.dk/downloads/setupepidatastattest.exe When a coming build is available for test this will be mentioned at the test page as usual- avialable through the link on the left side of the main menu.

1 0

I am not able to install EPIDATA ANALYSIS
by epidata-list＠lists.umanitoba.ca 05 Oct '05

05 Oct '05

Hi Epidata-list I tried several times to install EPIDATA ANALYSIS but unsuccesfully and the following message appears "Unknown Publisher". If some one did it successfully could he/she sent his/her setup to me or advice me on how to succeed in installing ANALYSIS __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

Double Entry problem with range control in last field/variable on form
by epidata-list＠lists.umanitoba.ca 01 Oct '05

01 Oct '05

With the very precise description: "Does anyone know of a workaround that would allow me to preserve error checking on the last variable without encountering this problem (short of changing the order the questions, which would confuse data enterers)...perhaps a way to hard code a record advance into the check file? " With such a precise formulation it is possible to remove the error - not by workaround. In other words - the discussion on the list is very important to outline problems and find where the exact cause of a problem is. When a precise reproducible description can be made - this points to a specific part of the programme which can then be fixed. The fix will be part of next release of epidata entry. Regards Jens Lauritsen EpiData Association

1 0

RES: EpiData-list Digest, Vol 23, Issue 11
by epidata-list＠lists.umanitoba.ca 30 Sep '05

30 Sep '05

Hello I've found the same problem in EpiData 3.1 at WinXP, when last field had some check applied. Regards, Fulvio Nedel Universidade do Sul de Santa Catarina Brazil -----Mensagem original----- De: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca]Em nome de epidata-list-request(a)lists.umanitoba.ca Enviada em: quinta-feira, 29 de setembro de 2005 14:01 Para: epidata-list(a)lists.umanitoba.ca Assunto: EpiData-list Digest, Vol 23, Issue 11 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..." _______________________________________________________ Novo Yahoo! Messenger com voz: liga��es, Yahoo! Avatars, novos emoticons e muito mais. Instale agora! www.yahoo.com.br/messenger/

1 0

Double Entry Record Advance problem isolated
by epidata-list＠lists.umanitoba.ca 30 Sep '05

30 Sep '05

Dear David, What about appending a dummy variable to the end of the questionnaire/database? Bill McKelvie, MD Diocese of Hyderabad TB Program Mirpur Khas, Sindh, Pakistan -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.6/111 - Release Date: 9/23/2005

1 0

RE: [EpiData-list] RE: Double Entry Record Advance problem isolated
by epidata-list＠lists.umanitoba.ca 30 Sep '05

30 Sep '05

Hi; Did you try to uncheck the option (files/options /advanced) 'Show errors that occur in calculations ...' I noticed that it sometimes 'unblocks' checks that would otherwise either freeze the application or cause an unexpected behavior. Gilles ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : jeudi 29 septembre 2005 00:46 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] RE: Double Entry Record Advance problem isolated After some troubleshooting, I found that this problem only occurs if the last variable of the instrument has range checking defined. When I removed any references to the last variable in the check file, the records advanced properly in double entry mode. However, this was at the expense of removing the error checking mechanism from a question. Does anyone know of a workaround that would allow me to preserve error checking on the last variable without encountering this problem (short of changing the order the questions, which would confuse data enterers)...perhaps a way to hard code a record advance into the check file? - David -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Monday, September 26, 2005 1:07 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Records not advancing in verification mode I've been experiencing some strange behavior with the new double entry feature in EpiData 3.1. Here's what's happening: After reaching the last field of a record in the double entry record file and clicking "yes" to save, the cursor immediately jumps to the first field of the record that was just entered and highlights it....instead of advancing. In order to verify additional records, I need to manually advance to a clean record using either ctrl-N or the F8 shortcut key. This happens consistently (100% of the time), on my WinXP machine. Appreciate any help, perhaps a change in settings or checkfile that would bypass this problem? - Thanks, David David Huh Research Assistant Department of Psychology University of Texas at Austin Phone: (541) 484-2123, ext. 2320 Fax: (541) 484-1108 _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

RE: Double Entry Record Advance problem isolated
by epidata-list＠lists.umanitoba.ca 28 Sep '05

28 Sep '05

After some troubleshooting, I found that this problem only occurs if the last variable of the instrument has range checking defined. When I removed any references to the last variable in the check file, the records advanced properly in double entry mode. However, this was at the expense of removing the error checking mechanism from a question. Does anyone know of a workaround that would allow me to preserve error checking on the last variable without encountering this problem (short of changing the order the questions, which would confuse data enterers)...perhaps a way to hard code a record advance into the check file? - David -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Monday, September 26, 2005 1:07 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Records not advancing in verification mode I've been experiencing some strange behavior with the new double entry feature in EpiData 3.1. Here's what's happening: After reaching the last field of a record in the double entry record file and clicking "yes" to save, the cursor immediately jumps to the first field of the record that was just entered and highlights it....instead of advancing. In order to verify additional records, I need to manually advance to a clean record using either ctrl-N or the F8 shortcut key. This happens consistently (100% of the time), on my WinXP machine. Appreciate any help, perhaps a change in settings or checkfile that would bypass this problem? - Thanks, David David Huh Research Assistant Department of Psychology University of Texas at Austin Phone: (541) 484-2123, ext. 2320 Fax: (541) 484-1108 _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Records not advancing in verification mode
by epidata-list＠lists.umanitoba.ca 26 Sep '05

26 Sep '05

I've been experiencing some strange behavior with the new double entry feature in EpiData 3.1. Here's what's happening: After reaching the last field of a record in the double entry record file and clicking "yes" to save, the cursor immediately jumps to the first field of the record that was just entered and highlights it....instead of advancing. In order to verify additional records, I need to manually advance to a clean record using either ctrl-N or the F8 shortcut key. This happens consistently (100% of the time), on my WinXP machine. Appreciate any help, perhaps a change in settings or checkfile that would bypass this problem? - Thanks, David David Huh Research Assistant Department of Psychology University of Texas at Austin Phone: (541) 484-2123, ext. 2320 Fax: (541) 484-1108

1 0

"Anova = Means command" in Epidata V.1Rel.1
by epidata-list＠lists.umanitoba.ca 15 Sep '05

15 Sep '05

Hello , For comparing "means" of two independent samples , Epidata performs Anova (= t-test). But it assumes that the two samples have equal variances.( I have compared the results of Epidata with SPSS and Epiinfo).It does Bartlett's test and the result of this test ,say, shows that two samples have unequal variances but it doesn't notice to Bartlett's test ! Then why does it do Bartlett's test ? ( In SPSS , for comparing two independent samples ,Levene's test is done first and then we can interpret our results for "means" according to the result for Levene's test. In Epiinfo , Bartlett's test is done and if it is significant , Kruskal-Wallis is done. ) Thanks Reza --------------------------------- Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort.

1 0

Re calculation formula
by epidata-list＠lists.umanitoba.ca 14 Sep '05

14 Sep '05

Hello! I need to calculate the sum of hours and days, in form of hours. So I did the formula as : total hours = days*24 + hours So when you have one day of time to be registered, and you have no umber of hours (i.e. zero), it is writting as "00" (two digits of zeros), then the "total hours" would give answer as "0", even though the number 1 is writting in days. When I triy to write the zero, as one digit (i.e. "0"), then it works fine. Any tip how to overcome it? Here is below a copy of the formula: d8 MUSTENTER AFTER ENTRY LET d10=d9*24 + d8 END END Thank you in advance! /Ziad -- Ziad El-Khatib Division of International Health Care and Research (IHCAR) Department of Public Health Sciences Karolinska Institutet

1 1

new page every table for printing
by epidata-list＠lists.umanitoba.ca 12 Sep '05

12 Sep '05

>I am trying to print off a number of tables that I have generated. >Preferably one per page and have not been able to accomplish this. Apart from the suggestion by GIlles Delmas you should look at style sheets with EpiData Analysis. See "page-break-before" in the definitions: http://www.w3.org/TR/REC-CSS2/page.html And experiment a bit. Let us all know how you manage. We can then put the style sheet code for general usage in analysis as a "how to ...." regards Jens Lauritsen EpiData Association ps. Regarding the append question. Just try to see how many records are possible. I tried one append ending with 1 million records (10^6) with no problems.

1 0

RE: [EpiData-list] Printing Tables
by epidata-list＠lists.umanitoba.ca 12 Sep '05

12 Sep '05

Hi; It all depends of the analysis version you are using. 1- from Epi 6 Analysis, the simplest way is to send results to an external text file that you can then edit with any text editor or word processor. ROUTE xxxx.txt TABLES AAAA BBBB TABLES CCCC BBBB ... ROUTE (the last route closes the file, so it can be handled by another program) Then, open the text file with Wordpad, Word... 2- From EpiData Analysis, use the command 'logopen', give a name to the file (e.g. logopen TEST); a file named TEST.HTM is created, containing all results produced (tables, graphs...). It can be opened with any web browser, or edited with Word, for example. Best regards, ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : vendredi 9 septembre 2005 17:20 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] Printing Tables Please forgive my ignorance of the program. I am trying to print off a number of tables that I have generated. Preferably one per page and have not been able to accomplish this. Is it possible to do and if so how? Thank you.

1 0

appending and number files to be read dynamically
by epidata-list＠lists.umanitoba.ca 11 Sep '05

11 Sep '05

Thank you and this is good to know. a coupe of questions, please. 1. this suggest the limit to the number of files to be appeneded is realted to machine memory? 2. this is the solution to the "lack" of ability to dynamically read multiple files? Would those of you who have used these techniques please let me know what size of the files you have been working with and, any other options you have used. Thank you very much, Kelly -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Fri 9/9/2005 8:14 PM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: [EpiData-list] Appending Dear Eleni: There are two ways to append - one is within EpiData, the other highly efficient within EpiData Analysis. If you append (not merge) files with the same same structure, try this in EpiData Analysis, ver 0.9 build 38: * ----Program begins next line cls logclose close * switch to the folder where your REC files are located cd c:\temp1 erase "abcd.rec" read "a.rec" append "b.rec" append "c.rec" append "d.rec" savedata "abcd.rec" close * Do some tabulation to check read "abcd.rec" tables sex res1 logclose * --- Program has ended previous line Best regards, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 429 9945 Web: http://www.tbrieder.org

1 0

Final release candidate of EpiData Analysis is available now
by epidata-list＠lists.umanitoba.ca 11 Sep '05

11 Sep '05

Good Colleagues The final release candidate for version one of EpIData Analysis has now been placed at Http://www.epidata.dk/testing.php A 7 page introduction document is also available. If none of you find any major errors version one is just around the corner for public release. All reported errors have been fixed. Several requests for features have been sent. These will be prioritised for later. Including work on versions in languages other than English. On EpiData.dk some reconstruction will take place in regards to downloading and credits etc. Also the funding.htm page has not been fully updated during this year. The updating is expected within a few weeks. Kind regards Jens Lauritsen EpiData Association

1 0

Appending
by epidata-list＠lists.umanitoba.ca 09 Sep '05

09 Sep '05

Dear Eleni: There are two ways to append - one is within EpiData, the other highly efficient within EpiData Analysis. If you append (not merge) files with the same same structure, try this in EpiData Analysis, ver 0.9 build 38: * ----Program begins next line cls logclose close * switch to the folder where your REC files are located cd c:\temp1 erase "abcd.rec" read "a.rec" append "b.rec" append "c.rec" append "d.rec" savedata "abcd.rec" close * Do some tabulation to check read "abcd.rec" tables sex res1 logclose * --- Program has ended previous line Best regards, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 429 9945 Web: http://www.tbrieder.org

1 0

Printing Tables
by epidata-list＠lists.umanitoba.ca 09 Sep '05

09 Sep '05

Please forgive my ignorance of the program. I am trying to print off a number of tables that I have generated. Preferably one per page and have not been able to accomplish this. Is it possible to do and if so how? Thank you.

1 0

Re Exporting labels to Excel?
by epidata-list＠lists.umanitoba.ca 09 Sep '05

09 Sep '05

Hello! Is it possible to export the data labels to Excel file as well? (e.g. to have labels instead of the variables name then, it works for SPSS and Stata, but could not find it for Excel). Thank you in advance! /Ziad -- Ziad El-Khatib Division of International Health (IHCAR) Department of Public Health Sciences Karolinska Institutet Norrbacka 2nd Floor SE-171 76 Stockholm, Sweden Tel: +46 (0)8 51770185 Mobile: +46 (0) 73 776 48 59 Fax: +46 (0)8 311590

1 0

Automating Append/Merge
by epidata-list＠lists.umanitoba.ca 08 Sep '05

08 Sep '05

Use EpiC, which you can download from the epidata website. EpiC let's you send commands to EpiData. It's all explained in the documentation. You can set up a sequence of commands in a file and get Windows to run them whenever you want. Jamie Hockin Public Health Agency of Canada 1. Query: Append/merge (epidata-list(a)lists.umanitoba.ca) > Is there a way to run append/merge commands in an automatic way? >I mean not running them through epidata menu. > >Thanks in advance > >Eleni Kalamara >Hellenic centre for infectious diseases control > >

1 0

RE: EpiData-list Digest, Vol 23, Issue 1
by epidata-list＠lists.umanitoba.ca 08 Sep '05

08 Sep '05

Hi; I propose you this Edit controls for VAR1: VAR1 if VAR1 = 1 then hide VAR10 ELSE unhide VAR10 ENDIF END END In this case, var10 will be greyed, and no entry will be possible as soon as var1 is put to 1; the second if is necessary in case you decide, once VAR1 has been put to 1 to come back to it, and to put another value. If 'unhide' is not specified, Var10 would stay unusable. Dr DIBY JEAN-PAUL KONAN Médecin Santé Publique Resp. Unité Epidémiologie INSP Côte d'Ivoire BPV 47 Abidjan epidata-list-request(a)lists.umanitoba.ca a écrit : 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. NOENTER? SKIP? Ifthen? (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Sep 2005 18:00:39 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] NOENTER? SKIP? Ifthen? To: Message-ID: <346E71A112CE(a)grade.org.pe> Content-Type: text/plain; charset="iso-8859-1" Hi I am a begginer in EpiData. I don't understand the syntax for doing the following task in the check file: If var1 = 1 , then I need the field of var10 in the "data entry form" to be locked. How do I do this? I tried: var10 BEFORE ENTRY IF (var1=1) THEN HIDE var10 ENDIF END END But it does not work Thanks for your help Kristian ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 23, Issue 1 ******************************************* --------------------------------- Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez le ici !

1 0

Query: Append/merge
by epidata-list＠lists.umanitoba.ca 08 Sep '05

08 Sep '05

To all list members: Is there a way to run append/merge commands in an automatic way? I mean not running them through epidata menu. Thanks in advance Eleni Kalamara Hellenic centre for infectious diseases control

1 0

RE: [EpiData-list] NOENTER? SKIP? Ifthen?
by epidata-list＠lists.umanitoba.ca 07 Sep '05

07 Sep '05

Hi; Try the following: Edit controls for VAR1: VAR1 if VAR1 = 1 then hide VAR10 ENDIF if VAR1 <> 1 then unhide VAR10 ENDIF END END In this case, var10 will be greyed, and no entry will be possible as soon as var1 is put to 1; the second if is necessary in case you decide, once VAR1 has been put to 1 to come back to it, and to put another value. If 'unhide' is not specified, Var10 would stay unusable. What you did could not work: VAR10 can't be hidden once you are on it. Good luck! ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : mardi 6 septembre 2005 01:01 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] NOENTER? SKIP? Ifthen? Hi I am a begginer in EpiData. I don't understand the syntax for doing the following task in the check file: If var1 = 1 , then I need the field of var10 in the "data entry form" to be locked. How do I do this? I tried: var10 BEFORE ENTRY IF (var1=1) THEN HIDE var10 ENDIF END END But it does not work Thanks for your help Kristian

1 0

NOENTER? SKIP? Ifthen?
by epidata-list＠lists.umanitoba.ca 05 Sep '05

05 Sep '05

Hi I am a begginer in EpiData. I don't understand the syntax for doing the following task in the check file: If var1 = 1 , then I need the field of var10 in the "data entry form" to be locked. How do I do this? I tried: var10 BEFORE ENTRY IF (var1=1) THEN HIDE var10 ENDIF END END But it does not work Thanks for your help Kristian

1 0

hidden values, but aggregate counts?
by epidata-list＠lists.umanitoba.ca 30 Aug '05

30 Aug '05

First, my thanks to Dirk for answering an earlier query of mine. Please forgive another question. For each record, I calculate a value at the bottom of the data entry form and determine if the respondent fits in group 1 or group 2. Is there any way to hide this group designation for the individual record (as in the value cannot be seen in the form), but still count the aggregate number of respondents fitting into group 1 or group 2? I consider using a temporary variable as a counter, but this raises complications if records are entered in separate batches or earlier records have their values modified. Thanks! Anthony

1 0

Double Entry Verification and several fields to match on
by epidata-list＠lists.umanitoba.ca 26 Aug '05

26 Aug '05

> [EpiData-list] verification question >>> [1] I would like to MATCH RECORDS by more than ONE FIELD when >>> preparing double entry verification - is this possible ? >>> [2] Once a file is verified, does the corrected data reside in the >>> *.REC or the *_dbl.REC file ? EpiData has two principles of validation: A. Compare two separate files entered independently. B. Compare at field level while entering data. Preparation of the two are both at the tool menu. A. Copy structure (of existing rec + chk file) B. Prepare Double Entry Verification Actual validation: A. Is done after all data have been entered. In the document menu you can "Validate Duplicate Files". When you specify the two files up to three fields can be used to match the two files. B. Is done while entering data the second time. You can only match on one field. The corrected data resides in the ..._dbl.rec file, which is the one you are adding data to. After point B you can run the two files with option A and get a record of how much was corrected while entering data the second time in ..._dbl.rec file. If you want to create a unique match while entering data on more than one field a typical way of doing so would be to create a key field like this: To do so, e.g. your matching fields are v1 v2 v3 in the check file: v1 mustenter end v2 mustenter end v3 mustenter after entry keyfield = string(v1)+" "+string(v2)+" "+string(v3) end keyfield noenter key unique end I am not sure how double entry would handle this, but make a test and see how it works. regards Jens Lauritsen EpiData Association

1 0

verification question
by epidata-list＠lists.umanitoba.ca 25 Aug '05

25 Aug '05

>>[1] I would like to MATCH RECORDS by more than ONE FIELD when preparing >>double entry verification - is this possible ? And if so, how do I do it ? >> >>[2] Once a file is verified, does the corrected data reside in the *.REC >>or the *_dbl.REC file ? >> >>Thank you.

1 0

Re: EpiData-list Digest, Vol 22, Issue 7 (Out of office)
by epidata-list＠lists.umanitoba.ca 25 Aug '05

25 Aug '05

I will be back at my desk on Monday 5 September 2005 . Until then my access to email will be very limited, and I will address most of it upon my return. If there is anything requiring urgent attention, please contact: Rebecca.Collins(a)lshtm.ac.uk +44 020 7927 22 14 or Rachel.Clarke(a)lshtm.ac.uk +44 020 7927 22 14 Kind regards Kristof >>> epidata-list 08/25/05 18:01 >>> 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..."

1 0

Analysis build 36 released
by epidata-list＠lists.umanitoba.ca 25 Aug '05

25 Aug '05

Analysis build 36 was just released for testing. at http://www.epidata.dk/testing.php Unless users report severe problems, the current build will be released as version 1.0 with some restrictions or removal of commands with problems, see below. Version 0.9 release 5 build 36 * Added or modified o A "select font" on first startup to guide the user for efficient setup of screen o Improved documentation of output formation o Table command can show categories defined as missing o New option controls if more than one instance of the programme can run o Aspects of handling missing value further implemented. o Parsing of strings changed to exclude trailing blanks: e.g "Lion " is the same as "Lion", but not the same as " Lion". o sorting of tables corrected o Tests of homegenity (interaction) in summary stratified 2x2 tables removed until final stable solution is found * Bugs fixed: o "Pointer error" in tables, graphs or describe fixed o Error in table estimates for 2x2 tables o Recnumber now returns number within current select o set listrec was not working Remaining known major issues to settle before v1.0 * Tables must be included in txt formatted log files Known major issues not settled or clarified * Relating files not tested fully * Appending in combination with records marked for deletion * Odds Ratios and RR in tables with Rare data (0 in cells) * Tests of homegenity (interaction) in summary stratified 2x2 tables removed until final stable solution is found Known issues not fixed (put on future list) * Correlate command results in "floating point error" when correlate cannot be calculated * Contents of strings should be converted to UPPER in logical statements to work. e.g. count if upper(v) = "TEST" * Setting format (set number format) is not consistent Kind regards Jens Lauritsen

1 0

match records by field help in verification
by epidata-list＠lists.umanitoba.ca 17 Aug '05

17 Aug '05

[1] I would like to MATCH RECORDS by more than ONE FIELD when preparing double entry verification - is this possible ? And if so, how do I do it ? [2] Once a file is verified, does the corrected data reside in the *.REC or the *_dbl.REC file ? Thank you.

1 0

Re: protecting formulas in check file?
by epidata-list＠lists.umanitoba.ca 12 Aug '05

12 Aug '05

You cannot protect the chk-file completely (e.g. against someone determined to change its contents), but you can protect it from accidental changes it by setting the read-only flag of the file (see "file attributes" of your operating system). Dirk Anthony (epidata-list-request(a)lists.umanitoba.ca) wrote: > I have some coefficient values and equations in my chk file and I wondered > if there was some way to protect them from being changed by another user > down the road? > > In other words, can I structure it so somone in the field can enter the data > into the form but not manipulate, accidentally or otherwise, the chk file > contents?

1 0

protecting formulas in check file?
by epidata-list＠lists.umanitoba.ca 11 Aug '05

11 Aug '05

I have some coefficient values and equations in my chk file and I wondered if there was some way to protect them from being changed by another user down the road? In other words, can I structure it so somone in the field can enter the data into the form but not manipulate, accidentally or otherwise, the chk file contents? Any help would be much appreciated. Thank you! Anthony

1 0

Why does calculation of age at given date not work ?
by epidata-list＠lists.umanitoba.ca 09 Aug '05

09 Aug '05

Question sent to info(a)epidata.dk: I wrote commands as following, which I follow the help commands: dob AFTER ENTRY LET age=round(int(("1997/11/01"-dob)/365.25)) END END But when I change "1997/11/01" into today, as in the following commands, it works! Why so? dob AFTER ENTRY LET age=round(int((today-dob)/365.25)) END END So I just want to ask what is the problem, because I strictly followed your commands in help manual, but age cannot be calculated on a given date. The formulations above are correct, with one exception. THe help file says also: EpiData was made in Europe and here dates are written in the notation dd/mm/yyyy, so to make the statements above work LET age=round(int(("1997/11/01"-dob)/365.25)) should be: LET age=round(int(("01/11/1997"-dob)/365.25)) regardless of which format dob has. It is better to send questions like this to the EpiData list at: epidata-list(a)lists.umanitoba.ca, since the info @ epidata.dk is very often overly filled with spam mails. Jens Lauritsen Coodinator and initiator of EpiData

1 0

Re: EpiData-list Digest, Vol 22, Issue 2
by epidata-list＠lists.umanitoba.ca 08 Aug '05

08 Aug '05

To see value labels you need not (only) the question file (.qes) but the records validation file, as well. One possibility for the different results you obtain is that the validation file (.chk) is not always in the directory EpiData expects it to be - EpiData lets you enter data, create a codebook etc. even if no validation file exists (or if the validation file is in a different directory as the records file .rec). In that case, however, no value labels can be applied. Dirk Cahterine Mathews (epidata-list-request(a)lists.umanitoba.ca) wrote: > Hi > We're using version 3.1, downloaded from the Epi Data site. This is the > first time we've used Epi Data. We are in the process of entering data > into it. Initally, when we created a codebook from the QES file, the > codebook displayed the values together with the value labels. But in > subsequent attempts to create a codebook from the same QES file, we have > found that the codebook won't show the value labels we entered into the > QES file. Sometimes it won't even show the values. Do you have any > ideas about this? ************************************************* Dr. Dirk Enzmann Institute of Criminal Sciences Dept. of Criminology Edmund-Siemers-Allee 1 D-20146 Hamburg Germany phone: +49-040-42838.7498 (office) +49-040-42838.4591 (Billon) fax: +49-040-42838.2344 email: dirk.enzmann(a)jura.uni-hamburg.de www: http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/E… *************************************************

1 0

data labels
by epidata-list＠lists.umanitoba.ca 08 Aug '05

08 Aug '05

Hi We're using version 3.1, downloaded from the Epi Data site. This is the first time we've used Epi Data. We are in the process of entering data into it. Initally, when we created a codebook from the QES file, the codebook displayed the values together with the value labels. But in subsequent attempts to create a codebook from the same QES file, we have found that the codebook won't show the value labels we entered into the QES file. Sometimes it won't even show the values. Do you have any ideas about this? Thanks! Catherine Mathews School of Public Health and Family Medicine University of Cape Town

1 0

Warmning: False Virus sent in name of EpiData
by epidata-list＠lists.umanitoba.ca 01 Aug '05

01 Aug '05

Warning of Virus sent in name of Epidata 1. Aug 2005 Users are warned against the spread of virus assumingly sent by epidata.dk. Known titles of these are IMPORTANT NOTIFICATION You have successfully updated your password Your Account is Suspended For Security Reasons And assumingly these are sent by: support(a)epidata.dk or webmaster(a)epidata.dk or admin(a)epidata.dk There is NO system at EpiData.dk which would send such information. Simply delete the mails without opening. I do not understand why someone are misusing the internet and collaborative efforts by spreading electronic virus. Quite disturbing to all of us. Regards Jens Lauritsen, EpiData Association

1 0

Status of EpiData Analysis development
by epidata-list＠lists.umanitoba.ca 08 Jul '05

08 Jul '05

Since release of first public test build of analysis in october last year good progress has been made. In judging progress it is important to recognize the nature of the EpiData Association, the size of economic contributions for development and the pricing principle - freeware. The latest build is available from http://www.epidata.dk/testing.php The list of what is fixed and remaing by build number is seen at: http://www.epidata.dk/analysisinfo/docs/versioninfo.htm The bug reporting database is shown at: http://asp.epidata.dk/support/default.asp The routine tests now include more than 350 conditions looking at as well overall, stratified and segmented conditions and comparing to external standard estimates. The aim of the complete test suite is to certify all available commands for a chosen number of representative datasets. The definite condition to meet before release is that the quality system certifies as well stability as correctness of estimation. But also that the implemented principles are logical in structure and documented such that decisions and requirements are clear to the end user. An example of this is the latest preparation of a detailed description of the principles of the output implementation of html and style sheets. The number of combinations of font selection, sizes and character sets is very large requiring control at the level of the end-user. This is available now, but for persons with very little or no knowledge in HTML and stylesheet principles the control of output can be a mystery. The status list includes : a. The main design principle of user interface, output formulation, number of commands, principle of missing data is final and most of it working. b.Finalisation of a simple way for users to define interface with local fonts etc. as part of the installation is almost finished. c. A coherent strategy for handling missing values across commands is being implemented. d. Some issues of table estimation exist. E.g. with correct turning of outcome and exposure. Some "Floating point and "Pointer" error messages occurs with some combinations of data e. Some aspects of graphing are giving problems. (Also relates to point b) Re c: e.g. if the user requests frequency tables for say 5 variables: 1. freq a b c d e 2. freq a b c d e /nomissing the first will show all data for all records, whereas the second will demand complete data for all five variables. This principle should be the same across all commands. And the implementation is needed as part of the testing of handling the data correctly. Kind regards -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Re:Problems with [-] key for entering missing values
by epidata-list＠lists.umanitoba.ca 04 Jul '05

04 Jul '05

Dirk Enzmann wrote: > Using the following .qes and .chk files with EpiData version 3.1, > EpiData's behavior is strange: > > If I use the [-] numeric key to enter missing values in the field > "schtype", EpiData jumps to the field "male" (i.e. "class" receives no > focus). If I use the [-] key in field "male", EpiData issues the error > message "'-' is not a valid floating point value" although missing > values are defined. > > The problem seems to be the movement to the next field after using the > [-] key, because if I drop field "coder" the problem of field "male" > does not occur. > > Is there a problem in the check file I did overlook or is this a > problem of EpiData version 3.1? Are there any solutions/suggestions? > two problems in above 1. I've noticed that the [-] key sometimes gives this error - the field is not accepted (the missing values are not recognized as legal). This seems to be a random occurrence. Closing the file and starting data entry again has solved the problem for me. 2. The problem of EpiData skipping a field after using [-] to enter a missing value can be addressed for now by checking whether the skipped field is blank before proceeding (see below). This problem only arises when the default missing value has the maximum number of digits in a numeric field. In Dirk's case, missing value is 9997 or 9999 in a #### field. Another solution is to make these special missing value codes negative numbers (e.g. -1) or smaller numbers (e.g. 999), which will be smaller than the field size. Then there is no skipping. This problem does not occur with fields of length one. Jamie Hockin Public Health Agency of Canada --------------------------------- * -- .chk -------------------------------- LABELBLOCK LABEL country * [0.2 ] 430 Austria 320 Belgium 3870 "Bosnia and Herzegovina" 11 Canada 3850 Croatia 3570 Cyprus 4200 "Czech Republic" 450 Denmark 440 "England and Wales" 3720 Estonia 3580 Finland 330 France 490 Germany 360 Hungary 3540 Iceland 3530 Ireland 390 Italy 3710 Latvia 3700 Lithuania 310 Netherlands 442 "Northern Ireland" 470 Norway 480 Poland 70 Russia 441 Scotland 3810 Serbia 3860 Slovenia 460 Sweden 410 Switzerland 10 "United States" 580 Venezuela END LABEL schtype * [0.3 ] 1 "slot1 (lowest grade)" 2 slot2 3 slot3 4 slot4 5 slot5 6 slot6 7 slot7 9998 "other schooltype" 9999 "no answer" END LABEL class * [0.4 ] 9997 "ambiguous answer" 9999 "no answer" END LABEL male * [1.0 ] 1 male 2 female 7 "ambiguous answer" 9 "no answer" END END * ======================================== BEFORE FILE HELP "ISRD2 pilot study nation" END * ======================================== casenum * [0.1 ] KEY Autosearch casenum RANGE 1 9999 MUSTENTER TYPE STATUSBAR "CaseNum = " END country * [0.2 ] * RANGE 1 9996 BEFORE ENTRY IF (ISBLANK(country)) THEN COMMENT LEGAL USE country SHOW ENDIF END COMMENT LEGAL USE country MUSTENTER REPEAT TYPE COMMENT END schtype * [0.3 ] RANGE 1 9996 MISSINGVALUE -1 * COMMENT LEGAL USE schtype MUSTENTER * TYPE COMMENT END class * [0.4 ] RANGE 1 9996 MISSINGVALUE 9997 9999 * COMMENT LEGAL USE class MUSTENTER AFTER ENTRY IF (class = 9997) THEN WRITENOTE "ambiguous answer" ENDIF END * TYPE COMMENT END male * [1.0 ] RANGE 1 2 MISSINGVALUE 7 9 * COMMENT LEGAL USE male * before entry * if (isblank(class)) then * goto class * endif * end MUSTENTER * TYPE COMMENT AFTER ENTRY IF (male = 7) THEN WRITENOTE "ambiguous answer" ENDIF END END coder * [66.0s] BEFORE ENTRY if (isblank(male)) then goto male endif TYPE "(alphanumeric)" GREEN END MUSTENTER WRITENOTE "@coder" END * -- end .chk --------------------------------

1 0

Problems with [-] key for entering missing values
by epidata-list＠lists.umanitoba.ca 03 Jul '05

03 Jul '05

Using the following .qes and .chk files with EpiData version 3.1, EpiData's behavior is strange: If I use the [-] numeric key to enter missing values in the field "schtype", EpiData jumps to the field "male" (i.e. "class" receives no focus). If I use the [-] key in field "male", EpiData issues the error message "'-' is not a valid floating point value" although missing values are defined. The problem seems to be the movement to the next field after using the [-] key, because if I drop field "coder" the problem of field "male" does not occur. Is there a problem in the check file I did overlook or is this a problem of EpiData version 3.1? Are there any solutions/suggestions? BTW: Unfortunately, if I want to label the missing values (an important feedback to the coder in case different types of "missingness") I cannot utilize the facility of EpiData to use the [-] key for entering missing values, because I cannot (better: should not) use COMMAND LEGAL and MISSINGVALUE with overlapping sets of values for the same field. This underscores the importance of the suggestions in my last mail (July 1, 2005) to the list. Here the code of the .qes and .chk files: * -- .qes -------------------------------- casenum country specific casenumber [0.1 ] #### country country code [0.2 ] #### schtype school type [0.3 ] #### class class [0.4 ] #### male gender [1.0 ] # coder Coder Initials: [66.0s] <A > * -- end .qes ---------------------------- * -- .chk -------------------------------- LABELBLOCK LABEL country * [0.2 ] 430 Austria 320 Belgium 3870 "Bosnia and Herzegovina" 11 Canada 3850 Croatia 3570 Cyprus 4200 "Czech Republic" 450 Denmark 440 "England and Wales" 3720 Estonia 3580 Finland 330 France 490 Germany 360 Hungary 3540 Iceland 3530 Ireland 390 Italy 3710 Latvia 3700 Lithuania 310 Netherlands 442 "Northern Ireland" 470 Norway 480 Poland 70 Russia 441 Scotland 3810 Serbia 3860 Slovenia 460 Sweden 410 Switzerland 10 "United States" 580 Venezuela END LABEL schtype * [0.3 ] 1 "slot1 (lowest grade)" 2 slot2 3 slot3 4 slot4 5 slot5 6 slot6 7 slot7 9998 "other schooltype" 9999 "no answer" END LABEL class * [0.4 ] 9997 "ambiguous answer" 9999 "no answer" END LABEL male * [1.0 ] 1 male 2 female 7 "ambiguous answer" 9 "no answer" END END * ======================================== BEFORE FILE HELP "ISRD2 pilot study nation" END * ======================================== casenum * [0.1 ] KEY Autosearch casenum RANGE 1 9999 MUSTENTER TYPE STATUSBAR "CaseNum = " END country * [0.2 ] * RANGE 1 9996 BEFORE ENTRY IF (ISBLANK(country)) THEN COMMENT LEGAL USE country SHOW ENDIF END COMMENT LEGAL USE country MUSTENTER REPEAT TYPE COMMENT END schtype * [0.3 ] RANGE 1 9996 MISSINGVALUE 9999 * COMMENT LEGAL USE schtype MUSTENTER * TYPE COMMENT END class * [0.4 ] RANGE 1 9996 MISSINGVALUE 9999 9997 * COMMENT LEGAL USE class MUSTENTER AFTER ENTRY IF (class = 9997) THEN WRITENOTE "ambiguous answer" ENDIF END * TYPE COMMENT END male * [1.0 ] RANGE 1 2 MISSINGVALUE 9 7 * COMMENT LEGAL USE male MUSTENTER * TYPE COMMENT AFTER ENTRY IF (male = 7) THEN WRITENOTE "ambiguous answer" ENDIF END END coder * [66.0s] BEFORE ENTRY TYPE "(alphanumeric)" GREEN END MUSTENTER WRITENOTE "@coder" END * -- end .chk -------------------------------- Dirk ************************************************* Dr. Dirk Enzmann Institute of Criminal Sciences Dept. of Criminology Edmund-Siemers-Allee 1 D-20146 Hamburg Germany phone: +49-040-42838.7498 (office) +49-040-42838.4591 (Billon) fax: +49-040-42838.2344 email: dirk.enzmann(a)jura.uni-hamburg.de www: http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/E… *************************************************

1 0

Bug in EpiData 3.1? (TYPE STATUSBAR)
by epidata-list＠lists.umanitoba.ca 01 Jul '05

01 Jul '05

I noticed some differences between EpiData 3.0 and 3.1 and a possible bug in version 3.1: 1) If I use the check command TYE STATUSBAR "CaseNum = " the value of the field (here: casenum) is only shown in the statusbar if the focus is on the field. If I move to other fields, the value is not visible anymore. This occurs in version 3.1 but not in 3.0. This seems to be an error of version 3.1. 2) Version 3.0 and 3.1 differ in the way they display values defined by RANGE, MISSINGVALUE, and/or COMMAND LEGAL (field). For example, I have a multiple response question and the first question is a filter (if checked, the following multiple response questions do not apply). Or there is no filter variable but I want that the coder first has to decide whether any of the multiple response questions are checked (this is what I use in the following example). If not, I want that all values are set to missing (9 - no answer) and the focus should be set to the next block of questions. On the other hand, if there is at least one answer checked, the focus should move to the first of the multiple response questions and the user has to enter one of the folling values: 0 (no checked), 1 (checked), or 7 (ambiguous answer). When all data are entered, I want that the value labels are defined as follows (because I want that the SPSS syntax attaches value labels to missing values, as well; 8 is necesseary because the whole block of questions may not be applicable): * --------------------------------------- LABEL notice 0 "somebody found out" 1 "nobody found out" 7 "ambiguous answer" 8 "not applicable" 9 "no answer" END * --------------------------------------- However, to help the coder I want that while entering the data he/she does not see these labels but the following: ----------------------------------------- 0 - (not checked) 1 - no 7 - (ambiguous answer) ----------------------------------------- With EpiData version 3.0 this is possible if I use the following check commands: * ======================================= beerdt MISSINGVALUE 9 8 7 * <- (1) BEFORE ENTRY HELP "MULTIPLE RESPONSE QUESTION\n\nQuestion 46.6: Anything checked? (y/n)" KEYS="YN" IF (RESULTVALUE=2) THEN beerdt=9 beerdtpa=9 beerdtpo=9 beerdtte=9 beerdtse=9 GOTO beerpun ENDIF COMMENT LEGAL SHOW * <- (2) 0 "(not checked)" 1 no 7 "(ambiguous answer)" END END COMMENT LEGAL USE notice * <- (3) MUSTENTER TYPE COMMENT RED JUMPS 1 beerpun 9 beerpun END AFTER ENTRY IF (beerdt=0) THEN clear beerdtpa clear beerdtpo clear beerdtte clear beerdtse ENDIF IF (beerdt=1) THEN beerdtpa=0 beerdtpo=0 beerdtte=0 beerdtse=0 ENDIF IF (beerdt = 7) THEN WRITENOTE "ambiguous answer" ENDIF IF (beerdt=9) THEN beerdtpa=9 beerdtpo=9 beerdtte=9 beerdtse=9 ENDIF END END * ======================================= However, with EpiData 3.1, I cannot use "MISSINGVALUE 9 8 7" (see: * <- (1)) _and_ "COMMAND LEGAL SHOW" (see: * <- (2)) or "COMMAND LEGAL notice" (see: * <- (3)) simultaneously. If I use (1) and (2), the user sees: ---------------------- 0 - (not checked) 1 - no 7 - (ambiguous answer) 9 - missing 8 - missing 7 - missing ---------------------- and is able to enter 9 (which should not be used) or 8 (which would be wrong). If I only use (2), the value (9) or (8) cannot be set by the "BEFORE ENTRY .. END" command or by an IF .. THEN condition in another field. To use (3) would also be no solution to this problem. Thus, only version 3.0 seems to allow a solution to this problem. My main question is: Are there any reasons why I should prefer version 3.1 to version 3.0? Or which check commands do I need to solve the problem in version 3.1? With respect to the missing values it would be extemely helpful if EpiData could create SPSS syntax that defines missing values according to the definitions in the EpiData check file. However, if (like in version 3.1) I cannot use MISSINGVALUE and "COMMAND LEGAL labelname" (because I want to label the missing values and to show the coder the meaning of the values entered) simultaneously , there are no missing value definitions that EpiData could use to create the SPSS syntax file. I think that there are two solutions to this problem: (1) If MISSINGVALUE and "COMMAND LEGAL labelname" are used simultaneously, in displaying the legal values the values defined in the LABEL block get priority (and values MISSINGVALUE are not duplicated in the display). This would solve the problem described above, as well. (2) Alternatively, if the MISSINGVALUE is commented out EpiData uses only the values defined by RANGE or COMMAND LEGAL, but uses the values defined by the MISSINGVALUE command that is preceded by "*" for creating the missing value definition in the SPSS syntax. For example: * ---------------------------------------- LABELBLOCK LABEL variable 1 no 2 yes 8 "not applicable" 9 "no answer" END END variable COMMENT LEGAL variable * MISSINGVALUE 9 8 END * ---------------------------------------- would create the following SPSS syntax: * ---------------------------------------- VALUE LABELS variable (1) 'no' (2) 'yes' (8) 'not applicable' (9) 'no answer'. MISSING VALUES variable (9,8). * ---------------------------------------- Regards, Dirk ************************************************* Dr. Dirk Enzmann Institute of Criminal Sciences Dept. of Criminology Edmund-Siemers-Allee 1 D-20146 Hamburg Germany phone: +49-040-42838.7498 (office) +49-040-42838.4591 (Billon) fax: +49-040-42838.2344 email: dirk.enzmann(a)jura.uni-hamburg.de www: http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/E… *************************************************

1 0

Export to SPSS, Variable names
by epidata-list＠lists.umanitoba.ca 24 Jun '05

24 Jun '05

Hello, I have a suggestion for the Epidata-Help-File, section "Export to SPSS": In Epidata you can use variable names (or field names) with a maximum of 10 characters. In newer versions of SPSS (12 or 13) you can use long variable names (64 Byte = 64 characters), in older versions only 8 characters. Exporting Epidata-fields with 10 characters to SPSS leads to shortened field names with 8 characters (for SPSS before Version 12). That causes a lot of work (e.g. renaming variables), if you think that 10 characters are exported. A hint in the Epidata-Help, that if the Data will be analysed in SPSS, the field names should have max. 8 characters, will be usefull. Greetings Juergen Spiegel *********************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493 Web: www.fifas.de e-mail: info(a)fifas.de

1 0

How to: Change id variable type from numerical to string
by epidata-list＠lists.umanitoba.ca 17 Jun '05

17 Jun '05

A question that came to epidata.dk: > In our EPI test.rec file we have made a 'clientnumber' field for a > maximum of 7 numbers entry (#######), for example to enter > clientnumber 3458. This test.rec file contains now several records. > But now we need to use the same field for entering a letters and > digits combination, f.e. P3467188. > I realise that we should have designed a string field <a >>. > > The clientnumber field not only needs to be longer than 7 numbers but > should be suitable for letters as well. > > Is it possible to change that in our current test.rec file? We prefer > that over making a new .qes file and an empty .rec file. > This is of general interest. the solution: 0. Make sure you have proper backup in case something goes wrong. 1. Either add a new field in the qes file with the letter part add a new field for combined letter + number add 2. or make qes and change to string field the same field update the rec file (just enter and epidata will ask ) 3. If you wish to add a certain letter to all previously added records add a recode block to the chk file or other file and run recode from the tools menu. See help file on recode e.g. if new string type id field is idNew and the old numerical one is id recodeblock idletter = "F" idnew = idletter + string(id) end plus to accomplish future records in same file: idnew noenter end idletter mustenter end id mustenter after entry idnew = idletter + string(id) end end -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

RE: selecting on string variables
by epidata-list＠lists.umanitoba.ca 08 Jun '05

08 Jun '05

>>> <epidata-list(a)lists.umanitoba.ca> 25-05-2005 16:59:11 >>> Why is this necessary? I see "LION", upper case and delineated with " ". Thanks, Kelly Because assigning this : if recnumber = 2 then animal = "LION" to a stringvariable of length 10 gets the value: "LION " not the value "LION" Computers are stupid and the designer makes the choices. My choice is that "LION " is different than "LION" Someone would argue that we should always use the trimmed value of string variables, such that "LION " is the same as "LION" but this would give the user a problem if he/she wanted to compare the full length string. The strategy of EpiData for as well data entry as the coming release of analysis is that we make as few decisions as possible and let the end user decide. This is in contrast to other software developers who often impose new and changed strategies and changed ways of doing things on the users (Who is then forced to keep upgrading and learning new ways of doing what they could do with the old principle). EpiData tries NOT to invent new ways of doing things, but stick to the well founded principles of Epi6 (with appropriate extensions for those who wish to use the new principles of further documentation). Regards Jens Lauritsen Initiator of EpiData Coordinator EpiData Association

1 1

RE: [EpiData-list] value labels
by epidata-list＠lists.umanitoba.ca 03 Jun '05

03 Jun '05

Hi. It's possible to store comment legal values up to 80 characters long (EpiInfo / EpiData limit for string length). To do so, refer to a lookup table (see 'Comment legal' help section for that.) ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : jeudi 2 juin 2005 15:03 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] value labels Hello to all! I have being using data entry software for my work and that of epi data is very interesting and smooth but my problem is that it can not take long value label with 256 characters. Is there anyone that can give me a suggestion of defining value labels for a variable with long characters. SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Fri, 27 May 2005 12:02:51 -0500 (CDT) Subject: EpiData-list Digest, Vol 19, Issue 9 > 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..." ------- End of Original Message -------

1 0

RE: [EpiData-list] Relational database
by epidata-list＠lists.umanitoba.ca 03 Jun '05

03 Jun '05

In order to add only 1 related record (thus automatically go back to 'mother' datafile as soon 1 related record has been saved, just add '1' (without ') at the end of the RELATE command Example: RELATE IDENTFIELD DATAFILE2.REC 1 Best regards, ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : mercredi 1 juin 2005 16:36 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] Relational database Hello! I have long questionnaire, so I divided it into two parts using through relational database. At the end of part 2, the EpiData is starting again part 2, taking it as new subrecord. How can I let EpiData start new record in part 1 (i.e. for a new person)? Thank you in advance! /Ziad

1 0

Topics in EpiData-List
by epidata-list＠lists.umanitoba.ca 02 Jun '05

02 Jun '05

The EpiData-list has been set up with two topics today: Analysis Data Entry A topic is a way to selectively receive only part of the mails from the discussion list. By default ALL mails are sent to all users. Even annoying ones, such as when I forgot to turn off an "out of office" message to the list last week (excuses) and all users received a message in Danish. How does topics work ? If a user is signed up to only "analysis", then only mails which contain the word "analysis" in the subject line or the first 15 lines of text in the body of the message will be sent to that user. If you wish to receive all mail: You do not have to do anything. If you wish to select only mails for one or the other topic: Go to this page in your browser http://lists.umanitoba.ca/mailman/options/epidata-list and edit your user profile. Further information is given on that page. For all users it is always good practice to choose wording of the subject such that other users can see what this mail is about. This is particularly true when topics are in effect. Regarding release of analysis I can inform you that we are progressing, but some errors in the basic handling of selecting data has postponed the release. The problem is related to a valid way of separating float values, such as e.g. 3.1 from 3.100000000001 and 3.097865491 Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

value labels
by epidata-list＠lists.umanitoba.ca 02 Jun '05

02 Jun '05

Hello to all! I have being using data entry software for my work and that of epi data is very interesting and smooth but my problem is that it can not take long value label with 256 characters. Is there anyone that can give me a suggestion of defining value labels for a variable with long characters. SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Fri, 27 May 2005 12:02:51 -0500 (CDT) Subject: EpiData-list Digest, Vol 19, Issue 9 > 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..." ------- End of Original Message -------

1 0

Relational database
by epidata-list＠lists.umanitoba.ca 01 Jun '05

01 Jun '05

Hello! I have long questionnaire, so I divided it into two parts using through relational database. At the end of part 2, the EpiData is starting again part 2, taking it as new subrecord. How can I let EpiData start new record in part 1 (i.e. for a new person)? Thank you in advance! /Ziad

1 0

(no subject)
by epidata-list＠lists.umanitoba.ca 31 May '05

31 May '05

Hi!everyone. I just obtain EPIDATA and I find it very useful. But I cann't analyze the data with Spss. Does Epidata have fountion to transform *.rec to *.sav? 　　　　　　　　致礼！　　　　　　　　stephen 　　　　　　　　stephen_ling(a)163.com 　　　　　　　　　　2005-05-31

1 2

Vedr.: [EpiData-list] (no subject) (Kontakt til Jens Lauritsen Uge 8 )
by epidata-list＠lists.umanitoba.ca 31 May '05

31 May '05

Jens Lauritsen, Overlæge afd.O-Ulykkes Analyse Gruppen, Odense Universitetshosptal Tæffes igen 1.juni. Kontakt evt. sekretariatet på (+45) 65412283 Ved hastesager kan der indtales besked på (+45) 21732293 Will be back June 1st.

1 0

RE: Date variable
by epidata-list＠lists.umanitoba.ca 27 May '05

27 May '05

Hi! The 3 variables (Day, Month and Year) have to be string (or at least, it works that way!) Assuming following variable names : Date: DATE, Day: DAY, Month: MONTH, Year: YEAR) In the After entry block of the date variable, place the lines below: DAY = day(DATE) MONTH = month(DATE) YEAR = year(DATE) Day, month and year are functions which automatically extract the corresponding values. Note: besste to create string variables, so days / months < 10 will stay the way thay have been entered, (03 will wtay 03 and not 3). Best regards Gilles -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : vendredi 20 mai 2005 05:05 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] Date variable Hi all! I am trying to create three variables: Day, Month and Year that would read automatically their values from Date variable (<dd/mm/yyyy>) but unfortunately can't get well how to do it, Any tips please? Thank You in advance! Best regards! /Ziad -- Medecins Sans Frontieres - Holland NorthSudan project Upper Nile State

1 0

RE: [EpiData-list] Re: selecting on string variables
by epidata-list＠lists.umanitoba.ca 25 May '05

25 May '05

Why is this necessary? I see "LION", upper case and delineated with " ". Thanks, Kelly -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Sunday, May 01, 2005 2:16 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re: selecting on string variables > 1. How to select "string variables" in Epidata Analysis ? > select outcome="death" An example should clarify: Try this: generate 3 // make 3 artificial records gen integer id = recnumber // create id variable define animal _________ // make a string variable * add value to the variable: if recnumber = 3 then animal = "monkey" if recnumber = 1 then animal = lower("LION") if recnumber = 2 then animal = "LION" . list ID ANIMAL 1 lion 2 LION 3 MONKEY * so we see that we have three values for the variable animal. * and we have two variables: . var Name Type Length Decimals ID Integer 12 0 ANIMAL String 9 0 %s9 * now we try various selects: select if animal = "LION" count No records available select // to select if upper(animal) = "LION" count No records available select select if upper(trim(animal)) = "LION" count Count : 2 The essense is therefore that to do a select on a string variable, you have to use as well sometimes the function upper() and the function trim() to get a proper selection. regards Jens Lauritsen Initiator of EpiData Coordinator EpiData Association

1 0

Creating three variables from one
by epidata-list＠lists.umanitoba.ca 21 May '05

21 May '05

Dear Ziad: I am not sure I understood you correctly, but if yes, this is what you would do: QES file: testdate <dd/mm/yyyy> dd ## mm ## yyyy #### sex <A> and CHK file: testdate MUSTENTER after entry dd=day(testdate) mm=month(testdate) yyyy=year(testdate) end end DD NOENTER END MM noenter END YYYY NOENTER END SEX MUSTENTER END Regards, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 429 9945 Web: http://www.tbrieder.org

1 0

Date variable
by epidata-list＠lists.umanitoba.ca 19 May '05

19 May '05

Hi all! I am trying to create three variables: Day, Month and Year that would read automatically their values from Date variable (<dd/mm/yyyy>) but unfortunately can't get well how to do it, Any tips please? Thank You in advance! Best regards! /Ziad -- Medecins Sans Frontieres - Holland NorthSudan project Upper Nile State

1 0

Outsourcing of your data processing/conversion requirements
by epidata-list＠lists.umanitoba.ca 09 May '05

09 May '05

Hi, We came across your organization while browsing the web. Kindly allow me to introduce ourselves to you. We are a professional outsourcing partner for all data conversion and related activities (http://www.DataConversion.co.in). Our data conversion division has been around since 1999, and was created with the intent of offering world-class data conversion services to international clientele. We undertake digital conversion of large volumes of content: newspapers, books, journals and a variety of forms, surveys, indexes and other documents from print, electronic images & microfilm. Our low cost digital archiving & metadata conversion services allow for libraries, repositories of special collections and other organizations with limited budgets to digitize their archives for web publication and distribution. Our range of services include, but are not limited to: Data Entry / Conversion / Capture Forms Processing Scanning / OCR Digital Archiving XML / SGML / HTML Formatting, Pre-Press and Typesetting (FrameMaker, QuarkXpress, InDesign) Data collection / Internet Research Proofreading and Copy-Editing Medical / Audio Transcription CAD Conversion Our staff is fully dedicated and capable to provide complete and accurate data conversion services to our worldwide customers at the lowest possible cost, and delivered at the required time. With a robust data security policy & business continuity plan in place, we fully safeguard customer data at all times. We understand the basic international business processes and ensure that all projects undertaken by us are completed within the stipulated time period with complete confidentiality, accuracy, and quality. We are one of the leading Indian organizations in our field, and serve many international organizations. For accomplishing jobs with us, a team of highly trained and dedicated professionals work at our state-of-the-art facilities located in New Delhi, India. Many companies are now outsourcing their work to India. Not only do they achieve substantial cost savings, the availability of a large number of professionally trained personnel also ensures high quality of work. We can serve you efficiently and cost effectively, and deliver as per your customized needs. With every project plan we design and implement, we work to earn our clients' trust. You pay for the services provided or hours worked - only when you need them! If you are interested in cutting your current costs to at least half, increasing your profit margins without compromising on the quality and turn-around time, then please do get back to us. We will be glad to send you a most competitive business proposal. I look forward to hearing back from you. Sincerely, Dhiraj Aggarwal CEO Mobile: +(91) 98100 50809 E-mail: info(a)DataConversion.co.in URL: http://www.DataConversion.co.in This email has been sent expecting the information to be of use and benefit to you. In case you do not wish to receive further emails from us, please send us an email with `REMOVE + your email address' in the subject line and we will remove your email address from our database. We apologize for the inconvenience caused to you.

1 1

Revising a questionnaire
by epidata-list＠lists.umanitoba.ca 02 May '05

02 May '05

Dear Colleagues, As I was using EpiData, I was impressed because it is simple to understand and even train someone on how to use it. However, I was challenged on how to revise a questionnanire and effect the revision into the record file. If you know how to do it, just direct me. I will be happy for your quick response. Regards, ___________________________________________ Lwanga B. Charles Department of Population Studies, Institute of Statistics and Applied Econ., Makerere University, Box 7062 Kampala, Tel: 256-77-575745 Alternative email: chlwanga(a)hotmail.com

1 1

Re: selecting on string variables
by epidata-list＠lists.umanitoba.ca 01 May '05

01 May '05

> 1. How to select "string variables" in Epidata Analysis ? > select outcome="death" An example should clarify: Try this: generate 3 // make 3 artificial records gen integer id = recnumber // create id variable define animal _________ // make a string variable * add value to the variable: if recnumber = 3 then animal = "monkey" if recnumber = 1 then animal = lower("LION") if recnumber = 2 then animal = "LION" . list ID ANIMAL 1 lion 2 LION 3 MONKEY * so we see that we have three values for the variable animal. * and we have two variables: . var Name Type Length Decimals ID Integer 12 0 ANIMAL String 9 0 %s9 * now we try various selects: select if animal = "LION" count No records available select // to select if upper(animal) = "LION" count No records available select select if upper(trim(animal)) = "LION" count Count : 2 The essense is therefore that to do a select on a string variable, you have to use as well sometimes the function upper() and the function trim() to get a proper selection. regards Jens Lauritsen Initiator of EpiData Coordinator EpiData Association

1 0

How to select "string variables" in Epidata Analysis ?
by epidata-list＠lists.umanitoba.ca 01 May '05

01 May '05

Dear sir, Hello. I am one of Epidata Users around the world. I can not select "string variables" by Epidata Analysis. I am not sure whether the "Epidata Analysis" program can select string variables. For example: Name of my Variable : Outcome and my Options for the variable : cure , death , disabled, unknown I write(or do) the command: select outcome="death" But no selection is done and this is the massage : No records available But I am sure that records are available because I myself have entered them and also EpiInfo software do select them ! Thank you REZA __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Do not test estimation in stratified 2x2 tables (b22)
by epidata-list＠lists.umanitoba.ca 15 Apr '05

15 Apr '05

Persons testing build 22 of analysis should notice that the list of issues to resolve before v1.0 contains the line: "Table command - thorough testing of correctness of estimates and inverting tables." Finalisation of estimation procedures started this week and was not included in build 22. The major new part of the programme in build 22 for testing is: a. All file types should be read properly now. Including files with encrypted fields. b. User defined different table design definitions and other refinements to the output design principles. (further documented with installation). regards Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Sending Data files by e-mail and continue working
by epidata-list＠lists.umanitoba.ca 14 Apr '05

14 Apr '05

> Hello everybody, > I sometimes get an error message "Error reading record" > when I open an Epidata *.rec file. ......... > I believe, that this error only happens with data files > that I received as email-attachments. My suggestion that in situations where you want to e-mail the rec file to another place, send it as a zip file. Some systems adds one line or a blank line to attachments, so I would: One of a-c. a From tools menu make an archive and send it - preferably encrypted, such that contents are not giving problems if the e-mail gets lost or sent to an inappropriate receiver. b. Save data file(s) etc. in a new compressed zip-file, include current date in filename: AFTER FILE BACKUP F:\backup\distinationdirectory ZIP myzipfile.zip [DATE] END c Save data file(s) etc. in a new encrypted data file, do not include current date in filename: AFTER FILE BACKUP F:\dist_dir ENCRYPT myencryptfile secretword END (Points b and c copied from the help file for EpiData v3.1 Jens Lauritsen EpiData Association

1 0

Epidata: "Error reading record"
by epidata-list＠lists.umanitoba.ca 14 Apr '05

14 Apr '05

Hello everybody, I sometimes get an error message "Error reading record" when I open an Epidata *.rec file. Sometimes it happens by opening the whole file (I can't open it), sometimes only, when I try to access the last entered record. When I export a data file with this error message (i.e. to SPSS), all records are exported correctly, nothing is lost (as far as I can see). I believe, that this error only happens with data files that I received as email-attachments. Is it possible, that sending *.rec-files by email "destroys" something in the file structure? Any suggestions how to avoid this problem? Thanks for help Juergen Spiegel *********************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493 Web: www.fifas.de e-mail: info(a)fifas.de

1 1

EpiData Analysis build 22 released
by epidata-list＠lists.umanitoba.ca 14 Apr '05

14 Apr '05

Version 0.9 build 22 has been put on the web today: Added or modified Reading of data files and chk files <b>final</b> (see note on recnumber definition above) Output adapted to W3c (www.w3c.org) standards, see pdf file in "docs" subfolder. Simplification of control of what is shown (commands, info, results): set showdefinitions<br>Note some inconsistencies are still there set parameter for table design added Reading of files with encrypted fields (prompt for password or add /key) Major commands can be used with first three letters Reading of missingvalue definitions Output changed to tables (improves speed) Several interface adaptations Added command history window (F7) Much improved examples on opening pages Improved reporting on append Bug removal: Crash when selecting block in output fixed. Documentation on output format described in a pdf file coming with the installation which is now 2 MB (two) Get the new build from: Http://www.epidata.dk/testing.php Note that all files should be readable now. ! regards Jens Lauritsen EpiData Association

1 0

Relate does not update structure automatically with changed qes file
by epidata-list＠lists.umanitoba.ca 12 Apr '05

12 Apr '05

>From the mail to info at epidata: > if you change a qes-file in a relational database, epidata doesn't ask > you to revise the rec-file if you open the file indirectly by the > higher-level file, but only if you open it directly. > cheers. mark Good point. Relate is a very complex system. So to change structure of files in the middle of loading is a potentially error resulting situation. But I agree that the user should be warned somehow. This should be added to the bug/problem reporting database - see link on www.epidata.dk -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0