- EpiData-list - University of Manitoba Mailing Lists

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

EpiData Analysis - difference error and information
by epidata-list＠lists.umanitoba.ca 26 Dec '07

26 Dec '07

As a follow up on the question reported to the list (in Spanish) I agree we should change: EpiData Analysis, such that error: if syntax of a given command is insufficient or erroneous examples: wrong variable name trying to read data without close information: all situations where an "expected" result did not happen, examples: no data in a variable name of file just read trying to drop variable which does not exist Report comments or situations , where the rule was not applied (once implemented) Another issue is translation. This will start for analysis. And also a translation tool will be developed Regards and happy new year to all. Thanks for support and comments over the previous year. Jens Lauritsen EpiData Association

1 0

List/export data using record filter on dates
by epidata-list＠lists.umanitoba.ca 25 Dec '07

25 Dec '07

>From a datafile, how do I list/export cases with dates between 1/1-31/12 2005. I try to use the record filter function but get the error message "...not a valid boolean expression". The Field type DD/MM/YYYY. Nikolai Stenfors

1 2

problema con epidata analisis
by epidata-list＠lists.umanitoba.ca 21 Dec '07

21 Dec '07

Buenas tardes. manejando el programa de epidata análisis, tengo unas rutinas pgm para correr reportes pero cuando el programa llega a una linea donde se saca cualquier tipo de analisis como una frecuencia simple, y no hay datos en la variable a analizas (en las encuestas digitadas esta variable no tiene ningún dato) el reporte marca un error de "no data present" y aborta el resto del reporte, por lo tanto no sigue ejecutando el resto de ordenes del pgm. alguien me podría ayudar para que cuando realizando estos análisis el programa siga asi no hallan datos corriendo el pgm como si lo hacia epi 6.4D. Agradeciendo la atención a la presente. Atentamente, ************************************************* Andrés Felipe Hincapié Saldarriaga ECA Comunicaciones y Sistemas Cali - Colombia Tel: +572 448 2630 Cel: 300 6078203 Dir. Carrera 36 17B - 07 E-mail: Andyhincapie(a)hotmail.com andyhincapie(a)yahoo.com ************************************************* ----- Mensaje original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviado: jueves, 20 de diciembre, 2007 13:52:24 Asunto: EpiData-list Digest, Vol 50, Issue 4 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. Is it possoble to program menus for Epidata? (epidata-list(a)lists.umanitoba.ca) 2. Re: Is it possoble to program menus for Epidata? (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Dec 2007 21:06:21 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Is it possoble to program menus for Epidata? To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <200712192006.lBJK6MVD002846(a)mail47.nsc.no> Content-Type: text/plain; charset="us-ascii" When I earlier used EpiInfo, I could design menu systems for the users in a study. I realise that the menus in Epidata contain some of those choices I used as menu items before. But is there any menu system for Windows (external to Epidata) that you could recommend as an "umbrella" menu system for running Epidata, including giving menu choices for analysis and tables (perhaps by running EPiInfo modules in the background)? Torleif Ruud ------------------------------ Message: 2 Date: Thu, 20 Dec 2007 15:53:40 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Is it possoble to program menus for Epidata? To: epidata-list(a)lists.umanitoba.ca Message-ID: <476A81F4.2040007(a)epiconcept.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello, Winglue is Menuing system wtrited as a replacement for Epiglue. It allow you to build menu in order to construct little application based on Epidata/Analysis/Epic Winglue use a syntax very close to Epiglue syntax and allow to use VB script in the .mnu file. It's completely freeware and you can dowload it at www.epiconcept.fr/fichiers/winglue/winglue.zip " Help file for winglue is included. You can find more help by downloading the english VBscript manual : http://infopathdev.com/downloads/free/default.aspx or go to online help : http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/h… Gilles Desve epidata-list(a)lists.umanitoba.ca a écrit : > When I earlier used EpiInfo, I could design menu systems for the users in a > study. I realise that the menus in Epidata contain some of those choices I > used as menu items before. But is there any menu system for Windows > (external to Epidata) that you could recommend as an "umbrella" menu system > for running Epidata, including giving menu choices for analysis and tables > (perhaps by running EPiInfo modules in the background)? > > > > Torleif Ruud > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 50, Issue 4 ******************************************* ____________________________________________________________________________________ ¡Capacidad ilimitada de almacenamiento en tu correo! No te preocupes más por el espacio de tu cuenta con Correo Yahoo!: http://correo.espanol.yahoo.com/

1 0

Menu systems in EpiData
by epidata-list＠lists.umanitoba.ca 20 Dec '07

20 Dec '07

Regarding the issue of menu systems I think the suggestion to explore the "Winglue Menuing system" is a good one. In Epidata Analysis a number of possibilities have been built in. With the next few months I expect to upload a short instruction in using these and will notify the list accordingly. The remainder of this text is highly technical and users without insight in html language should be warned at this point. The experienced user can do some experimentation with the following aspects a b c d : a. Look into the html code of the start.htm, the startfont.htm files found where EpiData Analysis was installed. Here you will e.g. see the following lines: <li>When you like the size: Click on the number to save your choice <br> <ul> <li> <A HREF='epi:cls;set echo=off;define fn __________________________ global;fn= "@sysdir";cd "@fn";copyfile "epidatastat.ini" "epidatastat.old" /replace;copyfile "epidatastat.10" "epidatastat.ini" /replace;set viewer font size=10;set echo=on;view "Start.htm"'>size=10</a>   The special features which can be used for definition of menu systems are: <A HREF='epi: ........'>size=10</a> meaning a non-standard html tag, with which the analysis system can run commands. And the only thing the user sees is the part "size=10". The remaining parts are standard analysis commands separated by ";". b. look at the SET commands Issue the command "set" and you will among other things see: . set DISPLAY COMMAND HISTORY OFF DISPLAY COMMAND PROMPT ON etc for COMMANDTREE ,DATABROWSER , MAINMENU, TOOLBAR , variables and woktoolbar. With a combination of creating your own html code with menu's and using these sets, the whole analysis programme can becomme a menu shell . (e.g. when all the display ...... are set to off). c. A simple example: c1 create a startfile, e.g. project.htm containing header etc and the two lines: - <a href="epidata.exe myfile.rec">Enter data in myfile</a> - <a href='epi: read myfile /close; cls; boxplot age; type "See my boxplot" /h3; printviewer; type "Menu: F8";'>See a box plot</a> c2 edit the ini file for epidatastat.ini to set all display "sets" to off. c3 add a line: set START PAGE =project.htm then when you start epidatastat.exe the project.htm file will be the new startfile, just containing the two lines. With knowledge of the html principles you can add tables, background pictures etc. d. look at the technical documentation available at www.epidata.dk/documentation.php regards Jens Lauritsen EpiData Association

1 0

Is it possoble to program menus for Epidata?
by epidata-list＠lists.umanitoba.ca 20 Dec '07

20 Dec '07

When I earlier used EpiInfo, I could design menu systems for the users in a study. I realise that the menus in Epidata contain some of those choices I used as menu items before. But is there any menu system for Windows (external to Epidata) that you could recommend as an "umbrella" menu system for running Epidata, including giving menu choices for analysis and tables (perhaps by running EPiInfo modules in the background)? Torleif Ruud

1 1

Size of surveys epidata can handle
by epidata-list＠lists.umanitoba.ca 13 Dec '07

13 Dec '07

Does epidata have a limit on the numbers of questions, or lines of text that a survey can be made up of?

1 1