- EpiData-list - University of Manitoba Mailing Lists

Run notebook
by epidata-list＠lists.umanitoba.ca 12 Apr '05

12 Apr '05

>Is it possible to add command to CHK file to run the notebook (F5) ... Yes - see the command WRITENOTE Example from help file : V10 AFTER ENTRY IF V10 > 100 THEN WRITENOTE "Please check if the value @V10 in field V10 is really true" ENDIF IF V10 > 110 THEN WRITENOTE "Unusual value of field V10 is entered. Please specify reasons for this value:" SHOW ENDIF END END to unconditionally open the entry: writenote show the example above will add the note, but not open the xxx.not file. Jens Lauritsen EpiData Association

1 0

Check file line numbering
by epidata-list＠lists.umanitoba.ca 11 Apr '05

11 Apr '05

Greetings. 1. I have a .CHK which has 473 lines 2. there are several include.txt files in the check code 3. when I want to do data entryI'm told there is a error in the .CHK file And do I want ot see 'them'..... I answer yes 4. the split screen appears with the .CHK on the left and the "offender" Section on the right 5. the line numbers in the right screen have nothing to do with the line Numbers on the left....as far as I can tell. 6. for example: "unexpected end of COMMENT LEGAL line 253 Followed in next line "Unknown command (end) in line 254 7. where did these line numbers come from? 8. at the point where the include occurs is line 13 and 9. the included file has 63 lines 10. any ideas??? Thanks, kelly

1 1

Run notebook
by epidata-list＠lists.umanitoba.ca 11 Apr '05

11 Apr '05

Hi! Is it possible to add command to CHK file to run the notebook (F5) for an "if " condition? for example If v1 = "yes" then execute (F5 button)? Thank you in advance! /Ziad Medecins Sans Frontiere (Sudan)

1 0

THANKS FOR BOTH SUGGESTIONS
by epidata-list＠lists.umanitoba.ca 11 Apr '05

11 Apr '05

INFORMATION IS VERY HELPFUL. IS THERE ANYONE WHO WOULD CONSIDER GIVING DEMONSTRATIONS?????? THANKS TO ALL, KELLY -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Thursday, April 07, 2005 1:01 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 18, Issue 4 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..."

1 0

Menu systems with EpiData
by epidata-list＠lists.umanitoba.ca 06 Apr '05

06 Apr '05

Kelly wrote yesterday that it would be relevant to create menu systems such as in Epi6. One way to do this would be to create in EpIData Analysis a new html file. Look at the info.htm supplied with the test version now available at http://www.epidata.dk/testing.php As part of this page there are three links looking like this: Examples of how the programme works: Graph: "Bar chart" (Click) "Statistical Process Control Chart" (Click) "Descriptive Means and descriptives" (Click) If you load the info.htm file into the editor of EpiData Analysis (press Viewer on the process toolbar and "edit HTML output" then you will see that behind the three links are actual commands, e.g. the link behind "Bar Chart" Contains: <A HREF='epi:CLS;close;set echo=off;define fn __________________________ glob;fn= "@sysdir"+"testdata";cd "@fn";read bromar;set warning=on;bar agegrp;cd; set command=off;echo Press F1 to view info again;set echo=on'>Bar chart</a> (Click) So even this looks a bit complicated you can see that it is ordinary commands, such as define fn ____________ global read bromar bar agegrp So to build a menu system that does analysis you could either have in the link: <a href=epi:'run myprogram.pgm'>do the analysis</a> or add the actual commands contained in the "myprogram.pgm" file separeted by semicolons. Users are encouraged to experiment with this type of developments. Examples could then be placed on the examples page of epidata.dk To facilitate such menu or analysis systems EpiData Analysis has been made such that almost all parts of the interface can be turned off, e.g. the main menu, toolbars or the command prompt. Jens Lauritsen Initiator and Coordinator for EpiData EpiData Association

1 0

Command line and demonstration
by epidata-list＠lists.umanitoba.ca 06 Apr '05

06 Apr '05

Greetings. 2 things. 1. I saw an example from Epidata which looked like this: c:\epidata\epidatastat myreport.pgm I haven't tried this but, does this mean that epidatastat will execute the .pgm??? I would lke to see all components of EpiData, analysis, editor etc. to be Able to for example: EpiENTER <file.rec>, EpiEDITOR <*.pgm>, EpiSIS <myreport.pgm> etc. Why? When developing systems using MENUs it seems to be better to 'hide' from the General user the database, reports .pgm etc. Selecting EpiData and then option 4 Exposes databases etc. to perhaps a not so sophisticated user. 2. I work for the CDC/Global AIDS Program and I think I have managed folks to Investigate placing EpiData, analysis etc. into what we call a software development Tool kit. I have been asked if I would conduct a 'brown bag' demonstration etc. I do not think I have enough experience as yet to do the software justice, expecially Analysis. Is there someone out there who would like to discuss this with me? Thanks and stay safe, kelly

1 2

How to import and restructure data and create a report every month in an easy way ?
by epidata-list＠lists.umanitoba.ca 05 Apr '05

05 Apr '05

Someone asked off line how to accomplish this If you have to restructure files often based on the same qes file the revision of structure can be saved as EpiC commands in a batch or command file (e.g. revise.cmd) See the documentation for EpiC for further instructions, e.g.: EpiC revise newqes.qes datafile.rec FIRST FORCE LOG="what_happended.log" Would revise the file "datafile.rec" based on contents of "newqes.qes" and force restructuring regardless of this would mean loosing fields (Option FORCE). The results are saved to the log file "what_happended.log" EpiC can do other parts also, e.g. create or open a zip archive or encrypt (decrypt) files. EpiC is available from the download page of http://www.EpiData.dk Example: Assume you recieve files with administrative data every month called datafile1.txt datafile2.txt datafile3.txt To import these data, make control lists and prepare a reports you do this: Create - a file called structure.qes which contains the same format for fields as the txt file with administrative data. - a file called newstructure.qes containing the fields you wish to keep in an approriate format. - a file called report.pgm which will in analysis append the three files and make a standard report. Then create the file revise.cmd with this content: *.......revise.cmd .................................................................... EpiC revise newqes.qes datafile.rec FIRST FORCE LOG="what_happended.log" EpiC import TXT datafile1.txt qes=structure.qes out=datafile1.rec delim=; q=text ignorefirst date=yymmdd EpiC import TXT datafile2.txt qes=structure.qes out=datafile1.rec delim=; q=text ignorefirst date=yymmdd EpiC import TXT datafile3.txt qes=structure.qes out=datafile1.rec delim=; q=text ignorefirst date=yymmdd EpiC revise newstructure.qes datafile1.rec FIRST FORCE LOG="what_happended.log" EpiC revise newstructure.qes datafile2.rec FIRST FORCE LOG="what_happended.log" EpiC revise newstructure.qes datafile3.rec FIRST FORCE LOG="what_happended.log" * then you could make a list of data from the centers involved: EpiC count center datafile1 datafile2 datafile3 LOG="centerlist"] *You could also export datafile1 to a spreadsheet format for the center with number 276 for particular checks: EpiC e xls datafile1.rec datacenter276.xls filter="CENTER=276" * and finally you could make a standard report using analysis: c:\program\epidata\epidatastat myreport.pgm .............................revise.cmd to here You would then only have to start the revise.cmd to create your monthly report. Please note that now all previous postings to EpiData are available in searchable form from: http://lists.umanitoba.ca/pipermail/epidata-list/ Jens Lauritsen Initiator and Coordinator of EpiData EpiData Association

1 0

How to change a field to encrypted form in an easy way ?
by epidata-list＠lists.umanitoba.ca 05 Apr '05

05 Apr '05

Someone asked off line how to accomplish this Situation: You have a file with say 1000 observations and you wish to encrypt the field containing social service numbers: 1. use epidata to make a qes file (tools menu - qes file from recfile) 2. edit the field in question from e.g. string field : v1 social id __________________________ to v1 social id <e > (same length) numerical: v1 social id ######################## to v1 social id <e > 3. Save the qes file 4. start enter data (point 4 on work process toolbar) and EpiData asks if you wish to update based on the revised qes file. 5. Do so and you are asked for passwords Thats all. Jens Lauritsen Initiator and Coordinator of EpiData EpiData Association

1 0

Re: EPIDATA with XP or XP-Pro -Administrator
by epidata-list＠lists.umanitoba.ca 04 Apr '05

04 Apr '05

>>> <epidata-list(a)lists.umanitoba.ca> 31-03-2005 16:52:43 >>> >I use EPIDATA software occasionally and everything works fine in Windows98 and Windows 2000. > But in Windows XP or XP-Pro when run as normal User (NOT Administrator) , EPIDATA refuses to open files (QES or REC) While running as ADMINISTRATOR, everything works OK ! Setting up user rights in Windows XP can be very troublesome. It is not possible to give general advice for this, since there are very many local policies. In some places users have no rights at all, in other restricted access to one folder, ...... The EpiData programme as such does not read any of these rights and can be freely copied from one folder, memory stick or CD-rom or moved without "real installation", since the registry access is not part of the installation (unless you decide to associate file types with epidata). To work with rec and qes files the users need write access rights in that folder. So instruct the users to work on their default data folder - e.g. this could be "C:\documents and settings\mdi256\documents". But to share files btw. users you would need common rights to that folder. Also the file "epidata.ini" is saved after running epidata with current settings of screen, options etc. So the user needs write rigths for that or an error message box will appear at closing of EpiData. So in general: a. Let each user install epidata in their own data space (it is only around 2-4Mb for the whole programme) and each user can work independently. b Set up your pc such that each user have sufficient rights Jens Lauritsen Initiator and Coordinator of EpiData EpiData Association

1 0

Why Can I not use labels from EpiData in Epi Info for windows
by epidata-list＠lists.umanitoba.ca 04 Apr '05

04 Apr '05

> I have a questionnaire entered in Epi Data 3.0 and want to analyze it in > Epi Info 3.2.2. When I bring in my data I lose all the value-lables > that I had defined using the command "label-block" in Epi Data. I want > to know what to do to keep these labels. > Sylvie Delcroix, France Epi Info for windows from CDC does not use labels. This is part of the reason I started EpiData, because in analysis the labels are crucial as documentation. If you want to use the labels in analysis you will have to use EpiData Analysis which is getting closer to release. If your analysis is general crosstables, descriptive statistics and graphs the test version available at http://www.epidata.dk/testing.php will do the work for you. You could decide the strategy: 1. Do the basic analysis you have to do anyway with EpiData Analysis. 2. If you need to do further advanced analysis do the rest in Epi Info for windows (or other software) Regards Jens Lauritsen EpiData Association

1 0

EPIDATA with XP or XP-Pro -Administrator
by epidata-list＠lists.umanitoba.ca 31 Mar '05

31 Mar '05

Dear Sir I use EPIDATA software occasionally and everything works fine in Windows98 and Windows 2000. But in Windows XP or XP-Pro when run as normal User (NOT Administrator) , EPIDATA refuses to open files (QES or REC) While running as ADMINISTRATOR, everything works OK ! Any suggestion or fix .. thanks in advance and many thanks to the creators of EPIDATA.

1 0

Re: EpiData - JUMPS involving calculations
by epidata-list＠lists.umanitoba.ca 17 Mar '05

17 Mar '05

You do not use the JUMP command, but rather use the logic you show in your message. Use the Edit button in the Check screen and type in the if statement. You have access to many useful functions as well - in this case the ABSolute value function. There are good examples in the help file accessible from within EpiData. WT2 if abs(wt1 - wt2) <= 0.5 then goto WT3 endif END Jamie Hockin Public Health Agency of Canada > > I am a new EpiData user. I am creating a data entry screen for > anthropometric data. > > There are two weight measurements - and a third if the first two > differ by +/- 0.5 kg. > > How can I incorporate this calculation in the JUMP section of the > Add/Revise Checks so > > (1) if WT1 - WT2 GE 0.5 OR LE -0.5 go to WT3 > (2) else go to HT1 [the next field] > > Thank you.

1 0

How to insert calculation in JUMP add/revise check
by epidata-list＠lists.umanitoba.ca 16 Mar '05

16 Mar '05

I am a new EpiData user. I am creating a data entry screen for anthropometric data. There are two weight measurements - and a third if the first two differ by +/- 0.5 kg. How can I incorporate this calculation in the JUMP section of the Add/Revise Checks so (1) if WT1 - WT2 GE 0.5 OR LE -0.5 go to WT3 (2) else go to HT1 [the next field] Thank you.

1 0

EpiData - JUMPS involving calculations
by epidata-list＠lists.umanitoba.ca 15 Mar '05

15 Mar '05

I am a new EpiData user. I am creating a data entry screen for anthropometric data. There are two weight measurements - and a third if the first two differ by +/- 0.5 kg. How can I incorporate this calculation in the JUMP section of the Add/Revise Checks so (1) if WT1 - WT2 GE 0.5 OR LE -0.5 go to WT3 (2) else go to HT1 [the next field] Thank you.

1 0

Re:Search problem
by epidata-list＠lists.umanitoba.ca 15 Mar '05

15 Mar '05

Could the problem be that the search is just marked as say 'forward' and you are sometimes already past the record you search for? Then marked 'search all records' instead or go to record 1 first. Best whises Claus Holst ----- Original Message ----- > epidata-list(a)lists.umanitoba > .ca To: > <epidata-list(a)lists.umanitoba.ca> > Sent by: cc: > epidata-list-bounces(a)lists.u Subject: > manitoba.ca > > > 15-03-2005 09:40 > > > > > > > > > > > > >>>> <epidata-list(a)lists.umanitoba.ca> 14-03-2005 17:41:54 >>> > "I'm a new user of EpiData, and have a question regarding "finding > records." > When I try to find a certain case using a "Find Records" command, I > sometimes get an error message saying "searching string(s) not found," > even > though the record I'm looking for is in the file. " > > A good strategy would be: > a enter a number you are sure to remember, e.g. 9999 in a new record. > b Move to record 1 (goto menu) > c. start search and make sure you have indicated that searching should > be done in that field. > d. after entering search criteria start the search > e. see if you stop at record 9999 > if not: there is an error in EpiData > if you get to 9999 : Probably you forgot to indicate the correct > record. > f. report to the list if it worked for you now. > g. delete the false record with 9999 (enter a true record in that > record or mark for deletion and pack-tools menu) > > regards > > Jens Lauritsen > Coordinator and initiator of EpiData > www.epidata.dk > > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > >

1 0

"find records" not working properly
by epidata-list＠lists.umanitoba.ca 15 Mar '05

15 Mar '05

>>> <epidata-list(a)lists.umanitoba.ca> 14-03-2005 17:41:54 >>> "I'm a new user of EpiData, and have a question regarding "finding records." When I try to find a certain case using a "Find Records" command, I sometimes get an error message saying "searching string(s) not found," even though the record I'm looking for is in the file. " A good strategy would be: a enter a number you are sure to remember, e.g. 9999 in a new record. b Move to record 1 (goto menu) c. start search and make sure you have indicated that searching should be done in that field. d. after entering search criteria start the search e. see if you stop at record 9999 if not: there is an error in EpiData if you get to 9999 : Probably you forgot to indicate the correct record. f. report to the list if it worked for you now. g. delete the false record with 9999 (enter a true record in that record or mark for deletion and pack-tools menu) regards Jens Lauritsen Coordinator and initiator of EpiData www.epidata.dk

1 0

"find records" not working properly
by epidata-list＠lists.umanitoba.ca 14 Mar '05

14 Mar '05

Hi all, I'm a new user of EpiData, and have a question regarding "finding records." When I try to find a certain case using a "Find Records" command, I sometimes get an error message saying "searching string(s) not found," even though the record I'm looking for is in the file. The identifier field I used is a numeric variable (caseid with four digits). Even more perplexing is for other data files, the "Find Records" works. I've created all data files in a same way, and don't understand why "Find Records" works sometimes, but not other times. Am I missing something or doing in a wrong way? I have a same problem with both EpiData 2.01 and 3.02 versions. Any helps or comments on this will be greatly appreciated. Best, Jin

1 0

autosearch and document
by epidata-list＠lists.umanitoba.ca 10 Mar '05

10 Mar '05

Dear Dr. Lauritsen, When I used "autosearch" command in the check file in order to prevent creation of duplicate records, I found that the "type comment on" command in the same field became disabled, and the double entry verfication is also disabled. Why ? And How to solve it? Sometimes in "View Data", "List Data" and "Codebook", the values of numeric fields were disappeard. I don't know why and have not discoverd any regluar rule. Thank you very much. Best Regards, Yali Zhang _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn

1 0

automatic date
by epidata-list＠lists.umanitoba.ca 08 Mar '05

08 Mar '05

Has anyone noticed the following with the automatic date field type <Today-dmy>? When entering the first record for the day, this field does not display today's date but displays the date when the last record was entered. Once a record has been entered and saved, this field is updated to the current date. When entering a new record I expected the automatic date to display today's date regardless of whether or not a record has been entered today. Do you have any idea why this is not the case? Thanks, Suzanna Suzanna Vidmar Senior Research Assistant Clinical Epidemiology and Biostatistics Unit Royal Children's Hospital Flemington Road Parkville Victoria 3052 telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000

1 1

Re: EpiData-list Digest, Vol 17, Issue 5 (Out of the office)
by epidata-list＠lists.umanitoba.ca 04 Mar '05

04 Mar '05

I will be out of the office from Friday March 4th through Friday March 11th, 2005. I will reply to your email as soon as possible. If you need immediate assistance please call Bennie Daughtry at (803) 545-4471.

1 0

Initial test of Analysis build 18 - TABLES
by epidata-list＠lists.umanitoba.ca 04 Mar '05

04 Mar '05

As I noticed the table was not implemented correctly in build 18, but should be correct (for the data I tested) in build 19. Build 19 was made available early today/late last night depending on where you live. The intention was to always have as pointed out by Jamie Hockin: TABLES outcomevar exposurevar stratifyvar1 stratifyvar2 stratifyvar3 Please review the adapted commands and functions list. You can search on (ctrl+f) "table epi" and in options for search mark out "helpfie" and the file will open in the output window. (the file has a formatting error now - but contents are there) set table labels=on[off] (Use comment legal "value labels" as text descriptors in tables) set table values=on[off] (show category values in tables) set table epi=on[off] (With on: tables are inverted (highest values in top left corner) set table percents=on[off] set table percents format="P1()"[off] (Content percents coloumn) 1: decimals () before after. e.g. "P2 %" set table percents header="%" (Contents of column header for percents) set table RR=on[off] show Risk Ratio in 2x2 tables set table OR=on[off] show Odds Ratios in 2x2 tables to control statistics output: set table statistics="OR RR EXACT CHI" eliminate the ones you do not want. e.g. set table statistics="CHI" regards Jens Lauritsen EpiData Association

1 0

Initial test of Analysis build 18 - TABLES
by epidata-list＠lists.umanitoba.ca 04 Mar '05

04 Mar '05

My favourite data set for TABLES is RELY.REC as it will eventually be a good test of MATCH. For this data, the 'inverted' table should read =========> tables rely case CASE RELY │ + - │ Total ───────────┼─────────────┼────── + │ 11 13 │ 24 - │ 3 29 │ 32 ───────────┼─────────────┼────── Total │ 14 42 │ 56 (from Epi6) EpiData Analysis gives me CASE RELY Y % N % Total % Y 11 (45.8) 3 (9.4) 14 (25.0) Y 13 (54.2) 29 (90.6) 42 (75.0) N 24 (100.0) 32 (100.0) 56 (100.0) Two problems: 1) The data are not inverted. However, the results are correct (OR, RR, etc) 2) Labelling for rows is not correct "N" row labelled "Y", "Total" row labelled "N" Percentages here are appropriate for Case-control study, but would not be of interest for Cohort study. Of course, the option to remove them is with the user. Turning on/off of OR and RR behaves as expected. if I turn off both OR and RR, I get a correct table: RELY CASE N Y Total N 29 13 42 Y 3 11 14 Total 32 24 56 So the problem is that with OR=on or RR=on, the rows and columns are switched, but the table has not been rotated to put CASE on top. I think that it will be more consistent to always put the first TABLES variable as the column header, or if the preferred practice for tables is to put the first variable as rows then we could accept 2x2 tables with the outcome in rows. The problem is that, looking at the output and the command, I'm confused about how I construct the command to get what I want. We have to enforce TABLES outcomevar exposurevar if we want RR to be calculated correctly. Jamie Hockin

1 0

New build of analysis (build 19)
by epidata-list＠lists.umanitoba.ca 04 Mar '05

04 Mar '05

A new build of analysis was just put out on www.epidata.dk/testing.php The table command was in a mess in build 18 from yesterday due to various technical problems (Apologies for the inconvenience.) Estimates for at least one data file are the same as with Stata 7 (Odds Ratios and RR). Also it has been defined such that the first variable on the tables command (tab) will always go across, the second down and any further will be used for stratification. The "set parameters" have been more standardised. Try "set" to see which ones are currently defined and their names. e.g. for tables: set table statistics="OR RR CHI EXACT" would include all whereas: set table statistics="OR CHI" would only include odds ratios, chi square measures The promised solving of reading unknown fields as character fields will be part of coming builds - not this one. regards Jens Lauritsen EpiData Association.

1 0

[Fwd: Short dates and menus in HTML]
by epidata-list＠lists.umanitoba.ca 03 Mar '05

03 Mar '05

This is good, Jens. Epi6 was so forgiving because it treated any unknown field as a string - a nice backwards compatibility feature as it turns out. Unfortunately, this went along with Epi6 producing invalid files from time to time. A good strategy for menus to do different analyses might be to create some .pgm files and simplify the HTML coding to just launch the appropriate .pgm. This would provide better documentation of complicated scripts. Once you get used to the syntax, HTML menus need not be any more complicated than EPI6 .mnu files. Outside of Analysis and with the right javascript tools & code fragments a lot is possible. Jamie Hockin

1 0

out of office reply
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

I will be out of office and not be checking my emails until March 4, 2005. marcel zwahlen

1 0

Svar: RE : [EpiData-list] Re: New analysis build (18) ready for testing(error reading date variables)
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

In the next build we will adopt the strategy that old formats such as <dd/mm>, <dd/mm/yy> or phone number fields will be read into analysis as strings. The user can then convert to date or numerical variables using functions in analysis. Jens Lauritsen EpiData Association.

1 0

RE : [EpiData-list] Re: New analysis build (18) ready for testing(error reading date variables)
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

Thanks Jens When you export oswego.rec to STATA using EpiData, you get a string variable in STATA that you have to work with, but no error I agree that this rather strange format with only mont hand day is not fantastic. Anyway, quite many people did use it because for brief studies it is OK The idea of developping a kind of conversion procedure makes sense, even if some recoding is needed after conversion like in STATA The crucial point is the ability to transfer old files to EpiData whether or not is absolutely "ready to use" Regards Robert -----Message d'origine----- De : epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] De la part de epidata-list(a)lists.umanitoba.ca Envoyé : mercredi 2 mars 2005 13:45 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] Re: New analysis build (18) ready for testing(error reading date variables) Robert wrote: "The last build does not work : cannot read rec file OSWEGO for example Any idea ??" This is a marvellous example of why end-users should participate in testing. It turns out that the version of OSWEGO.REC I am testing on has been updated with EpiData. When I do so all date fields are changed to full length dates including year. So I did not see the error. I can see now that with the original OSWEGO.REC I get the same error as indicated by Robert. Lesson learned: Make sure that testing includes types of error that you do not want to happen. In practice. We will from now on include a test of how analysis treats files with all the variable formats of Epi6. Even the ones we "abandoned", such as 2 digit year or dates without year. Rules from EpiData for these types of dates will be included in next build. (Extending to 4 digit years and adding current year to fields without year) regards Jens Lauritsen EpiData Association _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Re: New analysis build (18) ready for testing (error reading date variables)
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

Robert wrote: "The last build does not work : cannot read rec file OSWEGO for example Any idea ??" This is a marvellous example of why end-users should participate in testing. It turns out that the version of OSWEGO.REC I am testing on has been updated with EpiData. When I do so all date fields are changed to full length dates including year. So I did not see the error. I can see now that with the original OSWEGO.REC I get the same error as indicated by Robert. Lesson learned: Make sure that testing includes types of error that you do not want to happen. In practice. We will from now on include a test of how analysis treats files with all the variable formats of Epi6. Even the ones we "abandoned", such as 2 digit year or dates without year. Rules from EpiData for these types of dates will be included in next build. (Extending to 4 digit years and adding current year to fields without year) regards Jens Lauritsen EpiData Association

1 0

RE : [EpiData-list] New analysis build (18) ready for testing
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

The last buid does not work : cannot read rec file OSWEGO for example Any idea ?? Robert -----Message d'origine----- De : epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] De la part de epidata-list(a)lists.umanitoba.ca Envoyé : mercredi 2 mars 2005 12:27 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] New analysis build (18) ready for testing I have placed build 18 v0.9 of analysis on www.epidata.dk/testing.php earlier today. Many things have been changed since build 17. (Complete list on: http://www.epidata.dk/analysisinfo/docs/versioninfo.htm) Among these handling of OR and RR in tables. 2x2 tables are now "inverted" to make disease and exposed top left corner. Percentages are in different cells in tables than the numbers. Thereby allowing to add e.g. () around percentages APPEND command to read more than one file into memory. In particular it is important to secure that a- the tables produced by stratification are correct b- estimates based on stratified tables are correct. c- tables are formed correctly (counts and percentages) with and without option specifications. An example of set is: set table percents="P1()" *will make output like this: tab kmgrp decgrp KMGRP 2.5-3.4 % 3.5-3.7 % Total % 0- 25 km 120 (15.3) 156 (18.9) 596 (18.7) ..... but set table percents="P1[ %]" set table percents header="[Pct %]" *will for the same command give: tab kmgrp decgrp KMGRP 2.5-3.4 [Pct %] 3.5-3.7 [Pct %] Total [Pct %] 0- 25 km 120 [15.29 %] 156 [18.9 %] 596 [18.66 %] similarly set table or=off set table rr=off controls whether odds ratios and rate ratios are shown or not. To show change off to on. The testsuite used for validation is not fully completed. You can see how much was tested by running the command runtest validate which will run all pgm files in the subfolder validate and make a report at the end. regards jens Lauritsen EpiData Association, Odense Denmark. _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

How to learn using stylesheets and html
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

A good introductory text is found at http://www.w3c.org/Style/Examples/011/firstcss But very many similar sites are found around the world. The w3c is an organisation which has established standards for html and css. It can be quite usefull to see if a given stylesheet or web page in html follows these standards. The validators are found on the front page of w3c (http://www.w3c.org). For epidata it is the intention to have all html and style sheets in compliance with the w3c standards. (Note intention - sometimes not accomplished) regards Jens Lauritsen

1 0

Regarding Command line processing:
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

The bad news is: We have not and will not build a dedicated menu program to replace epiglue as part of the EpiData Association activities. The good news is: There are several other possibilities to replace Epi6 menus within the "EpiData frame" To maintain the QES-REC-CHK file principle (see later for other possibilities) 1. Make a qes/rec file which in individual fields uses the "execute" chk file command 2. Create batch files with EpiC which will accomplish many things such as zipping and encryption for backup or maling, importing or exporting of data for analysis, controlling data consistency (CHECKRANGE etc.) 3. In analysis: Build your own form such as the opening info.htm, where you can include commands. To learn how - look at the info.htm in any simple editor and replace commands in the<epi....> tag. And learn a bit of html language coding. You will find textbooks on that everywhere. If you run epidata analysis (the test version) the opening window shows contents of the file "info.htm". Part of this is: Examples of how the programme works: Graph: Bar chart (Click) Statistical Process Control Chart (Click) If the user clicks on "Bar Chart" a bar chart will be shown. Behind the click is a link to the following analysis commands: Graph: <A HREF='epi:close;set echo=off;define fn __________________________ glob;fn= "@sysdir"+"testdata";cd "@fn";read bromar;set warning=on;bar agegrp;cd; set command=off;echo Press F1 to view info again;set echo=on'>Bar chart</a> (Click) This looks a bit complicated to new users, but if you look more closely several words are well known EPI6 commands e.g. close set echo=off read bar So to make a menu point for showing descriptive statistics and let the user define select you would just add to the info.htm fil a line of text in an editor: Statistics <A HREF='epi:close;read datafile;select sex = ?Sex= 1 or 2?; describe;set echo=off;close;view info.htm;>By sex</a>(click) The difficult part of this to understand: select sex = ?Sex= 1 or 2? Analysis starts the select command but instead of running it lets the user input a value in a box on the screen. On that screen the text "Sex=1 or 2" is shown to guide the user. Similarly other select or defines could be made. You could also add two lines for fixed selections: Statistics <A HREF='epi:close;read datafile;select sex = 2; describe;close;view info.htm;>For males</a> Statistics <A HREF='epi:close;read datafile;select sex = 1; describe;close;view info.htm;>For Females</a> Outside the EpiData frame, but within the EPI6 menu principles: Maybe we could persuade EpiConcept and Denis Columbier to make Winglue available. Winglue is a replacement for epiglue. Other possible strategies would be to make a simple html page and include "tags" to run whichever programme you like or use other software - e.g. epi info for windows from CDC or larger server systems. regards jens Lauritsen EpiData Association, Odense Denmark.

1 0

New analysis build (18) ready for testing
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

I have placed build 18 v0.9 of analysis on www.epidata.dk/testing.php earlier today. Many things have been changed since build 17. (Complete list on: http://www.epidata.dk/analysisinfo/docs/versioninfo.htm) Among these handling of OR and RR in tables. 2x2 tables are now "inverted" to make disease and exposed top left corner. Percentages are in different cells in tables than the numbers. Thereby allowing to add e.g. () around percentages APPEND command to read more than one file into memory. In particular it is important to secure that a- the tables produced by stratification are correct b- estimates based on stratified tables are correct. c- tables are formed correctly (counts and percentages) with and without option specifications. An example of set is: set table percents="P1()" *will make output like this: tab kmgrp decgrp KMGRP 2.5-3.4 % 3.5-3.7 % Total % 0- 25 km 120 (15.3) 156 (18.9) 596 (18.7) ..... but set table percents="P1[ %]" set table percents header="[Pct %]" *will for the same command give: tab kmgrp decgrp KMGRP 2.5-3.4 [Pct %] 3.5-3.7 [Pct %] Total [Pct %] 0- 25 km 120 [15.29 %] 156 [18.9 %] 596 [18.66 %] similarly set table or=off set table rr=off controls whether odds ratios and rate ratios are shown or not. To show change off to on. The testsuite used for validation is not fully completed. You can see how much was tested by running the command runtest validate which will run all pgm files in the subfolder validate and make a report at the end. regards jens Lauritsen EpiData Association, Odense Denmark.

1 0

Command line processing
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

Greetings. I was wondering if Command Line Processing is available. I noticed EpiC 'stuff'. I was thinking something like EpiData <filename> for DataEntry in a BAT file or through .MNU Or EpIDataStat.exe <filename.pgm> etc. Thinking of a system which would be MENU driven. Obviously, I haven't tried any of this. Has anyone else? Thanks, kelly

1 2

Pia Muchaal/HC-SC/GC/CA is out of the office.
by epidata-list＠lists.umanitoba.ca 02 Mar '05

02 Mar '05

I will be out of the office starting 2005-02-25 and will not return until 2005-03-04.

1 0

out of office reply
by epidata-list＠lists.umanitoba.ca 01 Mar '05

01 Mar '05

I will be out of office and not be checking my emails until March 4, 2005. marcel zwahlen

1 0

several questions need your help.
by epidata-list＠lists.umanitoba.ca 01 Mar '05

01 Mar '05

A few comments based on mail from Yali Zhang <1. Is it possible to make the numbers right alignment in the field box after entry. No. A numerical field is by default left aligned. The problem is that the algoritms to calculate the length of the characters are not precise. So we have had to make the field a bit wider than the actual length of the characters. In the early versions of EpiData (v1.) sometimes for some users part of the numbers were hidden. >2. ... the double entry verification, if "08" is entered again ....."non matching value,the original value is 8, new value is 08" .How to solve this problem? Obviously for a numerical field "08" should be compared without the leading 0. Until we fix that just enter 8 without the leading 0. To get to next field hit return button. This will be fixed in the next build of EpiData. 3. Is the check file too large? And will it meet some difficulties when entering so many records? No - but for double entry make sure each observation has a unique key or id number for comparison. Regards Jens Lauritsen EpiData Association

1 0

several questions need your help.
by epidata-list＠lists.umanitoba.ca 01 Mar '05

01 Mar '05

Hello, I am using epidata 3.1 for data entry in a CMB project. Followings are some questions: 1. Is it possible to make the numbers right alignment in the field box after entry. 2. In our dataset, the width of some numeric fields is 2. When "08" is entered, "8" is saved. But in the double entry verification, if "08" is entered again, the dialog box will told you "non matching value,the original value is 8, new value is 08" .How to solve this problem? 3. Our check file is about 138kb, question file 56kb, and about 20,000 records is expected to be entered. Is the check file too large? And will it meet some difficulties when entering so many records? Thank you very much Best regards, 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 _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

1 0

reply for Command line processing
by epidata-list＠lists.umanitoba.ca 24 Feb '05

24 Feb '05

Greetings. Thanks Tony. I use that solution frequently but The DOS version. This would be nice, then we would have a Package. HELLO Denis, it has been a long time, how are you?! Stay safe, Kelly -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Tuesday, February 22, 2005 10:55 PM To: epidata-list(a)lists.umanitoba.ca Subject: RE: [EpiData-list] Command line processing I recently worked with Denis Columbier in Aceh, Indonesia. He had a windows implementation of the old DOS EpiGlue front end. This was used to make a menu interface to call EpiData, and run other commands/programs. I don't think it's publicly available yet, but Denis, if you are reading this can you fill us in? -- Tony Stewart -----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, 23 February 2005 5:33 AM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Command line processing Greetings. I was wondering if Command Line Processing is available. I noticed EpiC 'stuff'. I was thinking something like EpiData <filename> for DataEntry in a BAT file or through .MNU Or EpIDataStat.exe <filename.pgm> etc. Thinking of a system which would be MENU driven. Obviously, I haven't tried any of this. Has anyone else? Thanks, kelly _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list <!D2S:tonys@burnet.edu.au/good/c71b800f/>

1 0

Re: EpiData-list Digest, Vol 16, Issue 10 (Out of the office)
by epidata-list＠lists.umanitoba.ca 22 Feb '05

22 Feb '05

I will be out of the office this afternoon Tuesday Feb. 22, 2005. I will reply to your email as soon as possible. If you need immediate assistance please call Bennie Daughtry at (803) 545-4471.

1 0

Vedr.: [EpiData-list] New build of EpiData (fixes problem with files of special length) (Kontakt til Jens Lauritsen Uge 8 )
by epidata-list＠lists.umanitoba.ca 22 Feb '05

22 Feb '05

Jens Lauritsen, Overlæge afd.O-Ulykkes Analyse Gruppen, Odense Universitetshosptal Tæffes igen i Uge 9 Will be back from Febr. 29th.

1 0

New build of EpiData (fixes problem with files of special length)
by epidata-list＠lists.umanitoba.ca 22 Feb '05

22 Feb '05

A bug was reported last week which meant that for one particular file the "marked for deletion" status in the Data Entry Form was not shown correctly for that file, but correctly for all others. The bug has been located and was due to a special circumstance rarely happening (length of length of records was to be a multiplum of 78). So if you have not had this problem there is no need to download the latest build. There is a problem though with "not up to date" versions and builds on several servers around the world. This is not favourable, since the latest builds fix things that could be wrong in old versions. If any users know of downloads from other servers than www.epidata.dk please notify info(a)epidata.dk There is a solution for all of this servers to make sure the users gets the latest builds - even though supplied from other servers than www.epidata.dk Kind regards Jens Lauritsen EpiData Association

1 0

Re: [EpiData-list] MISSINGVALUE
by epidata-list＠lists.umanitoba.ca 10 Feb '05

10 Feb '05

>>> <epidata-list(a)lists.umanitoba.ca> 09-02-2005 17:46:07 >>> >Hello, >we ve just started using Epidata and we re really happy with it, but we also >do have a big problem with the MISSINGVALUE command, which we re not able to solve. MISSINGVALUE is a new concept in Epi Info "language". The idea is to define a certain value for indication of "unknown" or "irrelevant". When exporting the data for analysis the values defined as such will be marked as such when exporting to proper data analysis programs, such as Stata, SPSS and SAS. Also when we have the full EpiData Analysis running this will make use of the MISSING VALUE definitions. In the help file for EpiData 3.1 you can read: ...... (in before file block): MISSING VALUE V1-V4, V10, V20 9 8 7 (in the field block): MISSING VALUE 9 8 7 .... The syntax there in the help file is misleading since the command is MISSINGVALUE not "MISSING VALUE", so we will adapt the help file as soon as possible. So the problem is that we have managed to write the help file in a misleading way - this will happen every so often - clarifications or questions to the list is the way to proceed Regards Jens Lauritsen EpiData Association

1 0

MISSINGVALUE
by epidata-list＠lists.umanitoba.ca 09 Feb '05

09 Feb '05

Hello, we´ve just started using Epidata and we´re really happy with it, but we also do have a big problem with the MISSINGVALUE command, which we´re not able to solve. It has already been mentioned in the archive in December, but the answer to it didn´t really help us. We´re trying to use different missing values for different variables (e.g. 9 8 and 99 88 and 999 888) in one file. But the checkfile commands keep on disappearing, sometimes immediately, sometimes they work for some time and disappear later. Sometimes they´re there in the checkfile, but do not work, when we try to enter data. I´ve already tried to partition my file and use the RELATE function, to make sure the checkfile is not too long (they´re far less then 1000 lines now), but the problem persists. The problem also occurs working with version 3.1 as well as with 3.02. Would be great, if somebody could help us. Thank you in advance! Evelyn Müller Uniklinik Freiburg, Germany

1 0

Re: EpiData-list Digest, Vol 16, Issue 7 (Out of the office)
by epidata-list＠lists.umanitoba.ca 08 Feb '05

08 Feb '05

I will be out of the office Tuesday Feb. 8 and Wednesday Feb. 9, 2005. I will reply to your email as soon as possible. If you need immediate assistance please call Bennie Daughtry at (803) 545-4471.

1 0

'spanish documentation for epidata 3.0'
by epidata-list＠lists.umanitoba.ca 07 Feb '05

07 Feb '05

Hallo Nabil, Thanks for your response. Would you be able to indicate which website you were referring to for downloading the spanish documentation for Epidata v. 3 (or higher). I couldn't find the website identified in your message. Thanks again! Pia epidata-list-request(a)lists.u manitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent by: cc: epidata-list-bounces(a)lists.u Subject: EpiData-list Digest, Vol 16, Issue 5 manitoba.ca 2005-02-06 01:00 PM Please respond to epidata-list 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..." Today's Topics: 1. Re: EpiData-list Digest, Vol 16, Issue 4 (epidata-list(a)lists.umanitoba.ca) 2. Re: EpiData-list Digest, Vol 16, Issue 4 (epidata-list(a)lists.umanitoba.ca) ----- Message from epidata-list(a)lists.umanitoba.ca on Sat, 5 Feb 2005 19:54:59 +0100 ----- To: <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Re: EpiData-list Digest, Vol 16, Issue 4 Dear Spanish user Try this web site to download the spanish version. Best regards Nabil Brandl ----- Original Message ----- From: <epidata-list-request(a)lists.umanitoba.ca> To: <epidata-list(a)lists.umanitoba.ca> Sent: Saturday, February 05, 2005 7:00 PM Subject: EpiData-list Digest, Vol 16, Issue 4 > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > ---------------------------------------------------------------------------- ---- > Today's Topics: > > 1. 'spanish documentation' (epidata-list(a)lists.umanitoba.ca) > ---------------------------------------------------------------------------- ---- > _______________________________________________ > 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 1

Re: Formula in Check file
by epidata-list＠lists.umanitoba.ca 06 Feb '05

06 Feb '05

It seems the longest acceptable line is 204 characters. You can create and save longer lines using File,Open and choosing the checkfile, but EpiData 3.1 would not interpret the rest of these long lines for me. You can always break a formula down into smaller lines. Shorter lines are also better for documenting your calculations. e.g. f1 = a + b + c + d f1 = f1 + e + f + g Jamie Hockin Public Health Agency of Canada >I am trying to create a formula to calculate the sum of different fields. >In "Edit" option under "Check" window, when I write it, I close it and >save it, but later on I see that the line has been cut at the end, >does it have limited number of characters or ...? and how to solve it? > > >Help!! :-) > > >Thank you a lot! >Best regards and very nice week-end! >/Ziad > >

1 0

Re: EpiData-list Digest, Vol 16, Issue 4
by epidata-list＠lists.umanitoba.ca 05 Feb '05

05 Feb '05

Sorry, I forgot the link. Here is the link http://www.epidata.dk/download.php Nabil Brandl ----- Original Message ----- From: <epidata-list-request(a)lists.umanitoba.ca> To: <epidata-list(a)lists.umanitoba.ca> Sent: Saturday, February 05, 2005 7:00 PM Subject: EpiData-list Digest, Vol 16, Issue 4 > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > ---------------------------------------------------------------------------- ---- > Today's Topics: > > 1. 'spanish documentation' (epidata-list(a)lists.umanitoba.ca) > ---------------------------------------------------------------------------- ---- > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list >

1 0

Re: EpiData-list Digest, Vol 16, Issue 4
by epidata-list＠lists.umanitoba.ca 05 Feb '05

05 Feb '05

Dear Spanish user Try this web site to download the spanish version. Best regards Nabil Brandl ----- Original Message ----- From: <epidata-list-request(a)lists.umanitoba.ca> To: <epidata-list(a)lists.umanitoba.ca> Sent: Saturday, February 05, 2005 7:00 PM Subject: EpiData-list Digest, Vol 16, Issue 4 > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > ---------------------------------------------------------------------------- ---- > Today's Topics: > > 1. 'spanish documentation' (epidata-list(a)lists.umanitoba.ca) > ---------------------------------------------------------------------------- ---- > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list >

1 0

'spanish documentation'
by epidata-list＠lists.umanitoba.ca 04 Feb '05

04 Feb '05

Hallo, Does anyone know if documentation in Spanish is available for EpiData version 3 or higher? Many thanks, Pia

1 0

'spanish documentation'
by epidata-list＠lists.umanitoba.ca 04 Feb '05

04 Feb '05

With the installation comes a 4 page introduction file, choose Spanish language at http://www.epidata.dk/download.php Also Monica chiu made an extended explanation available from: http://epi.minsal.cl/epi/html/software/epi6.htm Although made with EpiData v2.1 you can use the same. If anyone wishes to do some translations all other documents found on either download or documentation page of EpiData.dk are available for translation. Regards (saludos) Jens Lauritsen

1 0

Check file + calculation formula
by epidata-list＠lists.umanitoba.ca 04 Feb '05

04 Feb '05

Hello! I am trying to create a formula to calculate the sum of different fields. In "Edit" option under "Check" window, when I write it, I close it and save it, but later on I see that the line has been cut at the end, does it have limited number of characters or ...? and how to solve it? Help!! :-) Thank you a lot! Best regards and very nice week-end! /Ziad Stockholm-Sweden

1 0

'spanish documentation'
by epidata-list＠lists.umanitoba.ca 03 Feb '05

03 Feb '05

Hallo, Does anyone know if documentation in Spanish is available for EpiData version 3 or higher? Many thanks, Pia

1 0

Svar: Re: [EpiData-list] If more than 1000 lines?
by epidata-list＠lists.umanitoba.ca 02 Feb '05

02 Feb '05

You should make a system using relate On the example page http://www.epidata.dk/examples.php you will find several examples. Some very complicated like the one YVES has made, but others are simple - but comprehensive, e.g. that included with the installation of EpiData you have the house,person,rec system. regards Jens Lauritsen

1 0

Re: EpiData-list Digest, Vol 16, Issue 1 (Out of the office)
by epidata-list＠lists.umanitoba.ca 02 Feb '05

02 Feb '05

I will be out of the office Tuesday Feb. 1, 2005. I will reply to your email as soon as possible. If you need immediate assistance please call Bennie Daughtry at (803) 545-4471.

1 0

If more than 1000 lines?
by epidata-list＠lists.umanitoba.ca 02 Feb '05

02 Feb '05

Hello! I am using EpiData version 3.1; When I have more than 1000 lines it gives error so EpiData can't run the REC form. Any suggestion(s) how to deal with it? Thank you a lot! /Ziad Stockholm-Sweden

1 2

RE : [EpiData-list] number of lines + number of characters?
by epidata-list＠lists.umanitoba.ca 02 Feb '05

02 Feb '05

As you kow by now 100 lines is the max What about the solution I posted ? Robert Jean FREUND -----Message d'origine----- De : epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] De la part de epidata-list(a)lists.umanitoba.ca Envoyé : mercredi 2 février 2005 16:52 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] number of lines + number of characters? Hello! While building questionnaire (QES) in EpiData version 3.1, I reach certain stage where keyboard can not type letters anymore. I tried to take away (delete) empty lines or to reduce spaces between words in the questionnaire, so then I could type. Does EpiData has limited number of characters, and please note that I had around 800 lines in total? Another question: what if I had more than 1000 lines, how to deal with it? Thank you a lot! /Ziad El-Khatib Stockholm-Sweden _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

RE : [EpiData-list] If more than 1000 lines?
by epidata-list＠lists.umanitoba.ca 02 Feb '05

02 Feb '05

The question is whether you need all your let say 80 variables at the same time! Usaually you don't. Then the solution is to split in several files each < 100 lines with an ID number for linking the records Hope it helps Robert Jean FREUND -----Message d'origine----- De : epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] De la part de epidata-list(a)lists.umanitoba.ca Envoyé : mercredi 2 février 2005 13:48 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] If more than 1000 lines? Hello! I am using EpiData version 3.1; When I have more than 1000 lines it gives error so EpiData can't run the REC form. Any suggestion(s) how to deal with it? Thank you a lot! /Ziad Stockholm-Sweden _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

number of lines + number of characters?
by epidata-list＠lists.umanitoba.ca 02 Feb '05

02 Feb '05

Hello! While building questionnaire (QES) in EpiData version 3.1, I reach certain stage where keyboard can not type letters anymore. I tried to take away (delete) empty lines or to reduce spaces between words in the questionnaire, so then I could type. Does EpiData has limited number of characters, and please note that I had around 800 lines in total? Another question: what if I had more than 1000 lines, how to deal with it? Thank you a lot! /Ziad El-Khatib Stockholm-Sweden

1 0

EpiData-list Digest, Vol 15, Issue 14
by epidata-list＠lists.umanitoba.ca 28 Jan '05

28 Jan '05

My e-mail system rejected the attached files because it is unsecure file. As I can see, the files in e-mail format. It will be better if files in TEXT or WORD foramt. Best regards and keep in touch Nabil Brandl

1 0

Re: EpiData-list Digest, Vol 15, Issue 14
by epidata-list＠lists.umanitoba.ca 28 Jan '05

28 Jan '05

My e-mail system rejected the attached files because it is unsecure file. As I can see, the files in e-mail format. It will be better if files in TEXT or WORD foramt. Best regards and keep in touch Nabil Brandl Denmark ----- Original Message ----- From: <epidata-list-request(a)lists.umanitoba.ca> To: <epidata-list(a)lists.umanitoba.ca> Sent: Friday, January 28, 2005 7:00 PM Subject: EpiData-list Digest, Vol 15, Issue 14 > 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..." > ---------------------------------------------------------------------------- ---- > Today's Topics: > > 1. just a trial after problems (epidata-list(a)lists.umanitoba.ca) > 2. ddd (epidata-list(a)lists.umanitoba.ca) > 3. essai? (epidata-list(a)lists.umanitoba.ca) > ---------------------------------------------------------------------------- ---- > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list >

1 0

essai?
by epidata-list＠lists.umanitoba.ca 28 Jan '05

28 Jan '05

essai

1 0

ddd
by epidata-list＠lists.umanitoba.ca 28 Jan '05

28 Jan '05

ddddd

1 0

just a trial after problems
by epidata-list＠lists.umanitoba.ca 28 Jan '05

28 Jan '05

1 0

CALLING EPIDATA FUNCTIONS
by epidata-list＠lists.umanitoba.ca 26 Jan '05

26 Jan '05

Hi, I need to find out ways in which one could call epidata export function from epi2000. by this i have in mind the following example; ITEM Begin Execute c:\FILE NAME.REC End This sample will call the rec file and execute it. I need to do the same but this time, to export a file to maybe spss. How can i achieve this? Thanks Joel

1 0

Re: EpiData-list Digest, Vol 15, Issue 9 (Out of the office)
by epidata-list＠lists.umanitoba.ca 19 Jan '05

19 Jan '05

I will be out of the office from Thu. Jan. 13 through Fri. Jan. 14, 2005. I will reply to your email as soon as possible. If you need immediate assistance please call the DPCP Administrative Assistant, Bennie Daughtry at 545-4471.

1 0

Release of v3.1 EpiData
by epidata-list＠lists.umanitoba.ca 19 Jan '05

19 Jan '05

Version 3.1 of EpiData has been placed for download on: Http://www.epidata.dk/downloads/php In all translated versions. The major news is: a. Now double entry verification can be done by comparing with first entry at record and field level. b. Users can define their own functions and add to the Check file language. c. An extended BACKUP command with possibility for zip and encryption has been added. d. A new SHOWLASTRECORD command has been added in which the last record is shown on opening a rec file instead of "NEW record". -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

RE: [EpiData-list] re: tables
by epidata-list＠lists.umanitoba.ca 18 Jan '05

18 Jan '05

Not a problem. Thanks for commenting. I believe he said it would Be sorted. Stay safe, Kelly -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Friday, January 14, 2005 5:16 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] re: tables Oops - sorry Kelly. I had FREQ on the brain when I was reading the list the other day. Seems to me this is just a design feature that will come in place when the final work is done on TABLES. The cell & column orders should be handled the same was as for FREQ (i.e. numeric order for integer and float) as you and Jens point out. Jamie

1 0

EpiData and memory
by epidata-list＠lists.umanitoba.ca 17 Jan '05

17 Jan '05

>>> <epidata-list(a)lists.umanitoba.ca> 12-01-2005 19:51:45 >>> Hi, How much RAM is required to run EpiData 3.02? Very little RAM should be needed, but clearly it would depend on the complexity of your system. What I would do in such a situation is: a. Try on a different computer with same technical capability (ram, processor etc). b. Try with the samples accompanying EpiData (in samples folder). Run them all and if some do not work c. Try on more advanced computer d. After opening the rec file for data entry press F2 twice and see if the small "status window" comes up. If b and c works and a does not. Some aspect of that particular computer could be a problem. I have seen an instance in which calling external programs (e.g. execute epic ......) caused some "older" pc's to break down. With v3.1 the addition of the backup command remedies the need to call epic for more complicated backup including encryption of the backup copy. We will consider to extend the F2-F2 window with a memory status. regards Jens Lauritsen Initiator and Coordinator of EpiData Denmark

1 0

Table command behavior (sort order and alignment)
by epidata-list＠lists.umanitoba.ca 16 Jan '05

16 Jan '05

Controlling alignment and sorting are separate issues. This is the current strategy for implementation: 1. Sorting a. Numerical variables: by numerical code: 1,2,3..etc b. String variables: alfa: a,b,c,d,e,f .....1234 ABCEFG....123... But also that we should introduce options such as: /reverse : meaning reverse order /count: based on how many counts are in each category. if count and reverse are combined smallest counts first /limit: Only show categories with more records than the indicated value The options I do not expect to have ready in first version, but the general sort order will be fixed. WIth the suggestions of Jamie Hockin there is a good work-around of how users could have a string variable containing numerical codes could be sorted according to numerical value correctly. 2. Alignment Alignment is a completely different issue since this is not controlled by the individidual command, but rather by the formatting system of the output. All alignment and format is controlled by a "cascaded style sheet" contained in the file epiout.css. So for instance for the left most column this would be for right alignment: .firstcol {color: black ;font-size: 10pt;font-family: Fixedsys; font-weight: normal; text-align: right; padding-right: 10px; } and for left alignment: .firstcol {color: black ;font-size: 10pt;font-family: Fixedsys; font-weight: normal; text-align: left; padding-right: 10px; } I suggest test persons try to work out different variants of the style sheet and we could provide these with the installation routine. Currently we are working on build 18 of analysis. We have managed to incorporate the same source code for reading chk files as in epidata, such that we secure complete correspondance btw. the two programs. THe other major change has been to increase the precision of the internal representation of real numbers. Both changes require a lot of testing and going over functions, this is why there has been a while since release of last build. Kind regards Jens Lauritsen Initiator and Coordinator of EpiData.

1 0

re: tables
by epidata-list＠lists.umanitoba.ca 14 Jan '05

14 Jan '05

Oops - sorry Kelly. I had FREQ on the brain when I was reading the list the other day. Seems to me this is just a design feature that will come in place when the final work is done on TABLES. The cell & column orders should be handled the same was as for FREQ (i.e. numeric order for integer and float) as you and Jens point out. Jamie

1 0

RE: [EpiData-list] re: tables
by epidata-list＠lists.umanitoba.ca 14 Jan '05

14 Jan '05

Greetings, Jamie. I agree and I do understand "padding" strings. However, the Example I used was age as integer and sex and integer. The reason I chose this example was because using Epi604D Analysis and issuing the command Tables age sex the result was 1-n for age and 1-2 for sex. The data is stored as integers for both. Having to convert to string and then pad sounds a bit much. I suggest that the TABLES command using integers in both Fields be changed to produce the same ordering as FREQ. And, if padding is going to be so important, I agree there should be a function. I do appreciate your response and I have encountered a few other items Of Which I'm keeping track and will send along once I have exhausted my efforts. Have a great weekend and stay safe, Kelly Kelly Bussell CDC Atlanta -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Thursday, January 13, 2005 3:07 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] re: tables Numeric fields display in the correct (ascending) order in FREQ. e.g. . freq time TIME No. % 0 1 2.50 1 1 2.50 14 1 2.50 22 1 2.50 31 1 2.50 ... 98 1 2.50 102 1 2.50 However, text fields are normally left-justified, even though FREQ shows them right-justified. With the same data and . define a ___ . let a = time . freq a A No. % 0 1 2.50 1 1 2.50 102 1 2.50 104 1 2.50 119 1 2.50 123 1 2.50 138 2 5.00 14 1 2.50 154 2 5.00 162 1 2.50 181 1 2.50 202 1 2.50 22 1 2.50 To right-justify the text field (or a copy of the text field would be safer as shown here): . define b ___ . b = copy(" ",1,3-length(trim(a)))+a . freq b B No. % 0 1 2.50 1 1 2.50 14 1 2.50 22 1 2.50 31 1 2.50 ... 92 1 2.50 97 1 2.50 98 1 2.50 102 1 2.50 104 1 2.50 I've used version 0.9 Build 17. This is a trick that is necessary with other systems as well, as strings tend to be stored left-justified unless you design it otherwise. Rather than have FREQ take care of this, it might be preferable to have a function to do the right-alignment of a field or do the left-padding of a string. e.g. b = LPAD(a) Jamie Hockin Public Health Agency of Canada

1 0

re: tables
by epidata-list＠lists.umanitoba.ca 13 Jan '05

13 Jan '05

Numeric fields display in the correct (ascending) order in FREQ. e.g. . freq time TIME No. % 0 1 2.50 1 1 2.50 14 1 2.50 22 1 2.50 31 1 2.50 ... 98 1 2.50 102 1 2.50 However, text fields are normally left-justified, even though FREQ shows them right-justified. With the same data and . define a ___ . let a = time . freq a A No. % 0 1 2.50 1 1 2.50 102 1 2.50 104 1 2.50 119 1 2.50 123 1 2.50 138 2 5.00 14 1 2.50 154 2 5.00 162 1 2.50 181 1 2.50 202 1 2.50 22 1 2.50 To right-justify the text field (or a copy of the text field would be safer as shown here): . define b ___ . b = copy(" ",1,3-length(trim(a)))+a . freq b B No. % 0 1 2.50 1 1 2.50 14 1 2.50 22 1 2.50 31 1 2.50 ... 92 1 2.50 97 1 2.50 98 1 2.50 102 1 2.50 104 1 2.50 I've used version 0.9 Build 17. This is a trick that is necessary with other systems as well, as strings tend to be stored left-justified unless you design it otherwise. Rather than have FREQ take care of this, it might be preferable to have a function to do the right-alignment of a field or do the left-padding of a string. e.g. b = LPAD(a) Jamie Hockin Public Health Agency of Canada

1 0

Re: EpiData-list Digest, Vol 15, Issue 5 (Out of the office)
by epidata-list＠lists.umanitoba.ca 13 Jan '05

13 Jan '05

I will be out of the office from Thu. Jan. 13 through Fri. Jan. 14, 2005. I will reply to your email as soon as possible. If you need immediate assistance please call the DPCP Administrative Assistant, Bennie Daughtry at 545-4471.

1 0

EpiData and memory
by epidata-list＠lists.umanitoba.ca 12 Jan '05

12 Jan '05

Hi, How much RAM is required to run EpiData 3.02? One of my coworkers has had problems with her laptop computer freezing after coding 5-6 records. She has Windows 95 and 64MB of RAM. The CHK file that she is using is rather large -- it is 113 KB and 5322 lines long. The REC file is 85 KB. I have tried coding into the same REC file on a computer with 512MB of RAM. I had no problems after coding 15 records. Could my coworker be having a problem with RAM, or could there be a problem with the length of the CHK file? Any guidance would be greatly appreciated. Thanks, Katie

1 0

Tables in analysis and output direction
by epidata-list＠lists.umanitoba.ca 06 Jan '05

06 Jan '05

Regarding printing: The epi6 mode of routing to screen, printer etc. is not possible with windows, but we could consider a printing command, e.g.: print file.txt which would direct that file to printer. The user could then first make a log file (logopen) and then afterwards send that file to the printer I think we could also make a possibility to print the output window as such. Concering the sort order of tables: TABLES AGE SEX (age sex are numeric) resulted in AGE listed as > 1 >10 >11 >Etc. To >19 > 2 >20 Obviously this should be adapted such that there is by default a chronological sort of a numerical field and by values of a field with comment legal. User control of sort order is already on the wish list. I suggest members of the list add name and country when adding information to the list. But do not add e-mail since all mails are available when searching on internet, so SPAM systems could catch the mail adresses. Notice also that return fields of mails are not included in the mail list so the list does not show any e-mail adresses Regards Jens Lauritsen EpiData Association Denmark

1 0

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

06 Jan '05

Greetings. Happy New Year! I am starting to use EpiData & Analysis and I think you are doing a nice job. I have not tried to access a printer directly in a .PGM as yet. I like very much the ability of Epi6 to allow me to program For users the destination of output e.g. screen, printer or to a file. I haven't seen any examples yet but in case there are none this Has always been important to site managers in the developing settings. I was doing FREQ and TABLES a moment ago and had the following result. FREQ AGE worked just fine TABLES AGE SEX (age sex are numeric) resulted in AGE listed as 1 10 11 Etc. To 19 2 20 21 22 Ect. To 29 3 30 31 I think this needs to be fixed. Or, what have I done wrong? Thank you and keep up the good work.

1 0

Encrypted fields in EpiData
by epidata-list＠lists.umanitoba.ca 04 Jan '05

04 Jan '05

The reason for placing the encrypted key encrypted in the header is: 1. There must be a place to compare the entered password with the true one Otherwise the decryption cannot work. You could argue that if a false key was provided, then nonsense would be returned and it would be up to the user to see that contents of an encrypted field was garbage. I would feel that was a dangerous situation, since if the user saved the record again, then the wrong key would be applied to garbage giving "double" garbage and no way to retrieve data. Another approach would be to save the key in a different file than the rec file header, but your arguments would apply equally to that. Certainly I can assure: The idea was NOT to provide a backdoor in case the user forgets their password. There is no way for EpiData crew or others to retrieve a forgotten passkey So the core of the reasoning has been: We rely on the "non-breakability" of the AES/Rijndael encryption principle and we need to know if the user uses the correct key - otherwise data could be lost. As a comparison, e.g. the password mechanism provided by WINZIP or Access is not reliable, there are programs on internet which will guess millions of passwords in few seconds for these - and find the one used. regards Jens Lauritsen Initiator and coordinator of EpiData

1 1

Line 640, error message
by epidata-list＠lists.umanitoba.ca 04 Jan '05

04 Jan '05

Thank you for the reply! Here is the answer in your text below: We should know more about the contents of the qes file to answer, e.g.: 1. How many lines in total --> So far it is 1616 lines. 2. How many fields are you planning --> the questionnaire is made of different categories. It is between 70-80 fields. 3. Are you using the "first word" or automatic options for creation of fields. --> First word. 4. which build and version of EpiData --> Version 3.02 5. Have you tried also with the v3.1 release candidate ? --> Unfortunately no. 6. Does preview of the same file work --> Yes! all the time with no problem at all! >>If you have as many fields as you indicate the error is either because you have more than 1000 lines in the qes file (which v3.1. will issue a warning for) or the automatic numbering of fields with similar names ran out of possible combinations. --> Does not EpiData take more than 1000 lines or? Happy 2005! /Ziad > I sent past message related to "field definition error in line > 640" message. > I tried to retype the QES form. So each five questions, I > switched the > QES file into REC file and did "checks" for it. I kept doing the > same > procedure, and I passed the line 640.

1 1

Re: error in line 640 (field definition)
by epidata-list＠lists.umanitoba.ca 31 Dec '04

31 Dec '04

> I sent past message related to "field definition error in line > 640" message. > I tried to retype the QES form. So each five questions, I > switched the > QES file into REC file and did "checks" for it. I kept doing the > same > procedure, and I passed the line 640. We should know more about the contents of the qes file to answer, e.g.: 1. How many lines in total 2. Hovw many fields are you planning 3. Are you using the "first word" or automatic options for creation of fields. 4. which build and version of EpiData 5. Have you tried also with the v3.1 release candidate ? 6. Does preview of the same file work If you have as many fields as you indicate the error is either because you have more than 1000 lines in the qes file (which v3.1. will issue a warning for) or the automatic numbering of fields with similar names ran out of possible combinations. Happy new year to everyone Jens Lauritsen

1 0

RE : [EpiData-list] Field definition error
by epidata-list＠lists.umanitoba.ca 29 Dec '04

29 Dec '04

Limits: * EpiData is a single user program. Workaround: Enter data on one PC and distribute copies for reading of data to other PC's. * Number of Records in a file (currently around 200.000). * All fields must fit within 999 lines of text. - but: You can combine files which each has that many lines (RELATE function -------- Message d'origine-------- De: epidata-list-bounces(a)lists.umanitoba.ca de la part de epidata-list(a)lists.umanitoba.ca Date: mer. 29/12/2004 09:33 À: epidata-list(a)lists.umanitoba.ca Cc: Objet: [EpiData-list] Field definition error Hello again! I sent past message related to "field definition error in line 640" message. I tried to retype the QES form. So each five questions, I switched the QES file into REC file and did "checks" for it. I kept doing the same procedure, and I passed the line 640. Later on, the message showed up again, and please note here that I was at line 1007, which means EpiData read line 640 already before and there was no problem. What happened now? Help!! Thank you and best regards /Ziad -- Ziad El-Khatib Clinical Cancer Epidemiology Z5:01, Karolinska Institutet 17 176 Stockholm Sweden Telephone: +46-8-517 72 946 Fax: +46-8-517 79 621 Mobile: +46-73-776 48 59 _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Field definition error
by epidata-list＠lists.umanitoba.ca 29 Dec '04

29 Dec '04

Hello again! I sent past message related to "field definition error in line 640" message. I tried to retype the QES form. So each five questions, I switched the QES file into REC file and did "checks" for it. I kept doing the same procedure, and I passed the line 640. Later on, the message showed up again, and please note here that I was at line 1007, which means EpiData read line 640 already before and there was no problem. What happened now? Help!! Thank you and best regards /Ziad -- Ziad El-Khatib Clinical Cancer Epidemiology Z5:01, Karolinska Institutet 17 176 Stockholm Sweden Telephone: +46-8-517 72 946 Fax: +46-8-517 79 621 Mobile: +46-73-776 48 59

1 0

Error message
by epidata-list＠lists.umanitoba.ca 27 Dec '04

27 Dec '04

Hello! I tried to run a REC file, I was getting this error message: "The field definition in line 593 could not be read or interpreted" This does not show when I "preview" the QES file. The field mentionned above is a number field (##).Everything looks ok for me. Any tips? Thank you in advance! Happy & Safe 2005! /Ziad -- Ziad El-Khatib Clinical Cancer Epidemiology Z5:01, Karolinska Institutet 17 176 Stockholm Sweden Telephone: +46-8-517 72 946 Fax: +46-8-517 79 621 Mobile: +46-73-776 48 59

1 0

Troubleshooting data file error message
by epidata-list＠lists.umanitoba.ca 20 Dec '04

20 Dec '04

The first thing to do when getting messages such as "Error in the data file <filename>" Would be to check if the latest backup copy you made gives the same answer (I assume everyone are taking regular backups). If you have no backup copy of the file in question and you have exported the data to SAS, just make SAS save the file as a delimited file and get it back via the qes file, which you have hopefully a copy of. An error often occurring is that users are saving other filetypes on top of data due to Windows NOT showing complete file name, but excluding extensions. Therefore one can by mistake think that there "save as .not file " (e.g. yourfile.not), but it was actually a .rec file (e.g. yourfile.rec). To exclude that possibility set up your windows to always show extensions for all types, also known files. Ask someone if you do not know how to- it is an option in explorer for folders. regards Jens Lauritsen EpiData initiator and coordinator.

1 0

EpiData Analysis v0.9 build 16 released
by epidata-list＠lists.umanitoba.ca 18 Dec '04

18 Dec '04

Build 16 of analysis has been uploaded. Added or modified update shows which values are changed with if statements. if started with a pgm file, that file will be executed. internal representation of float variable changed from double to extended Testsystem improved (e.g. try startnist.pgm) Bug removal and modification: String variables of length 1 are saved correctly negative values in result variables fixed lre() function corrected for negative values Calculation of 10,25,75 and 90 percentiles corrected recode function corrected to include limits btw. groups Various interface problems Adapted Commands.htm and Howto.htm file. Download from Http://www.epidata.dk/testing.php Remaining issues before release as v1 are: Implementing a system to handle incorrect data when reading (e.g. years like 0203) Some aspects of reading dbf files - report errors. Table command - simplifying output for stratified tables Printing can be a problem accross printers - report problems. Defining Boolean variables impossible (<Y>) due to interference with html language, use integer instead. But for many standard types of analysis and basic graphs it works quite well. Regards Jens Lauritsen Coordinator and initiator of EpiData EpiData Association, Odense, Denmark

1 0

Re: EpiData-list Digest, Vol 14, Issue 8 (Out of office)
by epidata-list＠lists.umanitoba.ca 17 Dec '04

17 Dec '04

I will be back at my desk on Tuesday 22/12/2004 morning. Until then I will have little opportunity to access my E-mail. Anything regarding the: Inter-Agency EMERGENCY ENVIRONMENTAL HEALTH FORUM Please send your message again to interagency(a)lshtm.ac.uk If there is anything other requiring urgent attention, please contact: Rebecca.Collins(a)lshtm.ac.uk +44 020 7927 22 14 or Rachel.Clarke(a)lshtm.ac.uk +44 020 7927 22 14 Kind regards Kristof >>> epidata-list 12/17/04 18:20 >>> 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

Troubleshooting data file error message
by epidata-list＠lists.umanitoba.ca 17 Dec '04

17 Dec '04

I am a new user of EpiData and I have successfully created data files and exported to SAS for analysis. One of the .rec files I recently created will not open and I get the following error message: Error in the data file <filename> The field definition in line 3 could not be read or interpreted. Any advice on how to correct this problem is appreciated.

1 0

FW: [EpiData-list] EpiData guideline - released for testing
by epidata-list＠lists.umanitoba.ca 14 Dec '04

14 Dec '04

Dear Ziad, Could you please email me a copy? - My email address is NWilson(a)iuatld.org. Thanks and regards Nevin Dr.Nevin Wilson, M.B., B.S., Junior TB Consultant International Union Against Tuberculosis and Lung Disease (The Union) 68, Boulevard Saint-Michel 75006 Paris, France Mobile : +91 94430 26848 Tele/Fax: +91 4262 266022 email: NWilson(a)iuatld.org website: www.iuatld.org -----Original Message----- From: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Sent: Friday, November 26, 2004 1:15 PM To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData guideline - released for testing Hello! The file is done now and I am sending it to test it. If someone is interested to have a copy, please write me back with your email address so I can email it to you (it is around 5.5Mb size) in PDF format. It is free for distribution as well! And anyone is welcome to write back with questions and/or suggestions! Note: I have intention to go further in guidelines development in case there is interest and fund (maybe?) to keep the work on? Best regards! /Ziad Karolinska Institute Stockholm - Sweden

1 2

Avoiding "jumps reset 9" in string fields.
by epidata-list＠lists.umanitoba.ca 13 Dec '04

13 Dec '04

To handle "jumps reset 9" for string fields this would have to be settled after the values are filled in. That is if the jump is to field "endnote1", then there could be a endnote1 before entry >IF (Q14=55) THEN > CLEAR Q15B > CLEAR Q16B >ENDIF end end Jens M. Lauritsen The EpiData Association, ps. The list does not disclose users e-mail adresses to minimise spam. If someone wishes to have direct comments you must add the e-mail directly in the text - as some did yesterday, but I suggest to do it in a way spam systems will not (should not) catch, e.g. "info at epidata.dk" that is put " at " instead of @

1 0

New introductory guide to EpIData
by epidata-list＠lists.umanitoba.ca 13 Dec '04

13 Dec '04

Ziad has sent me the pdf file of the notes for distribution. Look on Http://www.epidata.dk/documentation.php for downloading. The e-mail for correspondance to ZIAD is placed on the frontpage of the note. Thanks for the contribution. Jens M. Lauritsen, Consultant,MD. PhD. The EpiData Association,

1 0

Definition of Values, Jumps Reset
by epidata-list＠lists.umanitoba.ca 13 Dec '04

13 Dec '04

Jens, Thank you very much for your help. From reading the help file, I didn't realize that "JUMPS RESET 9" would actually fill in each variable with the full length. That actually works better for me. Is there anyway that I can reset only my numeric values to 9? I would prefer to keep my char variables clear when they're skipped. I tried writing: IF (Q14=55) THEN CLEAR Q15B CLEAR Q16B ENDIF I thought this might overwrite the "JUMPS RESET" for those variables, but it didn't work that way. Is there any other way to do this, aside from writing a bit of code (Q15A=99, CLEAR Q15B, etc...) for each variable between Q14 and ENDNOTE1? Also, regarding the message "Definition of values (comment legal, missingvalue, range ...)": In my program, I have code like in your example: v1 mustenter missingvalue 99 comment legal use label_q01 after entry if (v1 <> 8) and (v1 <> 14) and (v1 <> 21) and (v1 <> 99) then help "Wrong value entered" goto v1 endif end end The reason I did this is because I wanted the users to be able to override the legal values if they felt it was necessary to type in something other than 8, 14, 21, or 99 -- sometimes valid codes are added to our variables. Yet I wanted the users to still get a warning if they didn't use one of the legal values. I also had to add "range -9 99" in order for this to work with "comment legal use". As far as I understand, users cannot override legal values or range values. Please correct me if I am wrong. As a result, I stay away from using legal and range in my EpiData programs, unless I want to have value labels. While the after entry block above is seemingly unnecessary, it at least allows the user to click in the next appropriate field with their mouse and force the program to accept the value. Thank you, Katie Thornton Programmer Institute for Research on Poverty

1 0

EpiData guideline - released for testing
by epidata-list＠lists.umanitoba.ca 13 Dec '04

13 Dec '04

Hello! The file is done now and I am sending it to test it. If someone is interested to have a copy, please write me back with your email address so I can email it to you (it is around 5.5Mb size) in PDF format. It is free for distribution as well! And anyone is welcome to write back with questions and/or suggestions! Note: I have intention to go further in guidelines development in case there is interest and fund (maybe?) to keep the work on? Best regards! /Ziad Karolinska Institute Stockholm - Sweden

1 3

Definition of values (comment legal, missingvalue, range ....)
by epidata-list＠lists.umanitoba.ca 12 Dec '04

12 Dec '04

Often when users of EpIData send in files to epidata.dk for help it turns out that chk files are created more complex than actually needed. One example of this: From a chk file (opened in the editor, not in "Add/revise") example: labelblock LABEL label_q01 8 dog 14 Horse 21 "lazy tiger" end end v1 missingvalue 99 comment legal use label_q01 end In this situation only the values 8 14 21 and 99 plus "blank=missing" can be entered. If the v1 block is changed to: v1 mustenter missingvalue 99 comment legal use label_q01 end Only the values 8 14 21 and 99 can be entered. So there would be no reason to test in a "after entry .... end" block like this: v1 mustenter missingvalue 99 comment legal use label_q01 after entry if (v1 <> 8) and (v1 <> 14) and (v1 <> 21) and (v1 <> 99) then help "Wrong value entered" goto v1 endif end end One other aspect of this is that sometimes people define the same values in a RANGE and LEGAL and COMMENT LEGAL and MISSINGVALUE Any value should only be in one of these definitions. regards Jens Lauritsen

1 0

Definition of values (comment legal, missingvalue, range ....)
by epidata-list＠lists.umanitoba.ca 12 Dec '04

12 Dec '04

Often when users of EpIData send in files that are giving problems it turns out that the chk files are created more complex than actually needed e.g.: LABEL label_q01 8 dog

1 0

Re: Jumps reset
by epidata-list＠lists.umanitoba.ca 12 Dec '04

12 Dec '04

The command "jumps reset value", e.g. Q14 TOPOFSCREEN JUMPS RESET 9 55 ENDNOTE1 END will do: after entry in field q14 EpiData will check "Is q14 = 55" if so then jump to field endnote1, but before "landing in endnote1" : RESET all numerical variables from Q14 to ENDNOTE1 to missing ("." or ""). and furthermore : RESET 9 : fill all variables from q14 to ENDNOTE1 with as many 9's as the width of each field. That is if you have a field of width 2 the value will be 99, a field of length 10 will be filled with all 9's. So you cannot do: jumps reset 99. Only one digit is allowed, but the variables passed with the jump will get 99 if these fields are of width 2. Regards Jens Lauritsen Initiator and Coordinator of EpiData

1 0

MISSINGVALUE / JUMPS RESET commands
by epidata-list＠lists.umanitoba.ca 09 Dec '04

09 Dec '04

Send the chk + qes file to info(a)epidata.dk and we will check if it is a limit problem or what could be the cause. Also check that you are using most recent version, which is 3.02, but v3.1 is on the test page (www.epidata.dk/testing.php) - we are lacking final. In general it is a good suggestion to partition a study such that each type of data is in a particular file connected with relate. Also if you press F2 twice a small "debug" window will be shown with current file, variable and memory status. This can give further information. E.g. if you are working on the correct folder. Regards Jens Lauritsen Initiator and Coordinator of EpiData

1 0

MISSINGVALUE / JUMPS RESET commands
by epidata-list＠lists.umanitoba.ca 08 Dec '04

08 Dec '04

Hello, I've really enjoyed using EpiData, and I have to say that the application I am creating will be a HUGE improvement over what our data collectors had been using. They're excited to start using EpiData. I am having problems using some check file commands, however. When I use the command "Jumps Reset 99", this code mysteriously disappears from my .chk file without warning after I save and exit. If I use "Jumps Reset 9", it stays. I need to use 99, though, because 9 is a valid code for some of my variables. I am also having trouble using the Missingvalue command. When I type in "MISSINGVALUE 98" in a field, this code will also mysteriously disappear from my .chk file, though not always immediately, like "Jumps Reset 99" does. I have tried using the missingvalue command in the before file block, but I've had no luck with this. I am wondering if the size of my .chk file has anything to do with these problems. I saw in the help file that there is a limit of 64Kb if you work in the editor, but I use the add / revise checks feature so I'm not sure if this affects me. My .chk file is 90Kb, and over 4200 lines long. If I can't use Jumps Reset 99, this will increase the size of my .chk file even further. Besides the above problems, everything is working OK. Any advice that you can give would be greatly appreciated. Thank you, Katie Thornton Programmer Institute for Research on Poverty

1 0

Labels in stata after export from epidata
by epidata-list＠lists.umanitoba.ca 07 Dec '04

07 Dec '04

Correct. Thanks! However, in order for the value label to work properly in Stata, it seems that the value label must be written in ascending order, i.e. 0 No_Adjuv 1 Adjuv not the other way around. Halvor Sommerfelt At 00:28 07.12.2004 +0100, you wrote: >Most likely the problem is a Stata matter of how labels are shown in the >data browser > >Try in stata: >use xxxxxxxx (your file) >d >* check the formats >* set format for the variable with problems : >format %9.0g x (assume name is x) >browse > >Works here for me. If the display format is too narrow for a given >variable, then the label is not showing correctly in browse, but does show >correctly at : >label list >or >tab >or >freq >of that variable. > >If you still have problems send the rec+chk file as an attachment to >info(a)epidata.dk or indicate adress for download. > >regards > >-- >Jens Lauritsen >Coordinator and initiator of EpiData Project >http://www.epidata.dk > > >_______________________________________________ >EpiData-list mailing list >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 0

Re: labels in stata after export from epidata
by epidata-list＠lists.umanitoba.ca 06 Dec '04

06 Dec '04

Most likely the problem is a Stata matter of how labels are shown in the data browser Try in stata: use xxxxxxxx (your file) d * check the formats * set format for the variable with problems : format %9.0g x (assume name is x) browse Works here for me. If the display format is too narrow for a given variable, then the label is not showing correctly in browse, but does show correctly at : label list or tab or freq of that variable. If you still have problems send the rec+chk file as an attachment to info(a)epidata.dk or indicate adress for download. regards -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Problems with variable labels after transferring data from Epidata to Stata
by epidata-list＠lists.umanitoba.ca 06 Dec '04

06 Dec '04

Hi: I'm a newcomer to Epidata and am holding a course on Data entry and analysis for our Masters students this week. I have a problem in that variable labels that seem to work well in Epidata 3.02 are not maintained properly after exporting the data to Stata. It works fine when exporting to SPSS. The pictures under http://www.cih.uib.no/presentations/hsommerfelt/EpidataLabels.JPG illustrate the problem. I would greatly appreciate advice on how to solve the problem. Yours sincerely Professor Halvor Sommerfelt, MD, PhD, DTM, Centre for International Health, University of Bergen, Armauer Hansen Building, N-5021 Bergen, Norway Ph: +47 5597 4987 Fax: +47 5597 4979 http://www.cih.uib.no

1 1

RE: STATA labels
by epidata-list＠lists.umanitoba.ca 01 Dec '04

01 Dec '04

Jens Thanks what you advise does fix the problem. However even if the uncompressed STATA file is used and Epidata wants 1.000 in stead of 1, 1.000 is stillnot recognised as a legal value, if you put in 1.000 it says illegal entry. However the whole problem is circumvented when compressing the file as you suggest. Thanks paul Rheeder -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca]On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 30 November 2004 20:03 To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 13, Issue 9 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