- EpiData-list - University of Manitoba Mailing Lists

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

21 Dec '06

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

1 0

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

13 Dec '06

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

1 0

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

12 Dec '06

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

1 0

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

29 Nov '06

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

1 2

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

28 Nov '06

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

1 0

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

27 Nov '06

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

1 0

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

27 Nov '06

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

1 2

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

17 Nov '06

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

1 1

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

16 Nov '06

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

1 0

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

16 Nov '06

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

1 0