- EpiData-list - University of Manitoba Mailing Lists

Epidata with Nertworking
by epidata-list＠lists.umanitoba.ca 28 Apr '06

28 Apr '06

Hi Everyone, I have a quick question, I would like to know if it is possible to use Epidata on nertwork and more than one user to use it at the same time. Regards, Zaharani

1 2

RE: [EpiData-list] How should EpiData Analysis read a CSV (CommaSeparated File)
by epidata-list＠lists.umanitoba.ca 28 Apr '06

28 Apr '06

Hello! I totally agree with you Max on this question. Cheers, Bellinda -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Thursday, March 09, 2006 6:35 PM To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How should EpiData Analysis read a CSV (CommaSeparated File) Hello Jens, I would strongly argue that a missing is a missing and a 0 (zero) is a very distinct value - hence never turn missings into zero by default... or in short: Option 2 Bests Max On 10 Mar 2006, at 10:21, epidata-list(a)lists.umanitoba.ca wrote: > A question has come up. > > Please consider how you find reading of a CSV file in analysis > appropriate: > > > In a csv file the following data is found: > id, s, pos, sex, ill > 1,.,.,f,0 > 2...... etc (rest of records) > > The data in line can be interpreted in two ways: > Option 1: > ID= 1 > s= 0.0 > pos=0.0 > SEX = "f" ill = 0 > > Option 2: > ID= 1 > s= . > pos=. > SEX = "f" ill = 0 > > In other words the question is how to read ",.," should it be: > Option 1: as 0.0 (which is current behaviour) > or Option 2: . > > Any comments on desired behaviour appreciated. > > regards > > Jens Lauritsen > EpiData Association > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 3

Re : EpiData-list Digest, Vol 30, Issue 3
by epidata-list＠lists.umanitoba.ca 18 Apr '06

18 Apr '06

Hello, SPSS exports your data base towards Stata or DBASE by Using Stat Transfert. Then your data base in Epidata imports. Veiled what it is necessary to do. But I do not understand well that is what you want to do thereafter. If is to analyze you could better do it under SPSS Thanks yours Dr Jean-Paul DIBY-KONAN Médecin Santé Publique Responsable Unité Epidémiologie Institut National de Santé Publique 22 BP 1041 Abidjan 22 Rép. Côte d'Ivoire ----- Message d'origine ---- De : epidata-list-request(a)lists.umanitoba.ca À : epidata-list(a)lists.umanitoba.ca Envoyé le : Lundi, 17 Avril 2006, 5h01mn 57s Objet : EpiData-list Digest, Vol 30, Issue 3 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. Can Epidata read SPSS? (epidata-list(a)lists.umanitoba.ca) 2. Vedr.: [EpiData-list] Can Epidata read SPSS? (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 11 Apr 2006 11:29:43 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Can Epidata read SPSS? To: epidata-list(a)lists.umanitoba.ca Message-ID: <443B7707.2000604(a)socmed.ku.dk> Content-Type: text/plain; charset=ISO-8859-15; format=flowed I have a ready SPSS-file (which is awaiting the app.5000 questionnaires of 220 questions each) and want the database to be built up using Epidata in order to reduce errors. Does any of you know if (and how) Epidata can read this SPSS-file? I wanted to ask before I start writing the whole thing manually... -- Kind regards, Christina Schnohr Ph.d.-student, M.Sc.public health Department of Social Medicine Institute of Public Health Blegdamsvej 3 2200 N, Copenhagen Denmark ------------------------------ Message: 2 Date: Mon, 17 Apr 2006 18:04:23 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Vedr.: [EpiData-list] Can Epidata read SPSS? To: epidata-list(a)lists.umanitoba.ca Message-ID: <OFE9671DB0.1BAC101C-ONC1257153.0057D810-C1257153.00582A35(a)ipm.hosp.dk> Content-Type: text/plain; charset="ISO-8859-1" Convert it to Stata (using e.g. StatTransfer or saving it as a Stata-file directly from SPSS (ver 14)) and import it from the Data in/out menu in Epidata. Epidata find all your variablelabels and value labels from the SPSS file. Best regards Seniorstatistician Claus Holst Institute of Preventive Medicine Center for Health and Society Øster Søgade 18, 1 DK-1357 København K Phone +45 3338 3863 Fax +45 3332 4240 Sender: ch(a)ipm.hosp.dk The institute: http://www.ipm.hosp.dk EU projects: http://www.nugenob.org http://www.diogenes-eu.org/ epidata-list(a)lists.umanitoba.ca Sendt af: epidata-list-bounces(a)lists.umanitoba.ca 11-04-2006 11:29 Til: epidata-list(a)lists.umanitoba.ca cc: Emne: [EpiData-list] Can Epidata read SPSS? I have a ready SPSS-file (which is awaiting the app.5000 questionnaires of 220 questions each) and want the database to be built up using Epidata in order to reduce errors. Does any of you know if (and how) Epidata can read this SPSS-file? I wanted to ask before I start writing the whole thing manually... -- Kind regards, Christina Schnohr Ph.d.-student, M.Sc.public health Department of Social Medicine Institute of Public Health Blegdamsvej 3 2200 N, Copenhagen Denmark _______________________________________________ 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 30, Issue 3 *******************************************

1 0

Can Epidata read SPSS?
by epidata-list＠lists.umanitoba.ca 17 Apr '06

17 Apr '06

I have a ready SPSS-file (which is awaiting the app.5000 questionnaires of 220 questions each) and want the database to be built up using Epidata in order to reduce errors. Does any of you know if (and how) Epidata can read this SPSS-file? I wanted to ask before I start writing the whole thing manually... -- Kind regards, Christina Schnohr Ph.d.-student, M.Sc.public health Department of Social Medicine Institute of Public Health Blegdamsvej 3 2200 N, Copenhagen Denmark

1 1

RE: [EpiData-list] Searching records with same field value
by epidata-list＠lists.umanitoba.ca 04 Apr '06

04 Apr '06

Agree with LIST OF RECORDS suggestion and too appreciate Epidata. thanks -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Saturday, April 01, 2006 12:17 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Searching records with same field value Dear Jens, Greetings. Thanks for the good and stable Epidata 3.1. During the database management one often updates the previously entered records. For example in the population database of households I can use the house number to search the previously entered records of many members of same household. In Epidata when I use find option using house number only one record is displayed at a time. In EPI 6.04d one could see LIST OF RECORDS with same house number at a time and choose the desired one by moving the highlighter bar over it and pressing Enter key. Procedure -1. Press Ctrl-F key. 2. Enter specific house number in the House number field. 3. Press F3 key. That displays the list of previously entered records with the same house number. Hence specific record could be located for editing purpose. Epidata does not have that option at present. Please explore the possibity of incorporating similar option in the Epidata also. This option ia really helpful in large population databases. Once again thanks for this wonderful and stable freeware. Please convey my best wishes to Epidata team. Sincerely, Dr. Shavinder Singh Department of Community Medicine Christian Medical College, Ludhiana 141008 Punjab India

1 0

RE: [EpiData-list] error messages
by epidata-list＠lists.umanitoba.ca 04 Apr '06

04 Apr '06

Greetings. What happens if you have more than 1 need of the INI file? Suppose you have a 'system' for PMTCT with INI needs and a VCT system with different INI needs and etc. Would one create subfolders under Program files with different names for the .EXE and .INI files? Would not be a problem if on a single USER system but, what about the SYS administrator of several systems? Thanks. -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Thursday, March 30, 2006 2:44 AM To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] error messages This problem will occure in every place where user's don't have admin privilege. The (micrososft) recommended procedure is to put the executable in program file and only executable (wich include dll's) and all other data in the "documents and settings" folder. This mean that INI file wich is a setting file should also be in this folder. But if everybody agree whit that, I suppose that the program should be modified. Gilles Desve epidata-list(a)lists.umanitoba.ca a écrit : > Yes, we've come across the same problem this week, also happens when > you try to exit the browse window. It only happens on those computers > in the office without admin privileges. > > Tony > > -----Original Message----- > From: epidata-list-bounces(a)lists.umanitoba.ca > [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of > epidata-list(a)lists.umanitoba.ca > Sent: Thursday, 30 March 2006 6:31 AM > To: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] error messages > > > I've set up a data entry routine at one of the office computers. A > colleague ran into these error messages: > > when trying to run documentation->codebook > > Cannot create file file c:\program files\~epdlog1.tmp > > and when trying to exit (file->exit) > > Error writing to .INI file c:\program files\epidata\epidata.ini > > I'm guessing this would happen if the colleague does not have > permission to write to the c:\program files directory. Does that > sound right to others? > > Thanks. > > Richard Herrell > NIH > > > > --------------------------------- > Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ > countries) for 2¢/min or less. > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > <!D2S:tonys@burnet.edu.au/good/b401dd18e8b8cfb/> > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > -- Dr Gilles DESVE Directeur technique Tél : 01 53 02 40 61 ------------- EpiConcept ----------- Systèmes d'Information en Santé 47, rue de Charenton - 75012 PARIS 01 53 02 40 60 Fax : 01 53 02 40 62 --------- www.epiconcept.fr --------- Ce message et toutes les pièces jointes sont établis à l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d'en avertir l'expéditeur.

1 0

Lost information
by epidata-list＠lists.umanitoba.ca 03 Apr '06

03 Apr '06

Hi, Recently, we have lost part of information in the data entry file that we've entered earlier, and I'm wondering if someone else have experienced similar problems. Recently, our data entry staff found that information she had entered the other day disappeared from the file, mainly the ID variable two other variables next to it. The strange thing is that not all of the cases lost the information. Only about one-third of cases lost this information. We're investigating how this happened, and before concluding it might be results of human errors, I'd like to check if this kind of accident has happened to someone else. We're using EpiData 2.01 version. Thank you, Jin

1 0

Searching records with same field value
by epidata-list＠lists.umanitoba.ca 01 Apr '06

01 Apr '06

Dear Jens, Greetings. Thanks for the good and stable Epidata 3.1. During the database management one often updates the previously entered records. For example in the population database of households I can use the house number to search the previously entered records of many members of same household. In Epidata when I use find option using house number only one record is displayed at a time. In EPI 6.04d one could see LIST OF RECORDS with same house number at a time and choose the desired one by moving the highlighter bar over it and pressing Enter key. Procedure -1. Press Ctrl-F key. 2. Enter specific house number in the House number field. 3. Press F3 key. That displays the list of previously entered records with the same house number. Hence specific record could be located for editing purpose. Epidata does not have that option at present. Please explore the possibity of incorporating similar option in the Epidata also. This option ia really helpful in large population databases. Once again thanks for this wonderful and stable freeware. Please convey my best wishes to Epidata team. Sincerely, Dr. Shavinder Singh Department of Community Medicine Christian Medical College, Ludhiana 141008 Punjab India

1 0

RE: [EpiData-list] second try: order of missing valuesindocument->codebook
by epidata-list＠lists.umanitoba.ca 30 Mar '06

30 Mar '06

I gave it a try: - When the variable is NUMERIC (as it is the case in your file), missing (.) values appear at the end of the tabulation. When it is STRING, missing (.) values appear at the top of the tabulation as follows: var1S -------------------------------------------------------------------- var1S type: Texte majuscule Libellés des codes: libellé_var1s manquant: 3/7 valeurs uniques: 4 tabulation: Freq. P.100 Valeur Libellé 3 42.9 . 1 14.3 1 1 1 14.3 2 2 2 28.6 3 3 var2N -------------------------------------------------------------------- var2N type: Numérique Libellés des codes: libellé_var1s manquant: 3/7 fourchette: [2 ; 3] valeurs uniques: 3 tabulation: Freq. P.100 Valeur Libellé 3 42.9 2 2 1 14.3 3 3 3 42.9 . Note: as shown in your example, there is a redundancy in the checkblock: the variable is controlled by a list if valid values ('label_ramde7'), AND there a Range command (0-10,98). As it is already controlled by the list, it is not useful to control it twice with 'Range - legal'. Choose either of the 2 control systems, remove the other one, and check again. ______________________________________________ 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é : mardi 28 mars 2006 00:00 À : epidata-list(a)lists.umanitoba.ca Objet : RE: [EpiData-list] second try: order of missing valuesindocument->codebook That variable is a 2 digit number created with ## in the qes file. Here's the rest of the info about the variable in the codebook: type: Number value labels: label_ramde7 range/legal: 0-10,98 missing: 6/52 range: [3 ; 10] unique values: 8 epidata-list(a)lists.umanitoba.ca wrote: What kind of variable is it? This shouldn't happen id the variable is numeric. -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : vendredi 24 mars 2006 23:40 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] second try: order of missing values indocument->codebook Didn't hear from anyone, so I'm trying again (sorry). I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution ofvalues for thevariables. I just noticed that the missing values (.) appear at an almost random point in the otherwise ordered list (in this example,between 9 and 10). I compared the codebook with SAS tables and the data appear to be correct. tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates. _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list --------------------------------- Blab-away for as little as 1¢/min. Make PC-to-Phone Calls using Yahoo! Messenger with Voice.

1 1

RE: [EpiData-list] second try: order of missing values indocument->codebook
by epidata-list＠lists.umanitoba.ca 30 Mar '06

30 Mar '06

What kind of variable is it? This shouldn't happen id the variable is numeric. -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : vendredi 24 mars 2006 23:40 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] second try: order of missing values indocument->codebook Didn't hear from anyone, so I'm trying again (sorry). I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution ofvalues for thevariables. I just noticed that the missing values (.) appear at an almost random point in the otherwise ordered list (in this example,between 9 and 10). I compared the codebook with SAS tables and the data appear to be correct. tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

1 4

second try: order of missing values in document->codebook
by epidata-list＠lists.umanitoba.ca 24 Mar '06

24 Mar '06

Didn't hear from anyone, so I'm trying again (sorry). I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution ofvalues for thevariables. I just noticed that the missing values (.) appear at an almost random point in the otherwise ordered list (in this example,between 9 and 10). I compared the codebook with SAS tables and the data appear to be correct. tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

1 0

re: variable names
by epidata-list＠lists.umanitoba.ca 23 Mar '06

23 Mar '06

You can change this by selecting the option to use the first word as the field name (under File, Options, Create data file tab). This is described in the help files. You may have to reset your options when you install a new version. There is a newer version on epidata.dk now (12 March 2006) Jamie ============================= In the latest version of Epidata (12012006) field names is not functioning well. I choose field names to be the first word in the line and the software assigne the name with 10 first characters in the line. I can change field names but it is a lot of work. Is it any other solution? Luciana Petrucci Gigante

1 0

First word versus first 10 characters for field naming in EpiData Entry v3.1 (12012006)
by epidata-list＠lists.umanitoba.ca 23 Mar '06

23 Mar '06

We are looking into this problem, which is an error in the installation routine NOT in the actual software once installed. To get the correct behaviour you desire do this: 1. Start epidata.exe 2. Go into the options (see file menu) 3. Choose the "Create data file" part 4. Select either "first word" or "automatic" as you please. The issue in relation to installation will be solved, but until so do as shown in point 1-4. Regards Jens Lauritsen EpiData Association

1 0

Field names
by epidata-list＠lists.umanitoba.ca 23 Mar '06

23 Mar '06

In the latest version of Epidata (12012006) field names is not functioning well. I choose field names to be the first word in the line and the software assigne the name with 10 first characters in the line. I can change field names but it is a lot of work. Is it any other solution? Luciana Petrucci Gigante luciana(a)homemail.com

1 0

tabulation in documentation->codebook
by epidata-list＠lists.umanitoba.ca 22 Mar '06

22 Mar '06

I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution of values for the variables. I just noticed that the missing values appear at an almost random point in the otherwise ordered list (in this example, between 9 and 10). tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

1 0

RE: EpiData-list Digest, Vol 29, Issue 8
by epidata-list＠lists.umanitoba.ca 22 Mar '06

22 Mar '06

either a) or c)with notification -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca Sent: Mon 3/20/2006 1:23 PM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: EpiData-list Digest, Vol 29, Issue 8 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..."

1 0

RE: Design decision.... Restricted words
by epidata-list＠lists.umanitoba.ca 21 Mar '06

21 Mar '06

> Should we : > a. Adopt a strategy, where users are warned when creating files where > field names/variables are > given the same names as a restricted word - a warning. > > b. Maintain current where users will find out since either an error or > occur or nothing happens when > they create confusion in this way - a "non-friendly" way towards > users. > > c. A strategy where field names cannot have the same names as functions. > - a restrictive strategy. Hi, I don't fully understand what option a) implies. If an user receives a warning, can (s)he continues working?. And what next?. Will (s)he get an error sometimes?. In my opinion if there is a risk of conflict bettwen a command or funtion name and the name of a field or variable this name should be prohibited. So, i think the most restrictive option should be implemented (whith a very clear message saying "the word XXXXX is a reserved word, choose another for your variable name"). Saludos, Pedro Pedro Arias Bohigas John Ericssons gatan, 12 5 tr 112 22 Stockholm Sweden Phone (cell) 0734421130 Phone (international calls)+46734421130

1 0

Reserved names
by epidata-list＠lists.umanitoba.ca 21 Mar '06

21 Mar '06

If feasible, strategy a) would be my preference as it offers two things: first it teaches which field name is reserved, second that it cannot be used. Strategy b) is not user-friendly, and strategy c) is less transparent than strategy a) a. Adopt a strategy, where users are warned when creating files where field names/variables are given the same names as a restricted word - a warning. b. Maintain current where users will find out since either an error or occur or nothing happens when they create confusion in this way - a "non-friendly" way towards users. c. A strategy where field names cannot have the same names as functions. - a restrictive strategy. -- 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] Design decision for epidata analysis - missing andrestricted words
by epidata-list＠lists.umanitoba.ca 21 Mar '06

21 Mar '06

I'm also in favour of strategy a). It's certainly the simplest to implement. Gilles -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : dimanche 19 mars 2006 23:21 À : epidata-list(a)lists.umanitoba.ca Objet : Re: [EpiData-list] Design decision for epidata analysis - missing andrestricted words I vote for strategy a) to display a warning - this seems most user friendly and can reduce the problem well. Bests Max On 20 Mar 2006, at 7:34, epidata-list(a)lists.umanitoba.ca wrote: > This mail is technical in nature, if you are not interested in > technical aspects, just delete the mail. > > The issue of how to read ,., in a comma separated file is now solved > and can be tested in v 1.1, rel 7. build 68 - which is the latest on > the web site. > > One other issue which someone might want to comment on is the use of > restricted words. > We know that the use of the words e.g.: date year month weeknum and > other common terms which can also be functions gives a problem. > > It would be helpful if users will comment on strategies to handle > this. The current implementation is NOT to worry about this. In some > programmes there is a list of illegal terms. > > Should we : > a. Adopt a strategy, where users are warned when creating files where > field names/variables are > given the same names as a restricted word - a warning. > > b. Maintain current where users will find out since either an error or > occur or nothing happens when > they create confusion in this way - a "non-friendly" way towards > users. > > c. A strategy where field names cannot have the same names as > functions. - a restrictive strategy. > > In future similar questions as this I will attempt to add "Design > decision" .... in the subject line, such that users on the list not > wishing to get this type of mail can add to a filter. > > To check which version a particular build of EpiData Analysis has > issue the command: > . version > Current version: 1.1 Release 7 (Build 68) If you are on internet the > programme will also look up on the website the latest public release, > e.g.: > Latest public release 1.1 Release 1 (Build 62) Report problems and > suggestions to <the EpiData list> Development versions are located on > the <EpiData testing page> > > Where the text in < ......> are hyperlinks, such that if you click on > them your standard browser will open on those pages. > > regards > Jens Lauritsen > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Design decision for epidata analysis - missing and restricted words
by epidata-list＠lists.umanitoba.ca 19 Mar '06

19 Mar '06

This mail is technical in nature, if you are not interested in technical aspects, just delete the mail. The issue of how to read ,., in a comma separated file is now solved and can be tested in v 1.1, rel 7. build 68 - which is the latest on the web site. One other issue which someone might want to comment on is the use of restricted words. We know that the use of the words e.g.: date year month weeknum and other common terms which can also be functions gives a problem. It would be helpful if users will comment on strategies to handle this. The current implementation is NOT to worry about this. In some programmes there is a list of illegal terms. Should we : a. Adopt a strategy, where users are warned when creating files where field names/variables are given the same names as a restricted word - a warning. b. Maintain current where users will find out since either an error or occur or nothing happens when they create confusion in this way - a "non-friendly" way towards users. c. A strategy where field names cannot have the same names as functions. - a restrictive strategy. In future similar questions as this I will attempt to add "Design decision" .... in the subject line, such that users on the list not wishing to get this type of mail can add to a filter. To check which version a particular build of EpiData Analysis has issue the command: . version Current version: 1.1 Release 7 (Build 68) If you are on internet the programme will also look up on the website the latest public release, e.g.: Latest public release 1.1 Release 1 (Build 62) Report problems and suggestions to <the EpiData list> Development versions are located on the <EpiData testing page> Where the text in < ......> are hyperlinks, such that if you click on them your standard browser will open on those pages. regards Jens Lauritsen

1 1

Calculating elapsed time for a procedure crossing midnight ?
by epidata-list＠lists.umanitoba.ca 18 Mar '06

18 Mar '06

If the procedure will never be less than a few hours, this is just a matter of checking whether end time is less than start time - code added below. For a procedure or event that can take more than 24 hours, you have to have a separate field for end date. ---Jamie Dale wrote: > I'm a novice epidata user and am calculating elapsed time for a > procedure (never more than a few hours) which can cross midnight. > This is implicit if the ending time is less than the starttime. Can > anyone suggest how modify the code below to add a day when the endtime > is after midnight? Thanks! --Dale > > BEFORE FILE > DEFINE varStartTime ########.##### > DEFINE varEndTIME ########.##### > END > > STARTTIM > RANGE 0 23.59 > END > > ENDTIME > RANGE 0 23.59 > AFTER ENTRY > varStartTime=STARTDAT+TIME2NUM(STARTTIM) > varEndTime=STARTDAT+TIME2NUM(ENDTIME) if endtime < starttim then varendtime = varendtime + 1 // add one day to end time endif HOURSMIN=NUM2TIME(varEndTime-varStartTime) > END > > > HOURSMIN > NOENTER > END

1 0

Next build of EpiData Analysis ready for test before public release
by epidata-list＠lists.umanitoba.ca 17 Mar '06

17 Mar '06

The current test build of analysis (build 68) will be put out for general download unless some of you find serious problems. We know there are still some issues being tested, e.g. the rewriting of the table module is not completed and the handling of missing values in comma separated files. But other aspects are final, e.g. the development of detailed help files for a number of main commands and removal of some floating point error bugs. Regards Jens Lauritsen

1 0

How to read CSV files (missing versus zero)
by epidata-list＠lists.umanitoba.ca 16 Mar '06

16 Mar '06

As the discussion has rolled out I am sure we can all agree that "Missing data and zero are two totally different things and should never be interchanged. " Obviously I never intended to have a meaning other than stated with the sentence above. The problem which arose is however that when creating comma separated files it turns out that the contents of the files varies a lot depending on which system is creating the data files. Therefore I asked : > In other words the question is how to read ",.," should it be: > Option 1: as 0.0 (which is current behaviour) > or Option 2: . My worry was that around the world in some places some systems export a zero as ",.," whereas in other areas as ",," >From the messages added by users I decided to implement the latter option. That is in one of the next builds you will see that: Any content of a comma separated file will be imported as : missing if the content of the csv file is: ,., or ,, for a given field. A similar question is related to reading of "empty" boolean fields. E.g. access exports these as "FALSE" or "NO", not as "no value". There is only one cure to this type of problem: The software should not be given control of standards. The standard should be settled by the user or the user community. Regards Jens Lauritsen. EpiData Association

1 1

Re: Hystory/Visit/Treatment related files
by epidata-list＠lists.umanitoba.ca 14 Mar '06

14 Mar '06

Hi, Yves' answer is quite good. My only concern is whether bloodpresure should be recorded in a independent file (BLOOD.REC) or it is a field in the Visits.rec one. As far as I understood blood presure levels are going to be measured in each visits. If that is the case, in my opinion blood presure should be field of the visits.rec file. Treatment, I dare say, should be recorded in a independent file since it shouldn't change with every visit. What do you think? Greetings, Pedro Pedro Arias Bohigas John Ericssons gatan, 12 5 tr 112 22 Stockholm Sweden Phone (cell) 0734421130 Phone (international calls)+46734421130 > Dear epidata > > I would like to set up a database for a clinic. The 4 rec files are > history, visit, bloodresults and treatment. The clinicnr of the patient > is the unique id that I would like to carry over between these rec > files. Secondly the number of records for visits/bloodresults/treatment > for each patient with a specific clinicnr can be more than one over > time. However history only has to be completed once (can be mother > file?). > > When creating a relational database am I right if I say that I cannot > keep clinicnr as the unique nr in every rec file as that will only allow > ONE record with that clinicnr and I need to be able to do multiple > records eg for visits on that one clinicnr. The House.rec etc example > does not really help me with this as the visit rec file is the last rec > file. I have 3 "children files" following one after another. > > Please help with the check files to relate these 4 files whilst keeping > clinicnr as the unique id but allowing multiple records per clinicnr. > > Thanks > > Paul > > > > Prof Paul Rheeder > > Division of Clinical Epidemiology > > Faculty of Health Sciences > > University of Pretoria > > PO Box 667 > > Pretoria 0001 > > Tel 27 12 354 1488 > > Fax 27 12 354 1489 > > > > > > Hello Paul, > > Yes, you're right: in each "child file" there must be the clinicnr > (declared as "key") and, in your case, there must be also another > id-number in each child file declared as "key unique". > Usually, it's convenient to define a "visitnr" in each child file and to > concatenate "clinicnr | visitnr" in a unique id-number > > As far as the relations between files are concerned, I would recommend > to relate each child file to the master file (an not to relate the > first child file to the master file, then the second child file to the > first child file, and so forth). Please note that this can be done > anywhere in the master file (i.e. at a different place for each child > file or at a same place). Please note also that you can decide to open > a child file or not, according to the result of a question. > > Hereafter is an example of what you can do. Hope it helps. > > Happy computing! > > Yves > > > ************ > Master file (for example clinic.chk for clinic.rec file) > ************ > > CLINICNR (better if defined as string) > key unique > mustenter > END > > VAR1 > ... > END > > > VARXXX > ... > AFTER ENTRY > HELP "do you want to enter visit data for this patient? (Y/N)" > KEYS="YN" TYPE=CONFIRMATION > IF RESULTVALUE=2 THEN > GOTO nextvar > ELSE > IF RESULTVALUE=1 THEN > RELATE clinicnr VISIT.REC > ENDIF > ENDIF > END > END > > ... > > > VARYYY > ... > AFTER ENTRY > HELP "do you want to enter blood data for this patient? (Y/N)" > KEYS="YN" TYPE=CONFIRMATION > IF RESULTVALUE=2 THEN > GOTO nextvar > ELSE > IF RESULTVALUE=1 THEN > RELATE clinicnr BLOOD.REC > ENDIF > ENDIF > END > END > > > etc. > > > ************ > Child file (for example visit.chk for the visit.rec file) > ************ > > CLINICNR (string variable) > key > END > > ** please note that the above field will be automatically filled ** > > VISITNR (string variable) > key > mustenter > END > > VISITID (string variable) > key unique > BEFORE ENTRY > let visitid=clinicnr+visitnr > goto nextvar > END > END >

1 0

RELATE QUERY
by epidata-list＠lists.umanitoba.ca 14 Mar '06

14 Mar '06

Dear epidata I would like to set up a database for a clinic. The 4 rec files are history, visit, bloodresults and treatment. The clinicnr of the patient is the unique id that I would like to carry over between these rec files. Secondly the number of records for visits/bloodresults/treatment for each patient with a specific clinicnr can be more than one over time. However history only has to be completed once (can be mother file?). When creating a relational database am I right if I say that I cannot keep clinicnr as the unique nr in every rec file as that will only allow ONE record with that clinicnr and I need to be able to do multiple records eg for visits on that one clinicnr. The House.rec etc example does not really help me with this as the visit rec file is the last rec file. I have 3 "children files" following one after another. Please help with the check files to relate these 4 files whilst keeping clinicnr as the unique id but allowing multiple records per clinicnr. Thanks Paul Prof Paul Rheeder Division of Clinical Epidemiology Faculty of Health Sciences University of Pretoria PO Box 667 Pretoria 0001 Tel 27 12 354 1488 Fax 27 12 354 1489

1 1

RE: [EpiData-list] How should EpiData Analysis readaCSV(CommaSeparated File)
by epidata-list＠lists.umanitoba.ca 14 Mar '06

14 Mar '06

Missing data and zero are two totally different things and should never be interchanged. If you are analyzing data, missing values are automatically excluded (unless you specifically request them not to be). If the missing values are defaulted to zero they would be included in the analysis and drastically alter the analysis results. Cheers, Jackie -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: 14 March 2006 10:29 To: epidata-list(a)lists.umanitoba.ca Subject: RE: [EpiData-list] How should EpiData Analysis readaCSV(CommaSeparated File) On my point of view also, there is no way for a missing data to be treated as a zero. Gilles -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : dimanche 12 mars 2006 20:59 À : epidata-list(a)lists.umanitoba.ca Objet : AW: [EpiData-list] How should EpiData Analysis read aCSV(CommaSeparated File) I also agree that missing is not equal to zero. I hope the vote is clear on that marcel ________________________________ Von: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Gesendet: Fr 10.03.2006 13:57 An: epidata-list(a)lists.umanitoba.ca Betreff: RE: [EpiData-list] How should EpiData Analysis read a CSV(CommaSeparated File) Hello! I totally agree with you Max on this question. Cheers, Bellinda -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Thursday, March 09, 2006 6:35 PM To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How should EpiData Analysis read a CSV (CommaSeparated File) Hello Jens, I would strongly argue that a missing is a missing and a 0 (zero) is a very distinct value - hence never turn missings into zero by default... or in short: Option 2 Bests Max On 10 Mar 2006, at 10:21, epidata-list(a)lists.umanitoba.ca wrote: > A question has come up. > > Please consider how you find reading of a CSV file in analysis > appropriate: > > > In a csv file the following data is found: > id, s, pos, sex, ill > 1,.,.,f,0 > 2...... etc (rest of records) > > The data in line can be interpreted in two ways: > Option 1: > ID= 1 > s= 0.0 > pos=0.0 > SEX = "f" ill = 0 > > Option 2: > ID= 1 > s= . > pos=. > SEX = "f" ill = 0 > > In other words the question is how to read ",.," should it be: > Option 1: as 0.0 (which is current behaviour) > or Option 2: . > > Any comments on desired behaviour appreciated. > > regards > > Jens Lauritsen > EpiData Association > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

RE: [EpiData-list] How should EpiData Analysis read aCSV(CommaSeparated File)
by epidata-list＠lists.umanitoba.ca 14 Mar '06

14 Mar '06

On my point of view also, there is no way for a missing data to be treated as a zero. Gilles -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : dimanche 12 mars 2006 20:59 À : epidata-list(a)lists.umanitoba.ca Objet : AW: [EpiData-list] How should EpiData Analysis read aCSV(CommaSeparated File) I also agree that missing is not equal to zero. I hope the vote is clear on that marcel ________________________________ Von: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Gesendet: Fr 10.03.2006 13:57 An: epidata-list(a)lists.umanitoba.ca Betreff: RE: [EpiData-list] How should EpiData Analysis read a CSV(CommaSeparated File) Hello! I totally agree with you Max on this question. Cheers, Bellinda -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Thursday, March 09, 2006 6:35 PM To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How should EpiData Analysis read a CSV (CommaSeparated File) Hello Jens, I would strongly argue that a missing is a missing and a 0 (zero) is a very distinct value - hence never turn missings into zero by default... or in short: Option 2 Bests Max On 10 Mar 2006, at 10:21, epidata-list(a)lists.umanitoba.ca wrote: > A question has come up. > > Please consider how you find reading of a CSV file in analysis > appropriate: > > > In a csv file the following data is found: > id, s, pos, sex, ill > 1,.,.,f,0 > 2...... etc (rest of records) > > The data in line can be interpreted in two ways: > Option 1: > ID= 1 > s= 0.0 > pos=0.0 > SEX = "f" ill = 0 > > Option 2: > ID= 1 > s= . > pos=. > SEX = "f" ill = 0 > > In other words the question is how to read ",.," should it be: > Option 1: as 0.0 (which is current behaviour) > or Option 2: . > > Any comments on desired behaviour appreciated. > > regards > > Jens Lauritsen > EpiData Association > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Re: [EpiData-list] How should EpiData Analysis read a CSV
by epidata-list＠lists.umanitoba.ca 10 Mar '06

10 Mar '06

Hi every body, Yes, a missing value is a missing value and has no sense to convert it into 0. Option 2. Greetings Pedro Pedro Arias Bohigas John Ericssons gatan, 12 5 tr 112 22 Stockholm Sweden Phone (cell) 0734421130 Phone (international calls)+46734421130

1 0

How should EpiData Analysis read a CSV (Comma Separated File)
by epidata-list＠lists.umanitoba.ca 10 Mar '06

10 Mar '06

A question has come up. Please consider how you find reading of a CSV file in analysis appropriate: In a csv file the following data is found: id, s, pos, sex, ill 1,.,.,f,0 2...... etc (rest of records) The data in line can be interpreted in two ways: Option 1: ID= 1 s= 0.0 pos=0.0 SEX = "f" ill = 0 Option 2: ID= 1 s= . pos=. SEX = "f" ill = 0 In other words the question is how to read ",.," should it be: Option 1: as 0.0 (which is current behaviour) or Option 2: . Any comments on desired behaviour appreciated. regards Jens Lauritsen EpiData Association

1 2

/inc and /xmin /xmax in bar and histogram
by epidata-list＠lists.umanitoba.ca 27 Feb '06

27 Feb '06

These options have no place in bar and histograph Example 1 : /XMIN="0" /XMAX="10" /XINC=1 Example 2 : /XMIN="0" /XMAX="10" /XINC="1" and will be removed from the graph create form. bar: A bar uses only the values of the group variable assumed categorical. And each value represented in the data will be shown. A small space will separate the bars. Histogram Unless you use the option /Xonly a histogram uses all values from minimum to maximum value and fills in any intermediate value not found in the data. E.g. if data in variable V1 has values 10 20 30. : histogram v1 The histogram will show a bar with counts of observations at x=10 x=20 and x=30, and will show the values 11,12....19 21....29 without any bar. With : his v1 /xonly A condensed histogram will show with only values 10,20 and 30 and without space between the bars. regards Jens Lauritsen EpiData Association

1 0

EpiData-List: List index out of bounds
by epidata-list＠lists.umanitoba.ca 22 Feb '06

22 Feb '06

"When I try to open a newly created .rec-file for data entry I receive the error message "list index out of bounds (9174)". When such errors occur it is good practice to confirm that you are using latest version - 3.1 Jan 12th 2006: (120106) If not download latest and try again. regards Jens Lauritsen

1 0

Error opening .rec-file (9174)
by epidata-list＠lists.umanitoba.ca 21 Feb '06

21 Feb '06

When I try to open a newly created .rec-file for data entry I receive the error message "list index out of bounds (9174)". What does this mean? How to solve it? ************************************************* Dr. Dirk Enzmann Institute of Criminal Sciences Dept. of Criminology Edmund-Siemers-Allee 1 D-20146 Hamburg Germany phone: +49-040-42838.7498 (office) +49-040-42838.4591 (Billon) fax: +49-040-42838.2344 email: dirk.enzmann(a)jura.uni-hamburg.de www: http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/E… *************************************************

1 0

New Spanish Install for EpiData Analysis
by epidata-list＠lists.umanitoba.ca 20 Feb '06

20 Feb '06

The Spanish Install file has been updated to remedy the error seen. A lacking subfolder has been added. The exe file is the same. Our college from Cali-Columbia wrote: "La primera es que el instalador de la version en español de Epidata Analisis no funciona, lo eh bajado varias veces pero nunca lo puedo instalar...." Answer/Solution: Proeba otra vez. Regards Jens Lauritsen EpiData Association

1 0

XInc in /Graphics/Histogram or Bar
by epidata-list＠lists.umanitoba.ca 20 Feb '06

20 Feb '06

Hello, In Graphics menu or command line, Xinc (/graphics/histogram or bar) is inoperant. Example 1 : /XMIN="0" /XMAX="10" /XINC=1 Example 2 : /XMIN="0" /XMAX="10" /XINC="1" Thank you your help 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

1 0

re: Freq on related tables
by epidata-list＠lists.umanitoba.ca 18 Feb '06

18 Feb '06

If I understand properly, the problem arises with related files. FileA - fields are district, x, y, z (one record per person, say 25 people) FileB - fields are district, a, b, c (one record per district, say 5 districts) To get freq of field a: read filea relate district fileb freq a This works, total of freqs (with missing) is 25. But of the files are read in the wrong order: read fileb relate district filea freq a This will not work - you get only total of 5 freqs, one for each district, because EpiData only matches the first record in FileA for each district. I think that Epi6 complained about doing the relate this way. If I have misunderstood the problem, perhaps provide more of the commands you are using. Si he entendido mal el problema, quizás proporcione más de los comandos que usted está utilizando. Jamie Hockin Public Health Agency of Canada Andres wrote: > la segunda en con respecto a los reportes, cuando tengo dos tablas on relate, y deseo sacar una frecuencia de una variable de la tabla secundaria no me muestra correctamente el reporte, ejemplo, tengo una tabla con el nombre del barrio y el codigo, y tengo otra tabla donde se encuentra la informacion de todos los barrios como el codigo, el nombre, el tipo de barrio, el estrato, etc, cuando deseo hacer el reporte de los barrios en la tabla principal, y le digo que me realice un freq del nombre del barrio despues de realizar el relate, me imprime en ocaciones el codigo del barrio y en otros el nombre.... como puedo realizar la rutina para que siempre me imprima en nombre del barrio y no el codigo???? > >

1 0

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

17 Feb '06

Buenos Dias. tengo dos inquitudes con respecto a EpiData Analisis.... La primera es que el instalador de la version en español de Epidata Analisis no funciona, lo eh bajado varias veces pero nunca lo puedo instalar.... la segunda en con respecto a los reportes, cuando tengo dos tablas on relate, y deseo sacar una frecuencia de una variable de la tabla secundaria no me muestra correctamente el reporte, ejemplo, tengo una tabla con el nombre del barrio y el codigo, y tengo otra tabla donde se encuentra la informacion de todos los barrios como el codigo, el nombre, el tipo de barrio, el estrato, etc, cuando deseo hacer el reporte de los barrios en la tabla principal, y le digo que me realice un freq del nombre del barrio despues de realizar el relate, me imprime en ocaciones el codigo del barrio y en otros el nombre.... como puedo realizar la rutina para que siempre me imprima en nombre del barrio y no el codigo???? Gracias por la tencion Atentamente, Andres Felipe Hincapie S. Tecnico en Sistemas Instituto Cisalva - Universidad del Valle Cali - Colombia __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.espanol.yahoo.com/

1 0

RE: [EpiData-list] Jumps reset
by epidata-list＠lists.umanitoba.ca 15 Feb '06

15 Feb '06

Hi Juergen, Thank you for that, it works perfectly!! Kind Regards, Bellinda -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Wednesday, February 15, 2006 9:21 AM To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Jumps reset epidata-list(a)lists.umanitoba.ca schrieb: > Hi, > > I have a question about the jumps reset command. > > What I would like to do is based on the answers of 2 items in the > questionnaire I would like to either keep entering data or fill the rest > of the section with 7's. > > I know how to use one item jumps reset, but not how to do it for 2 > items. I was thinking about creating a sum of the items and then if the > sum equals a particular value either you keep going or fill. The two > items added together would have a range of 2-6 and when it's 2 I would > like to skip (fill) the section. However, my usage of EpiData up until > now has been rather basic, so the programming for this is a little > beyond me. Any help would be greatly appreciated. > > Cheers, > Bellinda > > Hi Bellinda, another way to do more complex skip and fill rules is using If ... then in a After Entry-Block for Item2, something like this: If (item1>1) and (item2>1) THEN var1=7 var2=7 var3=-7 var4=0 ... GOTO nextvar Endif That's more programming than "jumps reset" but much more flexible. Regards Juergen Spiegel -- *********************************************** 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 mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Re: [EpiData-list] Jumps reset
by epidata-list＠lists.umanitoba.ca 15 Feb '06

15 Feb '06

epidata-list(a)lists.umanitoba.ca schrieb: > Hi, > > I have a question about the jumps reset command. > > What I would like to do is based on the answers of 2 items in the > questionnaire I would like to either keep entering data or fill the rest > of the section with 7's. > > I know how to use one item jumps reset, but not how to do it for 2 > items. I was thinking about creating a sum of the items and then if the > sum equals a particular value either you keep going or fill. The two > items added together would have a range of 2-6 and when it's 2 I would > like to skip (fill) the section. However, my usage of EpiData up until > now has been rather basic, so the programming for this is a little > beyond me. Any help would be greatly appreciated. > > Cheers, > Bellinda > > Hi Bellinda, another way to do more complex skip and fill rules is using If ... then in a After Entry-Block for Item2, something like this: If (item1>1) and (item2>1) THEN var1=7 var2=7 var3=-7 var4=0 ... GOTO nextvar Endif That's more programming than "jumps reset" but much more flexible. Regards Juergen Spiegel -- *********************************************** 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

1 0

Jumps reset
by epidata-list＠lists.umanitoba.ca 15 Feb '06

15 Feb '06

Hi, I have a question about the jumps reset command. What I would like to do is based on the answers of 2 items in the questionnaire I would like to either keep entering data or fill the rest of the section with 7's. I know how to use one item jumps reset, but not how to do it for 2 items. I was thinking about creating a sum of the items and then if the sum equals a particular value either you keep going or fill. The two items added together would have a range of 2-6 and when it's 2 I would like to skip (fill) the section. However, my usage of EpiData up until now has been rather basic, so the programming for this is a little beyond me. Any help would be greatly appreciated. Cheers, Bellinda Bellinda Kallimanis Coordinator, Statistical Research University of South Florida Louis de la Parte Florida Mental Health Institute Department of Aging & Mental Health 13301 Bruce B. Downs Blvd. MHC1407 Tampa, FL 33612-3899 Ph. (813) 974 9861

1 0

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

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

How to: checking for duplicate records
by epidata-list＠lists.umanitoba.ca 19 Jan '06

19 Jan '06

Yes - I got this error too. The LIST statement should read: list if (k = k[_n-1]) or (k = k[_n+1]) * if you only want the first of two records to appear: list if k = k[_n+1] *** Of course you have to insert some duplicate records into a copy of bromar.rec first *** |Indeed some of the line breaks threw it a bit. I reformatted below - but |still get that strange TRUNC error like: |. list if k = (( k[_n-1]) or (k[_n+1])) |Operator TRUNC is incompatible with String |Operation aborted

1 1

How to: checking for duplicate records
by epidata-list＠lists.umanitoba.ca 18 Jan '06

18 Jan '06

Some of the line breaks in the example did not come through properly. This is how I ran it: *********** Read "C:\Program Files\EpiData\validate\estimates\bromar.rec" gen s(25) k = "s:" + trim(string(sex) ) k = trim(k) + "a:" + trim(string(age) ) k = trim(k) + "d:" + trim(string(dectime) ) sort k gen x=1 aggregate k /sum=x /close /notable freq n *********** It works fine. I think you were not executing the 'aggregate' statement. With /close, the 'aggregate' command closes your working file and creates a new one with the following fields: k, n, nx, sumx For this example, n, nx and sumx are the same values. Jamie Hockin Public Health Agency of Canada

1 1

checking for duplicate records
by epidata-list＠lists.umanitoba.ca 17 Jan '06

17 Jan '06

Is there an easy way to check for duplicate records during data cleaning after data entry? Currently we export EpiData sets to MS Excel and run a little routine - but maybe someone has some within EpiData solution. Tx Max

1 2

Converting string to number
by epidata-list＠lists.umanitoba.ca 17 Jan '06

17 Jan '06

I tried the solutions given but it didn't work - purhaps I have made some errors. Here is the printout: . read Loading data C:\Data\Test.rec, please wait.. File name : C:\Data\Test.rec Fields: 1 Total records: 3 Valid records: 3 ******************************************************************************************* NOTE: Test.rec contains the variable var1 (string) and the following cases: 10/01 11/02 11/03 ******************************************************************************************* . Run "C:\DOCUME~1\STIG~1.UHL\LOKALA~1\Temp\TMP67F.Tmp" . define var2 ## Var Name VAR2 of type Integer Var length: 2 decimals 0 . var2 = string(copy(var1,1,2)) Data type mismatch . close File closed . read Loading data C:\Data\Test.rec, please wait.. File name : C:\Data\Test.rec Fields: 1 Total records: 3 Valid records: 3 . Run "C:\DOCUME~1\STIG~1.UHL\LOKALA~1\Temp\TMP680.Tmp" . gen i var2 = string(copy(var1,1,2)) Data type mismatch ------------------------------------------------------------------------ Stig Uhlin tel 090-786 60 71 Stig.Uhlin(a)umdac.umu.se UMDAC 070-591 03 04 901 87 Umeå fax 090-786 67 62 ------------------------------------------------------------------------

1 0

How to: checking for duplicate records
by epidata-list＠lists.umanitoba.ca 16 Jan '06

16 Jan '06

The decision should be to define the time for this: a. At entry of data b. As part of the analysis or quality control during entry For A: ....................................................................................................................................... Two commands are important here: Key unique Autosearch list The "Key Unique" will prevent more than one instance of a value in a given field to be entered. "Autosearch list" will show you any other record with the same value as the current field already entered in the file. A "key unique" status can also be used when creating combined fields. E.g. if you wish to combine id + area + date of visit then at the combination of these the status of key will be investigated. qes id person id #### area township # visit date of visit # chk file: id and area are defined mustenter and date of visit. * control assumed a string variable visit mustenter after entry control = "id" + string(id) + " area:" + string(area) + "visit:" + visit end end control * notice as well "key unique" as "noenter" key unique noenter end ....................................................................................................................................... Analysis or quality control. To test this I added in the bromar.rec file five double records by copy and paste, but with the same id numbers. I also added 5 records but changed the id to a new value. First the easy one. Let us find the five where id number is the same: * Assume you wish to see variables with same value of id sex age and dectime * I prefer the "gen" to the "define k _____ " but this is not important. gen s(80) k = "id: " + string(id) k = trim(k) + "s:" + trim(string(sex) ) // the first "trim(k) is important !!! k = trim(k) + "a:" + trim(string(age) ) k = trim(k) + "d:" + trim(string(dectime) ) sort k * list now any two records where two consecutive records have the same value * notice [ _n-1] indicates previous record [ _n+1] next record * notice also the many parenthesis. They could be removed but makes sure of what is what. list if k = ( ( k[_n-1] ) or ( k[_n-1]) ) * An alternative would be to create a frequency table, but with many records (here 4000) * this is not going to work. So we use instead: define x # x = 1 * now count how many times a given value in k was there * do not show the table (takes too long) therefore /notable aggregate k /sum=x /close /notable . list n k if n > 1 N K 2 id30 s:2a:55d:4.4833 3 id5 s:2a:51d:3.8667 2 id75 s:2a:52d:4.9167 So we know that records are the same for id 30, 5 and 75. The same principle can be used for any number of variables which will fit within 80 characters. The problem is how many records should be controlled for possible double entry: For my example the number of records to control in roughly 4100 records is: Combine id and 3 variables: 5 (correct) Three variables only (sex age dectime) : 741 combinations with more than one record Four variables only (sex age dectime km) : 154 combinations with more than one record So the question "Is there an easy way" - is answered. It is easy if you have an id or a number of variables to compare by. Most likely more than 4-5 variables. Jens Lauritsen EpiData Association

1 1

Converting string to number
by epidata-list＠lists.umanitoba.ca 13 Jan '06

13 Jan '06

In Epi6 I often used the following define var1 ## let var1=stringvar[startposition,number ] to convert a part of a stringvariabel to an integer variable. Whar is the equivalance in EpiStat? The way to find this information in EpiData Analysis is the following: 1. press F1 (latest version 1.1) 2. This will either show the complete "commands and functions" reference, where a section shows functions or a specific command, if a word in the beginning of the command prompt is found as a key word in the commands ref. The answer to your question can then be found by: writing in the command prompt: functions // and then press F1 or by just pressing F1 and look for the functions near the bottom of the file. ANswer: define var1 ## var1 = string(var2) *or if you wish only a part of var2: var1 = string(copy(var2,1,1)) or simpler with command "gen" gen i var1 = string(var2) *or if you wish only a part of var2: gen i var1 = string(copy(var2,1,1)) "i" stands for integer variable regards Jens Lauritsen EpiData Association, Denmark functions

1 0

New website design and double entry problem
by epidata-list＠lists.umanitoba.ca 13 Jan '06

13 Jan '06

A "cure" for the double entry problem with special calculations has been found for EpiData Entry. A new build will be put out within the next few days. On the www.epidata.dk website a new front page has been created. I expect to adapt the menu on the left side within a week. Users having problems of seing parts of the page, please send a message to the list or to "info at epidata.dk" regards Jens Lauritsen EpiData Association

1 0

value labels list in Add/Revise checks
by epidata-list＠lists.umanitoba.ca 13 Jan '06

13 Jan '06

The add/revise system is one of the parts of the EpiData Entry system which was created in the very early stages of development. Therefore it is not optimal for neither the experienced or the beginner. The idea of the add/revise system is to create a visual interface to the CHK files ,which contain the actual commands and rules. E.g. If the user has 20 fields with the same definition of labels (1=yes 2=no 8=irrelevant 9=missing) then defining that in one field and then by Ctrl+C in that field you copy the definition very fast by moving with the arrow to the next 19 fields and pressing Ctrl+V. What should be developed is a more intuitive interface where as well: a. Field specific definitions are created (as now) b. File specific definitions, e.g. backup after closing, colour setting of background etc. are visually defined. Now for the question of labels in Susan Donath's question. The list box which you can scroll has the contents of two parts: 1. Labels (comment legal) defined in the common file epidata.lbl which resides with the exe file when you install EpIData Entry. The idea of the epidata.lbl file is that an institution or user can create a set of commonly used label (comment legal) definitions and then distribute them for all projects. 2. Any labels already defined in the current file If for a given variable no relevant definition of label has been created by either #1 or #2 then the user must define a new one. This is done by pressing the + key or the small + next to the scroll box with defined labels. By entering the new definition a new label is defined, which can then be used in other fields in the same file. Kind regards Jens Lauritsen EpiData Association

1 0

Converting string to number
by epidata-list＠lists.umanitoba.ca 13 Jan '06

13 Jan '06

In Epi6 I often used the following define var1 ## let var1=stringvar[startposition,number ] to convert a part of a stringvariabel to an integer variable. Whar is the equivalance in EpiStat? ------------------------------------------------------------------------ Stig Uhlin tel 090-786 60 71 Stig.Uhlin(a)umdac.umu.se UMDAC 070-591 03 04 901 87 Umeå fax 090-786 67 62 Jag jobbar numera 1/2 tid enl följande: jämna veckor onsdag-fredag udda veckor måndag-tisdag ------------------------------------------------------------------------

1 0

EpiData Analysis v1.1 (problems with prevention of several instances in Win98)
by epidata-list＠lists.umanitoba.ca 12 Jan '06

12 Jan '06

The principle of prevention of several instances have been reversed now. On all WinXP variants a small file "preventdouble.ea" will be installed where the exe file of analysis resides. If users try to start EpiData Analysis twice a warning will be issued telling that analysis is already running. The reason for this is that during teaching I have often experienced beginners not being able to find their work since they started maybe three or four simultaneous copies of analysis by double clicking on the start icon and not noticing the other running copies. Experienced users can block this mechanism by simply deleting the file. On Win9x (95 98, me etc) the file is NOT installed since on some PC's they were blocked when the control mechanism was started. Users can experiment with manual creation of an empty file with the same name. Only one other difference in behaviour is known : To run a command prompt from within analysis two commands exist: dos // which works on all pc's ! // which only works on XP+ variants of windows. regards Jens Lauritsen EpiData Association

1 0

value labels list in Add/Revise checks
by epidata-list＠lists.umanitoba.ca 12 Jan '06

12 Jan '06

Dear Epidata listers I am new to Epidata, my query is this: In Add/Revise checks, the list box lists only the first (alphabetically) five value labels, and [none]. I can't scroll in this list to select from the other value labels. How do I select other value labels? Thank you Susan Donath Senior Research Fellow Clinical Epidemiology and Biostatistics Unit Murdoch Children's Research Institute & University of Melbourne Department of Paediatrics Royal Children's Hospital Parkville, Vic. 3052. AUSTRALIA E-mail: susan.donath(a)mcri.edu.au Tel. 9345 4742 Fax 9345 6000 All numbers area code 03 or international prefix +6

1 0

EpiData Analysis v1.1 (problems with prevention of several instances in Win98)
by epidata-list＠lists.umanitoba.ca 08 Jan '06

08 Jan '06

It was reported that the new mechanism of preventing several instances running of analysis at the same time gives problems in windows 98. After telling that "another instance is running" the computer clogged and had to be rebooted. If other users experience this please report to the list. As an alternative I created an install routine which tests for windows version and have sent that one to the user with the problem. We might have to reverse the principle, such that at all installations (xp, 2000 and over) a file rundouble.ini is placed with the exe file by the default installation. If users want to run more than one instance they can delete the file or avoid the installation of that file by selecting "user specified installation" and unmark the option to install this. More news in a few days. regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 27, Issue 4 (out of office)
by epidata-list＠lists.umanitoba.ca 07 Jan '06

07 Jan '06

I will be out of the office January 9 and 10 and will respond to emails on January 11 elaine >>> epidata-list 01/07/06 12:01 >>> 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. V1.1 of EpiData Analysis released (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Sat, 07 Jan 2006 00:19:17 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] V1.1 of EpiData Analysis released To: epidata-list(a)lists.umanitoba.ca Message-ID: <43BEFAF5.6060209(a)epidata.dk> Content-Type: text/plain; charset="iso-8859-1" Today v1.1 of EpiData Analysis was released for general use. Due to translation efforts by Pedro Arias (parias) and Juan Carlos Fern*ndez Merino (Per*n) a partial translation to Spanish was made. The major changes are: New help file approach Mechanism to prevent several instances of analysis running (unless the user allows this) Default output file automatically started (EAoutput.htm) New commands, e.g. aggregate or stattab Enhanced commands, e.g. cumulative percentage in frequency tables. More label commands General fixing of problems and other enhancements. Please report problems of downloading or installation to this list. Kind regards Jens Lauritsen EpiData Association ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 27, Issue 4 *******************************************

1 0

V1.1 of EpiData Analysis released
by epidata-list＠lists.umanitoba.ca 06 Jan '06

06 Jan '06

Today v1.1 of EpiData Analysis was released for general use. Due to translation efforts by Pedro Arias (parias) and Juan Carlos Fernández Merino (Perón) a partial translation to Spanish was made. The major changes are: New help file approach Mechanism to prevent several instances of analysis running (unless the user allows this) Default output file automatically started (EAoutput.htm) New commands, e.g. aggregate or stattab Enhanced commands, e.g. cumulative percentage in frequency tables. More label commands General fixing of problems and other enhancements. Please report problems of downloading or installation to this list. Kind regards Jens Lauritsen EpiData Association

1 0

question
by epidata-list＠lists.umanitoba.ca 06 Jan '06

06 Jan '06

Hello How do I change the range for a field I have tried changing using the check and revise function but it still does not change on the data entry form and i don't know what i am doing wrong thank you Banky _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 1

Re: EpiData-list Digest, Vol 26, Issue 15 (out of office)
by epidata-list＠lists.umanitoba.ca 31 Dec '05

31 Dec '05

I will be out of the office from the afternoon of December 23 until the morning of January 3. elaine >>> epidata-list 12/31/05 12:00 >>> 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. V1.1 of EpiData Analysis ready (?) (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Sat, 31 Dec 2005 12:23:58 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] V1.1 of EpiData Analysis ready (?) To: epidata-list(a)lists.umanitoba.ca Message-ID: <43B66A4E.8060909(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Unless someone finds serious bugs in the testversion of EpiData Analysis v1.1 build 61 available from: the testing page: Http://www.epidata.dk/testing.php will be released for general usage about one week from today. Translation procedures have started and a preliminary partial installation procedure in Spanish can be tested. Many aspects are updated and enhanced. See: Http://www.epidata.dk/testing.php for a complete list. The major issue is a new focused help system, an aggregation (collapse) command and extensions such as a cumulative column in frequency tables. Work on revision of the stratified table analysis module will be made within the first quarter of 2006, in particular due to a recent donation from Health Canada and the Statistical Process Charts will be extended due to the collaboration with Gruk Norway. Regards and happy new-year to all Jens Lauritsen EpiData Association ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 26, Issue 15 ********************************************

1 0

V1.1 of EpiData Analysis ready (?)
by epidata-list＠lists.umanitoba.ca 31 Dec '05

31 Dec '05

Unless someone finds serious bugs in the testversion of EpiData Analysis v1.1 build 61 available from: the testing page: Http://www.epidata.dk/testing.php will be released for general usage about one week from today. Translation procedures have started and a preliminary partial installation procedure in Spanish can be tested. Many aspects are updated and enhanced. See: Http://www.epidata.dk/testing.php for a complete list. The major issue is a new focused help system, an aggregation (collapse) command and extensions such as a cumulative column in frequency tables. Work on revision of the stratified table analysis module will be made within the first quarter of 2006, in particular due to a recent donation from Health Canada and the Statistical Process Charts will be extended due to the collaboration with Gruk Norway. Regards and happy new-year to all Jens Lauritsen EpiData Association

1 0

rec file as email-attachment
by epidata-list＠lists.umanitoba.ca 19 Dec '05

19 Dec '05

1 0

New build of EpiData Entry and advancements on Analysis and a new help window
by epidata-list＠lists.umanitoba.ca 17 Dec '05

17 Dec '05

The reported problems of EpiData Entry when verifying double entry has been solved. The problem was that when the file to compare with was missing, then a mysterious error message was given. The principle has now been changed such that if the comparison file is not existing, then the verify procedure stops completely. The path information in the ...dbc file is no longer placed there. Therefore if the user wishes to compare to a first entry file residing in a different folder than where the ...dbl.rec file resides, then manually edit the ....dbc file. Analysis is advancing A lot of work has been put into finding a managable help file structure, which also accomodates translation. If you see on the http://www.epidata.dk/testing.php page, you will see that there is now a partial translation to Spanish and the English version. Some issues of always showing the correct file is still lacking, but is expected to be fixed within a few weeks. The test versions are placed on: http://www.epidata.dk/testing.php The upgraded EpiData Entry (build 18dec2005) is on the http://www.epidata.dk/download.php Version information for entry: http://www.epidata.dk/revision.htm analysis: http://www.epidata.dk/versioninfo.htm Kind regards Jens Lauritsen EpiData Association

1 0

RE: [EpiData-list] Date variable
by epidata-list＠lists.umanitoba.ca 15 Dec '05

15 Dec '05

It's more simple to to it step by step: 1- Your qes file has to contain a variable (string, length = 4. I call it YV1)) to store the year of the date entered in V1. 2- In the chk file, edit checkblock for V1, and add the line: YV1 = year(V1) 3- Then, it is possible to enter the check lines that will calculate the categories: If YV1 = "xxx" then CATEGORY = "xxx" Endif If YV1 = "yyy" then CATEGORY = "yyy" Endif (...) End (assuming there is a variable called Category!) That's it. It's better (although you can do without) to add NOENTER to YV1 checkblock, so that it will be impossible to enter another value by accident. Gilles Delmas -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : mardi 13 décembre 2005 18:57 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] Date variable I am having some difficulties playing around with a date variable (named v1, form dd/mm/yyyy). I wish to create a new variable with categories based upon different years within the original variable and I have tried copying the examples provided in the help section, but I'm not having any luck. Any direction would be greatly appreciated. Thanks, Kate

1 0

Howto: Group a date variable by calendar year
by epidata-list＠lists.umanitoba.ca 14 Dec '05

14 Dec '05

* Example pgm file to group a date variable V1 * created by: Jens Lauritsen, EpiData Association set show info=off generate 50 // generate 50 empty observations for testing define v1 <dd/mm/yyyy> define y #### y = 1900 + recnumber // could also be 1900 + _n v1 = dmy(1,7,y) * so now we have a date variable with dates from 1900 to 1950 * three different strategies to group. * Strategy 1: extract year from the date and recode to a string: define y1 #### define ys ________________________ y1 = year(v1) recode y1 to ys by 10 tab ys * Strategy 2: round the number into 10 year groups define y2 #### y2 = year(v1) y2 = trunc(y2/10)*10 // creates groups by 10 years tab y2 * If you use 5 instead of 10 you get 5 year groups * y2 = trunc(y2/5)*5 // creates groups by 5 years * strategy 3: split on specific dates: define y3 # let y3 = 0 if (v1 < dmy(1,10,1930) ) then y3 = 1 if (v1 >= dmy(1,10,1930)) and (v1 < dmy(1,10,1939) ) then y3 = 2 if (v1 >= dmy(1,10,1939)) and (v1 < dmy(1,10,1960) ) then y3 = 3 tab y3 * run the above to get the tabulations. ---------------------------------------------------------------------------------- Output: E.g. for strategy 1: No. % Cum % 1900 - 1909 9 18.00 18.00 1910 - 1919 10 20.00 38.00 1920 - 1929 10 20.00 58.00 1930 - 1939 10 20.00 78.00 1940 - 1949 10 20.00 98.00 1950 - 1959 1 2.00 100.00 Total 50 100% * strategy 2: No. % Cum % 1900 9 18.00 18.00 1910 10 20.00 38.00 1920 10 20.00 58.00 1930 10 20.00 78.00 1940 10 20.00 98.00 1950 1 2.00 100.00 Total 50 100% * strategy 3 No. % Cum % 1 30 60.00 60.00 2 9 18.00 78.00 3 11 22.00 100.00 Total 50 100% ---------------------------------------------------------------------------------- Regards Jens Lauritsen EpiData Association

1 0

Re: Double Entry Verification Mode Error, not virus
by epidata-list＠lists.umanitoba.ca 14 Dec '05

14 Dec '05

A new build (dec 13th) is almost ready which fixes some of the other issues of double entry mentioned earlier. Before releasing the new one we will find the cause of the error reported by Yali Zhang. If anyone else have issues of double entry please submit files to info @ epidata.dk Best Regards Jens Lauritsen EpiData Association

1 0

Date variable
by epidata-list＠lists.umanitoba.ca 13 Dec '05

13 Dec '05

I am having some difficulties playing around with a date variable (named v1, form dd/mm/yyyy). I wish to create a new variable with categories based upon different years within the original variable and I have tried copying the examples provided in the help section, but I'm not having any luck. Any direction would be greatly appreciated. Thanks, Kate

1 0

Double Entry Verification Mode Error, not virus
by epidata-list＠lists.umanitoba.ca 13 Dec '05

13 Dec '05

Hi, When I opened the T3_dbl.REC file for double entry, the system suggested that "DOUBLE ENTRY VERIFICATION MODE Error". I could open the T3_dbl.REC file, but I couldn't verify the entry. Why? How to solve it? There are some Chinese characters in the REC file. Thank you, Yali Zhang Department of Clinical Epidemiology Beijing Hui Long Guan Hospital Beijing Suicide Research and Prevention Center Beijing 10096 P.R.C Fax: 86-10-82951150 E-mail:zhang_bsrpc@hotmail.com zhangyali(a)crisis.org.cn _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

1 0

Color of files during data entry and backup as check file command
by epidata-list＠lists.umanitoba.ca 12 Dec '05

12 Dec '05

In the help file users can find information on this: color data black yellow aqua color background white But not further information on how to use these check file commands. One example is: BEFORE FILE color data black yellow aqua color background white end Which will give yellow fields and aqua current entry fields. The background will be white and the colour of texts black. Backup as check file command The backup command documentation is incorrect in the help file. The help file says: AFTER FILE BACKUP F:\backup\distinationdirectory ZIP myzipfile.zip [DATE] END This should be: (to create a zip file with the date appended to the zip file name) AFTER FILE BACKUP F:\backup\distinationdirectory ZIP myzipfile [DATE] END It is always good practice to search the help file for a given word and if the examples are insufficient - then suggest to the list how it could be formulated. If users are not using the help system and this is due to faulty help system, then criticise the help system. But sometimes it appears that questions are asked without the user spending time on: 1. Looking in the help system 2. Searching old messages in the epidata-list on the topic 3. Looking in the further documentation supplied at the web page. http://www.epidata.dk/documentation.php We are now experimenting with solutions to translate analysis and create focused help. Users knowing of funding resources for translation please contact me at: info"at"epidata.dk (replace "at" with @) Best Regards Jens Lauritsen EpiData Association

1 0

RE: [EpiData-list] "date" fields
by epidata-list＠lists.umanitoba.ca 12 Dec '05

12 Dec '05

I don't think it is possible to modify the way EpiData 'understands' dates. Nevertheless, you cas add a check that refuses the date when it doesn't verify a certain condition: For example, if the date has to be at least 10 days before the date of entry, you will aff the following checkblock to the date field: DATE1 If DATE1 > today - 10 then Help "DATE1 has to be at least 10 days before today" goto DATE1 Clear DATE1 ENDIF END Line 1 (Help...) will display an error message each time the error condition is met. Line 2 & 3 (Goto / clear) will, as soon as the error message is akcnowledged, return to the field and erase what was previously entered, until a valid entry is entered (or nothing). ______________________________________________ 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é : vendredi 9 décembre 2005 13:32 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] "date" fields Hello everybody I have made a .qes with several fields "date". If I want to enter data in such a field and type 1 then return, the field is automatically filled with 01/12/2005 (5/12/2005 if I type 5). Is it possible to avoid this automatic entry ? Thank you very much and have a nice day Beatrice

1 0

"date" fields
by epidata-list＠lists.umanitoba.ca 09 Dec '05

09 Dec '05

Hello everybody I have made a .qes with several fields "date". If I want to enter data in such a field and type 1 then return, the field is automatically filled with 01/12/2005 (5/12/2005 if I type 5). Is it possible to avoid this automatic entry ? Thank you very much and have a nice day Beatrice

1 0

colors of background, fields and letters
by epidata-list＠lists.umanitoba.ca 09 Dec '05

09 Dec '05

Hello everybody I have made a .qes, a .rec and a .chk files and I have to give the .rec and .chk files to a person who will enter the data. In "epidata" on my computer I have defined (file - options) color of background, fields, police and color of the letters.. Is it possible to keep these settings in these .chk and .rec file, so that the person will see the same colors as me without changing the settings of her "epidata" ? Thank you very much and have a nice day Beatrice

1 0

Transfering database from Excel to Epidata
by epidata-list＠lists.umanitoba.ca 07 Dec '05

07 Dec '05

Hello Is there anyway I can copy a database created in Exce or accessl to Epidata or do I have to manually re-create this in Epidata again. thank you. _________________________________________________________________ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

1 1

AW: [EpiData-list] Formatting and exporting data
by epidata-list＠lists.umanitoba.ca 06 Dec '05

06 Dec '05

Dear Jens I fully agree and support your approach to preserve maximum accuracy with the data at hand and the make the display somewhat flexible hopefully in a generic way or command specific. Additionally, the exact accuracy of the data should be preserved when exporting or saving in another data format. with best wishes marcel *********** Marcel Zwahlen, PhD Department of Social and Preventive Medicine University Berne Finkenhubelweg 11 CH-3012 Bern Switzerland phone ++41-31-631.3554 facsimile ++41-31-631.3520 email: zwahlen(a)ispm.unibe.ch http://www.ispm.unibe.ch/ -----Ursprüngliche Nachricht----- Von: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Gesendet: Samstag, 3. Dezember 2005 11:45 An: epidata-list(a)lists.umanitoba.ca Betreff: [EpiData-list] Formatting and exporting data The question of how to format data by Susanne Widmar is a good one. Allow me to give a lengthy explanation since this is an issue in which we should agree on a uniform principle as well for import, export and use of data in EpiData Analysis. This relates to two aspects: 1. Accuracy of data - data types (binary, integer, real, double...) - we wish to replicate the precision of the collected data 2. How many decimals are shown on output from commands - we wish to see as much as needed for the interpretation - often less than aspect 1. In Stata the format is for some commands controlling the number of decimals, such as the CI command, whereas for other commands the display format is part of the command specification. The same "confusion" is now in EpiData Analysis where there is only partial consistency of showing and controlling formatting. In my view output formatting of the output should be decided by the command not by the data. In v1.1 build 54+ of EpiData Analysis (now available for testing) I have implemented for frequencies new options: freq v1 /D0 // would give percentages with no decimals freq v1 /D1 // would give percentages with one decimal For cross tables there are the settings for tables: TABLE PERCENT FORMAT COL P1() TABLE PERCENT FORMAT ROW P1{} TABLE PERCENT FORMAT TOTAL P1[] in which the user can define the number of decimals for the percentages For other commands (describe, means..) the display format of commands is either fixed or depending on the size of the estimates. User specification of output format will be implemented later. For import and export to Stata we could rewrite the procedures to work on datatype rather than format as it is now, if this is possible. We could then set all numerical variables to format %9.0g Another strategy could be to allow EpiData Analysis to save data in Stata format (which Bill Gould CEO of StataCorp has given permission to do). I suggest that users comment on the uniform strategy: a. All calculation is based on maximum accuracy with the data at hand b. Output formation should be part of each command. c. Data storage (type of variable) should be as strict as possible. Accomplishment of this is more important than speed of import and export. Regards Jens Lauritsen EpiData Association

1 0

Formatting and exporting data
by epidata-list＠lists.umanitoba.ca 05 Dec '05

05 Dec '05

Thanks Jens for your prompt and detailed response to my question about exporting numeric fields for use in Stata. While the fix you suggest in Stata (for var * : capture format X %9.0g) is simple for experienced Stata users, it's a bit painful as a general approach for new users. I'm definitely in favour of exporting according to type and sticking to %9.0g formatting, if this is possible. Cheers, Suzanna Suzanna Vidmar Research Fellow Clinical Epidemiology and Biostatistics Unit Royal Children's Hospital Flemington Rd Parkville Victoria 3052 telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000

1 0

Re: Appending based on "dbf" files
by epidata-list＠lists.umanitoba.ca 03 Dec '05

03 Dec '05

A user reported problems with appending files which were exported from Excel as Dbase (dbf) I suggest you export as csv instead since some of the DBF files Excel creates are NOT of the correct format. An alternative could be to try different DBF formats (dbaseII DbaseIII DbaseIV) Some mails to the list regarding this problem were sent as HTML. The list will from today convert such mails to text format. But it is preferable that mails to the list are sent as plain text, since these mails are shorter - a nice gesture to persons with slow modem lines. In some mail programs, e.g. Thunderbird http://www.mozilla.com/thunderbird/ which is a freeware programme one can define which type of mails a certain receiver of mails can read. Jens Lauritsen EpiData Association

1 0

Re: Display format and Stata export
by epidata-list＠lists.umanitoba.ca 03 Dec '05

03 Dec '05

For NON-Stata users this mail is not relevant. Regarding the display format I forgot to show a solution: 1. export data to Stata format Either use EpiData and choose the version of Stata you prefer or use EpiC 2. Read the data into Stata 3. Set the display format as you desire: e.g. for a file myfile.rec to export to Stata and set numerical format %9.0g for all variables: epic export stata test\testdata\bromar.rec * replace Start Stata and issue the commands: use bromar.dta for var * : capture format X %9.0g ci ....... The reason for capture is that if you have a string variable there would be an error. Instead of the "for var *" you can use for var v1 v3 v13 etc and name the variables explicitly. In newer versions of Stata an alternative is foreach Kind regards Jens Lauritsen EpiData Association

1 0

Formatting and exporting data
by epidata-list＠lists.umanitoba.ca 03 Dec '05

03 Dec '05

The question of how to format data by Susanne Widmar is a good one. Allow me to give a lengthy explanation since this is an issue in which we should agree on a uniform principle as well for import, export and use of data in EpiData Analysis. This relates to two aspects: 1. Accuracy of data - data types (binary, integer, real, double...) - we wish to replicate the precision of the collected data 2. How many decimals are shown on output from commands - we wish to see as much as needed for the interpretation - often less than aspect 1. In Stata the format is for some commands controlling the number of decimals, such as the CI command, whereas for other commands the display format is part of the command specification. The same "confusion" is now in EpiData Analysis where there is only partial consistency of showing and controlling formatting. In my view output formatting of the output should be decided by the command not by the data. In v1.1 build 54+ of EpiData Analysis (now available for testing) I have implemented for frequencies new options: freq v1 /D0 // would give percentages with no decimals freq v1 /D1 // would give percentages with one decimal For cross tables there are the settings for tables: TABLE PERCENT FORMAT COL P1() TABLE PERCENT FORMAT ROW P1{} TABLE PERCENT FORMAT TOTAL P1[] in which the user can define the number of decimals for the percentages For other commands (describe, means..) the display format of commands is either fixed or depending on the size of the estimates. User specification of output format will be implemented later. For import and export to Stata we could rewrite the procedures to work on datatype rather than format as it is now, if this is possible. We could then set all numerical variables to format %9.0g Another strategy could be to allow EpiData Analysis to save data in Stata format (which Bill Gould CEO of StataCorp has given permission to do). I suggest that users comment on the uniform strategy: a. All calculation is based on maximum accuracy with the data at hand b. Output formation should be part of each command. c. Data storage (type of variable) should be as strict as possible. Accomplishment of this is more important than speed of import and export. Regards Jens Lauritsen EpiData Association

1 0

Display format
by epidata-list＠lists.umanitoba.ca 01 Dec '05

01 Dec '05

This is a question/comment for the folk at EpiData. Much of the data here is entered in EpiData and then analysed in Stata. I've noticed that in Stata the display format for a field is the same as the data entry format in EpiData. For example if the field "smoke" (0=no, 1=yes) has the field type set to # in EpiData, in Stata the display format is %1.0f. This can cause confusion with Stata commands that base the display format of their output on the display format of the field, e.g. the Stata command "ci". If I type the following into Stata: ci smoke, binomial The output I get looks like this: Variable | Obs Mean Std. Err. [95% Conf. Interval] -------------+--------------------------------------------------------------- sex | 44 0 0 0 0 because the mean, SE, and CI have been rounded to the nearest integer. Is it necessary for the output/exported format of fields to be the same as the data entry format? Can numeric fields be exported with a format of at least 9.0g? Cheers, Suzanna Suzanna Vidmar Research Fellow Clinical Epidemiology and Biostatistics Unit Royal Children's Hospital Flemington Rd Parkville Victoria 3052 telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000

1 0

re: appending files properly
by epidata-list＠lists.umanitoba.ca 30 Nov '05

30 Nov '05

1 0

Re: How to append datasets properly
by epidata-list＠lists.umanitoba.ca 29 Nov '05

29 Nov '05

To assist Kate with the appending problem we must know more: a. Are you using EpiData Entry or EpiData Analysis b. Which version and build See about box or in analysis: Version c. Show a listing of the variable types of the four variables in each of the two files. To do this: In EpiData Entry: Document - file structure In Analysis: read the file and then issue the command "var" Cut and paste into for the relevant four variables into a new mail to the epidata-list Regards Jens Lauritsen EpiData Association

1 0

Appending
by epidata-list＠lists.umanitoba.ca 29 Nov '05

29 Nov '05

Kate: Could it be that one of the variables at some places has an illegal value? I observed it with dates: while EpiData will accept a year "203" for instance, it seems that if you append in EpiData Analysis, you could get this type of error message. You could go to the variable(s) in question in EpiData Analysis, sort on the variable, browse and look at the beginning an the end whether there is anything that could be fishy. This of course after you used the command "variables" in both datasets to ensure that the structure is indeed identical. Hans I have a question regarding appending files properly. I'm attemping to append 2 datasets, and the program states that 4 variables among the 2 datasets are incompatible. The variables appear to be consistent across both datasets, so I'm at a bit of a loss. Any help would be appreciated. Thanks, Kate -- 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

How to append datasets properly
by epidata-list＠lists.umanitoba.ca 28 Nov '05

28 Nov '05

1 0

How to: Create SPC graphs with same x period axis value for two consecutive periods
by epidata-list＠lists.umanitoba.ca 23 Nov '05

23 Nov '05

Question to info at Epidata: I have two successive periods: 1 and 2 I wish a graph where the first 6 observations in each period are included and on the graph the x axis should say 1 2 3 4 5 6 in both of them Using the Ichart.rec example included in installation of EpiData Analysis: file: ichart.rec which has 27 observations variables: lege : counts for a given doctor (lege is doctor in Norwegian) dag : consecutive number of observations (values are 1 - 27) Assume that period 1 in the study was observation 1-14 and observation 15-27 was period 2. Read the data en calculate as indicated after the "//" is comments ................................................................................................ read ichart define d ## d = _n // _n is the same as recnumber the observation number of the data if d > 15 then d = d -15 // now d is the correct number withing each period select if d < 7 // only include first 6 observations from each period ichart dag lege // this would show x axis with values of variable dag ichart dag lege /break=7 /xlabel=d // this would make a break for the two periods and use d as label ................................................................................................ Similarly for date variables: ................................................................................................ ichart tid lege /break="01/01/2003" /xlabel=d // if the value of "tid" was "01/01/2003" for observation 7 ................................................................................................ The format of the break value should for dates be the same as the x axis variable. The graph above will show a gap btw. the two periods since the x-axis variable has values from 1 to 27 If one has consecutive numbers e.g. 1-12 and you wish to have larger separation of the two periods: ................................................................................................ define d1 ## d1 = _n if d1 > 6 then d1 = d1+2 // experiment a bit if you wish 1, 2 or more added ichart d1 lege /break=7 /xlabel=d // this would move the two parts of the graph apart ................................................................................................ Regards Jens Lauritsen EpiData Association ps. Unfortunately the /xlabel option is not in the current commands and functions reference. Will be added to next release.

1 0

RE: [EpiData-list] new to epidata: 2 questions
by epidata-list＠lists.umanitoba.ca 21 Nov '05

21 Nov '05

1- CHK file size: I use to edit most of my chk files with an editor (metapad is the most convenient I could find, and it's freeware); I use to work with quite large chk files, and I never noticed anything wrong with opening it with an expernal text editor. 2- Variables deleted from the qes file: No, variables will not be removed from the check file. Here is what to do: 1st time you try to enter dada after the QES has been modified: Display: 'Revise data from revised revised QES file?' Click Yes Display: The revised QES file will cause loss of data in these fields... (list of fields that have been removed) click "Accept" Then, warning displays: "Could not apply checks (...)" click Yes. The CHK file opens on the left side of the screen, while a log file explaining where the detected errors are. Move (left) to the concerned area (ex: variable DATA1 has been removed. Go to the line containing checks for DATA1, and delete all lines from this block (from DATA1 to the last END of the block). You should also use the 'Find' feature to look for DATA1 within the whole chk file (in case other variables refer to it in their checks) and remove all DATA1 occurrences. Gilles Delmas InVS Paris -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : vendredi 18 novembre 2005 22:26 À : epidata-list(a)lists.umanitoba.ca Objet : RE: [EpiData-list] new to epidata: 2 questions Many thanks to all of you who answered my questions. Here's another one. I need to removed a number of variables and revise the .chk file to correspond to the .rec file. The easiest thing to do would be to make the changes in an editor (notepad, e.g.). The Epidata documentation says that a .chk file may not be more than 64K (I believe) if it is being created in an editor. The .chk file is now about 108K. Does this mean I can't make the changes in an editor? Richard Herrell NIMH 2 I've discovered I need to delete a number of variables from the data file. This seems straightforward since I can simply delete them from the .qes file and they will be deleted from the .rec file. What happens to the .chk file when I open the new .rec file with deleted variables? Will Epidata revise the .chk file by deleting the checks for variables that no longer exist? --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click.

1 0

RE: [EpiData-list] new to epidata: 2 questions
by epidata-list＠lists.umanitoba.ca 18 Nov '05

18 Nov '05

-----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : mardi 15 novembre 2005 21:14 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] new to epidata: 2 questions I'm fairly new to Epidata and have a couple of questions: 1 In the file manager, the check file I've created has "recovered file fragments" as the file type. Is that correct? >>>> Recovered file fragments: Yes, this is normal, as Windows uses also the CHK suffix to name specific system files. Don't worry about it, as Epidata knows how to open these files. In case you want to open these files with an external text editor (to enter advanced check commands), right-click on the corresponding CHK file, select "Open with..." and browse to your favorite text editor (e.g. Wordpad, metapad...) 2 I've discovered I need to delete a number of variables from the data file. This seems straightforward since I can simply delete them from the .qes file and they will be deleted from the .rec file. What happens to the .chk file when I open the new .rec file with deleted variables? Will Epidata revise the .chk file by deleting the checks for variables that no longer exist? >>>> No, variables will not be removed from the check file. Here is what to do: 1st time you try to enter dada after the QES has been modified: Revise data from revised revised QES file? (Yes) The revised QES file will cause loss of data in these fields... (list of fields removed) click "Accept" Then, warning displays: "Could not apply checks (...)" click Yes The CHK file opens on the left side of the screen, while a log file explaining where the detected errors are. Move (left) to the concerned area (ex: variable DATA1 has been removed. Go to the line containing checks for DATA1, and delete all lines from this block (from DATA1 to the last END of the block). You should also use the 'Find' feature to look for DATA1 within the whole chk file (in case other variables refer to it in their checks) and remove all DATA1 occurrences. Many thanks for any help. Richard Herrell NIMH ______________________________________________ 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 ______________________________________________

1 1

How to: Select observations based on string variables
by epidata-list＠lists.umanitoba.ca 18 Nov '05

18 Nov '05

To work efficiently with string variables a few techniques are needed: To work with string variables some functions are needed: Length of a string: length("Abcde") = 5 Convert to upper: upper("Abcde") = "ABCDE" Remove blanks: trim("Abcde ") = "Abcde" Look for a given text in a string: pos("Abcde","cd") = 3 A. How do I select those with empty contents of a variable S (string). In person language this would mean: 1. Remove all blanks/spaces from my variable 2. Is the trimmed length of the variable greater than zero ? Yes: The string is NOT empty No: The string is empty So in analysis language this is: 1: trim(S) 2: length(trim(S)) and to use this as select : "YES" from above: Select if (length(trim(S)) > 0) "NO" from above: Select if (length(trim(S)) = 0) alternative: "YES" from above: Select if ( trim(S) <> "") "NO" from above: Select if ( trim(S) = "") The user will notice the many parenthesis ( ). The reason I add an outer parenthesis is to be sure that the whole sentence is handled correctly. B. How to select observations with a certain string value: In person language this would mean: 1. Make sure not to confuse lower and upper case entry of the text 2. Identify the string I wish to search on 3. Does the variable contain the string ? And in analysis language this is: 1: upper(S) 2: e.g. "DOG" 3: pos(upper(S),"DOG") and to use this as select : "YES" from above: Select if (pos(upper(S),"DOG") > 0 ) "NO" from above: Select if (pos(upper(S),"DOG") = 0 ) C. Complicated string values: Assume you wish to select all text strings with content DOG, but not if these also contained the word "WHITE" - that is find all dogs, but exclude the white ones. Select if ( (pos(upper(S),"DOG") > 0 ) and (pos(upper(S),"WHITE") = 0 )) If you wished to find all DOGs or CATs: Select if ( (pos(upper(S),"DOG") > 0 ) or (pos(upper(S),"CAT") = 0 ) ) It is often difficult to get the correct number of parenthesis. But start with the innermost one and build from there. Handling all types of strings with different national characters is difficult, therefore it is good practice to use upper() and many parenthesis to assist the programme in working correctly. Jens Lauritsen EpiData Association

1 0

RE: [EpiData-list] : 2 questions
by epidata-list＠lists.umanitoba.ca 17 Nov '05

17 Nov '05

hi. in my experience: 1. "recovered file fragments" is a MS naming of .chk files. and probaly other rhings it doesn't know about. 2. if you remove a variable from the .QES and try to enter data the error message will appear saying that the variable name you have in the .CHK is an UNKNOWN COMMAND. 3. so, the answer to your question is: no, Epidata will not remove from the .chk variables which have been removed from the .QES. you'll have to do this yourself...at least it's what I have to do. -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Tue 11/15/2005 3:14 PM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: [EpiData-list] new to epidata: 2 questions I'm fairly new to Epidata and have a couple of questions: 1 In the file manager, the check file I've created has "recovered file fragments" as the file type. Is that correct? 2 I've discovered I need to delete a number of variables from the data file. This seems straightforward since I can simply delete them from the .qes file and they will be deleted from the .rec file. What happens to the .chk file when I open the new .rec file with deleted variables? Will Epidata revise the .chk file by deleting the checks for variables that no longer exist? Many thanks for any help. Richard Herrell NIMH --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click.

1 0

re: 2 questions from Richard
by epidata-list＠lists.umanitoba.ca 16 Nov '05

16 Nov '05

| 1 In the file manager, the check file I've created has "recovered file fragments" as the file type. Is that correct? A: .chk is also the file type used by Windows when it checks your disk and finds orpha bits of files. You'll rarely, if ever, use or care about these files. I suggest you go to EpiData's options (File, Options), select the 'File Associations' tab, check all the boxes and click on 'Associate File Types'. Then all of your EpiData files will be properly described. > >2 I've discovered I need to delete a number of variables from the data file. This seems straightforward since I can simply delete them from the .qes file and they will be deleted from the .rec file. What happens to the .chk file when I open the new .rec file with deleted variables? Will Epidata revise the .chk file by deleting the checks for variables that no longer exist? > > You have two choices here. You may edit the chk file using File, Open. In the file dialogue, select the 'Files of type' to be 'EpiData check file (.chk)'. This brings up the full .chk file in EpiData's text editor. Just block the lines that begin with the name of the field you deleted and ending with its matching 'END' - this will be just before the next field name. Or you can click on 'Check' in the workflow buttons. EpiData will ask you if you want to delete the lines for the fields you removed (respond 'No') or comment them out (respond 'Yes'). However, EpiData won't actually do these things unless you change something, or pretend to change something, so that the 'Save' button becomes active. So you can just click on 'Edit' for any field, click on 'Accept changes' and then click on 'Save'. It is useful to get to know what .chk files look like inside, so I suggest the first option unless you are uneasy about editing files. Jamie Hockin Public Health Agency of Canada

1 0

string variables
by epidata-list＠lists.umanitoba.ca 16 Nov '05

16 Nov '05

1 0

new to epidata: 2 questions
by epidata-list＠lists.umanitoba.ca 15 Nov '05

15 Nov '05

I'm fairly new to Epidata and have a couple of questions: 1 In the file manager, the check file I've created has "recovered file fragments" as the file type. Is that correct? 2 I've discovered I need to delete a number of variables from the data file. This seems straightforward since I can simply delete them from the .qes file and they will be deleted from the .rec file. What happens to the .chk file when I open the new .rec file with deleted variables? Will Epidata revise the .chk file by deleting the checks for variables that no longer exist? Many thanks for any help. Richard Herrell NIMH --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click.

1 0

EpiData Entry and EpiC - new build/release (14nov2005)
by epidata-list＠lists.umanitoba.ca 15 Nov '05

15 Nov '05

(141105): Bug fix and modifications to EpiData Entry has been released for all languages: * o New startup parameter /FINDvarname=text e.g. EpiData.exe mydata.rec /FINDid=45 would start epidata.exe, look for number 45 in field id. If not found then add a new record and put the value 45 into field id. o If EpiDatastat.exe is found in same folder as EpiData.exe, then show tools with Analysis. o Adding of verified End Of Record status marker ^ (verified) in double entry o Bugfixes: Find-record did not respect filter AutoSearch error fixed (affected if same value as last record was entered) Save Record will not save an empty record Type statusbar error when autosearch and type statusbar was in same field Double Entry could not save records marked for deletion * In the next few days we will further check on the reported errors with double entry (lack of moving to new records) Kind regards Jens Lauritsen EpiData Association

1 0

Version 1.1 of Analysis ready for testing
by epidata-list＠lists.umanitoba.ca 14 Nov '05

14 Nov '05

V1.1 of analysis is ready for testing. Major news is: * Modified Output file principle - default file will open on start of programme * New commands o aggregate (abbreviation agg) - create aggregated statistics o stattables (abbreviation stattab) - tabulate aggregated statistics o label variables (label "text" ) * Modifications to set o "Set window font size" defines size of "F3/F2/F7" windows on right side of screen o "Set editor font size" defines size of font in editor o "Set graph colour" defines bar chart colouring (default value: 123456) o Variable label addition to tables, graphs etc. controlled with "set var label" and "set var name" * Modified Commands o SPC charts: Test1 modified for Run Charts o SPC charts: Missing in count variable allowed o temporary select "if" must be placed at the end of a command except: select and count "if" must follow select/count o Variable label added to frequency tables o Link to introduction pdf file added to help menu o Right mouse click on variable (F3 window) shows all variable definitions o Default colouring of bar charts: Each bar separate colour o Graphs addition of Y axis text: /Ytext= and /Xtext= (default is variable label of x-variable) * Bugs fixed: o error with parsing of if command - which could replace data o Means group error with one observation in a group Please see all changes on: http://www.epidata.dk/analysisinfo/docs/versioninfo.htm The stattables / aggregate command will produce summary statistics based on grouping of the dataset and optionally save the results as a file or shift from current file to the aggregated file. A number of statistics are available, see command reference for further information. For Epi Info v6 users the Stattables is a replacement for the sumfreq and sumtab command. regards Jens Lauritsen

1 0