January 2008 - EpiData-list - University of Manitoba Mailing Lists

News sent out - and analysis b130 ready for testing
by epidata-list＠lists.umanitoba.ca 31 Jan '08

31 Jan '08

I placed build 130 on the www.epidata.dk/testing.php for download. Please see if recently reported bugs are solved as I expect. Most importantly it will be welcomed if some have the time to see if the adapted menu system is clear. The change is needed to facilitate translation. Some experimentation can be done with translation but it is not in place completely. (translators can request material). Some issues are still unsolved in v2, such as special types of merge and other details having the status "unresolved" in the Mantis database. A news message has been sent to all 1046 persons registered on the "receive news from EpiData Association". I am not sure if an error occurred, but possibly everyone received the message four times (apologies if this is so). Regards Jens Lauritsen EpiData Association

1 0

Export SPSS : name variables length
by epidata-list＠lists.umanitoba.ca 31 Jan '08

31 Jan '08

Hello, When exported from epidata, variables are limited to 8 characters. Recent version of SPSS (V11 and above) allows longer names. Would it be possible to add an option on the export dialog box to allow a length fixed by the user ? A command line option for epic would be necessary to take into account this parameter. In CHK files it is possible to specify MISSING VALUES with the appropriate command. When data are exported to SPSS, the MISSING VALUES syntax is not created. Would it be possible to add this syntax in the next minor release of Epidata ? Thanks for all. Jean-Marie Chrétien Centre de Recherche Clinique CHU ANGERS - FRANCE

1 0

New EpiData Entry v3.1 (build 27Jan2008) uploaded -warning of incorrect counts with analysis tab /cc option
by epidata-list＠lists.umanitoba.ca 28 Jan '08

28 Jan '08

A new compilation of EpiData Entry has been uploaded for all languages. The following bugs have been fixed: Bug fix for export to SPSS (dates) Bug fix jump to noenter field Integers up to 9 digits saved as integer (extended from 4) for compatibility with Analysis Backup relative paths fixed Various other issues, see Mantis database Regarding the long integers (9 digits) - this will be changed in an upload of EpiData Analysis expected later this week. The revised build of analysis will also fix the wrong placement of counts in "Tab ..... /cc" , where there is a misplacement of counts btw. columns. (Mantis issue reported) Until the bugfix has been uploaded get correct counts by also adding the /obs option. E.g. tab case sex ham eggs protein /cc /obs And use the correct counts in the "obs" column. Odds ratios and ChiSq tests are correct. The translation of analysis is in preparation and the implementation of this has revealed need for more clear separation of the various menu parts. Before final upload a testversion will be placed for comments on the testing page. The list will be notified, when this occurs. Regards Jens Lauritsen EpiData Association

1 0

Guide Epidata Analyse en francais
by epidata-list＠lists.umanitoba.ca 21 Jan '08

21 Jan '08

Bonjour, Je vous annonce qu'un guide de EPIDATA Analysis 2.0 est disponible en *.pdf sur le site suivant <http://www.reseau-naissance.fr> http://www.reseau-naissance.fr, page Epidémiologie Ce guide fait 17 pages. Merci de vos avis. PS : A la réflexion, il manque un "config.epi" comme dans EPIINFO pour paramétrer par défaut les résultats des commandes comme les % dans les tableaux comme dans la version 1.0 ! Bernard BRANGER - Médecin coordinateur Réseau de périnatalité "Sécurité Naissance - Naître ensemble" des Pays de la Loire 1, allée Baco - 44000 NANTES Tel 02 40 48 55 81 - Fax 02 40 12 40 72 Courriel : <mailto:bernard.branger@naitre-ensemble-ploire.org> bernard.branger(a)naitre-ensemble-ploire.org Site Internet : <http://www.reseau-naissance.fr> http://www.reseau-naissance.fr _____ J'utilise la version gratuite de SPAMfighter pour utilisateurs privés. 4605 e-mails spam ont été bloqués jusqu'à maintenant. Les utilisateurs payant n'ont pas ce message dans leurs e-mails. Essayez SPAMfighter <http://www.spamfighter.com/lfr> gratuitement maintenant!

1 0

Re: Exporting to SPSS
by epidata-list＠lists.umanitoba.ca 17 Jan '08

17 Jan '08

Hi Bruce, Perhaps one could press just "enter" key without any number (known 999 treated as missing by EpiData) rather than leaving it blank. If you leave it blank without pressing enter EpiData may not recognise it as missing consequently SPSS will not. You will also need to chance the missing code 9 or 999 to SPSS missing code. Kind regards Tieble On 17/01/2008, epidata-list-request(a)lists.umanitoba.ca < epidata-list-request(a)lists.umanitoba.ca> wrote: > > 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 to SPSS messed up by missing data > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Export to SPSS messed up by missing data > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 16 Jan 2008 15:50:29 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export to SPSS messed up by missing data > To: "EpiData List" <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <73dc8140801161250k4c49d36bge7101df054e1727e(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello folks. I just noticed that when I export to SPSS, things can end up > either missing or in the wrong columns when there are empty fields in the > .rec file. Here's a simple example I generated to test it. I created a > .qes file that looks like this: > > {string1} String variable 1 __________ > {num1} Numeric variable 1 ## > {datevar1} Date variable 1 <yyyy/mm/dd> > > {string2} String variable 2 __________ > {num2} Numeric variable 2 ## > {datevar2} Date variable 2 <yyyy/mm/dd> > > {string3} String variable 3 __________ > {num3} Numeric variable 3 ## > {datevar3} Date variable 3 <yyyy/mm/dd> > > ------------------------------- > > Then I entered a couple rows of data, with complete data on row 1, but > incomplete data on row 2 (num1 and datevar 1 were left blank). > When I export to Excel, I get the following (which is correct): > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > DATEVAR3 > record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3 > 06/01/2008 > rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23 > 02/01/2008 > > But if I export to SPSS, I get this, which is not correct: > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > DATEVAR3 > record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3 > 01/06/2008 > rec 2.1 . . 2201/01/20 8 . 2301/02/20 > 8 . > > My first thought was that SPSS 16 is lousing things up. (I've been forced > to upgrade from v15 due to an institutional decision, and I've noticed > several other problems with v16). But the same problem occurred when I > tried on another machine running SPSS 11. > > Has anyone else run into this? I didn't find any mention of it in the > archives. > > What I'm doing for now to circumvent the problem is this: > > 1) Exporting to SPSS to get syntax for all the variable and value labels > 2) Exporting to Excel to get the data into a format I can read with SPSS > 3) Creating syntax to import the Excel file, then adding the variable and > value label syntax generated by exporting to SPSS. > > It's not terribly more complicated than a straight export to SPSS, but it > would be nice if I could do it in one step. > > By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2, 4 > gigs of memory IIRC). > > Thanks, > Bruce > > -- > Bruce Weaver > bweaver(a)lakeheadu.ca > www.angelfire.com/wv/bwhomedir > "When all else fails, RTFM." > > > ------------------------------ > > Message: 2 > Date: Thu, 17 Jan 2008 09:34:49 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Export to SPSS messed up by missing data > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <478F1329.8000402(a)fifas.de> > Content-Type: text/plain; charset="iso-8859-1" > > Hello Bruce, > > I had a similar problem, when I exported strings with a length of 80 > characters, which is the maximum. The datalist-syntax for spss was wrong > and imported only 79 (!) characters, so that the following variables > started one column to the left. If the following variable is numeric > with the lenght 1, it will be missing. > > Regards > Juergen > > > epidata-list(a)lists.umanitoba.ca schrieb: > > Hello folks. I just noticed that when I export to SPSS, things can end > up > > either missing or in the wrong columns when there are empty fields in > the > > .rec file. Here's a simple example I generated to test it. I created a > > .qes file that looks like this: > > > > {string1} String variable 1 __________ > > {num1} Numeric variable 1 ## > > {datevar1} Date variable 1 <yyyy/mm/dd> > > > > {string2} String variable 2 __________ > > {num2} Numeric variable 2 ## > > {datevar2} Date variable 2 <yyyy/mm/dd> > > > > {string3} String variable 3 __________ > > {num3} Numeric variable 3 ## > > {datevar3} Date variable 3 <yyyy/mm/dd> > > > > ------------------------------- > > > > Then I entered a couple rows of data, with complete data on row 1, but > > incomplete data on row 2 (num1 and datevar 1 were left blank). > > When I export to Excel, I get the following (which is correct): > > > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > > DATEVAR3 > > record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3 > > 06/01/2008 > > rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23 > > 02/01/2008 > > > > But if I export to SPSS, I get this, which is not correct: > > > > STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 > > DATEVAR3 > > record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3 > > 01/06/2008 > > rec 2.1 . . 2201/01/20 8 . 2301/02/20 > > 8 . > > > > My first thought was that SPSS 16 is lousing things up. (I've been > forced > > to upgrade from v15 due to an institutional decision, and I've noticed > > several other problems with v16). But the same problem occurred when I > > tried on another machine running SPSS 11. > > > > Has anyone else run into this? I didn't find any mention of it in the > > archives. > > > > What I'm doing for now to circumvent the problem is this: > > > > 1) Exporting to SPSS to get syntax for all the variable and value labels > > 2) Exporting to Excel to get the data into a format I can read with SPSS > > 3) Creating syntax to import the Excel file, then adding the variable > and > > value label syntax generated by exporting to SPSS. > > > > It's not terribly more complicated than a straight export to SPSS, but > it > > would be nice if I could do it in one step. > > > > By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2, > 4 > > gigs of memory IIRC). > > > > Thanks, > > Bruce > > > > > > -- > *********************************************************** > Freiburger Institut fuer angewandte Sozialwissenschaft e.V. > FIFAS > Erasmusstr. 16, D-79098 Freiburg > Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493 > Web: www.fifas.de > E-Mail: info(a)fifas.de > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 51, Issue 3 > ******************************************* >

1 0

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 17 Jan '08

17 Jan '08

I will be out of the office starting 01/15/2008 and will not return until 01/23/2008. If you require immediate assistance, please contact Stephen Drew at extension 5330. Thank-you and have an excellent day, Alyshia

1 0

Export to SPSS messed up by missing data
by epidata-list＠lists.umanitoba.ca 17 Jan '08

17 Jan '08

Hello folks. I just noticed that when I export to SPSS, things can end up either missing or in the wrong columns when there are empty fields in the .rec file. Here's a simple example I generated to test it. I created a .qes file that looks like this: {string1} String variable 1 __________ {num1} Numeric variable 1 ## {datevar1} Date variable 1 <yyyy/mm/dd> {string2} String variable 2 __________ {num2} Numeric variable 2 ## {datevar2} Date variable 2 <yyyy/mm/dd> {string3} String variable 3 __________ {num3} Numeric variable 3 ## {datevar3} Date variable 3 <yyyy/mm/dd> ------------------------------- Then I entered a couple rows of data, with complete data on row 1, but incomplete data on row 2 (num1 and datevar 1 were left blank). When I export to Excel, I get the following (which is correct): STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 DATEVAR3 record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3 06/01/2008 rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23 02/01/2008 But if I export to SPSS, I get this, which is not correct: STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3 DATEVAR3 record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3 01/06/2008 rec 2.1 . . 2201/01/20 8 . 2301/02/20 8 . My first thought was that SPSS 16 is lousing things up. (I've been forced to upgrade from v15 due to an institutional decision, and I've noticed several other problems with v16). But the same problem occurred when I tried on another machine running SPSS 11. Has anyone else run into this? I didn't find any mention of it in the archives. What I'm doing for now to circumvent the problem is this: 1) Exporting to SPSS to get syntax for all the variable and value labels 2) Exporting to Excel to get the data into a format I can read with SPSS 3) Creating syntax to import the Excel file, then adding the variable and value label syntax generated by exporting to SPSS. It's not terribly more complicated than a straight export to SPSS, but it would be nice if I could do it in one step. By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2, 4 gigs of memory IIRC). Thanks, Bruce -- Bruce Weaver bweaver(a)lakeheadu.ca www.angelfire.com/wv/bwhomedir "When all else fails, RTFM."

1 1

How to: relate files - how can I get only one record in sub files for each main record ?
by epidata-list＠lists.umanitoba.ca 03 Jan '08

03 Jan '08

Hi, This is fine but I want to have a field in the middle of the form that determines whether to stop and save the record and return to File A or to relate to another file. If the value is 1 save and return. If the value is 2 continue entering data. v4 AFTER ENTRY IF V4 = 2 THEN RELATE id fileC ELSE GOTO WRITE ENDIF END But this (GOTO WRITE) doesn't quite work. Epidata saves the record ok, and returns to File a but then somehow returns to File b in Read Only mode. My structure is exactly as below. I'd like to stay in file a. Note, F10 does not work in this case. I have to use mouse to close. Thanks....Edward ------- Ziad asked: How to go for new record if you have two parts in EpiData? >/ I have database made of two parts. When we finish data entry in "part 2", />/ instead of moving to new record file, and we expect to see part 1, we get />/ new record file in part 2. />/ /I assume the situation is this: a. enter data into file A b. at latest field in file A perform a relate to file B based on unique ID c. continue with more data in B d. at last field in file B you wish to continue with next record in file A. IF you specify in file A last field: after entry relate id fileB end Then after entering last field in file B you will have a new record in file B, but if you instead: after entry relate id fileB 1 end then only one record will be entered in file B and you will return to file A Example: qes files: file a: id <IDNUM> v1 first field # v2 date <dd/mm/yyyy> v3 relate # file b: id ##### v1 first field # v2 date <dd/mm/yyyy> v3 relate # Chk files: file a: id KEY UNIQUE 1 END v3 AFTER ENTRY RELATE id fileb 1 END END file b: id KEY UNIQUE 1 END Kind regards Jens Lauritsen EpiData Association -- (\_ _/) (='.'=) ('')_('') -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Substring function in EpiData Entry
by epidata-list＠lists.umanitoba.ca 01 Jan '08

01 Jan '08

Happy New Year to all! In EpiData Analysis, you can state: if substr(varx,3,2)="YY" then vary="XX" Would anybody know if there is an equivalent to that in EpiData Entry? Thank you, Hans

1 1