Hello,
I have a problem with relate for two related files (with merge command), and its OK with EPI INFO 6 (DOS)
The key is fiche. I wrote these commands (I simplify) :
read first.rec
merge fiche /file=second.rec
and is written :
Non-unique key in: second.rec
The two files .chk are :
- first.rec
FICHE
KEY UNIQUE
END
ONEVAR
IF ONEVAR=1
THEN
RELATE FICHE SECOND.REC
ENDIF
END
- second.rec
FICHE
KEY 1
END
Thank you
PS : In lifetable Help
/haz and /G are notified
but these commands are not effective
Bernard BRANGER - Médecin coordinateur
Réseau de Santé en Périnatalité
"Sécurité Naissance - Naître ensemble"
des Pays de la Loire
1, allée Baco - 44000 NANTES
Tél 02 40 48 55 81 - Fax 02 40 12 40 72
See the EXAMPLE files in the EpiData folder: house.chk, person.chk, visit.chk
These show how relate works in EpiData Entry, and your files would seem to match them. In Entry, the relationship goes from
house --> relate to person --> relate to visit that is, multiple persons per house, and multiple visits per person.
In Analysis (as in Epi Info), the order is reversed:
read visit merge personid /file="person.rec" etc.
So your example should be
read second merge fiche /file=first
Jamie
Bernard wrote:
I have a problem with “relate” for two related files (with merge command), and it’s OK with EPI INFO 6 (DOS)…
The key is “fiche”. I wrote these commands (I simplify) :
read “first.rec”
merge fiche /file=”second.rec”
and is written :
Non-unique key in: second.rec
participants (1)
-
epidata-list＠lists.umanitoba.ca