Re : EpiData-list Digest, Vol 37, Issue 8 - EpiData-list

28 Nov 2006


      Bonjour,
Merci de ne plus m'envoyer de messages!!!
Cordialement
----- Message d'origine ----
De : "epidata-list-request@lists.umanitoba.ca" epidata-list-request@lists.umanitoba.ca
À : epidata-list@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@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@lists.umanitoba.ca
You can reach the person managing the list at
    epidata-list-owner@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@lists.umanitoba.ca)
   2. Re: relational databases- using a mother file field in    a
      check for a child file field (epidata-list@lists.umanitoba.ca)
   3. Re: Value Label (epidata-list@lists.umanitoba.ca)
   4. Re: relational databases- using a mother file field    in a
      check for a child file field (epidata-list@lists.umanitoba.ca)
   5. relational databases- using a mother file field    in     a check
      for a child file field (epidata-list@lists.umanitoba.ca)
----------------------------------------------------------------------
Message: 1
Date: Mon, 27 Nov 2006 16:54:24 +1100
From: epidata-list@lists.umanitoba.ca
Subject: [EpiData-list] relational databases- using a mother file
    field in a check for a child file field
To: epidata-list@lists.umanitoba.ca
Message-ID: 5.1.0.14.2.20061127165249.018c76c8@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@mcri.edu.au
------------------------------
Message: 2
Date: Tue, 28 Nov 2006 12:08:49 +1100
From: epidata-list@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@lists.umanitoba.ca"
    epidata-list@lists.umanitoba.ca
Message-ID:
    525bc0510611271708q5b0863c8x25ba004ddd750fc0@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@lists.umanitoba.ca <
epidata-list@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@lists.umanitoba.ca
Subject: Re: [EpiData-list] Value Label
To: epidata-list@lists.umanitoba.ca
Message-ID: 456B6C1C.90103@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@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@lists.umanitoba.ca
Message-ID: 456B66C1.10406@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@lists.umanitoba.ca
Subject: [EpiData-list] relational databases- using a mother file
    field    in     a check for a child file field
To: epidata-list@lists.umanitoba.ca
Message-ID: 5.1.0.14.2.20061128152929.00c4f020@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@mcri.edu.au
------------------------------
________________________________________
EpiData-list@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