- EpiData-list - University of Manitoba Mailing Lists

Consistency check on date field
by epidata-list＠lists.umanitoba.ca 11 Feb '06

11 Feb '06

There is a date (<DD/MM/YYYY>) field on my REC file; date entered here has to be before today. Copy of the check block I wrote for it: dquest AFTER ENTRY IF (DQUEST>TODAY) THEN HELP "Can't be after today!" TYPE=ERROR GOTO dquest CLEAR dquest ENDIF IF (DQUEST<DISOL) THEN HELP "Can't be before sampling date !" TYPE=ERROR GOTO dquest CLEAR dquest ENDIF END END As a matter of fact, it works well, but error message each time an 'illegal value' is entered on the field: 'error in IF expression: cannot apply opLT to boolean operands'. Only way not to see these error msgs each record: I unchecked the 'Show errors that occur in calculations in the check file during data entry'. Someone has an idea? What did I make wrong? Thanks Gilles

1 1

Check files as Email Attachment
by epidata-list＠lists.umanitoba.ca 09 Feb '06

09 Feb '06

1 0

Export code in a .chk file
by epidata-list＠lists.umanitoba.ca 09 Feb '06

09 Feb '06

>.....I used the EXPORT.exe from an old version of Epi-Info with the EXECUTE command in epidata. It seems to work very well. This would work, but if you have properly defined e.g. missing values and value labels (comment legal) in the chk file for your study, then neither variable lable, value label or missing value will be exported to SPSS with the old epi6 export file (I could be wrong). Regarding BACKUP command. If you want one copy marked with current date: IF you want as well a working copy in the backup folder and a zip copy, something like this (the principle here should be tested with proper files): AFTER FILE * first backup from current folder to f:\backup BACKUP F:\backup\ * then create a copy of that folder with EpiC: c:\epidata\EpiC zip f:\backupzip\prjA path replace date f:\backup * The backup file from today would be: f:\backupzip\prjA_09feb2006.zip * then export to SPSS c:\epidata\EpiC e spss f:\backup\file1 f:\spss\file1 replace c:\epidata\EpiC e spss f:\backup\file2 f:\spss\file1 replace c:\epidata\EpiC e spss f:\backup\file3 f:\spss\file1 replace c:\epidata\EpiC e spss f:\backup\file4 f:\spss\file1 replace c:\epidata\EpiC e spss f:\backup\file5 f:\spss\file1 replace END Note that all folders must be created before calling epic first time. With the EpiC.exe being used all labels will be exported. I suggest that you send the final solution to this list, such that other users can see the solution. Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Re: EpiData-list Digest, Vol 28, Issue 3
by epidata-list＠lists.umanitoba.ca 07 Feb '06

07 Feb '06

Thanks a lot for these solutions. In fact, i found a solution this morning : I used the EXPORT.exe from an old version of Epi-Info with the EXECUTE command in epidata. It seems to work very well. By the way, i'd like to know if it is possible to use the BACKUP command twice ( in order to copy all .rec in a different repertory, that is used to export and also make an archive each time I ( or the doctor in charge with this ) enter data.) Thanks again Jerome Externe au Centre de Recherche Clinique CHU d'Angers 2006/2/7, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca>: > 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. Export code in a .chk file (epidata-list(a)lists.umanitoba.ca) > 2. RE: Export code in a .chk file (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 06 Feb 2006 23:46:06 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export code in a .chk file > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <43E7D1AE.6050003(a)epidata.dk> > Content-Type: text/plain; charset="iso-8859-1" > > > I'm searching how i could export data to spss using code in a check > file.The form is made out of 5 differents .rec, related by a KEY variable. > > The easiest would be to export the files via the EpiC batch processor, > which you get from the Epidata.dk web site on the download page. > Include this in an "after file" block, which should work. Alternatively > if you system still blocks the file create a cmd or bat file containing > the epic commands, something like (experiment a bit): > > EpiC export spss file1 * replace > EpiC export spss file2 * replace > EpiC export spss file3 * replace > EpiC export spss file4 * replace > EpiC export spss file5 * replace > > Now you have your five spss syntax files that you ran in SPSS. > > Other examples are: > EpiC e stata allaes * > Exports allaes.rec in the same directory as epic.exe to a new Stata file > with the filename allaes.dta. All records in allaes.rec are exported. > > EpiC e xls allaes * filter="ID=276" > Exports allaes.rec to allaes.xls. Only records where the field ID equals > the value 276 are exported. > > EpiC e SPSS allaes * filter="AESRATER='TP'" > Exports allaes.rec to allaes.dbf. Only records where AESRATER equals > 'TP' are exported. > > EpiC e epd allaes "c:\new\newallaes.rec" fromrec=100 torec=199 WITHDELS > REPLACE > Exports allaes.rec to a new epidata datafile called > c:\new\newallaes.rec. Only records #100-#199 are exported. Include > marked for deletion and replace the datafile. > > Regards > > Jens Lauritsen > EpiData Association > > ps. The ability to pay contributions with credit-card to EpIData > Association will be closed within a few weeks. The early contributions > only barely exceeds the costs for running that service. Future donations > (after the closure) will have to be made with bank-bank transfer. > > > ------------------------------ > > Message: 2 > Date: Tue, 7 Feb 2006 09:38:58 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] Export code in a .chk file > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <A7EAEBFDDEDEF440A7BDD772C73046A2050C9C56(a)xch-vac.ivs.local> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Jerome; > You should use EPIC command processor (http://www.epidata.dk/download.php#epic), in association with Winglue (or executed from a good old .BAT file). Epic can handle data export to numerous formats -including SPSS. Directions for use and syntax examples are provided. > > 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é : lundi 6 février 2006 10:52 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] Export code in a .chk file > > Hi, > > I'm searching how i could export data to spss using code in a check file. > The form is made out of 5 differents .rec, related by a KEY variable. But it's supposed to be used by someone who doesn't have a strong experience with computers. Is there a way to export these 5 files automaticly, and get the 5 .txt for spss export updated each record ? > > Thanks > > Jerome > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 28, Issue 3 > ******************************************* >

1 0

RE: [EpiData-list] Export code in a .chk file
by epidata-list＠lists.umanitoba.ca 07 Feb '06

07 Feb '06

Hi Jerome; You should use EPIC command processor (http://www.epidata.dk/download.php#epic), in association with Winglue (or executed from a good old .BAT file). Epic can handle data export to numerous formats -including SPSS. Directions for use and syntax examples are provided. 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é : lundi 6 février 2006 10:52 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] Export code in a .chk file Hi, I'm searching how i could export data to spss using code in a check file. The form is made out of 5 differents .rec, related by a KEY variable. But it's supposed to be used by someone who doesn't have a strong experience with computers. Is there a way to export these 5 files automaticly, and get the 5 .txt for spss export updated each record ? Thanks Jerome

1 0

Export code in a .chk file
by epidata-list＠lists.umanitoba.ca 06 Feb '06

06 Feb '06

> I'm searching how i could export data to spss using code in a check file.The form is made out of 5 differents .rec, related by a KEY variable. The easiest would be to export the files via the EpiC batch processor, which you get from the Epidata.dk web site on the download page. Include this in an "after file" block, which should work. Alternatively if you system still blocks the file create a cmd or bat file containing the epic commands, something like (experiment a bit): EpiC export spss file1 * replace EpiC export spss file2 * replace EpiC export spss file3 * replace EpiC export spss file4 * replace EpiC export spss file5 * replace Now you have your five spss syntax files that you ran in SPSS. Other examples are: EpiC e stata allaes * Exports allaes.rec in the same directory as epic.exe to a new Stata file with the filename allaes.dta. All records in allaes.rec are exported. EpiC e xls allaes * filter="ID=276" Exports allaes.rec to allaes.xls. Only records where the field ID equals the value 276 are exported. EpiC e SPSS allaes * filter="AESRATER='TP'" Exports allaes.rec to allaes.dbf. Only records where AESRATER equals 'TP' are exported. EpiC e epd allaes "c:\new\newallaes.rec" fromrec=100 torec=199 WITHDELS REPLACE Exports allaes.rec to a new epidata datafile called c:\new\newallaes.rec. Only records #100-#199 are exported. Include marked for deletion and replace the datafile. Regards Jens Lauritsen EpiData Association ps. The ability to pay contributions with credit-card to EpIData Association will be closed within a few weeks. The early contributions only barely exceeds the costs for running that service. Future donations (after the closure) will have to be made with bank-bank transfer.

1 0

Export code in a .chk file
by epidata-list＠lists.umanitoba.ca 06 Feb '06

06 Feb '06

Hi, I'm searching how i could export data to spss using code in a check file. The form is made out of 5 differents .rec, related by a KEY variable. But it's supposed to be used by someone who doesn't have a strong experience with computers. Is there a way to export these 5 files automaticly, and get the 5 .txt for spss export updated each record ? Thanks Jerome

1 0

Re: [EpiData-list] wild cards in variable names?
by epidata-list＠lists.umanitoba.ca 30 Jan '06

30 Jan '06

I have 70 variables, named var1, var2, . . . var70 > Each has a corresponding numerical variable, which is calculated from > the value of var, during data entry, via an IF THEN ELSE statement in > the check file: > > var1num, var2num, . . . var70num > > I would like each varXnum to be zero by default, when a new record is > opened. Easy: (try): before file defaultvalue var1num-var70num 0 end You must get v3.1 latest build (jan 2006) for this to work. Also the variables must be placed in sequence. The first implementation of defaultvalue wasa a bit different, updated installation files with the text below in the help files are uploaded with about 30 minutes. The command DEFAULTVALUE can be used to assign a certain value instead of “blank” for any fields. Default values can be defined like this: In a BEFORE FILE or BEFORE RECORD block you add: DEFAULTVALUE ALL | ALLSTRINGS | ALLSTRING | ALLNUMERIC x Similarly for lists of fields: DEFAULTVALUE field1-field10,field12 x DEFAULTVALUE field14-field20,field11 "x" In a field block: DEFAULTVALUE x A DEFAULTVALUE expands the range, legal or comment legal definitions of a field. If DEFAULTVALUE 9 is part of a field block then the value 9 is allowed to be entered even if e.g. RANGE 1-5 is also defined. Field block specification overrules a general definition in a BEFORE FILE or BEFORE RECORD block. DEFAULTVALUEs will be exported as part of the any COMMENT LEGAL definitions for the field in question. The category text assigned will be “Default”. *NOTE: The value assignment only takes place in new records. Not in already entered records.* / / /Examples:/ (in before file block): DEFAULTVALUE ALL 9 fills all numerical and string fields with 9 DEFAULTVALUE ALL “No info” ALLstrings fills all string fields with “No info” (in a field block): DEFAULTVALUE 2001 assigns the value 2001 as default. (in a string field): DEFAULTVALUE “No Information” assigns the value “No Information” as default. Regards Jens Lauritsen EpiData Association ps. The revising of the website is almost done (a few pages are left).

1 0

wild cards in variable names?
by epidata-list＠lists.umanitoba.ca 26 Jan '06

26 Jan '06

I have 70 variables, named var1, var2, . . . var70 Each has a corresponding numerical variable, which is calculated from the value of var, during data entry, via an IF THEN ELSE statement in the check file: var1num, var2num, . . . var70num I would like each varXnum to be zero by default, when a new record is opened. I found the BEFORE RECORD command, which it seems would do the job. But I want to save on typing, so is there a wildcard character, such as * , so I can type just one command in a BEFORE RECORD block, like this: BEFORE RECORD var*num = 0 END Thanks. -- Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton and Wilson Family Practice Residency, Johnson City, NY cryanatbinghamtondotedu GnuPG and PGP public keys available at http://pgp.mit.edu "If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea." [Antoine de St. Exupery]

1 0

Final problem in " How to: checking for duplicate records"
by epidata-list＠lists.umanitoba.ca 22 Jan '06

22 Jan '06

Apologies for having expressed the "compare current record with previous record or next record" as list if k = ( ( k[_n-1] ) or ( k[_n-1]) ) which should have been: list if ( ( k = k[_n-1] ) or ( k = k[_n+1]) ) The aggregate (tab stat) does not have a /save option, the most efficient is to: aggregate k /sum=x /close /notable select if n > 1 savedata "newfile.rec" Then the newfile.rec would contain only replicates. Jens Lauritsen EpiData Association ps. The revised web site www.epidata.dk is still in construction. I will give a notice when the new design has been completely implemented.

1 1