February 2006 - EpiData-list - University of Manitoba Mailing Lists

EpiData Entry - Export possible bug
by epidata-list＠lists.umanitoba.ca 15 Feb '06

15 Feb '06

Export "1.rec" to "2.rec" reproduces properly the "1.rec" file but the "2.chk" file is incorrectly truncated. -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 429 9945 Web: http://www.tbrieder.org

1 0

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

12 Feb '06

Hello The final code is : AFTER FILE BACKUP "C:\formulaire\sauvegardes" ZIP form DATE EXECUTE "C:\formulaire\bin\EpiC.exe" "e SPS C:\formulaire\donnees\Registre.rec C:\formulaire\exportation_spss\Registre.sps REPLACE" NOWAIT EXECUTE "C:\formulaire\bin\EpiC.exe" "e SPS C:\formulaire\donnees\reponse_DT4.rec C:\formulaire\exportation_spss\reponse_DT4.sps REPLACE" NOWAIT EXECUTE "C:\formulaire\bin\EpiC.exe" "e SPS C:\formulaire\donnees\reponse_somatostatine.rec C:\formulaire\exportation_spss\reponse_somatostatine.sps REPLACE" NOWAIT EXECUTE "C:\formulaire\bin\EpiC.exe" "e SPS C:\formulaire\donnees\reponse_triac.rec C:\formulaire\exportation_spss\reponse_triac.sps REPLACE" NOWAIT EXECUTE "C:\formulaire\bin\EpiC.exe" "e SPS C:\formulaire\donnees\reponse_T3.rec C:\formulaire\exportation_spss\reponse_T3.sps REPLACE" NOWAIT EXECUTE "C:\formulaire\bin\EpiC.exe" "e SPS C:\formulaire\donnees\reponse_dopaminergique.rec C:\formulaire\exportation_spss\reponse_dopaminergique.sps REPLACE" NOWAIT END i don't know if "" are needed ( they were with EXPORT.exe binary file ), but it works well. With Export.exe, only one file is created, a .sps file with labels and data. With EpiC.exe, it's like epidata, datas are in a .txt file and labels with data emplacement in a .sps. I made a .sps called EXPORTATION.sps, wich is made with copies of all .sps files ( registre.sps, reponse_*.sps ), and then merge all these data with the numdos key and then create a registre_reponse.sav spss file. In fact, i only use new .txt files made "after file". In didn't found something to export only data to .txt in a sps-readable format. But it doesn't matter, all works. Thanks a lot for help and for EpiC.exe ( it came very just on time, as I had to give the form last friday ;) ). Jerome P.S : if someone want it, i can send the .sps file but it's not the right place here ;) 2006/2/9, 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. Check files as Email Attachment (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Feb 2006 09:18:11 +0100 (CET) > 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: > <25242.130.226.78.129.1139473091.squirrel(a)webmail.webhosting.dk> > Content-Type: text/plain; charset=iso-8859-1 > > >.....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 > > > > > ------------------------------ > > Message: 2 > Date: Thu, 09 Feb 2006 13:37:47 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Check files as Email Attachment > To: EpiData-list(a)lists.umanitoba.ca > Message-ID: <BAY106-F319344F1FC4736B1646EFC5030(a)phx.gbl> > Content-Type: text/plain; charset="iso-8859-1"; format="flowed" > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 28, Issue 5 > ******************************************* >

1 0

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