- EpiData-list - University of Manitoba Mailing Lists

Related files
by epidata-list＠lists.umanitoba.ca 04 Apr '10

04 Apr '10

Hello, I have two related files : The first “pere.rec with : - QES File Fiche #### var1 ## var2 ## - CHK File fiche key unique end var2 if var2=1 then relate fiche pere.rec endif if var2<>1 then gotowrite endif end The second “fille.rec” with : - QES File fiche #### var3 ## var4 ## - CHK File fiche key end These two related files are correct to entry. But, in analysis, the commands : Read "D:\Bernard\Epidemio\pere.rec" merge fiche /file=”fille.rec" Reponse of software : Non-unique key in: D:\Bernard\Epidemio\fille.rec It is the same problem with “key unique” and “key” with “1” at the end. Thank you your help. Bernard Branger, France _____ J’utilise la version gratuite de SPAMfighter <http://www.spamfighter.com/lfr> pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 1455 courriels spam. Optimisez votre PC trop lent <http://www.spamfighter.com/SLOW-PCfighter/Lang_FR/?cid=sigfr>

1 2

Res: EpiData-list Digest, Vol 78, Issue 1
by epidata-list＠lists.umanitoba.ca 02 Apr '10

02 Apr '10

Hello Pedro Emmanuel and all EpiData friends. I think it might be a keyboard problem. I have experienced some similar problem when writing in LaTeX (in a Sweave file for R). Don't remember well in which UTF-8 (with RKWard and Kile under Linux) or ISO-8859-1 encoding what looked in screen and paper like ">" didn't work like such operator. I guess I solved the problem by converting the code and retype the ">"s. Hope it helps :-) Fúlvio B. Nedel Curso de Medicina, Universidade de Santa Cruz do Sul Brasil ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Quinta-feira, 1 de Abril de 2010 14:00:28 Assunto: EpiData-list Digest, Vol 78, Issue 1 Observação: a mensagem encaminhada está anexada. 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. Exporting to epidata format - not valid boolean expression (epidata-list(a)lists.umanitoba.ca) 2. Exporting to epidata format - not valid boolean expression BUG??? (epidata-list(a)lists.umanitoba.ca) ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com

1 0

Exporting to epidata format - not valid boolean expression BUG???
by epidata-list＠lists.umanitoba.ca 01 Apr '10

01 Apr '10

Hello EpiData friends, I just sent an email about an error "invalid boolean expression" when trying to export to EpiData format with EpiData entry with filters. I guess that I found an unexpected bug. When I use the following filters the export is OK (alt1 is numeric variable formated as ####.##). alt1 <> 42 alt1 = 42 But when I use the following filters the export give this error. alt1 >= 42 alt1 <= 42 alt1 > 42 alt1 < 42 Therefore, I guess there is something to do with the > or < signs! Did anyone experience such an error before? Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil ---------- Forwarded message ---------- From: Pedro Emmanuel Alvarenga Americano do Brasil < emmanuel.brasil(a)gmail.com> Date: 2010/4/1 Subject: Exporting to epidata format - not valid boolean expression To: epidata-list(a)lists.umanitoba.ca Hello EpiData friends, Im having a little trouble that I would appreciate very much some help. I have a rec file which I would like to create a subset. I tried to use the EpiData entry data export, using the filter option. When I set the filter such as: hepato <> 2 it is ok. But when I set the filter as alt1 >= 42 ... or I set the filter as ... (alt >= 42) or (hepato <> 2) I get an error saying this is not a valid boolean expression. I tried in several different ways and I couldnt figure out what Im doing worng. Any tip? Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil

1 0

Exporting to epidata format - not valid boolean expression
by epidata-list＠lists.umanitoba.ca 01 Apr '10

01 Apr '10

Hello EpiData friends, Im having a little trouble that I would appreciate very much some help. I have a rec file which I would like to create a subset. I tried to use the EpiData entry data export, using the filter option. When I set the filter such as: hepato <> 2 it is ok. But when I set the filter as alt1 >= 42 ... or I set the filter as ... (alt >= 42) or (hepato <> 2) I get an error saying this is not a valid boolean expression. I tried in several different ways and I couldnt figure out what Im doing worng. Any tip? Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil

1 0

Linking Epidata to an online database
by epidata-list＠lists.umanitoba.ca 26 Mar '10

26 Mar '10

Hi Are there any of you who have experience with linking Epidata to an online database? If so, how did you manage to do so and how did it work? I am to start up a large study where several subinvestigators will have to enter data from there own computer on a daily basis. I think it would be an advantage to the data management, if we did not have to merge all the datafiles manually, but instead enter them into an online database after each entry session. Thank you, for your help!

1 2

Can Epi Data present text in Kiswahili
by epidata-list＠lists.umanitoba.ca 23 Mar '10

23 Mar '10

We would like to have both english and kiswahili presented in the data entry screen. Is this possible?? Thanks. Conrad

1 0

Re: EpiData-list Digest, Vol 77, Issue 12
by epidata-list＠lists.umanitoba.ca 22 Mar '10

22 Mar '10

Dear Hans, Thank you for asking; indeed the idno is key unique 1 in file.rec1 and key unique 2 in file.rec2 and file.rec 3. I have tested the files using different computers (at least 3) they all work fine (sorry for not stating this in my previous request). However, the error occurs and continues to occur when I use my lap top (Vista) and yet this is my main tool to design the entire database. Clearly, the error may not be associated with EpiData; but something to do with my laptop (with Vista, in particular). Are there any solutions or just ignore it? Kind regards Tieble On 21 March 2010 17:00, <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. Re: "Cannot apply opGT to missing operands" > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 20 Mar 2010 21:26:16 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] "Cannot apply opGT to missing operands" > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4BA52F68.6030302(a)tbrieder.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear Tieble: > > Just to get it out of the way (apologies if it is too trivial a > question): is your idno KEY UNIQUE in file1.rec and KEY in file2.rec? I > am asking because I simulated it and get no error message. > > Hans > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > > Dear colleagues, > > > > Is there a possible solution to avoid the error message > > "Error in IF expression; Cannot apply opGT to missing operands" > > during data entry under the check commands below? > > NB: (values and labels 0=No; 1=Yes) for varsv1 > > > > varsv1 > > COMMENT LEGAL USE label_varsv1 > > MUSTENTER > > TYPE COMMENT > > AFTER ENTRY > > IF varsv1=1 THEN > > GOTO WRITE > > ENDIF > > IF varsv1=0 THEN > > RELATE idno file2.rec > > ENDIF > > END > > END > > I am not sure if this error message is related to a bug or typo. > > Your help would be very appreciated. > > > > Tieble > > London, UK > > > > > > -- > Hans L Rieder, MD, MPH > Jetzikofenstr 12 > 3038 Kirchlindach > Switzerland > > Tel: +41 31 829 4577 > Mob: +41 79 321 9122 > Web: http://www.tbrieder.org > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 77, Issue 12 > ******************************************** >

1 1

"Cannot apply opGT to missing operands"
by epidata-list＠lists.umanitoba.ca 20 Mar '10

20 Mar '10

Dear colleagues, Is there a possible solution to avoid the error message "Error in IF expression; Cannot apply opGT to missing operands" during data entry under the check commands below? NB: (values and labels 0=No; 1=Yes) for varsv1 varsv1 COMMENT LEGAL USE label_varsv1 MUSTENTER TYPE COMMENT AFTER ENTRY IF varsv1=1 THEN GOTO WRITE ENDIF IF varsv1=0 THEN RELATE idno file2.rec ENDIF END END I am not sure if this error message is related to a bug or typo. Your help would be very appreciated. Tieble London, UK

1 1

Text editor for EpiData Analysis programs
by epidata-list＠lists.umanitoba.ca 18 Mar '10

18 Mar '10

Jens and I gave last week a course for operations research fellows in The Union's training program. One colleague pointed us to the excellent free Crimson text editor (http://www.crimsoneditor.com/). Jens wrote then the necessary key and language components that can be inserted into the editor to read and edit EpiData programs color-coded to reduce errors if you wish to edit your analysis programs outside the native EpiData Analysis text editor. I can strongly recommend it. Visit the EpiData website http://www.epidata.dk/download.php page and look at the bottom for utilities. Hans PS: Thank you, Zaw, for pointing us to the editor, and thank you Jens, to make it particularly useful for EpiData Analysis programs.

1 2

Re: EpiData-list Digest, Vol 77, Issue 8
by epidata-list＠lists.umanitoba.ca 18 Mar '10

18 Mar '10

Hi Jamie, Thank you very much; it worked in my hands and I managed to reproduce it successfully. I will try to apply it to the entire multilevel database Tieble London, UK On 17 March 2010 17:00, <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. Change the colour of data entry form; and entering contact > number for each person (epidata-list(a)lists.umanitoba.ca) > 2. Re: Change the colour of data entry form; and entering > contact number for each person (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Mar 2010 19:41:03 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Change the colour of data entry form; and > entering contact number for each person > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <bf1bb7701003161241o6a547b5fxd5d665ca74b6398b(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear colleagues, > > I am designing relational database and would like the data entry staff > to be able to enter the identification number (idno) and not to have to > type > in the contact number of each idno (person). The field for the contact > number should be field automatically for each idno. More importantly, it > should start with one for each idno. > > For example for idno 001 contact 1; 2; 3; 4; 5; 6; 7; 8; 9; 10 > for idno 002 contact 1; 2; 3; > ..................................100 > > Clearly, given that idno is a string; I have tried the following command > which > IDNO > AFTER ENTRY > IF IDNO=IDNO THEN > LET CONTACTNUM=1+RECORDCOUNT > ENDIF > END > The result is not different from automatic contact number. > Any suggestions will be appreciated. > > Thank you for your time and suggestions > > Tieble > > > ------------------------------ > > Message: 2 > Date: Tue, 16 Mar 2010 19:30:09 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Change the colour of data entry form; and > entering contact number for each person > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP90051533776303A978B93FFD2D0(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > Here is one solution that requires you to have a field in the main case > .rec file that holds the number of contacts entered so far. It may not be > perfect, but should work for data entry and record review just fine. > > There are 4 files in my example > main.qes - the Main case file > main.chk > contact.qes - the Contact file > contact.chk > > The .chk files pass the highest contact number back and forth using the > global variable xcon and the data entry person cannot change the contact > number. > > The "before record" block in contact.chk increments xcon to give the next > contact number, but this only gets saved back to main.rec when a new record > is saved. If only existing records are revised and saved, the number of > contacts does not change. > > This is a example of related files communicating with each other through a > global variable. > > I hope this helps. >

1 0