From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9912E" ========================================================================= Date: Wed, 29 Dec 1999 10:44:28 +0100 Reply-To: gilles Sender: Epi Info Discussion Group From: gilles Subject: Re: source for anthropometric data?? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit >If possible, I would prefer to obtain an "electronic" dataset. > >Since EPI-INFO calculates anthropometric z-scores, I asumed that the data >is in this program, but when I look through the files, I don't see >anything that is obvious.... Epi-Info don't use data tables but calculate each z-scores using interpolation of the curve. Since the curve is quite complexe the calcul in Turbo-Pascal is not so easy ! Some years ago I translat it in clipper (DBASE Compiler), I can send you a copy if you are interrested May be you can also contact NCHS, to obtain more recent information. Gilles DESVE EpiConcept ========================================================================= Date: Wed, 29 Dec 1999 10:32:14 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: As the Millenium Wanes... Comments: cc: EPI Info Helpdesk MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We hope to have another beta version of Epi Info 2000 ready for downloading in the next couple of weeks. An upgrade to make the DOS version of Epi Info Y2K compliant has been available on the Epi Info Website since 1997. Those who believe in the "just-in-time" inventory system may want to upgrade this week. If you downloaded the upgrade prior to December, a couple of small bug-fixes are included in the current version (concerning export of dates to dBASE and settting a RANGE for a date in the CHECK program). > To make Epi Info 6.04B Year 2000 Compliant, download the 4BUPDATE.EXE file > from the website: HTTP://WWW.CDC.GOV/EPO/EPI/DOWNEPI6.HTM > > It is a self-expanding file that will overwrite existing EpiInfo > executable files, but WILL NOT delete data files. Enter "Y" (Yes) to all > 17 "overwrite" prompts you will see. > > INSTALLING: > Before installing the 4BUPDATE, YOU MUST BE SURE THAT YOU HAVE THE CURRENT > version 6.04(b) installed on your PC. Place the 4BUPDATE.EXE (a > self-extracting compressed file) in your EPI6 directory. By using the > mouse, copy the 4BUPDATE to C:\EPI6. Double click on the 4BUPDATE.EXE > file, a black DOS screen should appear asking a series of OVERWRITE > questions. Please type "Y" for yes, then enter after each question until > the update is complete. Check the main screen of EPI-INFO for the version > number and the upgrade. The screen should read: version 6.04b to c > upgrade. Your software is now Y2K compliant. > > If you need further assistance, please contact: > Epi Info Technical Support > Centers For Disease Control and Prevention > 770.488.8440 > epiinfo@cdc.gov > > Since we do not know all the users of Epi Info, we have provided the Y2K upgrade and documentation via our Website, and have made it known to members of the Epi Info listserv group, the CDC Y2K group, and to probably hundreds of institutions that have inquired by mail. We are grateful to TEPHINET and others for helping to spread the word. The past 2 years of the EIS course have used the upgraded version of Epi Info, and Y2K compliance with Epi Info has been explained in the course. A utility is provided in the upgrade to convert previous data files to 4-digit year fields. New files, of course, should be created with 4-digit years when designing the questionnaire. French and Spanish versions of the upgrade are available from other websites referenced under Translations. Translations in other languages may not be Y2K compliant. What happens if you use a non-Y2K compliant Epi Info in the new millenium? Probably there will be no negative consequences if all dates are in the 21st century. Calculation of time intervals spanning 2 centuries may be faulty. If you are using a translation that does not have a Y2K upgrade, we recommend testing the program with the computer system date set to a date in January 2000 to detect any potential problems. By entering time intervals (ages) rather than calculating them within a program, even obsolete software may remain useful in the new century if necessary. A complete beta-test version of Epi Info 2000 for Windows 95, 98, and NT is expected soon, to be followed, within the first quarter of 2000, by the released version. Happy Millenium to all, The Epi Info Development Team ========================================================================= Date: Thu, 30 Dec 1999 09:49:16 +1100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Catherine Bennett Subject: Problems with the "MATCH" command? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I need urgent assistance in running my matched analyses for an outbreak investigation. I am using Epi Info 6.04 (version b to c upgrade Oct97) to analyse data for a case control study of a salmonellosis outbreak.=20 I discovered discrepancies between the unmatched odds ratios that I = calculated=20 and the crude ORs generated during the matched analyses. Whilst I will be = using=20 the Mantel-HaenszeI matched OR, I was interested in comparing it with the = crude=20 OR to assess the impact of breaking the match as there has been some = discussion=20 on the degree to which we have matched our cases and controls with our = selection process (matching on case's telephone number prefix, a loose = geographic match in Australia). I then did some of the calculations by = hand and have arrived at the following conclusions about how Epi Info = handles data under the "match" command: =20 1) The Crude Odds Ratios calculated in matched analyses are only based on the discordant pairs (or triplets in my case as I have 2 controls per = case).=20 2) if there are missing exposure data for one control, the "match" = analysis will treat the remaining case and control as a pair & will include in analyses if discordant. 3) Including cases & controls where exposure data on the case is missing = will=20 not effect the calculation of Mantel-Haenzel matched ORs as the triplet is excluded from all calculations. The controls will be used in the calculatio= n of the crude OR, however, so the two statistics are based on different = samples,=20 though this is not immediately obvious to the user. Are these conclusions correct? If so, I have the following concerns.=20 1) Excluding all triplets where there is concordance between the case and = both=20 controls (ie all exposed or all unexposed) from the crude OR calculation has a dramatic impact on the unmatched OR. For one of my variables with=20 relatively rare exposure, excluding concordant triplets increased the unmatched OR from 7.5 to 36.0. Why is this crude OR calculated this way? 2) How do I calculate an appropriate crude OR to look for the impact of breaking matching? Do I have to screen every single exposure variable to see if data are missing and if it involves the case or controls, and if a case & control remain, if they are discordant -- just to identify the = subset to use to calculate an unmatched OR? 3) How does Epi Info amalgamate discordant pair data from a mix of triplet and paired (if one control is missing exposure information) case control = sets=20 when there are missing data? My calculations suggest that discordance = between=20 a case and its 'remaining' control is given more 'weight' (i.e. has more = impact on OR) than when the control with missing exposure information is = treated as if concordant with the case and analysed in the same way as = other triplets.=20 Finally, it also seems that if using a subset of cases (I am only = analysing a=20 certain phage type), all control sets are still identified in the "matched = sets" n value=20 whether or not their matched case has been selected in the phage type = subset. I=20 note that this does not effect the output, but it could mislead researchers= into thinking that matched analyses were based on more "matched sets" = than is actually the case. And again it means that crude and matched ORs = are based on completetly different samples. I worked around this by = tagging controls with the phage type of their respective case and selected = both case and controls by phage type. Thank you for your help. _____________________________ Dr Catherine Bennett Epidemiology Registrar Hunter Public Health Unit PO Box 466 Wallsend NSW 2287 AUSTRALIA +61 2 4924 6477 Ph +61 2 4924 6490 Fax huncbenn@doh.health.nsw.gov.au=20 catherib@ozemail.com.au=20 ========================================================================= Date: Wed, 29 Dec 1999 21:18:43 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "B. Gerstman" Subject: Data Analyis with Epi Info - Instructional Materials (2nd ed.) MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Dear Epi Info Colleagues: I've updated my online instructional manual *Data Analysis with Epi Info*= = located at http://www.sjsu.edu/faculty/gerstman/EpiInfo/. The current Tab= le of Contents reads: = -- Preface -- 1. Some Statistical Basics 2. How To Analyze Data = 3. Epi Info Version 6 Basics 4. Continuous Outcome, Single Group 5. Continuous Outcome, Paired Samples (Single Group) 6. Continuous Outcome, Two Independent Groups 7. Continuous Outcome, Several Independent Groups = 8. Continuous Outcome, Continuous Predictor (Correlation and= Regression) 9. Continuous Outcome, Multiple Predictors (Multiple Regression) = 10. Categorical Outcome, One Group 11. Categorical Outcome, Independent Groups 12. Binary Outcome, Single Group 13. Binary Outcome, Two Independent Groups, Forward-Direction= al (Cohort) Studies = 14. Binary Outcome, Two Independent Groups, Backward-Directional (Case-Control) Studies 15. Stratified Tables: Introduction to Confounding and Interaction 16. Binary Outcome, Paired (Matched) Samples 17. Binary Outcome, Test for Trend Future Chapters (not yet written): 18. Logistic Regression 19. Poisson Events 20. Comparison of Rates 21. Stratified Rates 22. Poisson Regression 23. Survival Analysis 24. Cox Proportional Hazards Model I think you'll find the work much improved. = Anyone interested in contributing Exercises or other instructional materi= al to the work is encouraged to contact me via B_Gerstman@compuserve.com. I look forward to the pending release of Epi Info 2000, at which time I will update the current material to conform to its output and procedures= . Best wished for a happy and healthy 2000! Sincerely, = Bud Gerstman San Jose, California, USA ========================================================================= Date: Wed, 29 Dec 1999 21:18:40 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "B. Gerstman" Subject: Interactive Statistical Calculation Pages MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Dear Epi Info Colleagues: FYI, here's the address of a great Web site that indexes and links many useful statistical resources on the Web: http://members.aol.com/johnp71/javastat.html The site includes links to both instructional and computational resources= . = Rgds, = Bud Gerstman ========================================================================= Date: Thu, 30 Dec 1999 10:27:28 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Problems with the "MATCH" command? Comments: cc: "Dicker, Richard C. " , "Sullivan Kevin (E-mail)" , "B. B. Gerstman (E-mail)" , "Friedman, Roger" , "Gu David (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" You have brought up some points about MATCH that we also have been pondering. It is quite correct that Epi 6 calculates a crude odds ratio that is not as crude as one might expect--i.e., it omits the tables with zero marginals. Of course the (completely) crude odds ratio can be calculated by using the TABLES command without the match variable. We would very much like to have these questions answered for Epi Info 2000; I am sending your email to several persons more qualified than I to comment. What output would you LIKE to see from MATCH with regard to the "crude" odds ratio? It would not be particularly difficult to present both the CRUDE OR (Matching disregarded) and also the CRUDE OR (Excluding tables with zero marginals), but there may be better choices or better wording that others can suggest. The last point you make is an excellent one for your own analysis, and the solution seems to be the reasonable one. Since Epi Info identifies the match based on the MatchID, the MatchID is assumed to indicate legitimate controls and cases within the currently selected records. MatchID's should be assigned so that they convey all the necessary information about the match, unless there is a way of selecting subsets of controls based on another variable. Thank you for your careful analysis of the issues. This is how Epi Info improves. We look forward to hearing from others who have suggestions on these issues. -----Original Message----- From: Catherine Bennett [mailto:huncbenn@DOH.HEALTH.NSW.GOV.AU] Sent: Wednesday, December 29, 1999 5:49 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Problems with the "MATCH" command? I need urgent assistance in running my matched analyses for an outbreak investigation. I am using Epi Info 6.04 (version b to c upgrade Oct97) to analyse data for a case control study of a salmonellosis outbreak. I discovered discrepancies between the unmatched odds ratios that I calculated and the crude ORs generated during the matched analyses. Whilst I will be using the Mantel-HaenszeI matched OR, I was interested in comparing it with the crude OR to assess the impact of breaking the match as there has been some discussion on the degree to which we have matched our cases and controls with our selection process (matching on case's telephone number prefix, a loose geographic match in Australia). I then did some of the calculations by hand and have arrived at the following conclusions about how Epi Info handles data under the "match" command: 1) The Crude Odds Ratios calculated in matched analyses are only based on the discordant pairs (or triplets in my case as I have 2 controls per case). 2) if there are missing exposure data for one control, the "match" analysis will treat the remaining case and control as a pair & will include in analyses if discordant. 3) Including cases & controls where exposure data on the case is missing will not effect the calculation of Mantel-Haenzel matched ORs as the triplet is excluded from all calculations. The controls will be used in the calculation of the crude OR, however, so the two statistics are based on different samples, though this is not immediately obvious to the user. Are these conclusions correct? If so, I have the following concerns. 1) Excluding all triplets where there is concordance between the case and both controls (ie all exposed or all unexposed) from the crude OR calculation has a dramatic impact on the unmatched OR. For one of my variables with relatively rare exposure, excluding concordant triplets increased the unmatched OR from 7.5 to 36.0. Why is this crude OR calculated this way? 2) How do I calculate an appropriate crude OR to look for the impact of breaking matching? Do I have to screen every single exposure variable to see if data are missing and if it involves the case or controls, and if a case & control remain, if they are discordant -- just to identify the subset to use to calculate an unmatched OR? 3) How does Epi Info amalgamate discordant pair data from a mix of triplet and paired (if one control is missing exposure information) case control sets when there are missing data? My calculations suggest that discordance between a case and its 'remaining' control is given more 'weight' (i.e. has more impact on OR) than when the control with missing exposure information is treated as if concordant with the case and analysed in the same way as other triplets. Finally, it also seems that if using a subset of cases (I am only analysing a certain phage type), all control sets are still identified in the "matched sets" n value whether or not their matched case has been selected in the phage type subset. I note that this does not effect the output, but it could mislead researchers into thinking that matched analyses were based on more "matched sets" than is actually the case. And again it means that crude and matched ORs are based on completetly different samples. I worked around this by tagging controls with the phage type of their respective case and selected both case and controls by phage type. Thank you for your help. _____________________________ Dr Catherine Bennett Epidemiology Registrar Hunter Public Health Unit PO Box 466 Wallsend NSW 2287 AUSTRALIA +61 2 4924 6477 Ph +61 2 4924 6490 Fax huncbenn@doh.health.nsw.gov.au catherib@ozemail.com.au ========================================================================= Date: Thu, 30 Dec 1999 11:16:18 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: FW: [EPI-INFO] Interactive Statistical Calculation Pages Comments: To: "B. Gerstman" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Thanks, We will probably put a link to this site in the menu or documentation for Epi 2000. It really takes the pressure off us to have every statistical routine in the world in the product. If it weren't for the difficulty of maintenance, one could make a giant STATCALC consisting of nothing a menu that calls the URL's in this site. -----Original Message----- From: B. Gerstman [mailto:B_Gerstman@COMPUSERVE.COM] Sent: Wednesday, December 29, 1999 9:19 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Interactive Statistical Calculation Pages Dear Epi Info Colleagues: FYI, here's the address of a great Web site that indexes and links many useful statistical resources on the Web: http://members.aol.com/johnp71/javastat.html The site includes links to both instructional and computational resources. Rgds, Bud Gerstman ========================================================================= Date: Thu, 30 Dec 1999 14:39:08 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Stephen S Rinsler Subject: Re: source for anthropometric data?? In-Reply-To: In , on 12/28/99 at 04:28 PM, "Dean, Andrew G." said: >Formulas. Look at the source code in MEASURE.PAS. It's just a text >file, and the code is more or less readable even if you don't know >Pascal. >-----Original Message----- >From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] >Sent: Tuesday, December 28, 1999 4:18 PM >To: EPI-INFO@LISTSERV.CDC.GOV >Subject: Re: [EPI-INFO] source for anthropometric data?? >In , on >12/28/99 > at 02:08 PM, "Dean, Andrew G." said: >>The calculations are contained in equations in the Pascal file >>Measure.PAS that is included with Epi Info 6. A variety of coefficients >>are used with interpolation, but individual data points are not given. It >>may be possible to obtain individual data points from Dr. Kuczmarski, but >>we do not have a public set that has been validated and can be given out. >>-----Original Message----- >[SNIP] >Pardon my ignorance, but how can you evaluate data (ie, calculate >z-scores) without such a reference dataset? >Steve >-- >----------------------------------------------------------- >stever1@mindspring.com >Stephen S Rinsler, MD >Chester, NJ 07930 >----------------------------------------------------------- Ok -- I obviously completely understood what goes on with the anthropometric module; it won't tell you that a certain height and/or weight are at a certain percentile or z-score with the 50th %ile of a particular reference population (such as the one used by NCHS in generating US infant growth charts). Rather, it is a calculating tool for producing z-scores of a particular group of individuals whose weights and lengths or heights have been entered into EPI-INFO. Is there any way to relate these results to a standard population? Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Thu, 30 Dec 1999 15:55:03 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: source for anthropometric data?? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" MEASURE.PAS receives the age, sex, height, and weight of a single child, compares this with the CDC/WHO 1977/1985 Growth Reference Curves and returns the percentile, z-score and other parameters based on equations that are used in the module. My understanding is the the equations are supplied with different coefficients depending on the dimensions of the child and that interpolation occurs because not all the necessary values are included. In other words, equations are used rather than a simple look-up table to produce the results. But you can consider the results to be similar to those obtained from a look-up table. -----Original Message----- From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] Sent: Thursday, December 30, 1999 2:39 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] source for anthropometric data?? In , on 12/28/99 at 04:28 PM, "Dean, Andrew G." said: >Formulas. Look at the source code in MEASURE.PAS. It's just a text >file, and the code is more or less readable even if you don't know >Pascal. >-----Original Message----- >From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] >Sent: Tuesday, December 28, 1999 4:18 PM >To: EPI-INFO@LISTSERV.CDC.GOV >Subject: Re: [EPI-INFO] source for anthropometric data?? >In , on >12/28/99 > at 02:08 PM, "Dean, Andrew G." said: >>The calculations are contained in equations in the Pascal file >>Measure.PAS that is included with Epi Info 6. A variety of coefficients >>are used with interpolation, but individual data points are not given. It >>may be possible to obtain individual data points from Dr. Kuczmarski, but >>we do not have a public set that has been validated and can be given out. >>-----Original Message----- >[SNIP] >Pardon my ignorance, but how can you evaluate data (ie, calculate >z-scores) without such a reference dataset? >Steve >-- >----------------------------------------------------------- >stever1@mindspring.com >Stephen S Rinsler, MD >Chester, NJ 07930 >----------------------------------------------------------- Ok -- I obviously completely understood what goes on with the anthropometric module; it won't tell you that a certain height and/or weight are at a certain percentile or z-score with the 50th %ile of a particular reference population (such as the one used by NCHS in generating US infant growth charts). Rather, it is a calculating tool for producing z-scores of a particular group of individuals whose weights and lengths or heights have been entered into EPI-INFO. Is there any way to relate these results to a standard population? Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Thu, 30 Dec 1999 16:33:44 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Stephen S Rinsler Subject: Re: source for anthropometric data?? In-Reply-To: In , on 12/30/99 at 03:55 PM, "Dean, Andrew G." said: >MEASURE.PAS receives the age, sex, height, and weight of a single child, >compares this with the CDC/WHO 1977/1985 Growth Reference Curves and >returns the percentile, z-score and other parameters based on equations >that are used in the module. My understanding is the the equations are >supplied with different coefficients depending on the dimensions of the >child and that interpolation occurs because not all the necessary values >are included. In other words, equations are used rather than a simple >look-up table to produce the results. But you can consider the results >to be similar to those obtained from a look-up table. >-----Original Message----- [SNIP] Hmm So the generated z-scores are definitely based on the REFERENCE values. What happens when one is dealing with a group that is obviously different from the US based data? Do analyses compare the z-score of (say) the median of the study group to the reference group, or defining the size of the fraction with less than a certain z-score? (I guess I should RTFM again...). Thanks Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Thu, 30 Dec 1999 16:44:43 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Stephen S Rinsler Subject: Re: As the Millenium Wanes... In-Reply-To: In , on 12/29/99 at 10:32 AM, "Dean, Andrew G." said: >We hope to have another beta version of Epi Info 2000 ready for >downloading in the next couple of weeks. >An upgrade to make the DOS version of Epi Info Y2K compliant has been >available on the Epi Info Website since 1997. >Those who believe in the "just-in-time" inventory system may want to >upgrade this week. If you downloaded the upgrade prior to December, a >couple of small bug-fixes are included in the current version (concerning >export of dates to dBASE and settting a RANGE for a date in the CHECK >program). > > To make Epi Info 6.04B Year 2000 Compliant, >download the 4BUPDATE.EXE file > > from the website: >HTTP://WWW.CDC.GOV/EPO/EPI/DOWNEPI6.HTM > > > > It is a self-expanding file that will overwrite >existing EpiInfo > > executable files, but WILL NOT delete data >files. Enter "Y" (Yes) to all > > 17 "overwrite" prompts you will see. > > > > INSTALLING: > > Before installing the 4BUPDATE, YOU MUST BE >SURE THAT YOU HAVE THE CURRENT > > version 6.04(b) installed on your PC. Place >the 4BUPDATE.EXE (a > > self-extracting compressed file) in your EPI6 >directory. By using the > > mouse, copy the 4BUPDATE to C:\EPI6. Double >click on the 4BUPDATE.EXE > > file, a black DOS screen should appear asking a >series of OVERWRITE > > questions. Please type "Y" for yes, then enter >after each question until > > the update is complete. Check the main screen >of EPI-INFO for the version > > number and the upgrade. The screen should >read: version 6.04b to c > > upgrade. Your software is now Y2K compliant. > > > > If you need further assistance, please contact: > > Epi Info Technical Support > > Centers For Disease Control and Prevention > > 770.488.8440 > > epiinfo@cdc.gov > > > > >Since we do not know all the users of Epi Info, we have provided the Y2K >upgrade and documentation via our Website, and have made it known to >members of the Epi Info listserv group, the CDC Y2K group, and to >probably hundreds of institutions that have inquired by mail. We are >grateful to TEPHINET and others for helping to spread the word. The past >2 years of the EIS course have used the upgraded version of Epi Info, and >Y2K compliance with Epi Info has been explained in the course. >A utility is provided in the upgrade to convert previous data files to >4-digit year fields. New files, of course, should be created with >4-digit years when designing the questionnaire. >French and Spanish versions of the upgrade are available from other >websites referenced under Translations. Translations in other languages >may not be Y2K compliant. >What happens if you use a non-Y2K compliant Epi Info in the new >millenium? Probably there will be no negative consequences if all dates >are in the 21st century. Calculation of time intervals spanning 2 >centuries may be faulty. If you are using a translation that does not >have a Y2K upgrade, we recommend testing the program with the computer >system date set to a date in January 2000 to detect any potential >problems. By entering time intervals (ages) rather than calculating them >within a program, even obsolete software may remain useful in the new >century if necessary. >A complete beta-test version of Epi Info 2000 for Windows 95, 98, and NT >is expected soon, to be followed, within the first quarter of 2000, by >the released version. >Happy Millenium to all, >The Epi Info Development Team - I had previously downloaded a 4bupdate.exe file (? 5-6 months ago), but I decided to download this one. The site says the file size is 1368224 bytes, but when I download it, it apparently is a 1182762 byte file. I started the extraction process and it states that the archive date is Sept 23, 1997. The "old" 4bupdate.exe file is 1274457 bytes and also has an archive date of Sept 23, 1997. The site doesn't provide an archive date for the latest 4bupdate file, but your note suggests that it is a 1999 creature. Signed Confused. Happy New Year (new millenium -1). Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Thu, 30 Dec 1999 22:56:15 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jens M. Lauritsen" Subject: weight height (sourcecode ....) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" May I suggest that you contact prof Boldsen at the "j-boldsen@win-chs.sdu.dk". He worked intensively with that relation. Kindly Jens Lauritsen ps. I tried to mail directly,but Mail sent to : stever1@mindspring.com was rejected. ========================================================================= Date: Fri, 31 Dec 1999 16:57:48 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "B. Gerstman" Subject: Interactive Statistical Calculation Pages Comments: To: Andy Dean MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Sounds good, Andy. The development and maintenance of statistical routine= s and the interface needed to run them can be labor- intensive. I support t= he principal of taking pressure off the development team so they can more effectively focus on Epi Info's strengths: reliable data management and basic statistical procedures. Keep the faith, Bud Gerstman Message text written by Epi Info Discussion Group > = Thanks, We will probably put a link to this site in the menu or documentation for= Epi 2000. It really takes the pressure off us to have every statistical routine in the world in the product. If it weren't for the difficulty of= maintenance, one could make a giant STATCALC consisting of nothing a menu= that calls the URL's in this site. -----Original Message----- From: B. Gerstman [mailto:B_Gerstman@COMPUSERVE.COM] Sent: Wednesday, December 29, 1999 9:19 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Interactive Statistical Calculation Pages Dear Epi Info Colleagues: FYI, here's the address of a great Web site that indexes and links many useful statistical resources on the Web: http://members.aol.com/johnp71/javastat.html The site includes links to both instructional and computational resources= . Rgds, Bud Gerstman < ========================================================================= Date: Fri, 31 Dec 1999 16:57:57 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "B. Gerstman" Subject: EPI-INFO: Dr. Bennett's Questions about the MATCH command Comments: To: Catherine Bennett MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Dear Dr. Bennett and Epi Info Colleagues, Dr. Bennett raises interesting questions about analyzing matched data whe= n information about some pairs is incomplete. I will allow those of you familiar with the MATCH command to address some of the computational specifics, as I seldom use this command myself. I can, however, address some of generalities about matching, or at least add my point of view. First, two general opinions: = (A) It is important recognize that only discordant tuples contain= useful inferential information, at least as it pertains to inferences regarding risk. We must, therefore, discard (or treat differently) tuples= which are concordant. This upsets some researchers, since it seems unfair= and, undoubtedly, is a waste of information (or is it?). Nevertheless, sample-matching has shifted our attention to differences *within* tuples and not differences between subjects. Perhaps I am a purest -- or just an= old fuddy duddy -- but is seems to me that the sampling method should dictate the analysis, even if a correct answer is achieved by breaking th= e match. (B) According to Epi Info's documentation, the MATCH command stratifies data according to a tuple indicator. I haven't worked out the math, but such estimates (based on Mantel-Haenszel weighted average risks= and variability) might be asymptotically equal while being mathematically= different. (Estimates of variance differ.) Again, I defer to my MATCH-command-familiar colleagues to comment on this. = Now, with respect to Dr. Bennett's specific questions, here's my tuppence= : Question 1) Excluding all triplets where there is concordance between the= case and both controls (ie all exposed or all unexposed) from the crude O= R calculation has a dramatic impact on the unmatched OR. For one of my variables with relatively rare exposure, excluding concordant triplets increased the unmatched OR from 7.5 to 36.0. Why is this crude OR calculated this way? Response: Although I can't comment on why the crude OR was calculated in any particular way, I can suggest that the concordant triplets *should* b= e excluded and the crude odds ratio *should* be ignored. The unbiased estimate (unbiased from a statistical perspective, not epidemiologic perspective) appears to be 36.0. Also, an excellent piece on how to use information in incomplete pairs while still preserving matching in the complete pairs is published in this week's American Journal of Epidemiolo= gy (Am J Epidemiol 1999;150:1340-5). It's worth checking out. = Question 2) How do I calculate an appropriate crude OR to look for the impact of breaking matching? Do I have to screen every single exposure variable to see if data are missing and if it involves the case or controls, and if a case & control remain, if they are discordant -- just = to identify the subset to use to calculate an unmatched OR? Response: I suggest that you do NOT break the match, but if you must, the= computation of the 2x2 table would depend on how you've structured your data. I might just be easiest to tally the number of exposed case, unexposed cases, exposed controls, and unexposed controls, and then use Statcalc or EpiTable to compute your crude odds ratios. Alternatively a TABLES command might work. = Question 3) How does Epi Info amalgamate discordant pair data from a mix = of triplet and paired (if one control is missing exposure information) case control sets when there are missing data? My calculations suggest that discordance between a case and its 'remaining' control is given more 'weight' (i.e. has more impact on OR) than when the control with missing exposure information is treated as if concordant with the case and analys= ed in the same way as other triplets. = Response: See Richard Dicker's consultation on how Epi Info accomplishes this fact, and what to do in the face of matching. Your other questions c= an be classified as "how do I deal with missing data?" This depends a lot on= your philosophy: either your are "intention to treat" type or not. (Perha= ps I oversimplify). My suggestion: Do not make any assumptions about missin= g observations: treat them neither exposed or unexposed, and as neither a concordance nor discordance. Also see the missing-indicator article, mentioned above (Am J Epidemiol 1999;150:1340-5). [Last question] Finally, it also seems that if using a subset of cases (I= am only [analyzing] a certain phage type), all control sets are still identified in the "matched sets" n value whether or not their matched cas= e has been selected in the phage type subset. I note that this does not effect the output, but it could mislead researchers into thinking that matched analyses were based on more "matched sets" than is actually the case. And again it means that crude and matched ORs are based on [completely] different samples. I worked around this by tagging controls with the phage type of their respective case and selected both case and controls by phage type. Response: I concur. The thing to do is SELECT out the subtype of interest= and ignore the rest. = Rgds and happy computing, Bud Gerstman B_Gerstman@compuserve.com Message text written by Epi Info Discussion Group > = I need urgent assistance in running my matched analyses for an outbreak investigation. I am using Epi Info 6.04 (version b to c upgrade Oct97) to= analyse data for a case control study of a salmonellosis outbreak. = I discovered discrepancies between the unmatched odds ratios that I calculated = and the crude ORs generated during the matched analyses. Whilst I will be= using = the Mantel-HaenszeI matched OR, I was interested in comparing it with the= crude = OR to assess the impact of breaking the match as there has been some discussion = on the degree to which we have matched our cases and controls with our selection process (matching on case's telephone number prefix, a loose geographic match in Australia). I then did some of the calculations by ha= nd and have arrived at the following conclusions about how Epi Info handles data under the "match" command: = 1) The Crude Odds Ratios calculated in matched analyses are only based on= the discordant pairs (or triplets in my case as I have 2 controls per case). = 2) if there are missing exposure data for one control, the "match" analys= is will treat the remaining case and control as a pair & will include in analyses if discordant. 3) Including cases & controls where exposure data on the case is missing will = not effect the calculation of Mantel-Haenzel matched ORs as the triplet i= s excluded from all calculations. The controls will be used in the calculation of the crude OR, however, so the two statistics are based on different samples, = though this is not immediately obvious to the user. Are these conclusions correct? If so, I have the following concerns. = 1) Excluding all triplets where there is concordance between the case and= both = controls (ie all exposed or all unexposed) from the crude OR calculation has a dramatic impact on the unmatched OR. For one of my variables with = relatively rare exposure, excluding concordant triplets increased the unmatched OR from 7.5 to 36.0. Why is this crude OR calculated this way? 2) How do I calculate an appropriate crude OR to look for the impact of breaking matching? Do I have to screen every single exposure variable to see if data are missing and if it involves the case or controls, and if a= case & control remain, if they are discordant -- just to identify the subset to use to calculate an unmatched OR? 3) How does Epi Info amalgamate discordant pair data from a mix of triple= t and paired (if one control is missing exposure information) case control sets = when there are missing data? My calculations suggest that discordance between = a case and its 'remaining' control is given more 'weight' (i.e. has more impact on OR) than when the control with missing exposure information is treated as if concordant with the case and analysed in the same way as other triplets. = Finally, it also seems that if using a subset of cases (I am only analysi= ng a = certain phage type), all control sets are still identified in the "matche= d sets" n value = whether or not their matched case has been selected in the phage type subset. I = note that this does not effect the output, but it could mislead researche= rs into thinking that matched analyses were based on more "matched sets" tha= n is actually the case. And again it means that crude and matched ORs are based on completetly different samples. I worked around this by tagging controls with the phage type of their respective case and selected both case and controls by phage type. Thank you for your help. _____________________________ Dr Catherine Bennett Epidemiology Registrar Hunter Public Health Unit PO Box 466 Wallsend NSW 2287 AUSTRALIA +61 2 4924 6477 Ph +61 2 4924 6490 Fax huncbenn@doh.health.nsw.gov.au = catherib@ozemail.com.au = < From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9912D" ========================================================================= Date: Mon, 22 Nov 1999 23:12:47 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kurt Hedlund Subject: Re: source for anthropometric data?? In-Reply-To: <199912220142.UAA25893@smtp6.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Tack Carlos och God Jul p=E5 dig, Kurt At 20:52 1999-12-21 -0500, you wrote: >I am seeking a source for the length/height and weight data used to >construct growth charts. While the growth charts are widely available and >referenced, I have not found a source from which I can obtain the >datasets. > >Appreciate any assistance in finding a source from which I could obtain >this data. > >Steve > >-- >----------------------------------------------------------- >stever1@mindspring.com >Stephen S Rinsler, MD >Chester, NJ 07930 >----------------------------------------------------------- > > ========================================================================= Date: Fri, 24 Dec 1999 08:49:42 +0300 Reply-To: alanf@AfricaOnline.Co.Ke Sender: Epi Info Discussion Group From: ALAN FERGUSON Organization: PERSONAL Subject: Manipulating data bases MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit It must be a common problem with a simple solution, but, as a relatively new EPI user, I can't work it out satisfactorily. I have a data base from a large community-based health project with data for about 20 variables coming in via health facilities on a monthly basis. I want to aggregate this in different ways, firstly into a set of REC files which reflect different time-slices and administrative units, and then write some programs for inexperienced users to drop out indicators, graphs etc. The stumbling block seems to be the SUMTABLES command. I cannot see how to crosstabulate aggregates of variables by, say, a set of months or a set of sub-regions, and output the results to a new REC file. The specific problems are a) you can effectively only work on one variable at a time in a SUBTABLES crosstab and b) restrictions on the use of string variables in SUBTABLES. >From the NETSS example (SUMMARY.PGM), it looks easy, but I find it hard to copy the logic and get the same outputs. Any suggestions would be welcome. ========================================================================= Date: Fri, 24 Dec 1999 10:51:49 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: Manipulating data bases Comments: To: alanf@AfricaOnline.Co.Ke Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=zfWGuQP1vq9UIX7rPWcJtRvuzSoUhtw7NrGoWCqEg9e3eyg1SV3hl3EA" --0__=zfWGuQP1vq9UIX7rPWcJtRvuzSoUhtw7NrGoWCqEg9e3eyg1SV3hl3EA Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable It isn't entirely clear what you want to do. It seems your original dat= aset is in case-by-case form, in which situation, you cannot use SUMTABLES. SUM= TABLES only works on the output from a TABLES command via: ROUTE SUMMFILE.REC OUTPUT TABLES VAR1 VAR2 VAR3 ... VARn READ SUMMFILE SUMTABLES COUNT VARx VARy The variable COUNT must be the first in the SUMTABLES command as it giv= es the aggregate counts in the table created above. Browse SUMMFILE (or whatev= er you call it) to see the structure. You can also OUTPUT SUMTABLES to get .rec files with greater aggregatio= n. SUMMARY.PGM reads a .rec file that is already aggregated, and the varia= ble CASECOUNT holds the cell counts in the large table used by that NETSS e= xample. Your variables VAR1, VAR2, ... VARn on the OUTPUT TABLES or SUMTABLES c= an by string variables. Hope that helps. Much of what you want to do can be accomplished with E= PI6 report generator, too, if you just want to produce nice canned reports.= ---------------------- Jamie Hockin MD,MSc -------------------------- Director, Field Epidemiology _ Directeur, Programme de formation Training Program _|\ en =E9pid=E9miologie d'intervention= LCDC, Health Canada :| \ LLCM, Sant=E9 Canada PL 0602B Tunney's Pasture | LP 0602B Pr=E9 Tunney Ottawa ON K1A 0L2, Canada Ottawa (Ontario) K1A 0L2, Canada Jamie_Hockin@hc-sc.gc.ca 613 957-1764 FAX: 613 941-6028 http://www.hc-sc.gc.ca/hpb/lcdc/survlnce/fetp ALAN FERGUSON on 99/12/24 12:49:42 AM Please respond to alanf@AfricaOnline.Co.Ke To: EPI-INFO@LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: [EPI-INFO] Manipulating data bases = --0__=zfWGuQP1vq9UIX7rPWcJtRvuzSoUhtw7NrGoWCqEg9e3eyg1SV3hl3EA Content-type: text/plain; charset=us-ascii Content-Disposition: inline It must be a common problem with a simple solution, but, as a relatively new EPI user, I can't work it out satisfactorily. I have a data base from a large community-based health project with data for about 20 variables coming in via health facilities on a monthly basis. I want to aggregate this in different ways, firstly into a set of REC files which reflect different time-slices and administrative units, and then write some programs for inexperienced users to drop out indicators, graphs etc. The stumbling block seems to be the SUMTABLES command. I cannot see how to crosstabulate aggregates of variables by, say, a set of months or a set of sub-regions, and output the results to a new REC file. The specific problems are a) you can effectively only work on one variable at a time in a SUBTABLES crosstab and b) restrictions on the use of string variables in SUBTABLES. >From the NETSS example (SUMMARY.PGM), it looks easy, but I find it hard to copy the logic and get the same outputs. Any suggestions would be welcome. --0__=zfWGuQP1vq9UIX7rPWcJtRvuzSoUhtw7NrGoWCqEg9e3eyg1SV3hl3EA-- ========================================================================= Date: Mon, 27 Dec 1999 10:35:39 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Epi Info 2000 Nearing Completion Comments: cc: "Sunki, Godha" MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" I'm not sure I understand the first wish. What do you mean by "compose the survey and put it in the background?" The second one we have tried to accommodate. When you compose a questionnaire with buckets of fields (> 255), Epi Info automatically creates related data tables ad infinitum and (we hope) keeps track of everything so that you think you are using a single humongous database. Naturally, this need testing. -----Original Message----- From: Thomas Slack [mailto:TSLACK@MAIL.MCG.EDU] Sent: Friday, December 17, 1999 8:35 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] Epi Info 2000 Nearing Completion Andrew, I'm glad that work is progressing well. As users we don't know how hard things are to do. Here are a couple of "bells and whistles" I'd like on Santa's list: We like to compose the survey and put it in the background. Is it possible to print the background with the response boxes? The other problem is the creation of Access databases. They are confined to 255 variables. Could Eppi someday be able to handle really large surveys? For production, we are using MS Access with frames and having to link forms and databases together, not much fun and will probably be difficult to maintain. We appreciate all of your efforts! Happy Holidays!, Tom Georgia Prevention Institute Medical College of Georgia ========================================================================= Date: Mon, 27 Dec 1999 16:09:50 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: source for anthropometric data?? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Chapter 23 on Nutritional Anthropometry in the Epi 6 manual has several references at the end. References 1 and 5 describe the 1985 revison of the 1977 NCHS reference growth curves that was adopted by WHO as the international standard, and is incorporated in Epi Info 6. NCHS is developing new curves for the US, but these have not yet been released. -----Original Message----- From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] Sent: Tuesday, December 21, 1999 8:53 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] source for anthropometric data?? I am seeking a source for the length/height and weight data used to construct growth charts. While the growth charts are widely available and referenced, I have not found a source from which I can obtain the datasets. Appreciate any assistance in finding a source from which I could obtain this data. Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Mon, 27 Dec 1999 18:30:28 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Stephen S Rinsler Subject: Re: source for anthropometric data?? In-Reply-To: I am seeking a computer file that contains appropriate height/length and weight data. What I have seen are the widely distributed charts (which are based on data but are a creation based on smoothing techniques (using the theory of knots, I believe) and references to paper publications. I spoke with Dr Kuczmarski at the Center for Health Statistics and he is sending me a copy of one of these. If possible, I would prefer to obtain an "electronic" dataset. Since EPI-INFO calculates anthropometric z-scores, I asumed that the data is in this program, but when I look through the files, I don't see anything that is obvious.... Is such a data file in EPI-INFO? Thanks in advance. Steve -------------------------------------------------------------------------------------------------- In , on 12/27/99 at 04:09 PM, "Dean, Andrew G." said: >Chapter 23 on Nutritional Anthropometry in the Epi 6 manual has several >references at the end. References 1 and 5 describe the 1985 revison of >the 1977 NCHS reference growth curves that was adopted by WHO as the >international standard, and is incorporated in Epi Info 6. >NCHS is developing new curves for the US, but these have not yet been >released. >-----Original Message----- >From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] >Sent: Tuesday, December 21, 1999 8:53 PM >To: EPI-INFO@LISTSERV.CDC.GOV >Subject: [EPI-INFO] source for anthropometric data?? >I am seeking a source for the length/height and weight data used to >construct growth charts. While the growth charts are widely available >and referenced, I have not found a source from which I can obtain the >datasets. >Appreciate any assistance in finding a source from which I could obtain >this data. >Steve >-- >----------------------------------------------------------- >stever1@mindspring.com >Stephen S Rinsler, MD >Chester, NJ 07930 >----------------------------------------------------------- -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Tue, 28 Dec 1999 14:08:27 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: source for anthropometric data?? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" The calculations are contained in equations in the Pascal file Measure.PAS that is included with Epi Info 6. A variety of coefficients are used with interpolation, but individual data points are not given. It may be possible to obtain individual data points from Dr. Kuczmarski, but we do not have a public set that has been validated and can be given out. -----Original Message----- From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] Sent: Monday, December 27, 1999 6:30 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] source for anthropometric data?? I am seeking a computer file that contains appropriate height/length and weight data. What I have seen are the widely distributed charts (which are based on data but are a creation based on smoothing techniques (using the theory of knots, I believe) and references to paper publications. I spoke with Dr Kuczmarski at the Center for Health Statistics and he is sending me a copy of one of these. If possible, I would prefer to obtain an "electronic" dataset. Since EPI-INFO calculates anthropometric z-scores, I asumed that the data is in this program, but when I look through the files, I don't see anything that is obvious.... Is such a data file in EPI-INFO? Thanks in advance. Steve ---------------------------------------------------------------------------- ---------------------- In , on 12/27/99 at 04:09 PM, "Dean, Andrew G." said: >Chapter 23 on Nutritional Anthropometry in the Epi 6 manual has several >references at the end. References 1 and 5 describe the 1985 revison of >the 1977 NCHS reference growth curves that was adopted by WHO as the >international standard, and is incorporated in Epi Info 6. >NCHS is developing new curves for the US, but these have not yet been >released. >-----Original Message----- >From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] >Sent: Tuesday, December 21, 1999 8:53 PM >To: EPI-INFO@LISTSERV.CDC.GOV >Subject: [EPI-INFO] source for anthropometric data?? >I am seeking a source for the length/height and weight data used to >construct growth charts. While the growth charts are widely available >and referenced, I have not found a source from which I can obtain the >datasets. >Appreciate any assistance in finding a source from which I could obtain >this data. >Steve >-- >----------------------------------------------------------- >stever1@mindspring.com >Stephen S Rinsler, MD >Chester, NJ 07930 >----------------------------------------------------------- -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Tue, 28 Dec 1999 16:17:58 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Stephen S Rinsler Subject: Re: source for anthropometric data?? In-Reply-To: In , on 12/28/99 at 02:08 PM, "Dean, Andrew G." said: >The calculations are contained in equations in the Pascal file >Measure.PAS that is included with Epi Info 6. A variety of coefficients >are used with interpolation, but individual data points are not given. It >may be possible to obtain individual data points from Dr. Kuczmarski, but >we do not have a public set that has been validated and can be given out. >-----Original Message----- [SNIP] Pardon my ignorance, but how can you evaluate data (ie, calculate z-scores) without such a reference dataset? Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- ========================================================================= Date: Tue, 28 Dec 1999 16:28:43 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: source for anthropometric data?? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Formulas. Look at the source code in MEASURE.PAS. It's just a text file, and the code is more or less readable even if you don't know Pascal. -----Original Message----- From: Stephen S Rinsler [mailto:stever1@MINDSPRING.COM] Sent: Tuesday, December 28, 1999 4:18 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] source for anthropometric data?? In , on 12/28/99 at 02:08 PM, "Dean, Andrew G." said: >The calculations are contained in equations in the Pascal file >Measure.PAS that is included with Epi Info 6. A variety of coefficients >are used with interpolation, but individual data points are not given. It >may be possible to obtain individual data points from Dr. Kuczmarski, but >we do not have a public set that has been validated and can be given out. >-----Original Message----- [SNIP] Pardon my ignorance, but how can you evaluate data (ie, calculate z-scores) without such a reference dataset? Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9912C" ========================================================================= Date: Wed, 15 Dec 1999 12:11:53 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Zambart Subject: Merry Christmas Comments: To: Zamnet Customer Support , Woody's Office Watch , "Winnie Dhaliwal [Gastroenterology]" , "Thorpe,Jane" , Tamara Hurst , Stephen Kennedy , Solveig Freudenthal , Sarah Lewin , Sarah Lee , Ryoko Murakami , Ruth Mcnerney , "Roz Sullivan (GAST) 2957190" , Royd Shisholeka , Royal Zambezi Lodge Ltd , Rosemary Hutchinson , "Richard C Pollok (GAST)" , Raymond Aldrin Daniels , "R. Namposya" , Phillipe de Jardin , Phillimon Ndubani , Petra de Haas , Peter Mwaba , PETER MWABA , Peter Godfrey-Faussett , Paul Sommerfield/TBALERT , PatsyG Gamwell , ouedraogo koudaogo , "Obioma G. Nnaemeka" , Nicole Fraser , "Nicola J Kingston (GAST) 13-7191" , Nicola Harding , Nicola Harding , National Food and Nutrition Commission , "Mwansa, Criticles" , Moonga Simuyandi , Mildred Bota , Michael Wavrin , MEMA kwa Vijana , Melody Mwenda , "MEJ. PK KASESE" <13230042@rgo.sun.ac.za>, "Maurice P Kelly (GAST)" , Matinde bijura , MaryAnn.DeGroote@UCHSC.edu, Mary Ross <081mary@chiron.wits.ac.za>, margarida muzala , Mainga Mukando , "M.Henderson" , LUSKAR PROJECT , kwibisa siyunyi , Karen Weyer , Julie Targett , Judith Glynn , Joseph Smalley , Joseph Nkolola , JOSEPH KAMANGA , Joseph Kamanga , John Holton , Joe Rodriguez , JOE MWABA , Joanne Cooper , Joanne Clark , jennifer georgeson , Isdore Chola Shamputa , "Isao Arita, MD." , Helen Ayles , Helen Ayles , Helen Ayles , Glenn Morris , Ginny Bond , G Mpetemoya , Fitzallan Regisford , fara elizabeth mwaba <98140065@tolka.dcu.ie>, Emma Watkins , Elizabeth Fara , "E. v.d. Weele" , d'souza <97970123@tolka.dcu.ie>, Douglas Webb , Dipankar Ghosh , Dick Van Soolingen , derick kambobe , dawson , Danielle , Connect2-SMTP Gateway , Claire Bertschinger , "Christine Blanshard (GAST) 13-7195" , Chris Chilufya Kalyamba , Cholwe Hope Nkomeshya , central@imis.org.uk, Cathie Roby , CATHERINE MEE , Carlton Evans , Boniface Moonze , betty , B Mbewe , Anner , Anne Fanning , Airwaves Ltd , AF-AIDS , admissions , ACCA , AARON MWALE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01BF46F5.92D7A0C0" This is a multi-part message in MIME format. ------=_NextPart_000_0019_01BF46F5.92D7A0C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks for communicating with ZAMBART STAFF During the year this goes to = wish you a very merry Xmas and a Happy and productive year 2000. =20 God bless you all.=20 =20 ------=_NextPart_000_0019_01BF46F5.92D7A0C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Thanks for communicating with ZAMBART STAFF During = the year=20 this goes to wish you a very merry Xmas and a Happy and productive year=20 2000.
 
God bless you all.
 
------=_NextPart_000_0019_01BF46F5.92D7A0C0-- ========================================================================= Date: Thu, 16 Dec 1999 15:46:16 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Epi Info 2000 Nearing Completion MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Despite the long silence from here, work on Epi Info 2000 is progressing well, and most of the features that were missing from the beta test versions are now in place. We have established a formal Testing, Quality Control, and Education Team under Dr. Juan Zubieta, and are systematically identifying and fixing the remaining bugs. The beta version on the ftp site is from late October. We hope to have another one ready for downloading in the next couple of weeks. Meanwhile, if you do wish to download the October version, the ftp address has changed to: ftp://epidemo:meds1998@sftp.cdc.gov/epi2000/ Let us know if you have difficulty with the ftp site. As before, please do not further distribute the above address except on a one-to-one basis, as it contains the password for access to the site. In particular, please do not publish it on the Internet or elsewhere, as we would like to confine the beta testers to those able to accept and deal with bugs, and who will not make the mistake of relying on beta software for real work. We will put up another notice when the next beta (? "Release Candidate 1???") is ready. With best wishes for the Holiday Season, Andy Dean and The Epi Info 2000 Development Team ========================================================================= Date: Fri, 17 Dec 1999 10:39:56 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: 19th ECTE - Please spread the news ... Comments: To: Epidemiology List , agd1@cdc.gov, alc@servidor.unam.mx, alkral@itsa.ucsf.edu, andrew.forbes@med.monash.edu.au, antunesc@mono.icb.ufmg.br, bengt.moller@mbox2.swipnet.se, bernt.lindtjorn@cih.uib.no, bmanyame@hqfaus01.unicef.org, bpazva@harare.iafrica.com, bxe2@cdc.gov, castellano.j@mcd.gen.de.us, cdckms@sph.emory.edu, chklein@manguinhos.ensp.fiocruz.br, ck@dynamite.com.au, coflunkc@leonis.nus.sg, consult@tstt.net.tt, coulombi@b3e.jussieu.fr, crmcc@gate.net, d.u.pfeiffer@massey.ac.nz, dnordlund@aol.com, eramalle@goriz.sendanet.es, esterman.adrian@health.sa.gov.au, evan.sergeant@smtpgwy.agric.nsw.gov.au, fmedpct@md2.md.chula.ac.th, fwolfe@msus1.msus.edu, g.hartel@mailbox.uq.edu.au, garst@uvapsy.psy.uva.nl, gomes@lelo.uem.mz, gpatrone@opal.tufts.edu, hans.stenlund@stat.umu.se, heberto@meakins.lan.mcgill.ca, jag.atrie@health.wa.gov.au, james_wood@compuserve.com, jaf@lamar.colostate.edu, jmatute@pronet.net.gt, jucar@cica.es, ljorm@doh.health.nsw.gov.au, lucas@dgsp.scstf.rcanaria.es, mamartinez@mail2.cti.unav.es, martinez_j@a1.rcdp.gov, mccleary@mrrc.bio.uci.edu, medicur1@edu.uch.gr, mikael.aberg@primnet.se, mikal.ustad@ism.uit.no, mulderym@fs7003.pg.tno.nl, pani@ymed.ks.se, per.blanck@mailbox.swipnet.se, pgnetto@ax.apc.org, pierreclaquin@compuserve.com, pmb@mhri.edu.au, promed@riosoft.softex.br, r.fisher@unsw.edu.au, ratti@usa.net, rbk8@cdc.gov, rmccart@epin.ab.umd.edu, rvs3@wonder.em.cdc.gov, sas@ipe.ufg.br, sonia@stat.psu.edu, statcon@ix.netcom.com, stefan.ma@commed.hku.hk, pturri@mail.state.tn.us, gilles@epiconcept.fr, normar01@mcgc16.med.nyu.edu, mcmillan@cc.ucsf.edu, jamie_hockin@inet.hwc.ca, mark_veitch.mdu@muwaye.unimelb.edu.au, jed5@cdc.gov, eramalle@mail.sendanet.es, Koomen.Em@net.HCC.nl, s.ritter@iop.bpmf.ac.uk, Rainer.Muche@medizin.uni-ulm.de, S.S.MASTANA@lboro.AC.UK, TCHUR@doh.health.nsw.gov.au, DDedman@phls.co.uk, jsantos@uec.inta.uchile.cl, Bob@exo.com, BHolden536@aol.com, kannika@cmu.chiangmai.ac.th, waa101@uriacc.uri.edu, ACTUARY@asko.donetsk.ua, EBRENNER@compuserve.com, jzg@cs.bham.ac.uk, FPetschke@t-online.de, wilsonsx@novell2.bham.ac.uk, jmc@med.pitt.edu, EpiMon@aol.com, gxs03@health.state.ny.us, busson@neptune.chu-stlouis.fr, steve.dunn@agric.nsw.gov.au, nbirkett@zeus.med.uottawa.ca, joe@ty-coch.demon.co.uk, JML@dadlnet.dk, damien@jolley.com.au, jason.muir@iname.com, loeffler@helios.nl.uu.net, scott@vet.uu.nl, bcjung11@netscape.com, Annie Lloyd , Arabella Duffield , peterhans@ubaclu.unibas.ch, Christopher Wroath , Christian Lengeler , Clare Gilbert , agd1@cdc.gov, alc@servidor.unam.mx, alkral@itsa.ucsf.edu, andrew.forbes@med.monash.edu.au, antunesc@mono.icb.ufmg.br, bengt.moller@mbox2.swipnet.se, bernt.lindtjorn@cih.uib.no, bmanyame@hqfaus01.unicef.org, bpazva@harare.iafrica.com, bxe2@cdc.gov, castellano.j@mcd.gen.de.us, cdckms@sph.emory.edu, chklein@manguinhos.ensp.fiocruz.br, ck@dynamite.com.au, coflunkc@leonis.nus.sg, consult@tstt.net.tt, coulombi@b3e.jussieu.fr, crmcc@gate.net, d.u.pfeiffer@massey.ac.nz, dnordlund@aol.com, eramalle@goriz.sendanet.es, esterman.adrian@health.sa.gov.au, evan.sergeant@smtpgwy.agric.nsw.gov.au, fmedpct@md2.md.chula.ac.th, fwolfe@msus1.msus.edu, g.hartel@mailbox.uq.edu.au, garst@uvapsy.psy.uva.nl, gomes@lelo.uem.mz, gpatrone@opal.tufts.edu, hans.stenlund@stat.umu.se, heberto@meakins.lan.mcgill.ca, jag.atrie@health.wa.gov.au, james_wood@compuserve.com, jaf@lamar.colostate.edu, jmatute@pronet.net.gt, jucar@cica.es, ljorm@doh.health.nsw.gov.au, lucas@dgsp.scstf.rcanaria.es, mamartinez@mail2.cti.unav.es, martinez_j@a1.rcdp.gov, mccleary@mrrc.bio.uci.edu, medicur1@edu.uch.gr, mikael.aberg@primnet.se, mikal.ustad@ism.uit.no, mulderym@fs7003.pg.tno.nl, pani@ymed.ks.se, per.blanck@mailbox.swipnet.se, pgnetto@ax.apc.org, pierreclaquin@compuserve.com, pmb@mhri.edu.au, promed@riosoft.softex.br, r.fisher@unsw.edu.au, ratti@usa.net, rbk8@cdc.gov, rmccart@epin.ab.umd.edu, rvs3@wonder.em.cdc.gov, sas@ipe.ufg.br, sonia@stat.psu.edu, statcon@ix.netcom.com, stefan.ma@commed.hku.hk, pturri@mail.state.tn.us, gilles@epiconcept.fr, normar01@mcgc16.med.nyu.edu, mcmillan@cc.ucsf.edu, jamie_hockin@inet.hwc.ca, mark_veitch.mdu@muwaye.unimelb.edu.au, jed5@cdc.gov, eramalle@mail.sendanet.es, Koomen.Em@net.HCC.nl, s.ritter@iop.bpmf.ac.uk, Rainer.Muche@medizin.uni-ulm.de, S.S.MASTANA@lboro.AC.UK, TCHUR@doh.health.nsw.gov.au, DDedman@phls.co.uk, jsantos@uec.inta.uchile.cl, Bob@exo.com, BHolden536@aol.com, kannika@cmu.chiangmai.ac.th, waa101@uriacc.uri.edu, ACTUARY@asko.donetsk.ua, EBRENNER@compuserve.com, jzg@cs.bham.ac.uk, FPetschke@t-online.de, wilsonsx@novell2.bham.ac.uk, jmc@med.pitt.edu, EpiMon@aol.com, gxs03@health.state.ny.us, busson@neptune.chu-stlouis.fr, steve.dunn@agric.nsw.gov.au, nbirkett@zeus.med.uottawa.ca, joe@ty-coch.demon.co.uk, JML@dadlnet.dk, damien@jolley.com.au, jason.muir@iname.com, loeffler@helios.nl.uu.net, scott@vet.uu.nl, bcjung11@netscape.com, Fran Horsfall , Greg Fegan , Hans Heuvelmans , Hisham Khogali , Jane Pryer , Johara Boukaa , John Howard , Juergen Smidt , Kevin Sullivan , Lola Gostelow , Mary Locking , Mary Manandhar , MSFH Khartoum , bart@hgea.org, jha@vms.huji.ac.il, jason.muir@iname.com, Jane.McCall@bhs.org, Giovanni.Leonardi@lshtm.ac.uk, Phil Atkinson , Prakash Shetty , Ric Price , Richard Bowman , Rob Davidson , rjfreund@NewNetra.ensp.fr, sph1804@utsph.sph.uth.tmc.edu, jehrlich@dairyvets.com, bcmiller@biostats.uwo.ca, penamanu@paho.org, chotiwan@who.net, fmedpct@md2.md.chula.ac.th, kclun@nus.edu.sg, ZHUKAK75@ccvax.mmc.edu, nfchu@hsph.harvard.edu, chklein@manguinhos.ensp.fiocruz.br, DANP@CIKC.ORG, jat.sandhu@bristol.ac.uk, Vera.Todorovic@bhcs-tr.trent.nhs.uk, johnf@netaxs.com, fgamboa@hotmail.com, rgempp@werken.ufro.cl, MODAOJUN@epid.lan.mcgill.ca, hegd@servidor.unam.mx, l.gostelow@scfuk.org.uk, jmc@med.pitt.edu, ananda@sunnet.com.br, flogisto@usa.net, N.C.Unwin@newcastle.ac.uk, s.loeffler@vet.uu.nl, jmatute@pronet.net.gt, cdckms@sph.emory.edu, lbautista@multinet.com.co, jchaui@ssdnet.com.ar, pab555@comadrid.es, yv.bonnier@ccisd.org, JML@dadlnet.dk, IOKOSUN@wpo.it.luc.edu, JUNG100W@cdc.gov, kevin_sullivan@oz.ped.emory.edu, marcelo@inf.ufsc.br, lbautista@multinet.com.co, maupome@unixg.ubc.ca, SHIYF@PUBLIC2.ZZ.HA.CN, Lengeler@ubaclu.unibas.ch, Steve Bennet , Steve Collins , Sue Chowdhury , Sue Ritter , Suraiya Ismail , Susan Foster , Thomas Crook , Tim Healing , Tim Healing , Welmoet Tuynman MIME-Version: 1.0 Nineteenth European Course in Tropical Epidemiology -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 4th to 15th September 2000 The Nineteenth European Course in Tropical Epidemiology will be hosted by : Centre for Tropical Diseases Hospital 'S.Cuore' Negrar - Verona - Italy In collaboration with : Mario Negri Institute for Pharmacological Research Course co-ordinator : Dr. Zeno Bisoffi bisoffi@linus.univr.it For information about the course, please contact : Dr. Gloria Castellani castelglo@iol.it Telephone : (ITALY) 045-6013324 Fascimile : (ITALY) 045-7500480 ========================================================================= Date: Fri, 17 Dec 1999 08:34:53 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Thomas Slack Subject: Re: Epi Info 2000 Nearing Completion Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Andrew, I'm glad that work is progressing well. As users we don't know how hard things are to do. Here are a couple of = "bells and whistles" I'd like on Santa's list: We like to compose the survey and put it in the background. Is it = possible to print the background with the response boxes? The other problem is the creation of Access databases. They are confined = to 255 variables. Could Eppi someday be able to handle really large surveys? For production, we are using MS Access with frames and having to link = forms and databases together, not much fun and will probably be difficult to maintain. We appreciate all of your efforts! Happy Holidays!, Tom Georgia Prevention Institute Medical College of Georgia ========================================================================= Date: Tue, 21 Dec 1999 20:52:57 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Stephen S Rinsler Subject: source for anthropometric data?? I am seeking a source for the length/height and weight data used to construct growth charts. While the growth charts are widely available and referenced, I have not found a source from which I can obtain the datasets. Appreciate any assistance in finding a source from which I could obtain this data. Steve -- ----------------------------------------------------------- stever1@mindspring.com Stephen S Rinsler, MD Chester, NJ 07930 ----------------------------------------------------------- From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9912B" ========================================================================= Date: Wed, 8 Dec 1999 10:51:36 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Cascade of include commands Comments: To: golliot@ext.jussieu.fr In-Reply-To: <384D1FBC.9DA99A30@idf.ext.jussieu.fr> MIME-Version: 1.0 Franck, You wrote: >I am trying to include sub menus using COMMENT LEGAL in a .CHK file. >It's easy to use an INCLUDE command to retrieve a text file. I would >like, however, to set up a cascade of include commands, so that each >item listed in the text file may call up another sub menu in order to >describe that item in greater detail. > >For example : > >First text file > > 1 INJECTION > 2 BLOOD SAMPLING > 3 SUTURE > >Second text file, under INJECTION > > 11 UNDEFINED > 12 SUBCUTANEOUS > 13 IM > 14 IV > >And so on for each of the three items. I am not sure that you can do it with INCLUDE statements. Here is a sort of solution: V1 COMMENT LEGAL 1 INJECTION 2 "BLOOD SAMPLING" 3 SUTURE END RESULT = . IF V1 = 1 THEN HELP " 1 Undefined, 2 Subcutaneous, 3 IM, 4 IV " 20 11 KEYS="1234" IF RESULT = 1 THEN LET V2 = 11 GOTO V3 ELSE IF RESULT = 2 THEN LET V2 = 12 GOTO V3 ELSE IF RESULT = 3 THEN LET V2 = 13 GOTO V3 ELSE IF RESULT = 4 THEN LET V2 = 14 GOTO V3 ENDIF ENDIF ENDIF ENDIF ENDIF END -- Mark Myatt ========================================================================= Date: Wed, 8 Dec 1999 11:47:02 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: PEPI for Windows test version - update Comments: To: Andy Dean , damien@jolley.com.au, agd1@cdc.gov, alc@servidor.unam.mx, alkral@itsa.ucsf.edu, andrew.forbes@med.monash.edu.au, antunesc@mono.icb.ufmg.br, bengt.moller@mbox2.swipnet.se, bernt.lindtjorn@cih.uib.no, bmanyame@hqfaus01.unicef.org, bpazva@harare.iafrica.com, bxe2@cdc.gov, castellano.j@mcd.gen.de.us, cdckms@sph.emory.edu, chklein@manguinhos.ensp.fiocruz.br, ck@dynamite.com.au, coflunkc@leonis.nus.sg, consult@tstt.net.tt, coulombi@b3e.jussieu.fr, crmcc@gate.net, d.u.pfeiffer@massey.ac.nz, dnordlund@aol.com, eramalle@goriz.sendanet.es, esterman.adrian@health.sa.gov.au, evan.sergeant@smtpgwy.agric.nsw.gov.au, fmedpct@md2.md.chula.ac.th, fwolfe@msus1.msus.edu, g.hartel@mailbox.uq.edu.au, garst@uvapsy.psy.uva.nl, gomes@lelo.uem.mz, gpatrone@opal.tufts.edu, hans.stenlund@stat.umu.se, heberto@meakins.lan.mcgill.ca, jag.atrie@health.wa.gov.au, james_wood@compuserve.com, jaf@lamar.colostate.edu, jmatute@pronet.net.gt, jucar@cica.es, ljorm@doh.health.nsw.gov.au, lucas@dgsp.scstf.rcanaria.es, mamartinez@mail2.cti.unav.es, martinez_j@a1.rcdp.gov, mccleary@mrrc.bio.uci.edu, medicur1@edu.uch.gr, mikael.aberg@primnet.se, mikal.ustad@ism.uit.no, mulderym@fs7003.pg.tno.nl, pani@ymed.ks.se, per.blanck@mailbox.swipnet.se, pgnetto@ax.apc.org, pierreclaquin@compuserve.com, pmb@mhri.edu.au, promed@riosoft.softex.br, r.fisher@unsw.edu.au, ratti@usa.net, rbk8@cdc.gov, rmccart@epin.ab.umd.edu, rvs3@wonder.em.cdc.gov, sas@ipe.ufg.br, sonia@stat.psu.edu, statcon@ix.netcom.com, stefan.ma@commed.hku.hk, pturri@mail.state.tn.us, gilles@epiconcept.fr, normar01@mcgc16.med.nyu.edu, mcmillan@cc.ucsf.edu, jamie_hockin@inet.hwc.ca, mark_veitch.mdu@muwaye.unimelb.edu.au, jed5@cdc.gov, eramalle@mail.sendanet.es, Koomen.Em@net.HCC.nl, s.ritter@iop.bpmf.ac.uk, Rainer.Muche@medizin.uni-ulm.de, S.S.MASTANA@lboro.AC.UK, TCHUR@doh.health.nsw.gov.au, DDedman@phls.co.uk, jsantos@uec.inta.uchile.cl, Bob@exo.com, BHolden536@aol.com, kannika@cmu.chiangmai.ac.th, waa101@uriacc.uri.edu, ACTUARY@asko.donetsk.ua, EBRENNER@compuserve.com, jzg@cs.bham.ac.uk, FPetschke@t-online.de, wilsonsx@novell2.bham.ac.uk, jmc@med.pitt.edu, EpiMon@aol.com, gxs03@health.state.ny.us, busson@neptune.chu-stlouis.fr, steve.dunn@agric.nsw.gov.au, nbirkett@zeus.med.uottawa.ca, joe@ty-coch.demon.co.uk, JML@dadlnet.dk, damien@jolley.com.au, jason.muir@iname.com, Epidemiology List , Joe Abramson , Neal Alexander , rjfreund@NewNetra.ensp.fr, sph1804@utsph.sph.uth.tmc.edu, jehrlich@dairyvets.com, bcmiller@biostats.uwo.ca, penamanu@paho.org, chotiwan@who.net, fmedpct@md2.md.chula.ac.th, kclun@nus.edu.sg, ZHUKAK75@ccvax.mmc.edu, nfchu@hsph.harvard.edu, chklein@manguinhos.ensp.fiocruz.br, DANP@CIKC.ORG, jat.sandhu@bristol.ac.uk, Vera.Todorovic@bhcs-tr.trent.nhs.uk, johnf@netaxs.com, fgamboa@hotmail.com, rgempp@werken.ufro.cl, MODAOJUN@epid.lan.mcgill.ca, hegd@servidor.unam.mx, l.gostelow@scfuk.org.uk, jmc@med.pitt.edu, ananda@sunnet.com.br, flogisto@usa.net, N.C.Unwin@newcastle.ac.uk, s.loeffler@vet.uu.nl, jmatute@pronet.net.gt, cdckms@sph.emory.edu, lbautista@multinet.com.co, jchaui@ssdnet.com.ar, pab555@comadrid.es, yv.bonnier@ccisd.org, JML@dadlnet.dk, IOKOSUN@wpo.it.luc.edu, JUNG100W@cdc.gov, kevin_sullivan@oz.ped.emory.edu, marcelo@inf.ufsc.br, lbautista@multinet.com.co, maupome@unixg.ubc.ca, SHIYF@PUBLIC2.ZZ.HA.CN, Lengeler@ubaclu.unibas.ch, bart@hgea.org, jha@vms.huji.ac.il, jason.muir@iname.com, Jane.McCall@bhs.org, Giovanni.Leonardi@lshtm.ac.uk MIME-Version: 1.0 Dear All, Work is moving forward on the porting of the illustrious PEPI suite of epidemiological / statistical program to the Microsoft Windows environment. The latest TEST version of these programs are available from: http://www.myatt.demon.co.uk At present there are two programs in the Windows suite. These combine the function of several of the original MS-DOS PEPI programs: WHATIS.EXE - A calculator (an expression evaluator with 24 memory registers for constants, interim results, and formulae) and computes probability values (and their inverse), confidence intervals, and time spans. COMPARE2.EXE - Provides procedures for use in comparisons of two independent groups or samples. It may be used for analyses of cross-sectional studies, cohort studies, case-control studies and trials, and for meta-analyses. The program handles stratified data, and can thus be used for meta-analyses (by entering each study as a separate stratum). As aids in meta- analysis, it provides the fail-safe N and a sensitivity analysis showing the effect (on the combined p-value) of excluding each study in turn. This trial version permits comparisons of: - Proportions or odds (2 x 2 tables) - Risks or other measures with number-of-individuals denominators - Exposed and unexposed (case-control study) - Occurrence of an event: rates with person-time denominators - Three or more categories, nominal or ordinal (2 x k table) - Three or more exposure levels (case-control study) COMPARE2.EXE provides many of the functions served by the MS-DOS format PEPI programs ATFRAC, CASECONT, CHISQ, COMBINE, EXACT2XK, MANNWHIT, MANTELX, RATES1 and RATES2. PEPI for Windows is a 16-bit Microsoft Windows application and will run under Microsoft Windows 3.1x, '95, '98, and NT 3.51 or later. PEPI for Windows is currently available only as a test version. Please report any problems you experience or any suggestions you may have to improve the package. Best wishes -- Mark Myatt ========================================================================= Date: Wed, 8 Dec 1999 16:15:58 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: Cascade of include commands Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=Wq8gtWTPzexo3JLAvWG1ucjSZ7xxYJrJcjRfhGHws3sOwYCvg1X3WCLb" --0__=Wq8gtWTPzexo3JLAvWG1ucjSZ7xxYJrJcjRfhGHws3sOwYCvg1X3WCLb Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable To go beyond Mark's example, however, is well beyond the capability of = Epi Info. Over the past 3 years, we have been building integrated systems for pub= lic health surveillance (both lab and case management functions). The objec= tive is to connect public health laboratory and case management systems at the = local level, in order to integrated the surveillance information. We ran into the cascading heirarchies problem two years ago with the la= b system. Our initial solution was to hard-code heirarchies (in Visual Basic and MS-Access) along the lines of what Mark shows you can do in Epi Info. A= s the heirarchies got more complex, we were no longer able to deal with them = that way and now have a very elegant method, but one that works only for those w= ho build systems on established platforms (Access, Oracle, and some others). To = the user, the heirarchies are dynamic and can actually be structured so that it l= ooks like: A,B,C --> 1,2,3 --> a,b,c --> i,ii,iii or when necessary: A,B,C --> i,ii,iii --> 1,2,3 i.e. a lab may classify some bacteria by genus, species, subtype, serot= ype, then biotype and others by genus, species, then biotype, serotype, etc etc. The software tool for this, the Reference Table Management System, is n= ot available, but we or our developer would be glad to provide more inform= ation to anyone building modern systems. A similar Hierarchical structure is bei= ng built into SNOMED-RT, the next version of SNOMED to come from the College of = American Pathologists. ---------------------- Jamie Hockin MD,MSc -------------------------- Director, Field Epidemiology _ Directeur, Programme de formation Training Program _|\ en =E9pid=E9miologie d'intervention= LCDC, Health Canada :| \ LLCM, Sant=E9 Canada PL 0602B Tunney's Pasture | LP 0602B Pr=E9 Tunney Ottawa ON K1A 0L2, Canada Ottawa (Ontario) K1A 0L2, Canada Jamie_Hockin@hc-sc.gc.ca 613 957-1764 FAX: 613 941-6028 http://www.hc-sc.gc.ca/hpb/lcdc/survlnce/fetp Mark Myatt on 99/12/08 05:51:36 AM Please respond to Epi Info Discussion Group = To: EPI-INFO@LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: Re: [EPI-INFO] Cascade of include commands = --0__=Wq8gtWTPzexo3JLAvWG1ucjSZ7xxYJrJcjRfhGHws3sOwYCvg1X3WCLb Content-type: text/plain; charset=us-ascii Content-Disposition: inline Franck, You wrote: >I am trying to include sub menus using COMMENT LEGAL in a .CHK file. >It's easy to use an INCLUDE command to retrieve a text file. I would >like, however, to set up a cascade of include commands, so that each >item listed in the text file may call up another sub menu in order to >describe that item in greater detail. > >For example : > >First text file > > 1 INJECTION > 2 BLOOD SAMPLING > 3 SUTURE > >Second text file, under INJECTION > > 11 UNDEFINED > 12 SUBCUTANEOUS > 13 IM > 14 IV > >And so on for each of the three items. I am not sure that you can do it with INCLUDE statements. Here is a sort of solution: V1 COMMENT LEGAL 1 INJECTION 2 "BLOOD SAMPLING" 3 SUTURE END RESULT = . IF V1 = 1 THEN HELP " 1 Undefined, 2 Subcutaneous, 3 IM, 4 IV " 20 11 KEYS="1234" IF RESULT = 1 THEN LET V2 = 11 GOTO V3 ELSE IF RESULT = 2 THEN LET V2 = 12 GOTO V3 ELSE IF RESULT = 3 THEN LET V2 = 13 GOTO V3 ELSE IF RESULT = 4 THEN LET V2 = 14 GOTO V3 ENDIF ENDIF ENDIF ENDIF ENDIF END -- Mark Myatt --0__=Wq8gtWTPzexo3JLAvWG1ucjSZ7xxYJrJcjRfhGHws3sOwYCvg1X3WCLb-- ========================================================================= Date: Thu, 9 Dec 1999 07:22:03 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sven Gudmund Hinderaker Subject: Epi6 and WinNT In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Hello. We recently had a course in use of EpiInfo. Regrettably, Epi6 could not run on the students' lab PCs with WinNT. We had to start from DOS, which was very inconvenient and confusing for the students. Even more so when students start working with their own data soon. We have Epi6 running OK with Win95 and from DOS. Has anybody had the same problem and solved it? Regards Sven Gudmund Hinderaker Centre for International Health; Armauer Hanssen's Building; University of Bergen; N-5021 Bergen; NORWAY email : sven.hinderaker@cih.uib.no Phone CIH: 5597 4985 Phone Home: 5520 2979 ========================================================================= Date: Thu, 9 Dec 1999 08:31:38 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Cascade of include commands In-Reply-To: <85256841.007492D9.00@smta00.hc-sc.gc.ca> MIME-Version: 1.0 Jamie Hockin writes: > >To go beyond Mark's example, however, is well beyond the capability of Epi Info. >Over the past 3 years, we have been building integrated systems for public >health surveillance (both lab and case management functions). The objective is >to connect public health laboratory and case management systems at the local >level, in order to integrated the surveillance information. > Perhaps it is too late to lobby CDC for better support of hierarchical coding systems (which are common in our work) to EpiInfo 2000. Mark -- Mark Myatt ========================================================================= Date: Thu, 9 Dec 1999 10:26:40 -0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Phil Subject: Re: Epi6 and WinNT MIME-Version: 1.0 Content-Type: text/plain We're running Epi6 under NT. Whats the problem? Phil > -----Original Message----- > From: Sven Gudmund Hinderaker [SMTP:sven.hinderaker@CIH.UIB.NO] > Sent: Thursday, December 09, 1999 6:22 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: [EPI-INFO] Epi6 and WinNT > > Hello. > We recently had a course in use of EpiInfo. Regrettably, Epi6 could not > run > on the students' lab PCs with WinNT. We had to start from DOS, which was > very inconvenient and confusing for the students. Even more so when > students start working with their own data soon. > We have Epi6 running OK with Win95 and from DOS. > > Has anybody had the same problem and solved it? > Regards > Sven Gudmund Hinderaker > Centre for International Health; Armauer Hanssen's Building; > University of Bergen; N-5021 Bergen; NORWAY > email : sven.hinderaker@cih.uib.no > Phone CIH: 5597 4985 > Phone Home: 5520 2979 ========================================================================= Date: Thu, 9 Dec 1999 20:54:58 -0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dr. Pedro Garbes-Netto" Subject: Re: Epi6 and WinNT Comments: cc: sven.hinderaker@cih.uib.no In-Reply-To: <4.2.0.58.19991209071358.00a047a0@pop3.uib.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Dear Sven, Although I run EPI6.04c in a DOS session of Win98 at home, in the office EPI6.04c runs in a same DOS session in NT4.0, without any problems. What was your problem ? Regards, Pedro At 07:22 09/12/99 +0100, you wrote: >Hello. >We recently had a course in use of EpiInfo. Regrettably, Epi6 could not run >on the students' lab PCs with WinNT. We had to start from DOS, which was >very inconvenient and confusing for the students. Even more so when >students start working with their own data soon. >We have Epi6 running OK with Win95 and from DOS. > >Has anybody had the same problem and solved it? >Regards >Sven Gudmund Hinderaker >Centre for International Health; Armauer Hanssen's Building; >University of Bergen; N-5021 Bergen; NORWAY >email : sven.hinderaker@cih.uib.no >Phone CIH: 5597 4985 >Phone Home: 5520 2979 > **************************************************************************** Prof. Pedro G. Garbes-Netto, M.D., M.Sc. Internal Medicine Dpt. School of Medicine Phone: 55 21 567-5990 Federal University Fluminense (FUF), Infectious Disease Service Fax: 55 21 567-5990 Hospital Servidores do Estado (HSE) Ministry of Health, Rio de Janeiro, Brazil. Local time: GMT-3h Medical Manager - GlaxoWellcome - Brazil. http://www.ibase.org.br/~diphserj/ E-Mail:pgnetto@ax.apc.org ***************************************************************************** ========================================================================= Date: Fri, 10 Dec 1999 08:47:38 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Fagan, Robert F." Subject: Re: Epi6 and WinNT MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" The most common problem I have seen with an NT setup is a failure to set the path within your DOS session. Click "my computer" click "control pannel" click "system" click "environment" and make sure your path (in the window list) is set correctly. If this is not the solution I would be very interested in hearing more about the problem. rff -----Original Message----- From: Dr. Pedro Garbes-Netto [mailto:pgnetto@AX.APC.ORG] Sent: Thursday, December 09, 1999 5:55 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] Epi6 and WinNT Dear Sven, Although I run EPI6.04c in a DOS session of Win98 at home, in the office EPI6.04c runs in a same DOS session in NT4.0, without any problems. What was your problem ? Regards, Pedro At 07:22 09/12/99 +0100, you wrote: >Hello. >We recently had a course in use of EpiInfo. Regrettably, Epi6 could not run >on the students' lab PCs with WinNT. We had to start from DOS, which was >very inconvenient and confusing for the students. Even more so when >students start working with their own data soon. >We have Epi6 running OK with Win95 and from DOS. > >Has anybody had the same problem and solved it? >Regards >Sven Gudmund Hinderaker >Centre for International Health; Armauer Hanssen's Building; >University of Bergen; N-5021 Bergen; NORWAY >email : sven.hinderaker@cih.uib.no >Phone CIH: 5597 4985 >Phone Home: 5520 2979 > **************************************************************************** Prof. Pedro G. Garbes-Netto, M.D., M.Sc. Internal Medicine Dpt. School of Medicine Phone: 55 21 567-5990 Federal University Fluminense (FUF), Infectious Disease Service Fax: 55 21 567-5990 Hospital Servidores do Estado (HSE) Ministry of Health, Rio de Janeiro, Brazil. Local time: GMT-3h Medical Manager - GlaxoWellcome - Brazil. http://www.ibase.org.br/~diphserj/ E-Mail:pgnetto@ax.apc.org **************************************************************************** * ========================================================================= Date: Fri, 10 Dec 1999 15:19:15 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sven Gudmund Hinderaker Subject: Re: Epi6 and WinNT In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 20:54 09.12.99 -0200, you wrote: >Dear Sven, >Although I run EPI6.04c in a DOS session of Win98 at home, in the office >EPI6.04c runs in a same DOS session in NT4.0, without any problems. >What was your problem ? >Regards, >Pedro We installed Epi6.04 on our WinNT PC lab. It can run EpiInfo, but the keyboard is garbled. Almost no characters are the same, "F6" writes "A", "S" wites "<" etc. We use norwegian keyboard on the PCs, no problem in other applications. Other machines with Win95 and norwegian keyboards have no problem here. We by-passed the problem temporarily by running EpiInfo from local network after booting with DOS. We look for a permanent solution. The network administrator could not solve this problem. Keyboard settings?? Sven Gudmund Hinderaker Centre for International Health; Armauer Hanssen's Building; University of Bergen; N-5021 Bergen; NORWAY email : sven.hinderaker@cih.uib.no Phone CIH: 5597 4985 Phone Home: 5520 2979 ========================================================================= Date: Tue, 14 Dec 1999 11:09:35 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: SampleLQ - Sampel size calculator for LQAS surveys Comments: To: Joe Abramson , Linda Morison , Andy Dean , Annie Lloyd , Christian Lengeler , agd1@cdc.gov, alc@servidor.unam.mx, alkral@itsa.ucsf.edu, andrew.forbes@med.monash.edu.au, antunesc@mono.icb.ufmg.br, bengt.moller@mbox2.swipnet.se, bernt.lindtjorn@cih.uib.no, bmanyame@hqfaus01.unicef.org, bpazva@harare.iafrica.com, bxe2@cdc.gov, castellano.j@mcd.gen.de.us, cdckms@sph.emory.edu, chklein@manguinhos.ensp.fiocruz.br, ck@dynamite.com.au, coflunkc@leonis.nus.sg, consult@tstt.net.tt, coulombi@b3e.jussieu.fr, crmcc@gate.net, d.u.pfeiffer@massey.ac.nz, dnordlund@aol.com, eramalle@goriz.sendanet.es, esterman.adrian@health.sa.gov.au, evan.sergeant@smtpgwy.agric.nsw.gov.au, fmedpct@md2.md.chula.ac.th, fwolfe@msus1.msus.edu, g.hartel@mailbox.uq.edu.au, garst@uvapsy.psy.uva.nl, gomes@lelo.uem.mz, gpatrone@opal.tufts.edu, hans.stenlund@stat.umu.se, heberto@meakins.lan.mcgill.ca, jag.atrie@health.wa.gov.au, james_wood@compuserve.com, jaf@lamar.colostate.edu, jmatute@pronet.net.gt, jucar@cica.es, ljorm@doh.health.nsw.gov.au, lucas@dgsp.scstf.rcanaria.es, mamartinez@mail2.cti.unav.es, martinez_j@a1.rcdp.gov, mccleary@mrrc.bio.uci.edu, medicur1@edu.uch.gr, mikael.aberg@primnet.se, mikal.ustad@ism.uit.no, mulderym@fs7003.pg.tno.nl, pani@ymed.ks.se, per.blanck@mailbox.swipnet.se, pgnetto@ax.apc.org, pierreclaquin@compuserve.com, pmb@mhri.edu.au, promed@riosoft.softex.br, r.fisher@unsw.edu.au, ratti@usa.net, rbk8@cdc.gov, rmccart@epin.ab.umd.edu, rvs3@wonder.em.cdc.gov, sas@ipe.ufg.br, sonia@stat.psu.edu, statcon@ix.netcom.com, stefan.ma@commed.hku.hk, pturri@mail.state.tn.us, gilles@epiconcept.fr, normar01@mcgc16.med.nyu.edu, mcmillan@cc.ucsf.edu, jamie_hockin@inet.hwc.ca, mark_veitch.mdu@muwaye.unimelb.edu.au, jed5@cdc.gov, eramalle@mail.sendanet.es, Koomen.Em@net.HCC.nl, s.ritter@iop.bpmf.ac.uk, Rainer.Muche@medizin.uni-ulm.de, S.S.MASTANA@lboro.AC.UK, TCHUR@doh.health.nsw.gov.au, DDedman@phls.co.uk, jsantos@uec.inta.uchile.cl, Bob@exo.com, BHolden536@aol.com, kannika@cmu.chiangmai.ac.th, waa101@uriacc.uri.edu, ACTUARY@asko.donetsk.ua, EBRENNER@compuserve.com, jzg@cs.bham.ac.uk, FPetschke@t-online.de, wilsonsx@novell2.bham.ac.uk, jmc@med.pitt.edu, EpiMon@aol.com, gxs03@health.state.ny.us, busson@neptune.chu-stlouis.fr, steve.dunn@agric.nsw.gov.au, nbirkett@zeus.med.uottawa.ca, joe@ty-coch.demon.co.uk, JML@dadlnet.dk, damien@jolley.com.au, jason.muir@iname.com, Epidemiology List , EpiInfo List ADMINISTRATOR , Fran Horsfall , bart@hgea.org, jha@vms.huji.ac.il, jason.muir@iname.com, Jane.McCall@bhs.org, Giovanni.Leonardi@lshtm.ac.uk, rjfreund@NewNetra.ensp.fr, sph1804@utsph.sph.uth.tmc.edu, jehrlich@dairyvets.com, bcmiller@biostats.uwo.ca, penamanu@paho.org, chotiwan@who.net, fmedpct@md2.md.chula.ac.th, kclun@nus.edu.sg, ZHUKAK75@ccvax.mmc.edu, nfchu@hsph.harvard.edu, chklein@manguinhos.ensp.fiocruz.br, DANP@CIKC.ORG, jat.sandhu@bristol.ac.uk, Vera.Todorovic@bhcs-tr.trent.nhs.uk, johnf@netaxs.com, fgamboa@hotmail.com, rgempp@werken.ufro.cl, MODAOJUN@epid.lan.mcgill.ca, hegd@servidor.unam.mx, l.gostelow@scfuk.org.uk, jmc@med.pitt.edu, ananda@sunnet.com.br, flogisto@usa.net, N.C.Unwin@newcastle.ac.uk, s.loeffler@vet.uu.nl, jmatute@pronet.net.gt, cdckms@sph.emory.edu, lbautista@multinet.com.co, jchaui@ssdnet.com.ar, pab555@comadrid.es, yv.bonnier@ccisd.org, JML@dadlnet.dk, IOKOSUN@wpo.it.luc.edu, JUNG100W@cdc.gov, kevin_sullivan@oz.ped.emory.edu, marcelo@inf.ufsc.br, lbautista@multinet.com.co, maupome@unixg.ubc.ca, SHIYF@PUBLIC2.ZZ.HA.CN, Lengeler@ubaclu.unibas.ch, melthorn@welch.jhu.edu MIME-Version: 1.0 Sorry to bother you all again after the PEPI for windows message but I have just added a new utility to my website ... SampleLQ is a sample size calculator for community-based LQAS (lot- quality assurance sampling) triage surveys. It implements the algorithms presented in: Valadez JJ, Assessing child survival programs in developing countries: testing lot quality assurance sampling, Harvard University Press, Boston, 1991 SampleLQ is a 16-bit Microsoft Windows application and will run under Microsoft Windows v3.1x, '95, '98, and NT 3.51 or later. The downloaded file will be called LQSetup.exe. This file is a self- extracting installer. Incidentally ... I know that a lot of you have downloaded the new test version of PEPI for Windows and we have not received any feedback. Please let us know if you like it or hate it. Mark -- Mark Myatt ========================================================================= Date: Tue, 14 Dec 1999 14:00:49 +0100 Reply-To: maugat@ext.jussieu.fr Sender: Epi Info Discussion Group From: Sylvie Maugat Organization: C.CLIN Paris-Nord Subject: related files MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------58387563A9A55E364402778C" Content-Transfer-Encoding: 8bit Il s'agit d'un message multivolet au format MIME. --------------58387563A9A55E364402778C Content-Type: multipart/alternative; boundary="------------62259CA72672898A897464EF" --------------62259CA72672898A897464EF Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, I generated an application with EPIGLUE using relationnal data file (patients data and catheters (KT) data). In qpat.chk I used RELATE codpat qkt.rec /chk:qktpat. It's all right. So, in my MNU file, I would like to use somethink like : DoEnter3 BEGIN %p1\reacat99\epi604c\ENTER %p1\reacat99\data\qpat.rec /chk:qpatfin END for enter patient data controlled with a different chk file (qpatfin.chk). In fact, I use already an qpat.chk somewhere else. But it doesn't work. What can I do? Is it posible ? Thanks for your help. -- _________________________________________ Sylvie MAUGAT Epidémiologiste CCLIN Paris-Nord 15-21 rue de l'Ecole de Médecine 75006 PARIS Tel : 01 40 46 42 00 --------------62259CA72672898A897464EF Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,
I generated an application with EPIGLUE using relationnal data file (patients data and catheters (KT) data).
In qpat.chk I used   RELATE codpat qkt.rec /chk:qktpat. It's all right.
So, in my MNU file,  I would like to use somethink like :
DoEnter3
BEGIN
  %p1\reacat99\epi604c\ENTER %p1\reacat99\data\qpat.rec /chk:qpatfin
END
for enter patient data controlled with a different chk file (qpatfin.chk). In fact, I use already an qpat.chk somewhere else.  But it doesn't work.
What can I do? Is it posible ?

Thanks for your help.

--

_________________________________________

Sylvie MAUGAT
Epidémiologiste
CCLIN Paris-Nord
15-21 rue de l'Ecole de Médecine
75006 PARIS
Tel : 01 40 46 42 00
  --------------62259CA72672898A897464EF-- --------------58387563A9A55E364402778C Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Carte pour MAUGAT Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: MAUGAT n: ;MAUGAT email;internet: maugat@idf.ext.jussieu.fr x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard --------------58387563A9A55E364402778C-- From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9912A" ========================================================================= Date: Wed, 1 Dec 1999 12:27:00 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert-Jean FREUND Subject: Re: calendar In-Reply-To: <4.2.1.19991130082954.00a91600@tunku.uady.mx> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_944044020==_" --=====================_944044020==_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable A 08:35 30/11/1999 -0600, vous avez =E9crit : >Dear members in the group: > >When I am entering my patients data in a file using Epiinfo, I need to >check the epidemiologic week that correspond to the disease onset for each >patient. >I would like to know if it is possible to incorporate in a QES or CHK file, >a procedure to call the calendar with epidemilogic weeks (IDCLND) available >in Epiinfo. > >Thank in advance for the help you could provide me > >Respectfully > >Jose A. Farfan > I enclose in this mail 2 small files : notify.rec is a file for training purposes with artificial data week.pgm does exactly what you want : calculate the week number I use this material with my students be careful for beginning and end of the year (week 0 or 1 ; week 53 or 1 ) Hope that helps Rovert --=====================_944044020==_ Content-Type: application/octet-stream; name="Week.pgm"; x-mac-type="5050474D"; x-mac-creator="474B4F4E" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Week.pgm" KiAgICAgICAgICAgICAgICAgICAgICBcXHwvLw0KKiAgICAgICAgICAgICAgICAgICAgICAobyBv KQ0KKnwtLS0tLS0tLS0tLS0tLS0tLW8wMG8tKF8pLW8wMG8tLS0tLS0tLS0tLS0tLS0tLS0tLXwN Cip8ICBSb2JlcnQgSi5GUkVVTkQgIEVwaWRlbWlvbG9naXN0ZSwgUHJvZmVzc2V1ciAgICB8DQoq fCAgRWNvbGUgTmF0aW9uYWxlIGRlIGxhIFNhbnRlIFB1YmxpcXVlICAgICAgICAgICAgfA0KKnwg IEF2IFByb2YgTGVvbiBCZXJuYXJkIDM1MDQzIFJFTk5FUy1DZWRleCBGUkFOQ0UgIHwNCip8ICB0 ZWwgMzMoMCkyIDk5IDAyIDI4IDYyICBmYXggMzMoMCkyIDk5IDAyIDI2IDIzICB8DQoqfCAgcmpm cmV1bmRAZW5zcC5mciAgICAgICAgICAgIGh0dHA6Ly93d3cuZW5zcC5mciAgfA0KKnwtLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLXwNCioNCiogYSBzbWFs bCBwcm9ncmFtIHRvIGNhbGN1bGF0ZSB0aGUgd2VlayBudW1iZXIgdXNpbmcgYSBzdGFydCBkYXRl DQoqIHdoaWNoIGlzIGFsd2F5cyAwMS8wMS95ZWFybm90aWZpY2F0aW9uDQoqIGNhbGN1bGF0aW5n IHdlZWsgbnVtYmVyIHVzaW5nIHRoZSBESVYgb3BlcmF0b3Igc2VlIHRoZSBib29rDQpyZWFkIE5P VElGWS5yZWMNCiogbm90aWZ5LnJlYyBpcyBhIGZpbGUgdXNlZCBmb3IgdHJhaW5pbmcgcHVycG9z ZXMNCmRlZmluZSBTVEFSVCA8bW0vZGQveXl5eT4NCmRlZmluZSB5ZWFyY2ggX19fXw0KeWVhcmNo ID0gZGF0ZSBbNyw0XQ0KU1RBUlQgPSAiMDEvMDEvIiArIHllYXJjaA0KZGVmaW5lIERJRiAjIyMN CkRJRiA9IGRhdGUgLSBTVEFSVA0KZGVmaW5lIFdFRUsgIyMNCldFRUsgPSAoRElGIGRpdiA3KSAr IDENCmxpc3QgZGF5IG1vbnRoIHllYXIgZGF0ZSBzdGFydCBkaWYgd2Vlaw0KGg== --=====================_944044020==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="Notify.rec" 8 0 #IDN 1 1 14 12 1 105 12 15 IDN #MONTH 1 2 14 12 2 0 2 15 MONTH #DAY 1 3 14 12 3 0 2 15 DAY #YEAR 1 4 14 12 4 0 2 15 YEAR #WEEKNOTIF 1 5 14 12 5 0 2 15 WEEKNOTIF _REGION 1 6 14 12 6 1 3 15 REGION _DATE 1 7 14 12 7 11 10 15 DATE #CASES 1 8 14 12 8 0 4 15 CASES 1.00000 4 4951484 04/04/1995 330! 2.0000012 7984931 07/12/1998 454! 3.00000 630992623 30/06/1999 310! 4.00000 4 1941387 01/04/1994 501! 5.00000 810993224 10/08/1999 724! 6.000001220985193 20/12/1998 770! 7.00000 6 4992317 04/06/1999 93! 8.00000 3 197 951 01/03/1997 973! 9.000001221965186 21/12/1996 765! 10.00000 22295 834 22/02/1995 968! 11.00000 4 3971474 03/04/1997 403! 12.0000012 2954863 02/12/1995 374! 13.00000 3 8951036 08/03/1995 431! 14.00000 11393 229 13/01/1993 548! 15.00000 513951984 13/05/1995 530! 16.00000 22293 876 22/02/1993 260! 17.00000 530922266 30/05/1992 187! 18.00000 1 992 255 09/01/1992 680! 19.00000 325961322 25/03/1996 972! 20.00000 9 1933533 01/09/1993 339! 21.00000 923993815 23/09/1999 396! 22.00000 5 8911985 08/05/1991 198! 23.00000 926933995 26/09/1993 534! 24.000001216935055 16/12/1993 587! 25.00000 314951183 14/03/1995 464! 26.00000 11494 263 14/01/1994 452! 27.00000 618912536 18/06/1991 597! 28.00000 410961575 10/04/1996 971! 29.00000 9 4943661 04/09/1994 625! 30.0000010 6974051 06/10/1997 885! 31.000001111944561 11/11/1994 919! 32.00000 4 7931465 07/04/1993 416! 33.00000 827993537 27/08/1999 587! 34.00000 428941756 28/04/1994 828! 35.00000 2 595 674 05/02/1995 814! 36.00000 21791 703 17/02/1991 759! 37.00000 22791 919 27/02/1991 975! 38.00000 1 693 147 06/01/1993 509! 39.00000 914963752 14/09/1996 385! 40.000001023994388 23/10/1999 200! 41.000001230955202 30/12/1995 16! 42.000001211965027 11/12/1996 910! 43.00000 327921356 27/03/1992 131! 44.00000 416971643 16/04/1997 805! 45.00000 22399 870 23/02/1999 140! 46.00000 5 7921951 07/05/1992 955! 47.000001030974479 30/10/1997 216! 48.00000 531912255 31/05/1991 187! 49.00000 7 9922829 09/07/1992 534! 50.00000 730933106 30/07/1993 873! 51.00000 4 4931446 04/04/1993 725! 52.00000 413951557 13/04/1995 296! 53.00000 516992090 16/05/1999 41! 54.00000 5 1911808 01/05/1991 940! 55.00000 316921191 16/03/1992 240! 56.00000 12597 409 25/01/1997 252! 57.0000012 2914838 02/12/1991 407! 58.00000 2 493 558 04/02/1993 716! 59.00000 717992952 17/07/1999 952! 60.00000113197 165 01/01/1900 852! 61.00000 527952186 27/05/1995 771! 62.000001213915023 13/12/1991 917! 63.00000 3 198 955 01/03/1998 94! 64.00000 21195 645 11/02/1995 148! 65.000001117984616 17/11/1998 884! 66.00000 620912551 20/06/1991 750! 67.00000 812993240 12/08/1999 325! 68.000001229915248 29/12/1991 731! 69.000001219935184 19/12/1993 948! 70.00000 415931548 15/04/1993 436! 71.00000 814933348 14/08/1993 534! 72.0000010 4964070 04/10/1996 205! 73.00000 525972130 25/05/1997 705! 74.0000011 4954406 04/11/1995 78! 75.0000012 4914973 04/12/1991 271! 76.000001129914857 29/11/1991 445! 77.000001018954270 18/10/1995 153! 78.00000 6 9982304 09/06/1998 59! 79.00000 12698 450 26/01/1998 125! 80.00000 422931657 22/04/1993 241! 81.0000012 2914835 02/12/1991 483! 82.00000 1 897 223 08/01/1997 954! 83.00000 7 4972707 04/07/1997 248! 84.00000 726963079 26/07/1996 538! 85.00000 2 398 548 03/02/1998 28! 86.00000 12993 528 29/01/1993 706! 87.00000 11493 217 14/01/1993 975! 88.00000 729993009 29/07/1999 379! 89.00000 312911126 12/03/1991 183! 90.00000 5 9951924 09/05/1995 171! 91.00000 330931306 30/03/1993 68! 92.00000 21092 659 10/02/1992 400! 93.00000 618932573 18/06/1993 818! 94.00000 9 5933611 05/09/1993 219! 95.000001016934268 16/10/1993 385! 96.000001226995243 26/12/1999 218! 97.00000 310941066 10/03/1994 997! 98.00000 530952252 30/05/1995 749! 99.000001029974458 29/10/1997 971! 100.00000 513922011 13/05/1992 242! 101.00000 13196 594 31/01/1996 428! 102.00000 526992116 26/05/1999 510! 103.000001211995088 11/12/1999 77! 104.00000 8 7933251 07/08/1993 780! 105.00000 726983068 26/07/1998 310! 106.000001221985130 21/12/1998 665! 107.00000 3 193 915 01/03/1993 305! 108.00000 523972155 23/05/1997 701! 109.000001027994370 27/10/1999 711! 110.00000 524952158 24/05/1995 245! 111.00000 919993878 19/09/1999 739! 112.00000 917933839 17/09/1993 934! 113.000001115994619 15/11/1999 260! 114.0000011 4964541 04/11/1996 908! 115.00000 21896 713 18/02/1996 94! 116.00000 7 7922731 07/07/1992 866! 117.00000 920983877 20/09/1998 238! 118.00000 9 4913685 04/09/1991 255! 119.00000 821923436 21/08/1992 204! 120.00000 327951392 27/03/1995 542! 121.00000 818943394 18/08/1994 337! 122.00000 3 8991052 08/03/1999 80! 123.00000 629982639 29/06/1998 609! 124.00000 21398 793 13/02/1998 617! 125.000001020954221 20/10/1995 253! 126.000001214985019 14/12/1998 735! 127.00000 618922574 18/06/1992 815! 128.00000 915953729 15/09/1995 4! 129.0000010 7934069 07/10/1993 972! 130.00000 831913572 31/08/1991 640! 131.0000011 9934518 09/11/1993 495! 132.00000 8 2953134 02/08/1995 834! 133.00000 720992962 20/07/1999 13! 134.00000 12096 361 20/01/1996 60! 135.00000 7 4992769 04/07/1999 710! 136.00000 813983331 13/08/1998 979! 137.00000 5 6931895 06/05/1993 818! 138.00000 714932812 14/07/1993 238! 139.00000 22799 928 27/02/1999 167! 140.00000 11399 218 13/01/1999 468! 141.00000 4 7991437 07/04/1999 245! 142.000001119974716 19/11/1997 569! 143.000001215985055 15/12/19981000! 144.00000 823983470 23/08/1998 418! 145.000001230935251 30/12/1993 968! 146.00000 4 8921511 08/04/1992 7! 147.00000 6 3972235 03/06/1997 823! 148.00000 5 1991828 01/05/1999 873! 149.000001129964895 29/11/1996 829! 150.00000 11994 342 19/01/1994 572! 151.0000011 3964485 03/11/1996 159! 152.00000 11195 277 11/01/1995 263! 153.00000 21599 782 15/02/1999 60! 154.00000 616932437 16/06/1993 619! 155.00000 727983083 27/07/1998 942! 156.00000 612992496 12/06/1999 62! 157.00000 2 292 586 02/02/1992 612! 158.0000011 5974503 05/11/1997 329! 159.00000 5 2981872 02/05/1998 481! 160.000001130974819 30/11/1997 129! 161.00000 521942170 21/05/1994 595! 162.00000 12799 430 27/01/1999 920! 163.00000 7 5962763 05/07/1996 115! 164.00000 328991389 28/03/1999 381! 165.00000 21196 678 11/02/1996 729! 166.00000 9 1943563 01/09/1994 102! 167.000001127914806 27/11/1991 289! 168.00000 416911673 16/04/1991 411! 169.00000 719982930 19/07/1998 786! 170.00000 925963932 25/09/1996 886! 171.0000012 5964986 05/12/1996 497! 172.000001222925147 22/12/1992 204! 173.00000 3 9971027 09/03/1997 771! 174.00000 13192 571 31/01/1992 614! 175.00000 21899 785 18/02/1999 245! 176.00000 326921304 26/03/1992 950! 177.00000 828923584 28/08/1992 840! 178.00000 2 798 679 07/02/1998 274! 179.000001027974309 27/10/1997 147! 180.00000 21693 782 16/02/1993 405! 181.00000 22296 889 22/02/1996 388! 182.00000 6 4992380 04/06/1999 152! 183.00000 5 3951877 03/05/1995 160! 184.00000113199 107 01/01/1900 325! 185.00000 523942125 23/05/1994 976! 186.000001229935283 29/12/1993 558! 187.00000 412911580 12/04/1991 748! 188.000001028974339 28/10/1997 854! 189.000001130984892 30/11/1998 159! 190.00000 427951718 27/04/1995 535! 191.0000012 5964987 05/12/1996 727! 192.00000 328951381 28/03/1995 856! 193.00000 11296 210 12/01/1996 849! 194.00000 22294 803 22/02/1994 229! 195.00000 622942523 22/06/1994 661! 196.00000 830983531 30/08/1998 473! 197.00000 7 6932795 06/07/1993 488! 198.00000 3 7991081 07/03/1999 163! 199.00000 9 5963642 05/09/1996 974! 200.00000 1 193 139 01/01/1993 484! 201.000001012984106 12/10/1998 136! 202.00000 926973901 26/09/1997 145! 203.0000010 7924136 07/10/1992 785! 204.00000 9 7983665 07/09/1998 852! 205.00000 819983327 19/08/1998 890! 206.000001211965008 11/12/1996 101! 207.00000 912983769 12/09/1998 274! 208.00000 316981193 16/03/1998 496! 209.00000 915953770 15/09/1995 451! 210.00000 925953978 25/09/1995 806! 211.00000 816943360 16/08/1994 714! 212.00000 313921176 13/03/1992 568! 213.00000 13095 559 30/01/1995 848! 214.000001227915278 27/12/1991 716! 215.00000 1 997 288 09/01/1997 295! 216.00000 1 694 148 06/01/1994 528! 217.000001214985095 14/12/1998 677! 218.00000 422911690 22/04/1991 966! 219.0000012 1964825 01/12/1996 91! 220.00000 425941730 25/04/1994 531! 221.00000 725943052 25/07/1994 135! 222.00000 6 3982260 03/06/1998 492! 223.00000 12799 422 27/01/1999 505! 224.000001218925183 18/12/1992 555! 225.00000 421961643 21/04/1996 63! 226.00000 22592 827 25/02/1992 30! 227.00000 615912438 15/06/1991 974! 228.0000010 2944051 02/10/1994 496! 229.00000 925963948 25/09/1996 480! 230.00000 7 7972795 07/07/1997 531! 231.000001018984212 18/10/1998 941! 232.00000 1 398 159 03/01/1998 550! 233.00000 718962906 18/07/1996 435! 234.00000 320931296 20/03/1993 534! 235.00000 7 9932821 09/07/1993 366! 236.00000 7 2942790 02/07/1994 916! 237.0000012 1914846 01/12/1991 321! 238.000001219995119 19/12/1999 277! 239.00000 513962084 13/05/1996 743! 240.00000 4 9961503 09/04/1996 129! 241.00000 321981273 21/03/1998 505! 242.00000 930973974 30/09/1997 59! 243.00000 810973265 10/08/1997 859! 244.00000 22593 874 25/02/1993 257! 245.00000 317921189 17/03/1992 35! 246.00000 820993440 20/08/1999 815! 247.000001223925262 23/12/1992 739! 248.00000 9 2973528 02/09/1997 543! 249.000001023944308 23/10/1994 796! 250.00000 9 5953606 05/09/1995 438! 251.00000 22799 984 27/02/1999 739! 252.00000 525922147 25/05/1992 260! 253.00000 2 495 531 04/02/1995 507! 254.000001112994657 12/11/1999 398! 255.00000 5 5991881 05/05/1999 551! 256.00000 12893 488 28/01/1993 769! 257.00000 815943366 15/08/1994 228! 258.00000 12994 515 29/01/1994 932! 259.00000 23094 125 01/01/1900 510! 260.00000 5 7951941 07/05/1995 89! 261.00000 318941111 18/03/1994 859! 262.000001211985069 11/12/1998 791! 263.00000 424941771 24/04/1994 669! 264.00000 7 9922807 09/07/1992 834! 265.00000 12697 450 26/01/1997 611! 266.00000 820913430 20/08/1991 949! 267.00000 8 6923287 06/08/1992 743! 268.00000 12393 403 23/01/1993 388! 269.000001226995287 26/12/1999 976! 270.00000 419921606 19/04/1992 527! 271.0000011 1924463 01/11/1992 308! 272.00000 812973211 12/08/1997 634! 273.000001215965003 15/12/1996 586! 274.00000 511931902 11/05/1993 96! 275.00000 21196 667 11/02/1996 392! 276.00000 3 493 936 04/03/1993 695! 277.00000 913973762 13/09/1997 588! 278.00000 2 199 538 01/02/1999 370! 279.000001025984375 25/10/1998 901! 280.00000 526932167 26/05/1993 916! 281.00000 6 9942364 09/06/1994 396! 282.00000 313991184 13/03/1999 83! 283.00000 526952132 26/05/1995 844! 284.00000 21896 786 18/02/1996 697! 285.00000 3 391 958 03/03/1991 828! 286.000001225935253 25/12/1993 518! 287.00000 510931926 10/05/1993 137! 288.00000 929953966 29/09/1995 682! 289.00000 12095 330 20/01/1995 608! 290.000001022954393 22/10/1995 758! 291.00000 820943424 20/08/1994 196! 292.00000 817973359 17/08/1997 755! 293.00000 7 8972753 08/07/1997 592! 294.00000 627962641 27/06/1996 895! 295.00000 910943772 10/09/1994 263! 296.000001219915106 19/12/1991 430! 297.00000 7 6952721 06/07/1995 169! 298.00000 422981688 22/04/1998 343! 299.00000 5 1931840 01/05/1993 877! 300.000001027964328 27/10/1996 820! 301.00000 614942473 14/06/1994 816! 302.0000012 1964808 01/12/1996 762! 303.00000 918923892 18/09/1992 16! 304.00000 621932521 21/06/1993 361! 305.00000 411981524 11/04/1998 871! 306.00000 8 2923189 02/08/1992 269! 307.00000 729993056 29/07/1999 127! 308.00000 721992939 21/07/1999 756! 309.00000 7 5952792 05/07/1995 571! 310.00000 521942128 21/05/1994 205! 311.000001129954823 29/11/1995 350! 312.000001027994326 27/10/1999 598! 313.00000 710932802 10/07/1993 582! 314.00000 822963437 22/08/1996 392! 315.00000 514972009 14/05/1997 797! 316.00000 323941239 23/03/1994 450! 317.00000 21995 850 19/02/1995 696! 318.00000 8 2963155 02/08/1996 715! 319.000001122944786 22/11/1994 854! 320.0000010 6984003 06/10/1998 654! 321.00000 411991524 11/04/1999 203! 322.00000 5 9991919 09/05/1999 549! 323.000001112944626 12/11/1994 114! 324.00000 621992537 21/06/1999 112! 325.00000 519982002 19/05/1998 536! 326.000001214955005 14/12/1995 698! 327.00000 12591 479 25/01/1991 523! 328.00000 310921010 10/03/1992 452! 329.00000 1 195 159 01/01/1995 508! 330.00000 7 5932726 05/07/1993 580! 331.00000 610982354 10/06/1998 432! 332.00000 916913786 16/09/1991 252! 333.00000 825943464 25/08/1994 920! 334.00000 712942862 12/07/1994 567! 335.00000 2 499 550 04/02/1999 380! 336.00000 326971336 26/03/1997 840! 337.000001111954582 11/11/1995 879! 338.00000 427981730 27/04/1998 75! 339.0000011 9974584 09/11/1997 568! 340.00000 5 2981890 02/05/1998 247! 341.000001019954278 19/10/1995 401! 342.00000 518992010 18/05/1999 295! 343.00000 1 999 281 09/01/1999 883! 344.00000 6 9922319 09/06/1992 413! 345.000001216955006 16/12/1995 960! 346.00000 827963526 27/08/1996 835! 347.00000 826913447 26/08/1991 304! 348.00000 9 1933576 01/09/1993 759! 349.00000 821923444 21/08/1992 441! 350.00000 429911779 29/04/1991 453! 351.00000 4 6911467 06/04/1991 367! 352.00000 624912507 24/06/1991 613! 353.00000 514982040 14/05/1998 214! 354.00000 4 3911421 03/04/1991 560! 355.00000 3 9991004 09/03/1999 814! 356.00000 313991166 13/03/1999 711! 357.00000 320961250 20/03/1996 898! 358.00000 322961252 22/03/1996 817! 359.00000 416981657 16/04/1998 409! 360.00000 316921169 16/03/1992 738! 361.00000 914993740 14/09/1999 677! 362.00000 22197 897 21/02/1997 43! 363.00000 410941570 10/04/1994 920! 364.00000 5 9951910 09/05/1995 284! 365.00000 93191 177 01/01/1900 24! 366.00000 525922188 25/05/1992 53! 367.00000 11695 374 16/01/1995 376! 368.000001210915095 10/12/1991 773! 369.00000 9 9943691 09/09/1994 867! 370.00000 324981264 24/03/1998 226! 371.00000 627952631 27/06/1995 157! 372.00000 320951233 20/03/1995 552! 373.00000 9 7983632 07/09/1998 773! 374.00000 819923450 19/08/1992 665! 375.00000 63195 103 01/01/1900 391! 376.00000 5 2931809 02/05/1993 666! 377.00000 3 396 983 03/03/1996 108! 378.00000 731913159 31/07/1991 404! 379.00000 819953321 19/08/1995 451! 380.00000 520912047 20/05/1991 817! 381.00000 927933913 27/09/1993 439! 382.0000012 5964928 05/12/1996 262! 383.00000 2 999 685 09/02/1999 124! 384.00000 8 2943144 02/08/1994 271! 385.00000 520912055 20/05/1991 648! 386.00000 311961189 11/03/1996 800! 387.000001029924493 29/10/1992 929! 388.000001126944858 26/11/1994 752! 389.00000 923933896 23/09/1993 238! 390.000001210955074 10/12/1995 164! 391.00000 323911279 23/03/1991 577! 392.00000 922973876 22/09/1997 146! 393.00000 312951178 12/03/1995 546! 394.00000 9 8993654 08/09/1999 957! 395.00000 828993546 28/08/1999 164! 396.00000 426981755 26/04/1998 468! 397.00000 412981561 12/04/1998 448! 398.00000 331971360 31/03/1997 933! 399.00000 21493 788 14/02/1993 764! 400.00000 331941369 31/03/1994 506! 401.000001010944149 10/10/1994 290! 402.000001013964139 13/10/1996 721! 403.00000 422991659 22/04/1999 485! 404.00000 519922075 19/05/1992 527! 405.0000011 1944408 01/11/1994 415! 406.00000 531912215 31/05/1991 562! 407.00000 22992 975 29/02/1992 529! 408.00000 11395 256 13/01/1995 995! 409.00000 11094 287 10/01/1994 34! 410.000001111924679 11/11/1992 932! 411.00000 12996 527 29/01/1996 567! 412.00000 13097 522 30/01/1997 374! 413.000001031944497 31/10/1994 720! 414.00000 624912549 24/06/1991 804! 415.00000 414991579 14/04/1999 573! 416.00000 315981130 15/03/1998 372! 417.00000 717922917 17/07/1992 714! 418.00000 924983924 24/09/1998 884! 419.00000 418981682 18/04/1998 171! 420.00000 11991 378 19/01/1991 299! 421.00000 312941171 12/03/1994 540! 422.00000 419911689 19/04/1991 626! 423.00000 317921160 17/03/1992 378! 424.00000 417921664 17/04/1992 939! 425.00000 531932235 31/05/1993 565! 426.00000 11796 394 17/01/1996 137! 427.000001125984745 25/11/1998 766! 428.00000 6 2932259 02/06/1993 524! 429.00000 3 6911047 06/03/1991 633! 430.000001029984494 29/10/1998 447! 431.00000 829983591 29/08/1998 376! 432.0000011 8994518 08/11/1999 486! 433.00000 918933833 18/09/1993 876! 434.00000 528952221 28/05/1995 169! 435.000001018924289 18/10/1992 79! 436.00000 322981251 22/03/1998 140! 437.000001018994237 18/10/1999 800! 438.00000 7 3932753 03/07/1993 531! 439.0000011 6914558 06/11/1991 576! 440.0000011 2924439 02/11/1992 449! 441.00000113193 106 01/01/1900 392! 442.00000 924923981 24/09/1992 843! 443.000001120924794 20/11/1992 756! 444.00000 611912435 11/06/1991 207! 445.000001020944286 20/10/1994 438! 446.00000 718962986 18/07/1996 735! 447.00000 6 8912319 08/06/1991 625! 448.00000 411961591 11/04/1996 837! 449.00000 628942657 28/06/1994 890! 450.000001017974266 17/10/1997 717! 451.000001211945016 11/12/1994 260! 452.000001019914292 19/10/1991 136! 453.00000 2 399 556 03/02/1999 605! 454.00000 5 2931882 02/05/1993 779! 455.00000 521932187 21/05/1993 789! 456.0000011 8914519 08/11/1991 716! 457.000001013954108 13/10/1995 685! 458.00000 12794 445 27/01/1994 312! 459.000001121944745 21/11/1994 636! 460.00000 6 4992365 04/06/1999 517! 461.00000 3 8981023 08/03/1998 602! 462.000001118974684 18/11/1997 42! 463.00000 428931709 28/04/1993 435! 464.000001129984891 29/11/1998 872! 465.0000011 6994517 06/11/1999 553! 466.00000 616962427 16/06/1996 465! 467.00000 1 796 191 07/01/1996 620! 468.00000 331971393 31/03/1997 759! 469.00000 810963279 10/08/1996 823! 470.000001214915070 14/12/1991 19! 471.00000 415941579 15/04/1994 509! 472.00000 5 2911830 02/05/1991 948! 473.00000 8 2953172 02/08/1995 664! 474.00000 715912804 15/07/1991 472! 475.00000 4 3981465 03/04/1998 969! 476.00000 12898 496 28/01/1998 580! 477.00000 9 8953683 08/09/1995 257! 478.00000 813953360 13/08/1995 920! 479.00000 714982826 14/07/1998 585! 480.00000 423981779 23/04/1998 224! 481.0000010 4934072 04/10/1993 394! 482.00000 1 497 138 04/01/1997 419! 483.00000 4 1921401 01/04/1992 67! 484.00000 929913931 29/09/1991 375! 485.000001116934674 16/11/1993 584! 486.00000 430981861 30/04/1998 104! 487.00000 817973391 17/08/1997 18! 488.00000 612992491 12/06/1999 487! 489.00000 911943703 11/09/1994 363! 490.00000 6 8962391 08/06/1996 122! 491.00000 519972005 19/05/1997 999! 492.00000 320921241 20/03/1992 141! 493.00000 4 7931445 07/04/1993 108! 494.00000 813963373 13/08/1996 695! 495.00000 614942446 14/06/1994 559! 496.00000 6 8932335 08/06/1993 930! 497.00000 3 296 957 02/03/1996 594! 498.00000 6 3912218 03/06/1991 186! 499.00000 6 4952338 04/06/1995 332! 500.00000 414941525 14/04/1994 472! 501.00000 810963235 10/08/1996 660! 502.00000 22194 883 21/02/1994 307! 503.00000 521952133 21/05/19951000! 504.00000 623972512 23/06/1997 893! 505.000001025954327 25/10/1995 905! 506.00000 530982208 30/05/1998 532! 507.00000 625952623 25/06/1995 472! 508.000001122964718 22/11/1996 854! 509.00000 517922005 17/05/1992 639! 510.000001128944805 28/11/1994 679! 511.00000 526932133 26/05/1993 150! 512.000001220935124 20/12/1993 342! 513.00000 5 2991831 02/05/1999 642! 514.00000 5 8991916 08/05/1999 253! 515.000001225965292 25/12/1996 866! 516.000001015914227 15/10/1991 776! 517.00000 11292 227 12/01/1992 54! 518.00000 63191 171 01/01/1900 449! 519.00000 327931365 27/03/1993 433! 520.00000 4 1921481 01/04/1992 667! 521.0000012 1934824 01/12/1993 950! 522.00000 21291 710 12/02/1991 726! 523.00000 622972513 22/06/1997 391! 524.00000 324961254 24/03/1996 654! 525.00000 425961730 25/04/1996 950! 526.00000 722912956 22/07/1991 373! 527.00000 21893 748 18/02/1993 826! 528.00000 2 497 579 04/02/1997 563! 529.000001030954453 30/10/1995 862! 530.00000 811913256 11/08/1991 123! 531.00000 4 3951451 03/04/1995 447! 532.00000 12099 391 20/01/1999 87! 533.000001018914262 18/10/1991 984! 534.00000 316971101 16/03/1997 42! 535.00000 829963528 29/08/1996 345! 536.00000 612942462 12/06/1994 482! 537.00000 11295 271 12/01/1995 676! 538.00000 913943786 13/09/1994 862! 539.00000 730973113 30/07/1997 303! 540.000001124964746 24/11/1996 267! 541.00000 423981717 23/04/1998 490! 542.00000 922933885 22/09/1993 3! 543.00000 430941865 30/04/1994 478! 544.000001113924608 13/11/1992 960! 545.0000010 3944039 03/10/1994 856! 546.0000010 3984057 03/10/1998 308! 547.00000 421941668 21/04/1994 615! 548.00000 21398 748 13/02/1998 572! 549.00000 825943469 25/08/1994 478! 550.00000 615932433 15/06/1993 957! 551.00000 926983959 26/09/1998 98! 552.00000 827943552 27/08/1994 80! 553.00000 511921989 11/05/1992 374! 554.00000 11499 230 14/01/1999 733! 555.00000 22099 823 20/02/1999 123! 556.0000012 6914927 06/12/1991 190! 557.00000 423981794 23/04/1998 976! 558.00000 331971316 31/03/1997 789! 559.00000 427911758 27/04/1991 245! 560.00000 8 6953254 06/08/1995 387! 561.00000 623942552 23/06/1994 101! 562.00000 924923952 24/09/1992 749! 563.00000 716972953 16/07/1997 276! 564.00000 21893 754 18/02/1993 277! 565.00000 913943711 13/09/1994 282! 566.00000 320991282 20/03/1999 97! 567.00000 322931208 22/03/1993 608! 568.00000 815973369 15/08/1997 860! 569.00000 11696 347 16/01/1996 968! 570.00000 310941052 10/03/1994 607! 571.00000 21096 681 10/02/1996 351! 572.0000011 2974460 02/11/1997 765! 573.000001218975185 18/12/1997 441! 574.00000 519972003 19/05/1997 484! 575.00000 6 6952319 06/06/1995 729! 576.00000 710992851 10/07/1999 700! 577.0000012 8984966 08/12/1998 462! 578.00000 13199 550 31/01/1999 743! 579.0000011 5924567 05/11/1992 747! 580.000001030944445 30/10/1994 569! 581.00000 326961368 26/03/1996 64! 582.00000 3 7921066 07/03/1992 69! 583.00000 22799 933 27/02/1999 237! 584.00000 1 895 233 08/01/1995 494! 585.00000 715982815 15/07/1998 68! 586.000001120914760 20/11/1991 198! 587.000001116914655 16/11/1991 357! 588.000001231925384 31/12/1992 519! 589.000001119954763 19/11/1995 762! 590.00000 11297 283 12/01/1997 647! 591.000001214915040 14/12/1991 751! 592.00000 12599 434 25/01/1999 122! 593.0000010 1914029 01/10/1991 720! 594.00000 710962862 10/07/1996 288! 595.00000 627942686 27/06/1994 749! 596.00000 4 6981430 06/04/1998 432! 597.00000 6 1972296 01/06/1997 322! 598.00000 2 596 607 05/02/1996 784! 599.00000 6 4942308 04/06/1994 476! 600.00000 927933933 27/09/1993 580! 601.0000011 9914535 09/11/1991 349! 602.00000 427911730 27/04/1991 967! 603.00000 423921743 23/04/1992 744! 604.00000 21197 616 11/02/1997 706! 605.00000 930993950 30/09/1999 173! 606.00000 617932411 17/06/1993 707! 607.00000 823963454 23/08/1996 849! 608.000001025964366 25/10/1996 684! 609.000001126914895 26/11/1991 156! 610.00000 625952639 25/06/1995 79! 611.00000 1 995 244 09/01/1995 845! 612.00000 6 6962349 06/06/1996 440! 613.00000 918933836 18/09/1993 980! 614.00000 429911773 29/04/1991 128! 615.00000 327971360 27/03/1997 769! 616.00000 7 1952639 01/07/1995 941! 617.000001213975093 13/12/1997 895! 618.00000 328981368 28/03/1998 625! 619.000001128994810 28/11/1999 27! 620.00000 4 2961432 02/04/1996 431! 621.000001210955002 10/12/1995 933! 622.00000 416951615 16/04/1995 714! 623.00000 512961960 12/05/1996 210! 624.00000 918933874 18/09/1993 592! 625.000001116944638 16/11/1994 397! 626.00000 11797 317 17/01/1997 179! 627.00000 13199 553 31/01/1999 192! 628.000001111984553 11/11/1998 737! 629.000001221945168 21/12/1994 369! 630.00000 726923074 26/07/1992 174! 631.00000 22797 910 27/02/1997 798! 632.00000 22592 851 25/02/1992 601! 633.00000 910933710 10/09/1993 819! 634.00000 817993397 17/08/1999 589! 635.00000 819983354 19/08/1998 457! 636.00000 418931634 18/04/1993 476! 637.000001216975031 16/12/1997 93! 638.000001011954190 11/10/1995 928! 639.00000 714992851 14/07/1999 316! 640.00000 8 5973108 05/08/1997 742! 641.00000 7 6972706 06/07/1997 296! 642.00000 715922909 15/07/1992 371! 643.00000 816953351 16/08/1995 895! 644.00000 726923046 26/07/1992 186! 645.00000 813923325 13/08/1992 283! 646.00000 11494 285 14/01/1994 311! 647.00000 310961023 10/03/1996 775! 648.00000 9 2943510 02/09/1994 5! 649.00000 11491 242 14/01/1991 223! 650.00000 5 2961835 02/05/1996 576! 651.00000 915923760 15/09/1992 382! 652.000001114914627 14/11/1991 208! 653.00000 824923417 24/08/1992 768! 654.00000 9 4993627 04/09/1999 966! 655.00000 428951740 28/04/1995 412! 656.00000 3 7941008 07/03/1994 869! 657.00000 426991701 26/04/1999 551! 658.00000 818943301 18/08/1994 543! 659.0000012 4924960 04/12/1992 158! 660.00000 410971548 10/04/1997 633! 661.00000 916993707 16/09/1999 501! 662.00000 8 3973104 03/08/1997 780! 663.00000 521972148 21/05/1997 654! 664.00000 419981618 19/04/1998 218! 665.000001010994175 10/10/1999 883! 666.00000 313991113 13/03/1999 497! 667.00000 617922539 17/06/1992 316! 668.00000 727963007 27/07/1996 18! 669.00000 21795 713 17/02/1995 585! 670.00000 63198 136 01/01/1900 467! 671.00000 711962827 11/07/1996 4! 672.00000 928943927 28/09/1994 812! 673.00000 5 7931903 07/05/1993 588! 674.00000 5 3931825 03/05/1993 572! 675.000001122994752 22/11/1999 103! 676.00000 628962656 28/06/1996 989! 677.00000 21697 739 16/02/1997 844! 678.000001226935231 26/12/1993 90! 679.000001011924101 11/10/1992 31! 680.00000 428921709 28/04/1992 70! 681.0000012 3964963 03/12/1996 460! 682.00000 524952123 24/05/1995 913! 683.000001030994433 30/10/1999 446! 684.00000 618972508 18/06/1997 153! 685.00000 529922225 29/05/1992 667! 686.00000 4 2951497 02/04/1995 836! 687.000001230945273 30/12/1994 542! 688.00000 4 2931477 02/04/1993 130! 689.00000 730983134 30/07/1998 331! 690.0000010 8944149 08/10/1994 251! 691.00000 522922192 22/05/1992 671! 692.000001124954797 24/11/1995 350! 693.000001129914853 29/11/1991 153! 694.00000 411931589 11/04/1993 873! 695.00000 730943155 30/07/1994 284! 696.00000 2 599 663 05/02/1999 209! 697.00000 621962528 21/06/1996 12! 698.00000 714972827 14/07/1997 309! 699.00000 317931186 17/03/1993 311! 700.00000 12593 493 25/01/1993 764! 701.00000 11092 222 10/01/1992 761! 702.00000 8 9983262 09/08/1998 243! 703.00000 1 994 202 09/01/1994 247! 704.00000 913943776 13/09/1994 77! 705.00000 7 6932739 06/07/1993 935! 706.0000011 9964527 09/11/1996 170! 707.000001028954387 28/10/1995 151! 708.00000 716922930 16/07/1992 827! 709.00000 5 2951845 02/05/1995 887! 710.00000113198 123 01/01/1900 768! 711.000001024954322 24/10/1995 473! 712.00000 12895 405 28/01/1995 929! 713.000001012934151 12/10/1993 983! 714.000001230975217 30/12/1997 628! 715.00000 1 893 292 08/01/1993 90! 716.0000010 6944046 06/10/1994 130! 717.00000 516972073 16/05/1997 151! 718.0000011 4954473 04/11/1995 892! 719.0000010 3934029 03/10/1993 320! 720.0000012 7954912 07/12/1995 117! 721.000001116994666 16/11/1999 627! 722.00000 629962689 29/06/1996 320! 723.00000 512971905 12/05/1997 762! 724.000001217925176 17/12/1992 914! 725.00000 529972206 29/05/1997 106! 726.00000 8 5993146 05/08/1999 22! 727.00000 926943985 26/09/1994 552! 728.00000 6 8972313 08/06/1997 685! 729.00000 93197 148 01/01/1900 255! 730.00000 22798 934 27/02/1998 14! 731.00000 718952986 18/07/1995 891! 732.00000 7 9922803 09/07/1992 706! 733.00000 3 399 981 03/03/1999 782! 734.00000 330911382 30/03/1991 168! 735.00000 915913763 15/09/1991 774! 736.00000 320951244 20/03/1995 753! 737.00000 723993045 23/07/1999 442! 738.00000 530942257 30/05/1994 548! 739.00000 6 8982314 08/06/1998 725! 740.0000010 9994146 09/10/1999 2! 741.00000 8 3973183 03/08/1997 61! 742.00000 626962611 26/06/1996 554! 743.00000 826913414 26/08/1991 732! 744.00000 11096 293 10/01/1996 852! 745.00000 420911669 20/04/1991 135! 746.00000 512961979 12/05/1996 18! 747.00000 717992967 17/07/1999 500! 748.00000 9 3983628 03/09/1998 954! 749.0000010 4994055 04/10/1999 251! 750.0000012 8934914 08/12/1993 301! 751.00000 616932411 16/06/1993 250! 752.00000 326941347 26/03/1994 359! 753.00000 4 5951451 05/04/1995 598! 754.00000 912963725 12/09/1996 517! 755.00000 326981307 26/03/1998 617! 756.00000 724943068 24/07/1994 604! 757.00000 617912445 17/06/1991 106! 758.000001129944815 29/11/1994 234! 759.00000 3 195 982 01/03/1995 625! 760.00000 614932476 14/06/1993 702! 761.00000 314971187 14/03/1997 19! 762.000001218945167 18/12/1994 591! 763.00000 524912195 24/05/1991 208! 764.00000 911993739 11/09/1999 323! 765.00000 63193 160 01/01/1900 927! 766.00000 831933502 31/08/1993 899! 767.00000 6 2952258 02/06/1995 240! 768.00000 816943369 16/08/1994 767! 769.00000 329991330 29/03/1999 556! 770.000001227995222 27/12/1999 627! 771.0000011 4954469 04/11/1995 665! 772.00000 22791 994 27/02/1991 468! 773.000001117914661 17/11/1991 829! 774.00000 314991128 14/03/1999 951! 775.000001126994826 26/11/1999 138! 776.00000 327931374 27/03/1993 376! 777.00000 822993444 22/08/1999 765! 778.00000 5 1971802 01/05/1997 435! 779.0000012 1934829 01/12/1993 98! 780.00000 321911297 21/03/1991 75! 781.00000 21097 629 10/02/1997 799! 782.00000 21099 679 10/02/1999 296! 783.00000113191 167 01/01/1900 908! 784.00000 916993739 16/09/1999 489! 785.00000 21199 607 11/02/1999 605! 786.00000 1 297 153 02/01/1997 827! 787.00000 930964017 30/09/1996 962! 788.000001128964890 28/11/1996 419! 789.00000 421991642 21/04/1999 640! 790.00000 5 8991963 08/05/1999 278! 791.00000 430971850 30/04/1997 224! 792.000001130954884 30/11/1995 188! 793.00000 817983365 17/08/1998 824! 794.000001128934845 28/11/1993 997! 795.00000 612992433 12/06/1999 798! 796.000001230975229 30/12/1997 657! 797.00000 611912411 11/06/1991 669! 798.00000 922993860 22/09/1999 548! 799.000001221995169 21/12/1999 303! 800.00000 910923753 10/09/1992 689! 801.00000 7 1972697 01/07/1997 389! 802.00000 430911843 30/04/1991 150! 803.00000 917993891 17/09/1999 821! 804.000001012994132 12/10/1999 112! 805.00000 429941744 29/04/1994 79! 806.00000 9 9963733 09/09/1996 759! 807.00000 613942497 13/06/1994 641! 808.00000 825943455 25/08/1994 54! 809.00000 617922582 17/06/1992 223! 810.00000 7 2922754 02/07/1992 678! 811.00000 611992457 11/06/1999 693! 812.000001121964784 21/11/1996 820! 813.00000 1 797 192 07/01/1997 68! 814.00000 5 6971856 06/05/1997 173! 815.00000 12599 421 25/01/1999 189! 816.00000 520942006 20/05/1994 705! 817.00000 525972144 25/05/1997 815! 818.00000 331931377 31/03/1993 450! 819.0000010 4974054 04/10/1997 998! 820.00000 721952923 21/07/1995 689! 821.00000 920963814 20/09/1996 620! 822.00000 93197 142 01/01/1900 290! 823.00000 8 2943121 02/08/1994 302! 824.00000 12495 406 24/01/1995 943! 825.00000 9 3913680 03/09/1991 622! 826.00000 43197 190 01/01/1900 571! 827.00000 731973189 31/07/1997 900! 828.00000 929923910 29/09/1992 771! 829.00000 12393 423 23/01/1993 990! 830.00000 715962981 15/07/1996 826! 831.000001121924744 21/11/1992 401! 832.0000010 8954194 08/10/1995 726! 833.00000 21394 777 13/02/1994 253! 834.00000 11595 350 15/01/1995 542! 835.00000 1 993 201 09/01/1993 48! 836.00000 4 8961578 08/04/1996 470! 837.00000 22393 859 23/02/1993 515! 838.00000 513951992 13/05/1995 148! 839.00000 316921183 16/03/1992 962! 840.00000 2 598 617 05/02/1998 772! 841.00000 811953293 11/08/1995 367! 842.00000 831913559 31/08/1991 995! 843.00000 314981196 14/03/1998 333! 844.00000 630962663 30/06/1996 686! 845.00000 1 692 173 06/01/1992 592! 846.00000 531912212 31/05/1991 898! 847.00000 1 598 159 05/01/1998 990! 848.00000 5 1971836 01/05/1997 456! 849.00000 630952611 30/06/1995 524! 850.00000 23092 169 01/01/1900 265! 851.00000 823993489 23/08/1999 541! 852.00000 425931741 25/04/1993 533! 853.00000 927933959 27/09/1993 383! 854.000001210925066 10/12/1992 237! 855.00000 315921179 15/03/1992 40! 856.00000 920963804 20/09/1996 247! 857.000001112934637 12/11/1993 406! 858.0000010 5924018 05/10/1992 239! 859.00000 12791 419 27/01/1991 139! 860.00000 12096 375 20/01/1996 682! 861.00000 7 8942705 08/07/1994 69! 862.00000 1 697 149 06/01/1997 654! 863.00000 310941045 10/03/1994 583! 864.00000 11997 395 19/01/1997 262! 865.00000 411931561 11/04/1993 341! 866.00000 311921157 11/03/1992 370! 867.000001230955233 30/12/1995 353! 868.00000 420981659 20/04/1998 942! 869.0000011 3974438 03/11/1997 730! 870.00000 9 3933677 03/09/1993 652! 871.000001226925211 26/12/1992 909! 872.00000 12098 306 20/01/1998 828! 873.00000 11599 358 15/01/1999 485! 874.000001120964716 20/11/1996 620! 875.00000 929913957 29/09/1991 378! 876.00000 816933330 16/08/1993 119! 877.000001126964894 26/11/1996 422! 878.00000 3 8971039 08/03/1997 434! 879.00000 715952862 15/07/1995 599! 880.000001025994335 25/10/1999 295! 881.00000 21292 723 12/02/1992 908! 882.00000 8 7983263 07/08/1998 904! 883.00000 8 8953207 08/08/1995 487! 884.00000 12997 564 29/01/1997 791! 885.00000 820993470 20/08/1999 8! 886.00000 912963754 12/09/1996 919! 887.00000 815973316 15/08/1997 713! 888.00000 4 5921475 05/04/1992 180! 889.00000 7 4962732 04/07/1996 63! 890.00000 913963791 13/09/1996 769! 891.000001120934791 20/11/1993 915! 892.000001123964741 23/11/1996 500! 893.00000 22395 804 23/02/1995 199! 894.000001230925387 30/12/1992 871! 895.00000 530982283 30/05/1998 681! 896.00000 320971294 20/03/1997 250! 897.00000 3 5911039 05/03/1991 972! 898.00000 7 1982611 01/07/1998 563! 899.00000 6 5912385 05/06/1991 753! 900.00000 8 7983239 07/08/1998 112! 901.00000 614952435 14/06/1995 667! 902.00000 9 5973631 05/09/1997 567! 903.00000 9 1943576 01/09/1994 521! 904.00000 312991160 12/03/1999 925! 905.00000 12093 365 20/01/1993 439! 906.00000 11297 250 12/01/1997 694! 907.00000 430981859 30/04/1998 571! 908.00000 618992505 18/06/1999 56! 909.0000012 9934976 09/12/1993 795! 910.00000 11195 222 11/01/1995 875! 911.00000 319961212 19/03/1996 232! 912.00000 22296 827 22/02/1996 413! 913.000001228995206 28/12/1999 808! 914.00000 817983352 17/08/1998 681! 915.00000 722912951 22/07/1991 203! 916.00000 831943562 31/08/1994 631! 917.00000 411991555 11/04/1999 71! 918.00000 329961363 29/03/1996 970! 919.00000 426941702 26/04/1994 288! 920.0000011 9934525 09/11/1993 766! 921.00000 412951532 12/04/1995 593! 922.0000011 5924536 05/11/1992 986! 923.00000 22691 994 26/02/1991 476! 924.000001220965107 20/12/1996 362! 925.00000 527982117 27/05/1998 726! 926.000001023954338 23/10/1995 990! 927.00000 515922068 15/05/1992 527! 928.00000 21794 768 17/02/1994 424! 929.00000 9 1993594 01/09/1999 738! 930.00000 630952603 30/06/1995 120! 931.00000 1 195 170 01/01/1995 272! 932.000001212975044 12/12/1997 892! 933.00000 415981574 15/04/1998 159! 934.00000 513922019 13/05/1992 630! 935.00000 411991579 11/04/1999 536! 936.00000 9 3953638 03/09/1995 710! 937.000001020944258 20/10/1994 527! 938.00000 329981308 29/03/1998 884! 939.000001210985015 10/12/1998 826! 940.00000 721942910 21/07/1994 529! 941.000001229915221 29/12/1991 1! 942.00000 8 5953182 05/08/1995 918! 943.000001211985008 11/12/1998 569! 944.000001121964710 21/11/1996 713! 945.00000 12798 487 27/01/1998 263! 946.00000 623932594 23/06/1993 121! 947.00000 624942522 24/06/1994 674! 948.000001117994674 17/11/1999 941! 949.00000 924983995 24/09/1998 429! 950.000001123974701 23/11/1997 851! 951.00000 422981638 22/04/1998 500! 952.00000 428971796 28/04/1997 509! 953.00000 422911628 22/04/1991 429! 954.00000 322911229 22/03/1991 554! 955.00000 21297 712 12/02/1997 774! 956.000001129974819 29/11/1997 892! 957.00000 3 494 948 04/03/1994 185! 958.0000012 2984810 02/12/1998 658! 959.0000010 1944036 01/10/1994 344! 960.00000 2 599 623 05/02/1999 17! 961.00000 814933360 14/08/1993 504! 962.00000 1 593 197 05/01/1993 795! 963.00000 21394 772 13/02/1994 550! 964.00000 816923370 16/08/1992 450! 965.00000 319911250 19/03/1991 389! 966.00000 823973466 23/08/1997 337! 967.000001024954367 24/10/1995 776! 968.00000 523992136 23/05/1999 633! 969.000001219975111 19/12/1997 549! 970.00000 21399 750 13/02/1999 764! 971.000001020914207 20/10/1991 509! 972.00000 927993917 27/09/1999 594! 973.00000 21695 774 16/02/1995 983! 974.00000 916923815 16/09/1992 250! 975.00000 22396 869 23/02/1996 217! 976.00000 8 5923271 05/08/1992 669! 977.0000012 9954955 09/12/1995 193! 978.00000 9 1993571 01/09/1999 971! 979.00000 410971534 10/04/1997 428! 980.000001031984459 31/10/1998 937! 981.000001126944863 26/11/1994 289! 982.000001017924275 17/10/1992 397! 983.00000 921993886 21/09/1999 174! 984.0000012 8954913 08/12/1995 641! 985.00000 9 6913603 06/09/1991 970! 986.00000 11791 393 17/01/1991 264! 987.000001213965095 13/12/1996 681! 988.0000011 5934534 05/11/1993 275! 989.000001226995231 26/12/1999 160! 990.000001229925294 29/12/1992 444! 991.00000 325921310 25/03/1992 894! 992.00000 3 195 938 01/03/1995 509! 993.00000 5 6941850 06/05/1994 797! 994.00000 827953509 27/08/1995 89! 995.00000 719982984 19/07/1998 306! 996.00000 713942847 13/07/1994 282! 997.00000 610932364 10/06/1993 429! 998.000001023934330 23/10/1993 551! 999.00000 5 4961825 04/05/1996 370! 1000.00000 323941267 23/03/1994 85! 1001.000001022944386 22/10/1994 807! 1002.00000 930913960 30/09/1991 358! 1003.00000 2 498 518 04/02/1998 157! 1004.00000 517912059 17/05/1991 724! 1005.0000012 5994987 05/12/1999 270! 1006.00000 621932554 21/06/1993 768! 1007.00000 426961770 26/04/1996 641! 1008.00000 6 3972269 03/06/1997 392! 1009.000001015964249 15/10/1996 111! 1010.00000 720962903 20/07/1996 189! 1011.00000 1 295 118 02/01/1995 73! 1012.00000 413941583 13/04/1994 555! 1013.00000 2 993 652 09/02/1993 355! 1014.00000 927973942 27/09/1997 734! 1015.00000 526952166 26/05/1995 366! 1016.00000 326961387 26/03/1996 411! 1017.00000 9 4973675 04/09/1997 656! 1018.00000 12996 563 29/01/1996 749! 1019.00000 331931375 31/03/1993 308! 1020.00000 820913483 20/08/1991 645! 1021.00000 8 4993188 04/08/1999 963! 1022.00000 11995 369 19/01/1995 196! 1023.00000 426981740 26/04/1998 183! 1024.000001221965185 21/12/1996 21! 1025.00000 4 9981507 09/04/1998 26! 1026.000001214975095 14/12/1997 188! 1027.00000 726913087 26/07/1991 733! 1028.00000 21194 651 11/02/1994 68! 1029.000001023934360 23/10/1993 703! 1030.00000 717922932 17/07/1992 896! 1031.00000 326981346 26/03/1998 534! 1032.00000 817953369 17/08/1995 866! 1033.000001113914683 13/11/1991 111! 1034.00000 9 6973660 06/09/1997 747! 1035.00000 22891 955 28/02/1991 690! 1036.00000 328921350 28/03/1992 557! 1037.00000 4 1981360 01/04/1998 580! 1038.00000 9 4973687 04/09/1997 895! 1039.0000010 6974031 06/10/1997 841! 1040.00000 422911669 22/04/1991 778! 1041.00000 9 4973634 04/09/1997 336! 1042.00000 522922108 22/05/1992 415! 1043.00000 22192 845 21/02/1992 689! 1044.00000 913973753 13/09/1997 59! 1045.00000 22499 895 24/02/1999 4! 1046.00000 612922407 12/06/1992 822! 1047.00000 726953040 26/07/1995 220! 1048.0000012 4974908 04/12/1997 937! 1049.00000 9 5983644 05/09/1998 360! 1050.00000 7 8922834 08/07/1992 88! 1051.00000 710922851 10/07/1992 544! 1052.00000 812963381 12/08/1996 236! 1053.00000 626952683 26/06/1995 883! 1054.000001125914719 25/11/1991 217! 1055.00000 11491 216 14/01/1991 828! 1056.00000 22799 951 27/02/1999 775! 1057.00000 1 393 192 03/01/1993 189! 1058.00000 728943048 28/07/1994 956! 1059.00000 612912435 12/06/1991 104! 1060.00000 8 7943245 07/08/1994 816! 1061.00000 428921772 28/04/1992 988! 1062.00000 720942945 20/07/1994 974! 1063.00000 826983423 26/08/1998 180! 1064.00000 418981667 18/04/1998 720! 1065.00000 727953069 27/07/1995 236! 1066.0000012 4964913 04/12/1996 387! 1067.000001023954310 23/10/1995 339! 1068.000001125934744 25/11/1993 151! 1069.00000 824963452 24/08/1996 219! 1070.00000 8 1973162 01/08/1997 584! 1071.000001110924590 10/11/1992 137! 1072.00000 9 9963753 09/09/1996 683! 1073.00000 410941548 10/04/1994 996! 1074.00000 2 294 566 02/02/1994 42! 1075.00000 7 8982746 08/07/1998 508! 1076.000001016924223 16/10/1992 898! 1077.00000 3 9941072 09/03/1994 179! 1078.00000 325951286 25/03/1995 990! 1079.000001228975256 28/12/1997 184! 1080.00000 1 794 103 07/01/1994 285! 1081.00000 720952937 20/07/1995 64! 1082.00000 516952064 16/05/1995 418! 1083.00000 930993935 30/09/1999 197! 1084.00000 418911659 18/04/1991 302! 1085.00000 723963035 23/07/1996 400! 1086.00000 318951162 18/03/1995 947! 1087.00000 418921608 18/04/1992 229! 1088.0000012 5954929 05/12/1995 173! 1089.00000 2 793 630 07/02/1993 96! 1090.00000 521952187 21/05/1995 8! 1091.00000 22693 967 26/02/1993 769! 1092.00000 913993773 13/09/1999 790! 1093.00000 22696 953 26/02/1996 483! 1094.000001010944115 10/10/1994 606! 1095.00000 614962429 14/06/1996 451! 1096.00000 1 695 188 06/01/1995 191! 1097.000001123914786 23/11/1991 927! 1098.0000011 2984453 02/11/1998 717! 1099.00000 312971195 12/03/1997 114! 1100.00000 5 2971829 02/05/1997 656! 1101.00000 529962285 29/05/1996 539! 1102.00000 3 392 916 03/03/1992 530! 1103.00000 712992833 12/07/1999 385! 1104.00000 8 3923144 03/08/1992 283! 1105.00000 21598 758 15/02/1998 812! 1106.00000 5 3931842 03/05/1993 678! 1107.00000 7 1962788 01/07/1996 769! 1108.00000 824943422 24/08/1994 918! 1109.00000 3 398 970 03/03/1998 568! 1110.00000 617982449 17/06/1998 398! 1111.00000 7 4982745 04/07/1998 329! 1112.00000 515972054 15/05/1997 317! 1113.00000 1 295 147 02/01/1995 579! 1114.00000 430971878 30/04/1997 787! 1115.00000 317951137 17/03/1995 243! 1116.000001229925245 29/12/1992 589! 1117.00000 325931225 25/03/1993 648! 1118.00000 918973873 18/09/1997 428! 1119.00000 324981265 24/03/1998 857! 1120.00000 913953751 13/09/1995 789! 1121.00000 615992436 15/06/1999 362! 1122.00000113196 146 01/01/1900 177! 1123.000001211915089 11/12/1991 160! 1124.00000 427951729 27/04/1995 511! 1125.00000 810993294 10/08/1999 132! 1126.000001115944609 15/11/1994 987! 1127.00000 6 9952334 09/06/1995 116! 1128.00000 617952429 17/06/1995 767! 1129.00000 1 792 180 07/01/1992 503! 1130.000001227935226 27/12/1993 162! 1131.00000 13094 540 30/01/1994 797! 1132.00000 5 3961826 03/05/1996 178! 1133.00000 710952809 10/07/1995 82! 1134.00000 614942439 14/06/1994 350! 1135.00000 318981152 18/03/1998 297! 1136.00000 4 4961472 04/04/1996 250! 1137.00000 93191 197 01/01/1900 919! 1138.00000 419941602 19/04/1994 74! 1139.00000 8 6973246 06/08/1997 257! 1140.00000 21294 749 12/02/1994 152! 1141.00000 12592 460 25/01/1992 748! 1142.00000 3 493 912 04/03/1993 573! 1143.00000 823993427 23/08/1999 352! 1144.00000 11497 247 14/01/1997 843! 1145.00000 621962509 21/06/1996 358! 1146.00000 427961746 27/04/1996 154! 1147.00000 7 3972781 03/07/1997 578! 1148.0000011 3944449 03/11/1994 327! 1149.00000 8 5973148 05/08/1997 277! 1150.000001119964739 19/11/1996 225! 1151.00000 620972591 20/06/1997 970! 1152.00000 731983163 31/07/1998 305! 1153.00000 912913748 12/09/1991 196! 1154.00000 422981667 22/04/1998 511! 1155.00000 12695 436 26/01/1995 719! 1156.000001217955128 17/12/1995 361! 1157.00000 12793 462 27/01/1993 912! 1158.00000 22596 813 25/02/1996 139! 1159.000001017974208 17/10/1997 640! 1160.00000 2 997 637 09/02/1997 880! 1161.000001022944315 22/10/1994 180! 1162.00000 629952644 29/06/1995 521! 1163.00000 5 7931924 07/05/1993 21! 1164.00000 1 393 154 03/01/1993 916! 1165.00000 1 495 128 04/01/1995 515! 1166.00000 23199 123 01/01/1900 332! 1167.00000 719932975 19/07/1993 48! 1168.00000 7 6972753 06/07/1997 40! 1169.000001126984853 26/11/1998 45! 1170.00000 21797 725 17/02/1997 270! 1171.00000 4 3911453 03/04/1991 836! 1172.00000 530912262 30/05/1991 425! 1173.00000 723923004 23/07/1992 181! 1174.000001014994113 14/10/1999 268! 1175.000001130984814 30/11/1998 253! 1176.00000 825913493 25/08/1991 613! 1177.000001210975092 10/12/1997 755! 1178.00000 11394 221 13/01/1994 999! 1179.00000 1 794 113 07/01/1994 801! 1180.00000 930983922 30/09/1998 382! 1181.000001028914394 28/10/1991 662! 1182.0000010 2994088 02/10/1999 45! 1183.00000 618912577 18/06/1991 894! 1184.00000 313911115 13/03/1991 39! 1185.00000 12291 425 22/01/1991 221! 1186.00000 11299 234 12/01/1999 201! 1187.00000 623922561 23/06/1992 892! 1188.00000 418961605 18/04/1996 374! 1189.000001017924226 17/10/1992 542! 1190.0000011 8954579 08/11/1995 454! 1191.000001113964658 13/11/1996 180! 1192.00000 612932478 12/06/1993 762! 1193.00000 820933490 20/08/1993 214! 1194.00000 11496 214 14/01/1996 651! 1195.00000 617972495 17/06/1997 194! 1196.00000 329961354 29/03/1996 558! 1197.00000 12797 455 27/01/1997 83! 1198.00000 22993 180 01/01/1900 827! 1199.00000 513911956 13/05/1991 743! 1200.00000 312951160 12/03/1995 677! 1201.00000 615942421 15/06/1994 727! 1202.000001126934838 26/11/1993 988! 1203.00000 721912958 21/07/1991 378! 1204.0000012 5934973 05/12/1993 815! 1205.00000 424941776 24/04/1994 150! 1206.000001221945141 21/12/1994 674! 1207.00000 5 6991887 06/05/1999 120! 1208.00000 421991653 21/04/1999 717! 1209.00000 824993486 24/08/1999 625! 1210.00000 4 3991476 03/04/1999 787! 1211.0000012 3934905 03/12/1993 898! 1212.000001012964138 12/10/1996 569! 1213.00000 630952681 30/06/1995 228! 1214.00000 93199 190 01/01/1900 654! 1215.00000 6 6922318 06/06/1992 742! 1216.00000 1 893 245 08/01/1993 561! 1217.00000 9 6963622 06/09/1996 117! 1218.00000 910913786 10/09/1991 191! 1219.00000 614982462 14/06/1998 817! 1220.00000 12597 414 25/01/1997 908! 1221.00000 12399 469 23/01/1999 166! 1222.00000 711972886 11/07/1997 621! 1223.000001213965086 13/12/1996 523! 1224.00000 810953228 10/08/1995 125! 1225.00000 22798 991 27/02/1998 902! 1226.00000 93191 117 01/01/1900 856! 1227.00000 4 7941475 07/04/1994 107! 1228.00000 619912546 19/06/1991 279! 1229.0000010 2934043 02/10/1993 155! 1230.0000010 6914094 06/10/1991 324! 1231.00000 5 2921882 02/05/1992 414! 1232.00000 921953822 21/09/1995 362! 1233.00000 414931568 14/04/1993 235! 1234.00000 616972445 16/06/1997 162! 1235.00000 9 2993533 02/09/1999 907! 1236.00000 830993501 30/08/1999 732! 1237.00000 424961775 24/04/1996 892! 1238.00000 628992630 28/06/1999 280! 1239.0000011 8954516 08/11/1995 201! 1240.000001121944713 21/11/1994 186! 1241.00000 4 5941454 05/04/1994 864! 1242.00000 418981612 18/04/1998 894! 1243.00000 93196 138 01/01/1900 91! 1244.00000 615952431 15/06/1995 192! 1245.000001231955306 31/12/1995 517! 1246.0000011 1924429 01/11/1992 884! 1247.00000 522962189 22/05/1996 162! 1248.00000 9 8913645 08/09/1991 398! 1249.00000 8 4933142 04/08/1993 981! 1250.000001025934354 25/10/1993 714! 1251.00000 724953044 24/07/1995 564! 1252.00000 414961584 14/04/1996 653! 1253.00000 1 794 162 07/01/1994 281! 1254.00000 7 5942771 05/07/1994 696! 1255.0000011 9964593 09/11/1996 220! 1256.00000 724943003 24/07/1994 90! 1257.00000 316951145 16/03/1995 435! 1258.00000 1 992 278 09/01/1992 351! 1259.00000 815963351 15/08/1996 258! 1260.00000 417941606 17/04/1994 353! 1261.00000 22592 801 25/02/1992 220! 1262.00000 1 693 137 06/01/1993 766! 1263.00000 827953546 27/08/1995 485! 1264.00000 325971292 25/03/1997 397! 1265.00000 812943227 12/08/1994 116! 1266.00000 12894 482 28/01/1994 872! 1267.00000 625992655 25/06/1999 918! 1268.00000 7 1962745 01/07/1996 303! 1269.00000 630992609 30/06/1999 929! 1270.00000 527982185 27/05/1998 405! 1271.00000 2 891 681 08/02/1991 511! 1272.00000 325971226 25/03/1997 388! 1273.0000010 1994046 01/10/1999 337! 1274.00000 710932893 10/07/1993 143! 1275.00000 7 2962731 02/07/1996 988! 1276.00000 43192 113 01/01/1900 187! 1277.00000 4 8921597 08/04/1992 732! 1278.00000 93195 171 01/01/1900 776! 1279.000001029954403 29/10/1995 194! 1280.000001214985054 14/12/1998 934! 1281.00000 2 795 611 07/02/1995 35! 1282.00000 515942079 15/05/1994 538! 1283.00000 22998 148 01/01/1900 285! 1284.00000 12792 450 27/01/1992 944! 1285.00000 618922546 18/06/1992 734! 1286.00000 8 8953247 08/08/1995 494! 1287.00000 21393 718 13/02/1993 910! 1288.00000 4 5951490 05/04/1995 575! 1289.000001124954751 24/11/1995 510! 1290.000001123954762 23/11/1995 336! 1291.00000 731953160 31/07/1995 453! 1292.000001120974719 20/11/1997 539! 1293.00000 329921309 29/03/1992 886! 1294.00000 422991649 22/04/1999 842! 1295.00000 623922582 23/06/1992 843! 1296.000001014994135 14/10/1999 335! 1297.00000 719952932 19/07/1995 575! 1298.00000 721962931 21/07/1996 559! 1299.00000 8 3933112 03/08/1993 452! 1300.00000 929953986 29/09/1995 447! 1301.00000 3 7921080 07/03/1992 204! 1302.00000 724923003 24/07/1992 738! 1303.00000 416951658 16/04/1995 692! 1304.00000 615992417 15/06/1999 707! 1305.00000 9 3963638 03/09/1996 875! 1306.00000 21092 691 10/02/1992 343! 1307.00000 12396 448 23/01/1996 903! 1308.00000 21491 731 14/02/1991 906! 1309.00000 7 8982707 08/07/1998 654! 1310.00000 7 3922734 03/07/1992 754! 1311.000001019924287 19/10/1992 341! 1312.0000012 5934993 05/12/1993 585! 1313.00000 4 9911529 09/04/1991 314! 1314.00000 418921667 18/04/1992 862! 1315.00000 918923841 18/09/1992 750! 1316.00000 626932675 26/06/1993 52! 1317.000001212995095 12/12/1999 725! 1318.000001224965284 24/12/1996 808! 1319.00000 2 593 638 05/02/1993 2! 1320.00000 611992488 11/06/1999 518! 1321.0000011 3964493 03/11/1996 397! 1322.00000 712972813 12/07/1997 532! 1323.00000 420951690 20/04/1995 885! 1324.000001128974872 28/11/1997 85! 1325.00000 430911859 30/04/1991 879! 1326.00000 313981179 13/03/1998 695! 1327.00000 928973923 28/09/1997 842! 1328.00000 524972192 24/05/1997 761! 1329.000001010944141 10/10/1994 702! 1330.00000 11295 241 12/01/1995 198! 1331.000001117984644 17/11/1998 629! 1332.00000 12893 460 28/01/1993 878! 1333.000001122914789 22/11/1991 477! 1334.00000 3 6991022 06/03/1999 798! 1335.00000 7 9942816 09/07/1994 78! 1336.00000 820993413 20/08/1999 255! 1337.00000 430981828 30/04/1998 815! 1338.00000 2 794 652 07/02/1994 822! 1339.00000 4 9931502 09/04/1993 67! 1340.00000 614982475 14/06/1998 797! 1341.000001115944614 15/11/1994 189! 1342.00000 418981636 18/04/1998 985! 1343.00000 623922506 23/06/1992 500! 1344.0000011 3984441 03/11/1998 407! 1345.00000 21894 706 18/02/1994 47! 1346.00000 1 994 234 09/01/1994 887! 1347.00000 914913706 14/09/1991 734! 1348.000001123984788 23/11/1998 363! 1349.00000 928913979 28/09/1991 951! 1350.000001112944685 12/11/1994 117! 1351.00000 12999 539 29/01/1999 528! 1352.00000 830983553 30/08/1998 653! 1353.00000 412991554 12/04/1999 338! 1354.00000 4 1941349 01/04/1994 499! 1355.00000 524982150 24/05/1998 986! 1356.00000 3 295 927 02/03/1995 335! 1357.000001026954321 26/10/1995 585! 1358.0000012 4954907 04/12/1995 678! 1359.00000 317961193 17/03/1996 688! 1360.000001011964130 11/10/1996 969! 1361.00000 321941290 21/03/1994 640! 1362.00000 6 2962209 02/06/1996 663! 1363.00000 730913156 30/07/1991 185! 1364.00000 623952526 23/06/1995 563! 1365.00000 12398 458 23/01/1998 933! 1366.000001014984126 14/10/1998 403! 1367.000001023934332 23/10/1993 630! 1368.000001119944776 19/11/1994 696! 1369.000001112954632 12/11/1995 459! 1370.0000010 6984014 06/10/1998 747! 1371.00000 4 2991419 02/04/1999 415! 1372.00000 511981914 11/05/1998 796! 1373.00000 22396 834 23/02/1996 896! 1374.00000 827913525 27/08/1991 702! 1375.00000 21098 657 10/02/1998 959! 1376.00000 515922051 15/05/1992 168! 1377.00000 324921284 24/03/1992 204! 1378.000001227975290 27/12/1997 636! 1379.00000 12991 591 29/01/1991 556! 1380.00000 8 8933292 08/08/1993 124! 1381.00000 5 6921905 06/05/1992 779! 1382.000001026994374 26/10/1999 342! 1383.000001226945287 26/12/1994 680! 1384.000001123914716 23/11/1991 662! 1385.00000 422971667 22/04/1997 469! 1386.00000 729953028 29/07/1995 852! 1387.000001127994851 27/11/1999 500! 1388.000001214965064 14/12/1996 585! 1389.00000 511951915 11/05/1995 435! 1390.00000 719922958 19/07/1992 599! 1391.00000 913973710 13/09/1997 590! 1392.00000 710922887 10/07/1992 897! 1393.000001214985089 14/12/1998 949! 1394.00000 614922406 14/06/1992 359! 1395.000001028934311 28/10/1993 328! 1396.00000 8 6983262 06/08/1998 726! 1397.00000 725963083 25/07/1996 571! 1398.00000 6 8932316 08/06/1993 734! 1399.00000 9 9913637 09/09/1991 611! 1400.00000 715962943 15/07/1996 30! 1401.00000 915913717 15/09/1991 225! 1402.00000 415941561 15/04/1994 342! 1403.00000 524932194 24/05/1993 732! 1404.00000 910953774 10/09/1995 327! 1405.000001124934786 24/11/1993 383! 1406.00000 8 8933278 08/08/1993 664! 1407.00000 619922577 19/06/1992 542! 1408.00000 23093 196 01/01/1900 740! 1409.00000 522922157 22/05/1992 24! 1410.00000 21593 714 15/02/1993 350! 1411.00000 21896 752 18/02/1996 81! 1412.00000 824943468 24/08/1994 375! 1413.00000 429971745 29/04/1997 73! 1414.000001118964782 18/11/1996 698! 1415.00000 8 9993229 09/08/1999 882! 1416.00000 721922969 21/07/1992 167! 1417.00000 23194 108 01/01/1900 500! 1418.0000010 2954069 02/10/1995 656! 1419.00000 9 6933621 06/09/1993 19! 1420.00000 12094 331 20/01/1994 228! 1421.00000 615912497 15/06/1991 982! 1422.00000 2 791 661 07/02/1991 473! 1423.00000 1 491 171 04/01/1991 612! 1424.00000 327991317 27/03/1999 656! 1425.00000 928913969 28/09/1991 782! 1426.00000 821983433 21/08/1998 984! 1427.00000 422961795 22/04/1996 881! 1428.00000 417931665 17/04/1993 383! 1429.00000 11596 337 15/01/1996 815! 1430.00000 12793 497 27/01/1993 273! 1431.00000 1 295 172 02/01/1995 303! 1432.00000 9 1943543 01/09/1994 129! 1433.00000 519942048 19/05/1994 353! 1434.000001121934725 21/11/1993 280! 1435.00000 6 5952345 05/06/1995 114! 1436.00000 22691 941 26/02/1991 446! 1437.00000 11197 279 11/01/1997 451! 1438.00000 421951649 21/04/1995 232! 1439.00000 911983743 11/09/1998 393! 1440.000001215915049 15/12/1991 635! 1441.000001221935160 21/12/1993 19! 1442.00000 711992886 11/07/1999 949! 1443.00000 22391 812 23/02/1991 789! 1444.00000 22799 953 27/02/1999 340! 1445.00000 3 7961039 07/03/1996 513! 1446.00000 5 4911819 04/05/1991 698! 1447.00000 22691 945 26/02/1991 717! 1448.00000 516942094 16/05/1994 130! 1449.000001014994146 14/10/1999 649! 1450.00000 2 697 687 06/02/1997 422! 1451.00000 711942857 11/07/1994 838! 1452.000001026934331 26/10/1993 606! 1453.00000 817963323 17/08/1996 969! 1454.000001029934477 29/10/1993 772! 1455.00000 928913989 28/09/1991 817! 1456.0000011 7994562 07/11/1999 461! 1457.00000 321981262 21/03/1998 170! 1458.00000 523952137 23/05/1995 986! 1459.000001228945259 28/12/1994 606! 1460.00000 611992456 11/06/1999 342! 1461.00000113193 178 01/01/1900 370! 1462.00000 6 9912347 09/06/1991 404! 1463.00000 21998 859 19/02/1998 824! 1464.00000 12295 453 22/01/1995 809! 1465.000001221935114 21/12/1993 657! 1466.00000 326981310 26/03/1998 145! 1467.00000 419921607 19/04/1992 433! 1468.000001127924807 27/11/1992 626! 1469.00000 613972425 13/06/1997 411! 1470.00000 13095 528 30/01/1995 365! 1471.0000011 6994528 06/11/1999 656! 1472.00000 414951554 14/04/1995 77! 1473.00000 326941360 26/03/1994 366! 1474.00000 311931036 11/03/1993 568! 1475.00000 1 594 197 05/01/1994 167! 1476.00000 7 7962710 07/07/1996 107! 1477.00000 11499 267 14/01/1999 204! 1478.000001030984481 30/10/1998 294! 1479.00000 9 3943619 03/09/1994 466! 1480.00000 814983384 14/08/1998 382! 1481.00000 22995 156 01/01/1900 100! 1482.00000 816963340 16/08/1996 575! 1483.00000121399502A 13/12/1999 710! 1484.00000103099442A 30/10/1999 160! 1485.00000 22492 82A 24/02/1992 188! 1486.00000 6 996232B 09/06/1996 713! 1487.00000 5 294182B 02/05/1994 663! 1488.00000 11895 32B 18/01/1995 170! 1489.00000 22092 82A 20/02/1992 810! 1490.00000 21894 72B 18/02/1994 956! 1491.00000 82392342B 23/08/1992 485! 1492.00000 1 993 22A 09/01/1993 667! 1493.00000 12399 42A 23/01/1999 435! 1494.00000 13197 52A 31/01/1997 807! 1495.00000 42596172A 25/04/1996 383! 1496.00000 22794 92A 27/02/1994 758! 1497.00000 2 894 62B 08/02/1994 995! 1498.00000 51798202B 17/05/1998 504! 1499.00000 52396212B 23/05/1996 408! 1500.00000 41191152B 11/04/1991 433! 1501.00000 8 299312A 02/08/1999 839! 1502.00000 43193 12A 01/01/1900 160! 1503.00000 51391192B 13/05/1991 402! 1504.00000101992422B 19/10/1992 859! 1505.00000 8 197312B 01/08/1997 512! 1506.00000101595422A 15/10/1995 23! 1507.00000 53096222A 30/05/1996 249! 1508.00000101693422B 16/10/1993 484! 1509.00000 7 395272B 03/07/1995 65! 1510.00000 62797262B 27/06/1997 661! 1511.00000 1 399 12B 03/01/1999 34! 1512.00000103196442B 31/10/1996 234! 1513.00000 91493372A 14/09/1993 3! 1514.00000 52693212A 26/05/1993 595! 1515.00000112092472B 20/11/1992 555! 1516.00000 91195372A 11/09/1995 747! 1517.00000 81091322B 10/08/1991 87! 1518.00000113093482A 30/11/1993 432! 1519.00000 5 791192A 07/05/1991 532! 1520.0000012 691492A 06/12/1991 814! 1521.00000 91993382B 19/09/1993 132! 1522.00000121497502A 14/12/1997 239! 1523.00000 61095232A 10/06/1995 439! 1524.00000 22495 82A 24/02/1995 678! 1525.0000011 194442A 01/11/1994 418! 1526.00000 42193162A 21/04/1993 456! 1527.00000 12896 42B 28/01/1996 884! 1528.00000 81795332A 17/08/1995 609! 1529.00000 72395302A 23/07/1995 119! 1530.00000111392462A 13/11/1992 446! 1531.00000 62591262B 25/06/1991 537! 1532.00000 13195 52A 31/01/1995 388! 1533.00000 62996262B 29/06/1996 824! 1534.00000 61199242A 11/06/1999 241! 1535.00000112093472A 20/11/1993 96! 1536.00000 41797162B 17/04/1997 483! 1537.00000 72691302B 26/07/1991 177! 1538.00000 4 996152A 09/04/1996 419! 1539.00000121795512B 17/12/1995 145! 1540.00000 5 997192A 09/05/1997 71! 1541.00000 4 497142A 04/04/1997 369! 1542.00000 62994262A 29/06/1994 880! 1543.0000011 194442A 01/11/1994 90! 1544.00000111093452A 10/11/1993 872! 1545.00000 61399242A 13/06/1999 16! 1546.00000 8 593312B 05/08/1993 337! 1547.00000 5 998192A 09/05/1998 141! 1548.00000 5 291182B 02/05/1991 389! 1549.00000 2 292 52B 02/02/1992 163! 1550.00000 11299 22A 12/01/1999 808! 1551.00000 8 796322B 07/08/1996 273! 1552.0000012 992502A 09/12/1992 601! 1553.00000122898522A 28/12/1998 378! 1554.00000112894482B 28/11/1994 859! 1555.00000 72698302B 26/07/1998 468! 1556.00000113093482B 30/11/1993 487! 1557.00000122893522A 28/12/1993 688! 1558.00000121394502A 13/12/1994 770! 1559.00000 12391 42B 23/01/1991 391! 1560.00000122399512B 23/12/1999 328! 1561.00000121692512B 16/12/1992 819! 1562.00000 63197 12A 01/01/1900 434! 1563.00000 61598242B 15/06/1998 626! 1564.00000 81496332B 14/08/1996 108! 1565.00000 31992122A 19/03/1992 573! 1566.00000 5 991192B 09/05/1991 759! 1567.00000112498472A 24/11/1998 666! 1568.00000111793462A 17/11/1993 558! 1569.00000 12598 42B 25/01/1998 818! 1570.00000 8 491312A 04/08/1991 4! 1571.00000112494472B 24/11/1994 48! 1572.00000 5 892192B 08/05/1992 725! 1573.00000 12496 42A 24/01/1996 347! 1574.00000 7 194262B 01/07/1994 862! 1575.00000 51194192A 11/05/1994 397! 1576.00000 62099252A 20/06/1999 815! 1577.00000 6 293222A 02/06/1993 834! 1578.00000 32397122A 23/03/1997 713! 1579.00000 7 197262B 01/07/1997 83! 1580.00000 3 194 92A 01/03/1994 992! 1581.0000011 897452B 08/11/1997 639! 1582.00000 91192372A 11/09/1992 642! 1583.00000 913973797113/09/1997 126! 1584.00000 3 9991097209/03/1999 307! 1585.00000 521932197121/05/1993 452! 1586.00000 526942197326/05/1994 591! 1587.000001031964497131/10/1996 651! 1588.00000 21896 797218/02/1996 463! 1589.00000 519952097319/05/1995 36! 1590.00000 1 499 197204/01/1999 923! 1591.00000 4 1921497301/04/1992 200! 1592.00000 7 5912797305/07/1991 293! 1593.00000 324931297224/03/1993 393! 1594.00000 3 6971097306/03/1997 917! 1595.00000 620992597220/06/1999 260! 1596.00000 422931697322/04/1993 159! 1597.00000 7 9992897309/07/1999 950! 1598.00000 429911797129/04/1991 610! 1599.0000011 8954597208/11/1995 432! 1600.000001129934897129/11/1993 333! 1601.000001021964397121/10/1996 90! 1602.00000 831933597131/08/1993 777! 1603.000001027974397227/10/1997 158! 1604.00000 5 4971897304/05/1997 628! 1605.00000 710982897210/07/1998 439! 1606.000001220995197120/12/1999 816! 1607.00000 810943297210/08/1994 410! 1608.00000 4 6921497106/04/1992 63! 1609.00000 9 8923697208/09/1992 50! 1610.00000 6 2932297102/06/1993 477! 1611.000001029974497129/10/1997 239! 1612.00000 522972197222/05/1997 90! 1613.00000 322961297322/03/1996 788! 1614.00000 12098 397220/01/1998 478! 1615.00000 528942297228/05/1994 723! 1616.00000 727913097327/07/1991 956! 1617.00000 712962897212/07/1996 992! 1618.000001217915197217/12/1991 355! 1619.0000012 9914997109/12/1991 613! 1620.00000 2 699 697306/02/1999 300! 1621.00000 410951597210/04/1995 998! 1622.00000 3 8921097108/03/1992 387! 1623.00000 12996 597229/01/1996 230! 1624.00000 514912097214/05/1991 822! 1625.00000 8 8923297308/08/1992 568! 1626.0000010 8994197308/10/1999 327! 1627.00000 8 2953197202/08/1995 335! 1628.00000 916963897216/09/1996 743! 1629.00000 620912597220/06/1991 403! 1630.00000 830953597230/08/1995 612! 1631.00000 23191 197301/01/1900 178! 1632.000001129914897329/11/1991 302! 1633.00000 11193 297211/01/1993 921! 1634.00000 518972097318/05/1997 883! 1635.000001129934897129/11/1993 755! 1636.000001023944397323/10/1994 149! 1637.00000 3 9981097309/03/1998 117! 1638.00000 813963397213/08/1996 853! 1639.00000 514942097114/05/1994 352! 1640.00000 310951097310/03/1995 952! 1641.00000 323931297223/03/1993 903! 1642.00000 626932697326/06/1993 434! 1643.00000 3 7951097307/03/1995 311! 1644.000001113964697313/11/1996 709! 1645.00000 417951697117/04/1995 464! 1646.00000 623982597323/06/1998 387! 1647.00000 21298 797112/02/1998 767! 1648.000001210965097110/12/1996 676! 1649.000001228965297228/12/1996 520! 1650.0000011 6984597106/11/1998 360! 1651.00000 411931597111/04/1993 523! 1652.00000 8 9933297309/08/1993 879! 1653.00000 911923797311/09/1992 70! 1654.00000 918963897218/09/1996 612! 1655.000001228955297328/12/1995 170! 1656.00000 422941697122/04/1994 573! 1657.00000 7 7952797207/07/1995 185! 1658.000001227915297227/12/1991 543! 1659.00000 322931297322/03/1993 130! 1660.00000 23193 197201/01/1900 939! 1661.000001215945097315/12/1994 37! 1662.00000 7 1952697301/07/1995 322! 1663.00000 7 3912797103/07/1991 615! 1664.000001220975197320/12/1997 459! 1665.00000 727983097327/07/1998 976! 1666.0000010 9954197209/10/1995 290! 1667.000001020984297220/10/1998 127! 1668.000001120944797220/11/1994 57! 1669.00000 12092 397320/01/1992 134! 1670.00000 930943997330/09/1994 846! 1671.0000011 7994597307/11/1999 536! 1672.00000 9 2933597202/09/1993 299! 1673.00000 731983197231/07/1998 921! 1674.0000011 4914497104/11/1991 307! 1675.00000 23193 197201/01/1900 316! 1676.00000 811983297111/08/1998 359! 1677.00000 312921197312/03/1992 717! 1678.00000 312981197312/03/1998 433! 1679.0000011 5924597305/11/1992 212! 1680.00000 928943997328/09/1994 163! 1681.00000 627972697127/06/1997 611! 1682.00000 22193 897121/02/1993 958! 1683.00000 526942197426/05/1994 591! 1684.00000 519952097419/05/1995 36! 1685.00000 4 1921497401/04/1992 200! 1686.00000 7 5912797405/07/1991 293! 1687.00000 3 6971097406/03/1997 917! 1688.00000 422931697422/04/1993 159! 1689.00000 7 9992897409/07/1999 950! 1690.00000 5 4971897404/05/1997 628! 1691.00000 322961297422/03/1996 788! 1692.00000 727913097427/07/1991 956! 1693.00000 2 699 697406/02/1999 300! 1694.00000 8 8923297408/08/1992 568! 1695.0000010 8994197408/10/1999 327! 1696.00000 23191 197401/01/1900 178! 1697.000001129914897429/11/1991 302! 1698.00000 518972097418/05/1997 883! 1699.000001023944397423/10/1994 149! 1700.00000 3 9981097409/03/1998 117! 1701.00000 310951097410/03/1995 952! 1702.00000 626932697426/06/1993 434! 1703.00000 3 7951097407/03/1995 311! 1704.000001113964697413/11/1996 709! 1705.00000 623982597423/06/1998 387! 1706.00000 8 9933297409/08/1993 879! 1707.00000 911923797411/09/1992 70! 1708.000001228955297428/12/1995 170! 1709.00000 322931297422/03/1993 130! 1710.000001215945097415/12/1994 37! 1711.00000 7 1952697401/07/1995 322! 1712.000001220975197420/12/1997 459! 1713.00000 727983097427/07/1998 976! 1714.00000 12092 397420/01/1992 134! 1715.00000 930943997430/09/1994 846! 1716.0000011 7994597407/11/1999 536! 1717.00000 312921197412/03/1992 717! 1718.00000 312981197412/03/1998 433! 1719.0000011 5924597405/11/1992 212! 1720.00000 928943997428/09/1994 163! --=====================_944044020==_ Content-Type: text/plain; charset="us-ascii" \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| --=====================_944044020==_-- ========================================================================= Date: Mon, 6 Dec 1999 21:52:28 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jose A. Farfan" Subject: sending a graph to a file Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Dear members on the group I am trying to save a scatter graph into a file using the ROUTE command, but I am not getting nothing sent to the file. I will appreciate if you could give me an advice about how to do this. Respectfully Jose A. Farfan ========================================================================= Date: Tue, 7 Dec 1999 09:27:28 -0800 Reply-To: gerald.daurat@wanadoo.fr Sender: Epi Info Discussion Group From: Gerald DAURAT Subject: Re: sending a graph to a file MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jose A. Farfan wrote: > > Dear members on the group > > I am trying to save a scatter graph into a file using the ROUTE command, > but I am not getting nothing sent to the file. I will appreciate if you > could give me an advice about how to do this. > > Respectfully > > Jose A. Farfan Within analysis (or Pgm program) First you have to chose a graph file format SET GRAPH = $CGM (if you want a CGM format file) I personnaly often use this format to insert graphs in Word documents. Files are reasonnably small and background color is not black. then route the results ROUTE .cgm (if you use cgm format of course) then send a graph command such as HISTOGRAM The file is automatically closed after the command. Be careful, you cannot get more than one graph in a single file, so remember to use different file names for different graphs. Gerald Daurat Monpellier France ========================================================================= Date: Tue, 7 Dec 1999 15:54:52 +0100 Reply-To: golliot@ext.jussieu.fr Sender: Epi Info Discussion Group From: Franck Golliot Organization: CCLIN Paris-Nord Subject: Cascade of include commands MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi everybody, I am trying to include sub menus using COMMENT LEGAL in a .CHK file. It's easy to use an INCLUDE command to retrieve a text file. I would like, however, to set up a cascade of include commands, so that each item listed in the text file may call up another sub menu in order to describe that item in greater detail. For example : First text file 1 INJECTION 2 BLOOD SAMPLING 3 SUTURE Second text file, under INJECTION 11 UNDEFINED 12 SUBCUTANEOUS 13 IM 14 IV And so on for each of the three items. Thanks for your help, -- Franck GOLLIOT - C.CLIN Paris-Nord Centre Interregional de Coordination de la Lutte contre les Infections Nosocomiales, Paris From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9911E" ========================================================================= Date: Tue, 30 Nov 1999 08:35:25 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jose A. Farfan" Subject: calendar Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Dear members in the group: When I am entering my patients data in a file using Epiinfo, I need to check the epidemiologic week that correspond to the disease onset for each patient. I would like to know if it is possible to incorporate in a QES or CHK file, a procedure to call the calendar with epidemilogic weeks (IDCLND) available in Epiinfo. Thank in advance for the help you could provide me Respectfully Jose A. Farfan ========================================================================= Date: Tue, 30 Nov 1999 15:56:14 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: calendar In-Reply-To: <4.2.1.19991130082954.00a91600@tunku.uady.mx> MIME-Version: 1.0 Jose A. Farfan writes: >Dear members in the group: > >When I am entering my patients data in a file using Epiinfo, I need to >check the epidemiologic week that correspond to the disease onset for each >patient. >I would like to know if it is possible to incorporate in a QES or CHK file, >a procedure to call the calendar with epidemilogic weeks (IDCLND) available >in Epiinfo. > >Thank in advance for the help you could provide me I don't think that can be done. You could use the TSR interface but it is probably easier just to use the CHECK language. Here is something from a surveillance system ... IF WEEK = . THEN IF NOTIF >= "01/01/2000" AND NOTIF <= "12/31/2000" THEN LET WEEK = (NOTIF - "01/01/2000") DIV 7 + 1 ENDIF ENDIF The start date is for the first day of epidemiological week one. This will be different in different years. The dates above are UK NOIDS weeks which differ (sometimes) from US MMWR weeks. -- Mark Myatt From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9911D" ========================================================================= Date: Tue, 23 Nov 1999 13:03:09 +0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: weird behavior with cyrillic DOS fonts and analysis .PGM files MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here's a strange potential bug. I'm writing some stuff in Russian for Epi Info, including some PGM files to determine which patients meet CDC criteria for infection. In the PGM files, I include some text for reporting who meets those criteria, and the text is in the ALT (CP866) code page. I use the TITLE and TYPE commands to get the text into a text file to which I'm ROUTEd. The DOS .PGM file contains normal, appropriate letters. The resulting text file is perfect but for the Russian S, which looks the same as C. That letter is transformed into a Russian V which looks like a B. I cannot for the life of me figure out why it would be recoding that one byte in particular. I don't have the actual code pages, so I don't know which bit(s) are switched nor can I understand why high ASCII bytes would be changed selectively like that. Does anyone have any idea? Fortunately I can substitute the English C, but that is pretty dang kludgy and I'd hate to explain that to some Russian that wants to improve my work later. Thanks for the time. smb ========================================================================= Date: Fri, 26 Nov 1999 09:04:07 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: EpiNut - Does it want whole numbers? MIME-Version: 1.0 EpiInfo-ers, Does EpiNut require AGE to be a whole number? I am getting very odd results with a floating point AGE. Mark -- Mark Myatt From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9911B" ========================================================================= Date: Thu, 11 Nov 1999 08:25:20 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: Leona Bassein Subject: MEDIA RELEASE: FIRST VIRUS TO ACTIVATE WHEN AN E-MAIL IS OPENED Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Questo e' il messaggio che riguarda outlook che avevo menzionato. >Delivered-To: bassein@orsola-malpighi.med.unibo.it >X-Sender: flescher@popmail.libero.it >X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) >Date: Wed, 10 Nov 1999 20:41:41 +0100 >To: sottili@alma.unibo.it,stat2@orsola-malpighi.med.unibo.it, > bassein@orsola-malpighi.med.unibo.it >From: Marita Nasman-Repo (by way of pac0838@iperbole.bologna.it) >Subject: MEDIA RELEASE: FIRST VIRUS TO ACTIVATE WHEN AN E-MAIL IS OPENED > > >This press release comes from Data Fellows. For more=20 >information on Data Fellows' mailing list policy,=20 >see end of message. > >FIRST VIRUS TO ACTIVATE WHEN AN E-MAIL IS OPENED > >Data Fellows warns the public of potential future threat > >Espoo, Finland - November 10, 1999 - Data Fellows Corporation, a leading >provider of Internet security solutions, today announced the first virus found >which activates by opening an e-mail message. VBS/Bubbleboy is the very= first >worm that is able to infect without opening an attachment. The worm will >execute immediately after the user has opened the message in Microsoft >Outlook. > >As of Tuesday afternoon, Data Fellows had received no reports of this virus >being in the wild, and it is not considered a big threat. However, Data >Fellows >wishes to warn the public of this new infection mechanism. The worm propagates >as a Microsoft Outlook message. This message does not have a separate >attachment, but the worm code is included in the message itself. However,= if >active scripting is disabled, the worm will not work. The worm uses ActiveX >features to open Microsoft Outlook and uses it to send itself to all >recipients >in all address books, like the Melissa virus. > >The message contains the following: > > From: (name of infected user) > Subject: BubbleBoy is back! > Body: The BubbleBoy incident, pictures and sounds > >The reference to Bubbleboy and the above link are references to a character in >an episode of the TV show "Seinfeld". > >The receiver of the e-mail becomes infected and spreads the worm without >opening any attachment. The message does not contain any attachments. The mass >mailing is executed only once per infected machine.=20 > >After the mass mailing, the worm will display a message box with the following >text: > > System error, delete "UPDATE.HTA" from the startup folder to solve > the problem. > >Bubbleboy is only able to spread under Microsoft Outlook 98, Microsoft Outlook >2000 and Microsoft Outlook Express that comes with Internet Explorer 5. It >does >not replicate under Windows NT. Bubbleboy uses a known security hole in >Microsoft Outlook to create the local HTA file. > >Microsoft has more information on this problem available at: >http://www.microsoft.com/Security/Bulletins/MS99-032faq.asp=20 > >They also have a patch to fix this problem at: >http://www.microsoft.com/security/Bulletins/ms99-032.asp=20 > >More technical information and screenshots of the virus are available at: >http://www.DataFellows.com/v-descs/bubb-boy.htm > > >About Data Fellows Corporation > >Data Fellows is a leading developer of centrally managed, widely= distributed >security solutions. The company offers a full range of award-winning, >integrated anti-virus, file encryption and VPN solutions for workstations, >servers and gateways. F-Secure products and Framework are uniquely suited= for >delivery of Security as a Service=99 by enterprise IT departments as well= as a >wide range of partners including ISPs, outsourcing firms and ASPs. For the >end-user, Security as a Service is invisible, automatic, reliable,= always-on, >and up-to-date. For the administrator, Security as a Service means >policy-based >management, instant alerts, and centralized management of a >massively-distributed user base. =20 > >Founded in 1988, Data Fellows is listed on the Helsinki Stock Exchange. The >company is headquartered in Espoo, Finland with North American headquarters in >San Jose, California, as well as offices in Canada, Germany, China, France, >Japan and the United Kingdom. Data Fellows is supported by a network of= VARs >and Distributors in over 90 countries around the globe. > >For further information, please contact > >USA: > >Data Fellows Inc. >Mr. Dan Takata, Technical Support >Tel. +1 408 938 6700,=20 >Fax +1 408 938 6701=20 >E-mail: Dan.Takata@DataFellows.com > >Finland: > >Data Fellows Corporation >Mikko Hypp=F6nen, Manager, Anti-Virus Research=20 >PL 24 >FIN-02231 Espoo >Tel. +358 9 859 900,=20 >Fax. +358 9 8599 0599 >E-mail: Mikko.Hypponen@DataFellows.com > >http://www.DataFellows.com/ > >Mailing list policy > >You have previously expressed interest in our products, or have asked >to be included on one of our press release lists by personally giving us >your e-mail address for this purpose.Our mailing list are for the >exclusive use and the expressed purpose of Data Fellows and are not >sold or or given to third parties. > >If you no longer wish to receive our press releases, or your email address= =20 >has been added to our lists without your consent, you can unsubscribe at=20 >http://www.DataFellows.com/news/subscribe.html > >If you only wish to receive our press releases concerning viruses,=20 >please go to=20 >http://www.DataFellows.com/news/subscribe.html >and first unsubscribe from=20 >press-english-interest@lists.datafellows.com >and then subscribe to=20 >press-english-virus-announcement@lists.datafellows.com > >________________________________________________ > > Marita Nasman-Repo tel: +358 9 8599 0613 > Communicator fax : +358 9 8599 0599 > mobile: +358 40 517 4613 > > Data Fellows Corporation http://www.DataFellows.com=20 > > F-Secure products: Integrated Solutions for Enterprise Security >_________________________________________________ > > > > From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9911A" ========================================================================= Date: Mon, 1 Nov 1999 09:22:15 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: FW: Improved Epi Info 2000 BETA Version Available-October 22, 199 9 Comments: cc: "Meert, Jean Pierre" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Improved Epi Info 2000 BETA Version Available-October 22, 1999 A new BETA version of Epi Info 2000 is available to a limited number of interested persons. Instructions are given below for downloading it by FTP, with a password. The target date for release of a debugged and tested version is the first quarter of 2000. The BETA version is primarily for testing. It has many more features than the BETA version of July 1999, but still has bugs. We intend to provide better versions every few weeks as they are completed. Please see the "GUIDED TOUR" from the main menu for an introduction to the system. A list of features not yet implemented is provided below. The following are required to run the BETA: 1. Windows 95, 98, or NT 2. A reasonably fast computer, with at least 32 meg of RAM 3. At least 50 megabytes of free hard disk space. Recent enhancements to the database engine by Microsoft require that we install a much larger set of files than were previously distributed. The Microsoft Internet Explorer IS NO LONGER REQUIRED, as Epi Info provides a small, off-line browser. The BETA should not be relied upon for serious epidemiologic work, and should not be distributed to others for that purpose. To see the features of the system under development, install the BETA as recommended, and run the main menu, EPI2000.EXE. Click on the GUIDED TOUR button and then print the document that appears. The TOUR outlines the features that currently work. Please do not post the BETA or password on WWW sites or through other public channels, although we are making the password available through this e-mail. Out intention is to limit distribution of the BETA to those seriously interested in a first look at the Epi 2000 technology, but who can tolerate partial features and the bugs associated with development. Bug reports should be sent to epiinfo@cdc.gov . Since this is a BETA test, we are asking for bug reports, and a questionnaire is provided for this purpose via the button called BETA RESULTS on the main menu. The Epi Info HelpLine will receive comments about the system or resolve specific problems about installation, but cannot provide help in developing applications with the new system until it is released. Comments of a general nature or suggestions can be sent to Dr. Andy Dean at agd1@cdc.gov Instructions for Downloading the BETA Version of Epi Info 2000 (Realizing that it is incomplete and not ready for serious work) To download the Epi2000 BETA files you can use a Web browser like the Microsoft Internet Explorer or Netscape, or an FTP software package like WS_FTP or Rapid Filer. To use the Netscape or Internet Explorer browsers, click on the following address, which includes the password: ftp://epidemo:meds1998@sftp.cdc.gov/ftp/epidemo/pub/epi2000/ If this does not bring up your web browser, you can copy the address (URL) to the address window in the browser and press enter. As always, with the Internet, if the first attempt does not work, try again. This transmits the userid, the password, the ftp site, and the correct directory all in one line, and should bring up a list of 25 SETUP files that can be downloaded by clicking on one at a time. Be sure that they arrive on your system with the same names they have in the ftp site. Realizing that those with fast connections will not want to interact with 25 downloads, we have provided a SINGLE file called ALL_IN_1.ZIP that contains all 25 setup files, and can be downloaded as a single unit. After downloading ALL_IN_1.ZIP, it must be Unzipped using PKUNZIP.EXE, WINZIP.EXE or another "unzipping" program. This will yield the 25 setup files that can be installed by clicking on SETUP.EXE. NOTES ON DOWNLOADING WITH PARTICULAR BROWSERS OR FTP UTILITIES The Internet Explorer sometimes appends "(1)" or "(2)" to SETUP. Change the filenames back to SETUP when you are asked to designate the filename. Netscape displays portions of downloaded files having a W0? extension as text that resembles garbage. Ignore this, click on "SAVE AS" (under the "FILE" menu) and click OK and Netscape will save the file correctly. If you are using FTP software other than a browser, the information needed is: NAME: sftp.cdc.gov USERID: epidemo PASSWORD: meds1998 Uninstalling Previous Versions of Epi Info 2000 If you have a previous beta test version on the computer, uninstall it before installing the new one. From My Computer, find and run the UNINSTAL.EXE program within the directory containing Epi Info 2000. In some versions, the program may be called UNWISE.EXE instead. Installing Epi Info 2000 After the 25 files are in a temporary directory on your hard disk or on 25 diskettes, install the BETA system as follows: These instructions assume that the program called SETUP and the necessary files are either on diskettes or on your hard disk. From the STARTUP menu in Windows 95 or Windows NT, choose RUN and enter the location of your setup file and its name, as in "C:\TEMP\SETUP.EXE", or use the browse button on the RUN dialog to find and select the same file and then click OK. The password for installation is DEMOONLY You will be asked whether you want the English or Spanish installation. Although you can install in Spanish, the Spanish version of the programs is not yet ready, so it is best to choose "U.S. English." After the first batch of files is copied to your hard disk (by a Microsoft program that installs MDAC-the database components of Visual Basic), you will be asked to reboot the computer. In Windows 95 or 98, there may be a second reboot after installing DCOM. Be sure to allow this to happen. Do not install or run other programs before completing the installation. After the reboot(s), you will be asked (again) whether you want English or Spanish. Choose English, and the rest of the programs will be installed. After experimenting with the BETA, you will be able to UNINSTALL it by running the UNWISE.EXE program found in the same directory with Epi Info 2000. Running Epi Info 2000 After installation, use the Epi Info 2000 icon on the DESKTOP, the PROGRAMS menu under START, or the Windows Explorer to run EPI2000.EXE. Getting Acquainted When you see the menu of Epi Info 2000, click on the button called GUIDED TOUR. The GUIDED.HTM file that appears gives specific instructions for the most efficient way to get acqainted with the programs. We strongly recommend that you print the GUIDED TOUR document, using the PRINT button at the top of the screen, and then use the printed document as your guide through the system. The following list applied to the July beta version. Notes tell what has changed. 1. The CFREQ, CTABLES, and CMEANS statistics for complex samples-still not converted from Pascal. 2. The ability to change field or variable names or data types after a data table has been created and data have been entered--Done 3. Access to ODBC databases--Done 4. A RELATE command in Analysis--Done 5. Analytic features for nutritional databases-Both Importing and batch calculations are in NutStat, but NCHS new reference curves have not yet been released 6. A program for entering data from the screen for statistical calculations (like STATCALC from Epi Info for DOS)-Temporarily Statcalc for DOS is included as a convenience 7. Several features of Epi Map-Epi Map now uses MapObjects 2 from ESRI. Points as well as color/pattern and dot density maps can be displayed. A list of Internet map resources is provided as a help file. 8. Printing of questionnaires-Done (enough to try out) 9. A report generator for Analysis-Not done. May be postponed until Version 2, but improvements in the LIST command are in process. 10. Changes in the way Views are linked to data tables --Completed. Known Bugs and Deficiencies * There is not yet an importation method for related files and check programs from Epi 6 * The BeforeEntry feature in check code is under construction * The MERGE command is not yet implemented in Analysis * Improvements to control width of LIST output are being made in Analysis * ROUTEOUT does not work in Analysis * MATCH variables in the TABLES command do not work in Analysis * There are some difficulties with IF in Analysis * The WRITE command in Analysis does not always work * A method for inserting rather than appending commands generated from dialogs in check code or pgm code is being developed * MEANS in Analysis chokes on missing values * The GISRES.HTM file giving GIS resources is missing We hope that you enjoy testing the BETA version of Epi Info 2000, and look forward to receiving your detailed findings, either by email or by sending the database BETATEST.MDB file containing comments entered from the BETA RESULTS button on the main screen. We have established a 4-person testing and quality-control team led by Dr. Juan Zubieta. They are using modern automated testing software to supplement manual testing and are keeping a weekly bug tally as we approach the feature-complete stage. The manual is currently being edited and should be in better shape within a month. ========================================================================= Date: Tue, 2 Nov 1999 12:51:56 +0530 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: sandra Subject: epi-info help desk MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I am no longer receiving emails from the epi-info help desk. Has this service been discontinued Sandra ========================================================================= Date: Tue, 2 Nov 1999 08:05:51 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Helpdesk Subject: Re: epi-info help desk MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Hello Sandra, The Epi Info service is still available. If you have any questions please contact us. Epi Info Technical Support Centers for Disease Control Epidemiology Program Office 4770 Buford Highway MS/K74 Atlanta, GA 30341 Phone: (770) 488-8440 Fax: (770) 488-8456 epiinfo@cdc.gov -----Original Message----- From: sandra [mailto:sandra@DANPCB.ORG] Sent: Tuesday, November 02, 1999 2:22 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] epi-info help desk I am no longer receiving emails from the epi-info help desk. Has this service been discontinued Sandra ========================================================================= Date: Tue, 2 Nov 1999 06:14:59 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Tropical diseases guideline Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I apologize that this is not an Epi/Info-specific question. Can any of = you offer the name of a reference or two regarding guidlines for control = and prevention of tropical diseases? thank you, Matt Snell, MPH Epidemiologist St. Luke's Regional Medical Center Boise, ID 83712 snellm@slrmc.org ========================================================================= Date: Tue, 2 Nov 1999 14:09:08 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Tropical diseases guideline In-Reply-To: MIME-Version: 1.0 Matt Snell writes: >I apologize that this is not an Epi/Info-specific question. Can any of you >offer the name of a reference or two regarding guidlines for control and >prevention of tropical diseases? The APHA guide "Control of Communicable Diseases Manual" is a good little book. "Manson's Tropical Disease" is an encyclopaedic reference with much on control. A good all-round reference is "Epidemiology and Community Control of Disease in Warm Climate Countries" By Derek Robinson (Ed.). You also might like to look at some disease specific text such as Bruce Chwatt's "Essential Malariology". Mark -- Mark Myatt ========================================================================= Date: Tue, 2 Nov 1999 12:00:17 -0400 Reply-To: psalt@jbcc.harvard.edu Sender: Epi Info Discussion Group From: "Pat Salt, Ph.D." Organization: Judge Baker Children's Center Subject: printing on a network problem MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT We're finding that we are not able to print EPI6.04 over a network - has anyone solved this problem? We're running Windows95 and the output gets to the printer queue but not beyond (to actually be printed). Do we have to wait for EPI2000 or can EPI6.04 do this? Many thanks, ************ Pat Salt, Ph.D. Judge Baker Children's Center 3 Blackfan Circle Boston, MA 02115 617-232-8390, ext. 2223 psalt@jbcc.harvard.edu ========================================================================= Date: Wed, 3 Nov 1999 08:55:07 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: printing on a network problem Comments: To: psalt@jbcc.harvard.edu In-Reply-To: <199911021703.MAA11767@ackroyd.harvard.edu> MIME-Version: 1.0 Pat Salt, Ph.D. writes: >We're finding that we are not able to print EPI6.04 over a network - >has anyone solved this problem? We're running Windows95 and >the output gets to the printer queue but not beyond (to actually be >printed). Do we have to wait for EPI2000 or can EPI6.04 do this? I assume you mean ANALYSIS ... ROUTE PRINTER (F5) opens a connection to the printer and will not release it until ROUTE SCREEN. On a network that is when the print job is closed and the network printer server can get on with its work. Try: ROUTE PRINTER * * Your ANALYSIS commands * NEWPAGE ROUTE SCREEN That should work. On some networks ANALYSIS can stall the print server. It is best to use ROUTE filename.ext to save results and print these from an editor later. Mark -- Mark Myatt ========================================================================= Date: Wed, 3 Nov 1999 15:28:11 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert-Jean FREUND Subject: Un manuel d auto formation a EpiInfo en francais Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_941635691==_" --=====================_941635691==_ Content-Type: text/plain; charset="us-ascii" Cher membres francophones de la liste, Je viens de publier EPIINFO MENE L ENQUETE un manuel d auto formation a EpiInfo Ce petit livre (120 pages) permet d apprebdre a realiser une enquete de A a Z depuis la problemetique jusqu a la publication des resultats Le document joint donne une description detaillee de l ouvrage Le livre est disponible au prix de 150 FF (livre et CDROM) plus port ( 16 FF en France et selon tarif international a l etranger) Editions ENSP Av du Pr Leon Bernard F 35043 RENNES Cedex et pour en savoir plus : rjfreund@ensp.fr et http://editions.ensp.fr --=====================_941635691==_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="internet.txt" " EpiInfo m=E8ne l'enqu=EAte " Vous utilisez EpiInfo depuis plusieurs ann=E9e, mais vous n'avez jamais eu= le temps d'aller jusqu'au bout de son apprentissage complet.=20 Ce livre est fait pour vous : vous y d=E9couvrirez les =E9l=E9ments qui vous= manquent et utiliserez les fonctions avanc=E9es du logiciel dont vous= ignoriez l'existence. Vous d=E9couvrez EpiInfo et souhaitez pouvoir rapidement le ma=EEtriser : ce= livre est =E9galement fait pour vous . Vous proc=E9derez vous-m=EAme =E0= l'apprentissage progressif et complet de ce logiciel puissant, en fondant= votre progression sur la m=E9thodologie de l'enqu=EAte en sant=E9 publique. Con=E7u comme un manuel d'auto-apprentissage, EpiInfo m=E8ne l'enqu=EAte= vous permet d'acqu=E9rir les bases m=E9thodologiques pour mener a bien la= r=E9alisation de votre premi=E8re enqu=EAte. Le livre aborde successivement les th=E8mes suivants : =09 * L'analyse des principales causes d'=E9chec des enqu=EAtes * Les =E9tapes pr=E9liminaires : probl=E9matique, contexte, variables, buts= et objectifs de l'=E9tude=20 * Le calcul du nombre de sujets n=E9cessaires afin d'obtenir les r=E9sultats= avec une pr=E9cision suffisante pour pouvoir les utiliser. * La logique du logiciel EpiInfo pour produire l'outil de recueil des= donn=E9es * La construction technique du questionnaire * La cr=E9ation du fichier de donn=E9es * La programmation du contr=F4le de la qualit=E9 des donn=E9es en saisie * La saisie des donn=E9es en pratique=20 * La mise en =9Cuvre du plan d'analyse et l'=E9criture de programmes= d'analyse. ainsi que la strat=E9gie d'analyse * La production par programmation dans EpiInfo des tableaux et graphiques = ainsi que la r=E9alisation du rapport d'enqu=EAte en utilisant Word(r) et= Excel(r) * La compatibilit=E9 des bases de donn=E9es EpiInfo apr=E8s le passage =E0= l'an 2000 * Les nouveaut=E9s et caract=E9ristiques de la toute derni=E8re version= fran=E7aise compatible an 2000 EpiInfo 6.04c L'auteur, Robert FREUND, est =E9pid=E9miologiste, professeur =E0 l'Ecole= Nationale de la Sant=E9 Publique. Il est co-traducteur de EpiInfo version 5= et coordonnateur de la traduction de EpiInfo version 6. Le livre est fourni avec un CDROM qui comporte les fichiers d'exemples= n=E9cessaires =E0 l'auto-apprentissage ainsi que les logiciels EpInfo 6.04c= compatible an 2000 en version fran=E7aise, EpiMap version fran=E7aise et= de nombreux utilitaires, dont ceux n=E9cessaires pour assurer la= compatibilit=E9 an 2000. --=====================_941635691==_ Content-Type: text/plain; charset="us-ascii" \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| --=====================_941635691==_-- ========================================================================= Date: Fri, 5 Nov 1999 09:28:47 -0400 Reply-To: psalt@jbcc.harvard.edu Sender: Epi Info Discussion Group From: "Pat Salt, Ph.D." Organization: Judge Baker Children's Center Subject: Re: printing on network problem MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Thanks to all who responded to our problem printing over a network. Our system manager - with your suggetions - has more or less fixed the problem. Once again, coming to those who use it regularly has provided help. Thanks! ************ Pat Salt, Ph.D. Judge Baker Children's Center 3 Blackfan Circle Boston, MA 02115 617-232-8390, ext. 2223 psalt@jbcc.harvard.edu ========================================================================= Date: Fri, 5 Nov 1999 11:40:48 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: different .dbf files MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Yes, Epi 2000 will read FoxPro files for Analysis. -----Original Message----- From: Dimitri E Zylberstein [mailto:zed@ALGONET.SE] Sent: Saturday, October 16, 1999 7:22 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] different .dbf files We have been using Epi upon our aplication writen in Clipper 5 (DOS), now we have uppgraded to a Windows version writen in Fox Pro, also with .dbf files. But there ate problems, Epi sends a message "wrong dbf format". Some of the files are readible, those without additional .ftp file. What to do? Will Epi 2000 be able to read FP generated dbf files? Regards Dimitri Zylberstein ========================================================================= Date: Wed, 3 Nov 1999 17:48:04 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: zoher Subject: Re: Un manuel d auto formation a EpiInfo en francais MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Bravo Robert ! Tu as fini par le faire. Il y a actuellement une discussion tres animée sur Epi-info sue la liste de diffusion de nosobase : nosobase@cismrelais.univ-lyon.fr Bien ŕ toi Zoher Robert-Jean FREUND a écrit: > Cher membres francophones de la liste, > > Je viens de publier EPIINFO MENE L ENQUETE un manuel d auto formation a > EpiInfo > Ce petit livre (120 pages) permet d apprebdre a realiser une enquete de A a > Z depuis la problemetique jusqu a la publication des resultats > > Le document joint donne une description detaillee de l ouvrage > > Le livre est disponible au prix de 150 FF (livre et CDROM) plus port ( > 16 FF en France et selon tarif international a l etranger) > > Editions ENSP > Av du Pr Leon Bernard > F 35043 RENNES Cedex > > et pour en savoir plus : > rjfreund@ensp.fr et > http://editions.ensp.fr > > ------------------------------------------------------------------------ > > Name: internet.txt > internet.txt Type: Plain Text (text/plain) > Encoding: quoted-printable > > ------------------------------------------------------------------------ > > \\|// > (o o) > |-----------------o00o-(_)-o00o--------------------| > | Robert J.FREUND Epidemiologiste, Professeur | > | Ecole Nationale de la Sante Publique | > | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | > | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | > | rjfreund@ensp.fr http://www.ensp.fr | > |--------------------------------------------------| From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9910D" ========================================================================= Date: Fri, 22 Oct 1999 10:34:38 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: DO other have this EPIGLUE bug? MIME-Version: 1.0 When I use the VIEW command with the /NOEDIT option: VIEW FILENAME.TXT /NOECHO I get garbled printing. Remove the /NOEDIT and all is OK. Do others have this problem? Mark -- Mark Myatt ========================================================================= Date: Fri, 22 Oct 1999 18:22:19 +0200 Reply-To: joerg@burkowitz.de Sender: Epi Info Discussion Group From: Joerg Burkowitz Subject: analysis command options In-Reply-To: MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Dear Epi Info users, it seems, that in the new version 6.04c is it not possible to name a rec-file and a pgm-file in one command like analysis /c:\epi\data\data.rec c:\epi\data\run1.pgm How can I manage it instead in epiglue to read an data-file (with parameter %1) and run a specific pgm-file? Joerg ********************************* Dr. Joerg Burkowitz PO-Box 1203, 27296 Langwedel Germany e-mail: joerg@burkowitz.de ********************************* ========================================================================= Date: Fri, 22 Oct 1999 14:56:58 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: EPI GLUE DROP DOWN MENU LENGTH LIMITS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sorry, I can't think of any way to do this from outside the Pascal program. Looks like you have to invent some computer-abbreviated Russian. -----Original Message----- From: Sam Brown [mailto:sam@VECNATECH.COM] Sent: Thursday, October 21, 1999 4:06 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] EPI GLUE DROP DOWN MENU LENGTH LIMITS Anyone know whether there's a way in 6.04 to increase the width of drop down menus? I have some options that in Russian that take a bit more space to communicate than in good old computer-abbreviated English and I'm running out of room. The manual doesn't mention this in the epiglue chapter. I have in mind MENUITEM within a POPUP. Thanks for the help. ========================================================================= Date: Sun, 24 Oct 1999 15:18:52 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Gerald DAURAT Subject: Re: DO other have this EPIGLUE bug? MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I personnaly did not try the /NOECHO command, but the /NOEDIT command works well with Epi604 c (either English or French version) both on Win 3.11 and win 95. Gérald Daurat Montpellier France Mark Myatt a écrit: > When I use the VIEW command with the /NOEDIT option: > > VIEW FILENAME.TXT /NOECHO > > I get garbled printing. Remove the /NOEDIT and all is OK. Do others have > this problem? > > Mark > > -- > Mark Myatt ========================================================================= Date: Mon, 25 Oct 1999 08:02:41 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: epi 2000 epiglue, subscript out of range error MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit I'm hoping this isn't a feature (and let me know if I shouldn't be asking questions about Beta on this list). Environment: Dell Inspiron 3500 Win 98, Russian version, 1st edition July release of epi2000 beta I'm preparing a menu for a CD for Russian epidemiologists. To save time, I decided just to use epiglue 2000 and a new .MNU file (named them both install.*). I'm encountering a weird error under certain conditions when I load it from a CD or the A: drive; it works beautifully off the hard drive (single partition, named C:). If I click on install.exe alone, or if I try to run it from the "Run" dialogue, or from a DOS prompt (both as "install.exe" and as "install.exe install.mnu"), I get the following error. Runtime error '9': subscript out of range However, if I drag install.mnu and drop it on install.exe, it loads up and runs like a charm. I have tried it with and without the Epiinfo.ini file that it writes, with no change. I have tried it from protected and non-protected floppies in the A: drive, from a CDRW in DirectCD (active read-write) mode, from a pressed CDRW. The only thing that works is this drag and drop. Questions/requests: Anyone have any idea what that could be? Any easy fixes from authors? Any chance of a glance at the source code to try to figure it out? Any work arounds that don't fix the bug that people can think of? Thanks millions in advance. Sam Brown Harvard/Mechnikov ========================================================================= Date: Wed, 27 Oct 1999 11:06:32 +0200 Reply-To: maugat@ext.jussieu.fr Sender: Epi Info Discussion Group From: Sylvie Maugat Organization: C.CLIN Paris-Nord Subject: chk file MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------ADDBA3683B9535290B297592" Content-Transfer-Encoding: 8bit Il s'agit d'un message multivolet au format MIME. --------------ADDBA3683B9535290B297592 Content-Type: multipart/alternative; boundary="------------F409B1F89427F06312E070DF" --------------F409B1F89427F06312E070DF Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, I hope someone'll be able to help me with that ... - To change color of help message, I try to use Epi Info color code behind the text in my .CHK file (12). It doesn't work! Anyone known what can I do ? - To ask "Writerec?" before going to catheter file, I try to use GOTO writerec but it doesn't work ! Anyone know what can I do? MY PATIENT.CHK FILE : IGS2 RANGE 1 200 AFTER entry GOTO writerec HELP " Retour au DOSSIER PATIENT apres saisie des FICHES CATHETER. Tapez entree " 2 5 12 RELATE codpat d:\reacat\data\qkt.rec END END -- _________________________________________ Sylvie MAUGAT Epidémiologiste CCLIN Paris-Nord 15-21 rue de l'Ecole de Médecine 75006 PARIS Tel : 01 40 46 42 00 --------------F409B1F89427F06312E070DF Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,
I hope someone'll be able to help me with that ...

-  To change color of help message, I try to use Epi Info color code behind the text in my .CHK file (12). It doesn't work!
Anyone known what can I do ?

- To ask "Writerec?" before going to catheter file, I try to use GOTO writerec but it doesn't work !
Anyone know what can I do?

MY PATIENT.CHK FILE :
IGS2
  RANGE 1 200
  AFTER entry
 GOTO writerec
  HELP " Retour au DOSSIER PATIENT apres saisie des FICHES CATHETER. Tapez entree " 2 5 12
  RELATE codpat d:\reacat\data\qkt.rec
  END
END
 
 

--

_________________________________________

Sylvie MAUGAT
Epidémiologiste
CCLIN Paris-Nord
15-21 rue de l'Ecole de Médecine
75006 PARIS
Tel : 01 40 46 42 00
  --------------F409B1F89427F06312E070DF-- --------------ADDBA3683B9535290B297592 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Carte pour MAUGAT Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: MAUGAT n: ;MAUGAT email;internet: maugat@idf.ext.jussieu.fr x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard --------------ADDBA3683B9535290B297592-- From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9910C" ========================================================================= Date: Sat, 16 Oct 1999 13:21:38 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Dimitri E Zylberstein Subject: different .dbf files Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" We have been using Epi upon our aplication writen in Clipper 5 (DOS), now we have uppgraded to a Windows version writen in Fox Pro, also with .dbf files. But there ate problems, Epi sends a message "wrong dbf format". Some of the files are readible, those without additional .ftp file. What to do? Will Epi 2000 be able to read FP generated dbf files? Regards Dimitri Zylberstein ========================================================================= Date: Sun, 17 Oct 1999 17:57:27 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: hlimburg Subject: different .dbf files MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Epi-Info can read the FoxPro 2.8 (DOS version) DBF files without problems= , but cannot read the FoxPro 6.0 DBF files. You can solve this problem by copying the FoxPro file you want to read in Epi-Info to an Epi directory,= specifying the format of the DBF file. example: USE FoxPro directory\myfile COPY TO C:\Epi6\Data\myfile FOX2X Hans Limburg > = We have been using Epi upon our aplication writen in Clipper 5 (DOS), now= we have uppgraded to a Windows version writen in Fox Pro, also with .dbf files. But there ate problems, Epi sends a message "wrong dbf format". So= me of the files are readible, those without additional .ftp file. What to do? Will Epi 2000 be able to read FP generated dbf files? Regards Dimitri Zylberstein < ========================================================================= Date: Mon, 18 Oct 1999 13:15:55 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Boom, Iris de" Subject: compstat 2000 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BF195A.252CF070" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BF195A.252CF070 Content-Type: text/plain; charset="iso-8859-1" Dear Sir / Madame, The COMPSTAT 2000 conference of the ISI International Association for Statistical Computing will take place in Utrecht, the Netherlands from 21 - 25 August 2000. Statistical computing provides the link between statistical theory and applied statistics. As at previous Compstats, the scientific programme will cover all aspects of this link, from the development and implementation of new statistical ideas through to user experiences and software evaluation. The programme should appeal to anyone working in statistics and using computers, whether in universities, industrial companies, government agencies, research institutes or as software developers. The conference will be jointly organised by the Department of Methodology and Statistics of Utrecht University and the Department of Statistical Methods of Statistics Netherlands. Papers may be submitted in any of the following categories: - Statistical research - Development of statistical methodology, especially topics that rely on computers and computing environments. - Computing - Contributions of computer algorithms, tools and environments to the practice of statistics. - Applied statistics - Innovative applications of statistical computing in any area of current interest. Th deadline for submitting abstracts is 8 November 1999. For more information about COMPSTAT 2000, you can consult the attached Word-document, or visit or web site. The address is http://neon.vb.cbs.nl/rsm/compstat. Jelke Bethlehem (Statistics Netherlands) Peter van der Heijden (Utrecht University) ------_=_NextPart_000_01BF195A.252CF070 Content-Type: application/msword; name="compstat 2000.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="compstat 2000.doc" 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAOwAAAAAAAAAA EAAAPQAAAAEAAAD+////AAAAADoAAAD///////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////s pcEAcQATBAAACBK/AAAAAAAAEAAAAAAABAAAKCEAAA4AYmpianQrdCsAAAAAAAAAAAAAAAAAAAAA AAATBBYAIjIAABZBAQAWQQEAKB0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAF0AAAAAAAYBAAAAAAAABgEAAAYB AAAAAAAABgEAAAAAAAAGAQAAAAAAAAYBAAAAAAAABgEAABQAAAAAAAAAAAAAAHIBAAAAAAAAcgEA AAAAAAByAQAAAAAAAHIBAAAAAAAAcgEAAAwAAAB+AQAALAAAAHIBAAAAAAAADggAAOoAAAC+AQAA FgAAANQBAAAAAAAA1AEAAAAAAADUAQAAAAAAANQBAAAAAAAA1AEAAAAAAADUAQAAAAAAANQBAAAA AAAAjAUAAAIAAACOBQAAAAAAAI4FAAAAAAAAjgUAAC8AAAC9BQAADAEAAMkGAAAMAQAA1QcAACQA AAD4CAAA9AEAAOwKAABkAAAA+QcAABUAAAAAAAAAAAAAAAAAAAAAAAAABgEAAAAAAADUAQAAAAAA AAAAAAAAAAAAAAAAAAAAAADUAQAAAAAAANQBAAAAAAAA1AEAAAAAAADUAQAAAAAAAPkHAAAAAAAA 1AEAAAAAAAAGAQAAAAAAAAYBAAAAAAAA1AEAAAAAAAAAAAAAAAAAANQBAAAAAAAAvgEAAAAAAADU AQAAAAAAANQBAAAAAAAA1AEAAAAAAADUAQAAAAAAAAYBAAAAAAAA1AEAAAAAAAAGAQAAAAAAANQB AAAAAAAAjAUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGgEAACwAAABGAQAALAAAAAYBAAAAAAAABgEA AAAAAAAGAQAAAAAAAAYBAAAAAAAA1AEAAAAAAACMBQAAAAAAANQBAADQAgAA1AEAAAAAAACkBAAA HgAAAOIEAACiAAAABgEAAAAAAAAGAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAjAUAAAAAAADUAQAAAAAAAKoBAAAUAAAA4Bx25lgZ vwFyAQAAAAAAAHIBAAAAAAAA1AEAAAAAAACEBQAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQ29t cHN0YXQgMjAwMA0NTG9jYWwgYXJyYW5nZW1lbnRzDQ1UaGUgQ29tcHN0YXQgMjAwMCBjb25mZXJl bmNlIG9mIHRoZSBJU0kgSW50ZXJuYXRpb25hbCBBc3NvY2lhdGlvbiBmb3IgU3RhdGlzdGljYWwg Q29tcHV0aW5nIHdpbGwgdGFrZSBwbGFjZSBpbiBVdHJlY2h0LCB0aGUgTmV0aGVybGFuZHMgZnJv bSAyMSAtIDI1IEF1Z3VzdCAyMDAwLiANDVRoZSBjb25mZXJlbmNlIHdpbGwgYmUgam9pbnRseSBv cmdhbmlzZWQgYnkgdGhlIERlcGFydG1lbnQgb2YgTWV0aG9kb2xvZ3kgYW5kIFN0YXRpc3RpY3Mg b2YgIFV0cmVjaHQgVW5pdmVyc2l0eSBhbmQgdGhlIERlcGFydG1lbnQgb2YgU3RhdGlzdGljYWwg TWV0aG9kcyBvZiBTdGF0aXN0aWNzIE5ldGhlcmxhbmRzLiBUaGUgRGVwYXJ0bWVudCBvZiBNZXRo b2RvbG9neSBhbmQgU3RhdGlzdGljcyBvZiBVdHJlY2h0IFVuaXZlcnNpdHkgaGFzIGEgc3Ryb25n IGludm9sdmVtZW50IGluIHN0YXRpc3RpY2FsIGNvbXB1dGluZyBhbmQgYXBwbGllZCBzdGF0aXN0 aWNzLiBTdGF0aXN0aWNzIE5ldGhlcmxhbmRzIGlzIGFsc28ga25vd24gZm9yIGl0cyBleHBlcnRp c2UgaW4gYXBwbGllZCBzdGF0aXN0aWNzLCBhbmQgZm9yIGl0cyBpbm5vdmF0aXZlIGFwcHJvYWNo IGluIHRoZSBhcHBsaWNhdGlvbiBvZiByZWNlbnQgZGV2ZWxvcG1lbnRzIG9mIGluZm9ybWF0aW9u IHRlY2hub2xvZ3kgdG8gc3VydmV5IGRhdGEgY29sbGVjdGlvbiBhbmQgcHJvY2Vzc2luZy4NDUFw cHJveGltYXRlbHkgMzUga2lsb21ldHJlcyBzb3V0aCBvZiBBbXN0ZXJkYW0gVXRyZWNodCBzdGFu ZHMgaW4gdGhlIGhlYXJ0IG9mIHRoZSBOZXRoZXJsYW5kcy4gSXQgd2FzIGZvdW5kZWQgaW4gNDgg YnkgdGhlIFJvbWFucywgd2hvIGJ1aWx0IGEgbWlsaXRhcnkgc2V0dGxlbWVudCBhbG9uZyB0aGUg c2hvcmUgb2YgdGhlIFJoaW5lLiBJbiA2OTUgdGhlIEVuZ2xpc2ggQmVuZWRpY3RpbmUgbW9uayBX aWxsaWJyb3JkIGNhbWUgdG8gY2hyaXN0aWFuaXNlIEZyYW5ja3MgYW5kIEZyaXNpYW5zIGFuZCBt YWRlIFV0cmVjaHQgdG8gYSBjZW50cmUgb2YgcmVsaWdpb24sIHdoaWNoIGlzIHN0aWxsIG5vdGlj ZWFibGUgaW4gcHJlc2VudCB0aW1lcy4gRm9yIGNlbnR1cmllcywgVXRyZWNodCB3YXMgdGhlIGxh cmdlc3QgYW5kIG9ubHkgY2l0eSBvZiBpbXBvcnRhbmNlIGluIHRoZSBub3J0aGVybiBwYXJ0IG9m IHRoZSBOZXRoZXJsYW5kcy4gVG9kYXksIFV0cmVjaHQgaXMgYW4gYXR0cmFjdGl2ZSBjaXR5LiBX aXRoIDIzMCwwMDAgaW5oYWJpdGFudHMgVXRyZWNodCBpcyB0aGUgZm91cnRoIGxhcmdlc3QgY2l0 eSBpbiBUaGUgTmV0aGVybGFuZHMsIG9ubHkgQW1zdGVyZGFtLCBSb3R0ZXJkYW0gYW5kIFRoZSBI YWd1ZSBoYXZpbmcgZ3JlYXRlciBwb3B1bGF0aW9ucy4gV2l0aCBpdHMgbWFnbmlmaWNpZW50IGNh dGhlZHJhbCwgY2h1cmNoZXMsIGNhbmFscyBtdXNldW1zIGFuZCBoaXN0b3JpYyBidWlsZGluZ3Mg ZGF0aW5nIGZyb20gdGhlIDE2dGggY2VudHVyeSBvbndhcmRzIFV0cmVjaHQgaXMgYSBjaXR5IG9m IG91dHN0YW5kaW5nIGN1bHR1cmUuIEFzIGhvc3QgdG8gdGhlIGxhcmdlc3QgVW5pdmVyc2l0eSBp biBUaGUgTmV0aGVybGFuZHMgVXRyZWNodCBhbHNvIG9mZmVycyBhIGxpdmVseSBhbmQgdmFyaWVk IHNvY2lhbCBzY2VuZSB3aXRoIGJ1c3kgcmVzdGF1cmFudHMsIGNhZmVzLCBwdWJzIGFuZCBuaWdo dHNwb3RzLiBVdHJlY2h0IGlzIGVhc3kgcmVhY2hlZCBieSByb2FkIGFuZCByYWlsLiBEZWxlZ2F0 ZXMgZmx5aW5nIGludG8gQW1zdGVyZGFtIFNjaGlwaG9sIEFpcnBvcnQgY2FuIHRha2UgdGhlIHRy YWluIGZyb20gdGhlIGFpcnBvcnQgZGlyZWN0bHkgdG8gdGhlIGNlbnRyZSBvZiB0aGUgY2l0eS4g SWYgeW91IHdvdWxkIGxpa2UgdG8gZmluZCBvdXQgbW9yZSBhYm91dCBVdHJlY2h0IGFuZCBob3cg dG8gcmVhY2ggaXQgcGxlYXNlIHZpc2l0IHRoZSB3ZWJzaXRlLg0NVGhlcmUgd2lsbCBiZSBhIGZ1 bGwgcHJvZ3JhbW1lIG9mIHNvY2lhbCBldmVudHMgaW5jbHVkaW5nIGEgQnVmZmV0IFJlY2VwdGlv biwgQ29uY2VydCwgRGlubmVyIGFuZCBleGN1cnNpb25zLCB0byBhbGxvdyBwYXJ0aWNpcGFudHMg dG8gZXhjaGFuZ2UgaWRlYXMsIG1lZXQgZnJpZW5kcyBhbmQgc2VlIG1hbnkgb2YgdGhlIGxvY2Fs IGF0dHJhY3Rpb25zLiANDVNjaWVudGlmaWMgUHJvZ3JhbW1lDQ1TdGF0aXN0aWNhbCBjb21wdXRp bmcgcHJvdmlkZXMgdGhlIGxpbmsgYmV0d2VlbiBzdGF0aXN0aWNhbCB0aGVvcnkgYW5kIGFwcGxp ZWQgc3RhdGlzdGljcy4gQXMgYXQgcHJldmlvdXMgQ29tcHN0YXRzLCB0aGUgc2NpZW50aWZpYyBw cm9ncmFtbWUgd2lsbCBjb3ZlciBhbGwgYXNwZWN0cyBvZiB0aGlzIGxpbmssIGZyb20gdGhlIGRl dmVsb3BtZW50IGFuZCBpbXBsZW1lbnRhdGlvbiBvZiBuZXcgc3RhdGlzdGljYWwgaWRlYXMgdGhy b3VnaCB0byB1c2VyIGV4cGVyaWVuY2VzIGFuZCBzb2Z0d2FyZSBldmFsdWF0aW9uLiBUaGUgcHJv Z3JhbW1lIHNob3VsZCBhcHBlYWwgdG8gYW55b25lIHdvcmtpbmcgaW4gc3RhdGlzdGljcyBhbmQg dXNpbmcgY29tcHV0ZXJzLCB3aGV0aGVyIGluIHVuaXZlcnNpdGllcywgaW5kdXN0cmlhbCBjb21w YW5pZXMsIGdvdmVybm1lbnQgYWdlbmNpZXMsIHJlc2VhcmNoIGluc3RpdHV0ZXMgb3IgYXMgc29m dHdhcmUgZGV2ZWxvcGVycy4gDQ1QYXBlcnMgbWF5IGJlIHN1Ym1pdHRlZCBpbiBhbnkgb2YgdGhl IGZvbGxvd2luZyBjYXRlZ29yaWVzOg1TdGF0aXN0aWNhbCByZXNlYXJjaCAtIERldmVsb3BtZW50 IG9mIHN0YXRpc3RpY2FsIG1ldGhvZG9sb2d5LCBlc3BlY2lhbGx5IHRvcGljcyB0aGF0IHJlbHkg b24gY29tcHV0ZXJzIGFuZCBjb21wdXRpbmcgZW52aXJvbm1lbnRzLg1Db21wdXRpbmcgLSBDb250 cmlidXRpb25zIG9mIGNvbXB1dGVyIGFsZ29yaXRobXMsIHRvb2xzIGFuZCBlbnZpcm9ubWVudHMg dG8gdGhlIHByYWN0aWNlIG9mIHN0YXRpc3RpY3MuDUFwcGxpZWQgc3RhdGlzdGljcyAtIElubm92 YXRpdmUgYXBwbGljYXRpb25zIG9mIHN0YXRpc3RpY2FsIGNvbXB1dGluZyBpbiBhbnkgYXJlYSBv ZiBjdXJyZW50IGludGVyZXN0Lg0NVGhlIHNjaWVudGlmaWMgcHJvZ3JhbW1lIHdpbGwgY29uc2lz dCBvZiBhIHZhcmlldHkgb2Ygc2Vzc2lvbnMsIHN1Y2ggYXMgcGFyYWxsZWwgYW5kIHBsZW5hcnkg cHJlc2VudGF0aW9ucywgaW52aXRlZCBhbmQgY29udHJpYnV0ZWQgcGFwZXJzLCBwb3N0ZXIgc2Vz c2lvbnMsIG9uZSBvciB0d28gdHV0b3JpYWxzLCBhbmQgc29mdHdhcmUgZGVtb25zdHJhdGlvbnMu IA1UaGUgU2NpZW50aWZpYyBQcm9ncmFtbWUgQ29tbWl0dGVlIHNlZWtzIHBhcGVycyB0b3VjaGlu ZyBvbiBhbGwgYXNwZWN0cyBvZiBjb21wdXRhdGlvbmFsIHN0YXRpc3RpY3MuIFRoaXMgaW5jbHVk ZXMgdGhlb3J5LCBhcHBsaWNhdGlvbnMsIGFuZCBpbXBsZW1lbnRhdGlvbnMuIA1UaGUgU2NpZW50 aWZpYyBQcm9ncmFtbWUgQ29tbWl0dGVlIGFsc28gd2VsY29tZXMgcGFwZXJzIGluIHRoZSBmaWVs ZCBvZiBPZmZpY2lhbCBTdGF0aXN0aWNzLCBpLmUuIHBhcGVycyBpbiB0aGUgZmllbGQgb2YgZGF0 YSBjb2xsZWN0aW9uLCBkYXRhIGVkaXRpbmcsIGRhdGEgYW5hbHlzaXMsIGFuZCBkYXRhIHB1Ymxp Y2F0aW9ucy4gDQ1QYXBlcnMgbWF5IGJlIHNlbGVjdGVkIGJ5IHRoZSBTY2llbnRpZmljIFByb2dy YW1tZSBDb21taXR0ZWUgYXMgZnVsbCBjb250cmlidXRpb25zLCBzaG9ydCBjb250cmlidXRpb25z IG9yIHBvc3RlcnMuIFNlbGVjdGlvbiBpcyBiYXNlZCBvbiBzdWJtaXR0ZWQgYWJzdHJhY3RzIG9m IHVwIHRvIHR3byBwYWdlcy4gVGhlc2Ugc2hvdWxkIGluY2x1ZGUgdGhlIG1haW4gcmVzdWx0cyBh bmQgcmVmZXJlbmNlcywgaGlnaGxpZ2h0aW5nIG5vdmVsIGFzcGVjdHMgYW5kIGluZGljYXRpbmcg dGhlaXIgcmVsZXZhbmNlIHRvIHRoZSBhYm92ZSBtZW50aW9uZWQgdGhyZWUgY2F0ZWdvcmllcy4g RnVydGhlciBkZXRhaWxzIGFuZCBzYW1wbGUgYWJzdHJhY3QgZm9ybWF0cyBjYW4gYmUgZm91bmQg b24gdGhlIHdlYnNpdGUuIEZ1bGwgY29udHJpYnV0aW9ucyB3aWxsIGJlIHJlZmVyZWVkIGFuZCBw dWJsaXNoZWQsIHdpdGggdGhlIGludml0ZWQgcGFwZXJzLCBpbiBhIHZvbHVtZSBvZiAgUHJvY2Vl ZGluZ3MgYnkgUGh5c2ljYSBWZXJsYWcuIFNob3J0IGNvbW11bmljYXRpb25zIGFuZCBwb3N0ZXJz IHdpbGwgYmUgcHVibGlzaGVkIGluIGEgMm5kIHZvbHVtZSBieSBTdGF0aXN0aWNzIE5ldGhlcmxh bmRzIGFuZCBVdHJlY2h0IHVuaXZlcnNpdHkuDQ1BdCB0aGUgY29uZmVyZW5jZSwgc2V2ZXJhbCBw cmljZXMgd2lsbCBiZSBhd2FyZGVkOiANVGhyZWUgcHJpY2VzLCBlYWNoIHdvcnRoIDEwMDAgRHV0 Y2ggR3VpbGRlcnMsIHdpbGwgYmUgYXdhcmRlZCBmb3IgdGhlIGJlc3QgdGhyZWUgY29udHJpYnV0 aW9ucyBzdWJtaXR0ZWQgYW5kIHByZXNlbnRlZCBieSB5b3VuZyBwYXJ0aWNpcGFudHMgKHVwcGVy IGFnZSBsaW1pdCAzNSB5ZWFycyBmb3IgYWxsIGF1dGhvcnMgb24gQXVndXN0IDMxLCAyMDAwKS4g DUEgcHJpY2Ugd2lsbCBiZSBhd2FyZGVkIGZvciB0aGUgYmVzdCBwb3N0ZXIgcHJlc2VudGF0aW9u LiANDUludml0ZWQgc3BlYWtlcnMNDUtleW5vdGUgc3BlYWtlcnMNRG9uYWxkIFJ1YmluIChUaGUg YnJvYWQgcm9sZSBmb3IgbXVsdGlwbGUgaW1wdXRhdGlvbiBpbiBzdGF0aXN0aWNhbCBzY2llbmNl KSwgYW5kDVBldGVyIEtvb2ltYW4gKE1hc3MgaW1wdXRhdGlvbiB2ZXJzdXMgc2VxdWVudGlhbCB3 ZWlnaHRpbmcgb2YgYSB2aXJ0dWFsIGNlbnN1cykNQXQgdGhlIG1vbWVudCBpbnZpdGVkIHNwZWFr ZXJzIGluY2x1ZGUNTm9lbCBDcmVzc2llIChTcGFjZS10aW1lIEthbG1hbiBmaWx0ZXJpbmcgYW5k IE1DTUMpLCANQW50b2luZSBkZSBGYWxndWVyb2xsZXMgKGdlbmVyYWxpemVkIGxpbmVhciBtb2Rl bHMgd2l0aCBiaWxpbmVhciB0ZXJtcyksDURhdmlkIERyYXBlciAoQ29tcHV0YXRpb25hbCBpc3N1 ZXMgaW4gTUNNQyBmaXR0aW5nIG9mIG11bHRpbGV2ZWwgbW9kZWxzKSwgDURhdmlkIEhhbmQgKE1l dGhvZG9sb2dpY2FsIGlzc3VlcyBpbiBkYXRhIG1pbmluZykNR2VvcmdlcyBIZWJyYWlsIChQcmFj dGljYWwgZGF0YSBtaW5pbmcgaW4gYSBsYXJnZSB1dGlsaXR5IGNvbXBhbnkpLCANWW91bmdqbyBM ZWUgKEFuYWx5c2lzIG9mIGNvcnJlbGF0ZWQgbm9uLUdhdXNzaWFuIGRhdGEgdmlhIGhpZXJhcmNo aWNhbCBnZW5lcmFsaXplZCBsaW5lYXIgbW9kZWxzKSwgDUhlbG11dCBMdWV0a2Vwb2hsIChCb290 c3RyYXBwaW5nIGltcHVsc2UgcmVzcG9uc2VzIGluIFZBUiBhbmFseXNlcyksIA1BZ3VzdGluIE1h cmF2YWxsIChTb21lIGFwcGxpY2F0aW9ucyBvZiB0aGUgc2lnbmFsIGV4dHJhY3Rpb24gdGVjaG5p cXVlIHRvIHNvY2lvZWNvbm9taWMgdGltZSBzZXJpZXMpLCANRXJpY2ggTmV1d2lydGggKFNwcmVh ZHNoZWV0cyBpbiBzdGF0aXN0aWNhbCBlZHVjYXRpb24pLCANV2FsdGVyIFJhY3Vnbm8gKEJheWVz IGZhY3RvcnMgZm9yIG1vZGVsIHNlbGVjdGlvbiBhbmQgcHJlZGljdGlvbikgDUhhbnMgdmFuIEhv dXdlbGluZ2VuIChOb25wcm9wb3J0aW9uYWwgaGF6YXJkcyBtb2RlbHMgaW4gc3Vydml2YWwgYW5h bHlzaXMpLCANQXJpIFZlcmJ5bGEgKFNwYXRpby10ZW1wb3JhbCBtb2RlbGxpbmcpLA1QbGVhc2Ug Y2hlY2sgb3VyIGhvbWUgcGFnZSBmb3IgdGhlIGxhdGVzdCBhbmQgbW9yZSBkZXRhaWxlZCBpbmZv cm1hdGlvbi4NDQ1Tb2Z0d2FyZSBkZW1vbnN0cmF0aW9uIGFuZCBib29rIGV4aGliaXRpb24NDVRo ZXJlIHdpbGwgYmUgZGVtb25zdHJhdGlvbiBzdGFuZHMgZm9yIHNvZnR3YXJlIHByb2R1Y2VycyB0 byBwcmVzZW50IHRoZWlyIHByb2R1Y3RzLCBhbmQgYm9vayBleGhpYml0aW9ucy4NIA0NSW1wb3J0 YW50IGRlYWRsaW5lcw0NQWJzdHJhY3RzIHJlY2VpdmVkIChwb3N0IG9yIGUtbWFpbCk6CTggTm92 ZW1iZXIgMTk5OSAgIA1Ob3RpZmljYXRpb24gdG8gYXV0aG9yczoJCTE1IERlY2VtYmVyIDE5OTkN Q29udHJpYnV0ZWQgcGFwZXIgZm9yIHJlZmVyZWVpbmc6CTExIE1hcmNoIDIwMDANRmluYWwgdmVy c2lvbnMgb2YgY29udHJpYnV0ZWQgcGFwZXJzCTEgTWF5IDIwMDAgDVNob3J0IGNvbW11bmljYXRp b25zIGFuZCBwb3N0ZXJzOgkxIE1heSAyMDAwDQ0NTG9jYWwgT3JnYW5pc2luZyBDb21taXR0ZWUN DVdpbSBKYW5zZW4gLCBDaGFpciAoVXRyZWNodCBVbml2ZXJzaXR5KQ1Eb3V3ZSB2YW4gZGVyIFNs dWlzIChOZXRoZXJsYW5kcyBTb2NpZXR5IGZvciBTdGF0aXN0aWNzIGFuZCBPcGVyYXRpb24gcmVz ZWFyY2gpDUdlcnJpdCBTdGVtZXJkaW5rIChJU0kpDUxlb25pZWtlIFdpam5nYWFyZHMgKFV0cmVj aHQgVW5pdmVyc2l0eSkNDQ1TY2llbnRpZmljIFByb2dyYW1tZSBDb21taXR0ZWUNDVBldGVyIHZh biBkZXIgSGVpamRlbiwgTmV0aGVybGFuZHMsIENoYWlyDUplbGtlIEJldGhsZWhlbSwgTmV0aGVy bGFuZHMNQW5kcmVqIEJsZWplYywgU2xvdmVuaWENV29sZmdhbmcgSGFlcmRsZSwgR2VybWFueQ1S b2dlciBQYXluZSwgVW5pdGVkIEtpbmdkb20NQ2hyaXN0aWFuIFJvYmVydCwgRnJhbmNlDVJvYmVy dGEgU2ljaWxpYW5vLCBJdGFseQ0NDVJlZ2lzdHJhdGlvbiBmZWVzDQ1FYXJseSBSZWdpc3RyYXRp b247IGRlYWRsaW5lID0gMSBBcHJpbCAyMDAwLA1JQVNDL0lTSS9PdGhlciBBcHByb3ZlZAlOTEcg NjUwLDAwDU90aGVycwkJCQlOTEcgNzUwLDAwDQ1TdGFuZGFyZCBSZWdpc3RyYXRpb247IGRlYWRs aW5lID0gMjEgSnVuZSAyMDAwLA1JQVNDL0lTSS9PdGhlciBBcHByb3ZlZAlOTEcgNzUwLDAwDU90 aGVycwkJCQlOTEcgODUwLDAwDQ1MYXRlIFJlZ2lzdHJhdGlvbjsgDWFmdGVyIDIxIEp1bmUgIDIw MDAJCU5MRyA5NTAsMDANDVN0dWRlbnRzIChzZW5kIGluIGRvY3VtZW50IG9mIFVuaXZlcnNpdHkg UmVnaXN0cmF0aW9uKSBOTEcgMTUwLDAwDQ0NQWRkcmVzcyBmb3IgY29ycmVzcG9uZGVuY2ULDUZC VSBDb25ncmVzcyBCdXJlYXUNVXRyZWNodCBVbml2ZXJzaXR5C0F0dG46IE1ycy4gTWFyY2VsbGUg QnVtYQtQLk8uIEJveCA4MDEyNQszNTA4IFRDIFV0cmVjaHQLVGhlIE5ldGhlcmxhbmRzIAsLUGhv bmU6ICszMSAzMCAyNTMgMjcyOAtGYXg6IAkrMzEgMzAgMjUzIDU4NTELRS1tYWlsOiBjb21wc3Rh dEBmYnUudXUubmwgDQ1Gb3IgbW9yZSBpbmZvcm1hdGlvbiBhbmQgZm9yIHJlZ2lzdHJhdGlvbiBz ZWUNd2Vic2l0ZTogaHR0cDovL25lb24udmIuY2JzLm5sL3JzbS9jb21wc3RhdA0NVG8gZW5zdXJl IHRoYXQgeW91IHJlY2VpdmUgZnVydGhlciBpbmZvcm1hdGlvbiwgDXBsZWFzZSBzZW5kIGFuIGVt YWlsIHRvIBMgSFlQRVJMSU5LIG1haWx0bzpjb21wc3RhdEBmYnUudXUubmwgARRjb21wc3RhdEBm YnUudXUubmwVLA1vciBhIGxldHRlciB0byB0aGUgYWRkcmVzcyBhYm92ZS4NDQ0NDQ0NAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAA4EAAAPBAAAIgQAAIkM AACeDAAAyg4AAN8OAABODwAAVw8AALYPAADIDwAAEBYAACEWAACLGgAAtxoAACUbAAA5GwAALRwA AEkcAAAEHQAAJB0AAE0dAABOHQAA7R0AAAAeAABIHwAAZB8AAAogAAAcIAAAwyAAAMQgAADpIAAA 6iAAAOsgAAD9IAAA/iAAACghAAAA/fn9+f31/fX99f35/fn9+f35/fn9+f35/fn98P3p/d/p3On9 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEMEoPAAATAgiBA2oAAAAABggBQ0oYAFUIAQ0DagAAAABD ShgAVQgBCDBKDwBDShgAAAc2CIFDShgABzUIgUNKGAAEQ0oYACUABAAADgQAAA8EAAAiBAAAIwQA AMYEAADHBAAA5QYAAOYGAAC7CwAAvAsAAIgMAACJDAAAngwAAJ8MAACNDgAAjg4AAMoOAABODwAA tg8AAB0QAAAeEAAA7xAAAI4RAABNEgAAThIAANIUAADTFAAABxUAAP0AAAAAAAAAAAAAAAD7AAAA AAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAA AAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7 AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAA AAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAA AAD2AAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAPEAAAAAAAAAAAAAAADxAAAAAAAAAAAAAAAA8QAA AAAAAAAAAAAAAPEAAAAAAAAAAAAAAADxAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAPEAAAAAAAAA AAAAAAAAAAUAAAomDAtGAAAFAAAKJgALRgEAAAEAAAABAQAAHAAEAAAOBAAADwQAACIEAAAjBAAA xgQAAMcEAADlBgAA5gYAALsLAAC8CwAAiAwAAIkMAACeDAAAnwwAAI0OAACODgAAyg4AAE4PAAC2 DwAAHRAAAB4QAADvEAAAjhEAAE0SAABOEgAA0hQAANMUAAAHFQAA1BUAAA8WAAAQFgAAIRYAACIW AAAzFgAAhRYAANUWAAD8FgAA/Pn28/Dt6ufk4d7b2NXSz8zGvrayrqqmop6alo6Ggn56dm5mYgAA AAAAAAAHBivt//8HDA8Ge+3//wgBAAkBCgYAAAAPBs3t//8IAQAJAQoFAAAABwbe7f//BwwHBt/t //8HDAcG8O3//wcMBwbx7f//BwwPBizu//8IAgAJAQoEAAAADwb57v//CAIACQEKAwAAAAcGLe// /wcMBwYu7///BwwHBrLx//8HDAcGs/H//wcMBwZy8v//BwwHBhHz//8HDAcG4vP//wcMBwbj8/// BwwPBkr0//8IAQAJAQoCAAAADway9P//CAEACQEKAQAAAAoGNvX//wgBAAkBAAUGcvX//wUGc/X/ /wUGYff//wUGYvf//wUGd/f//wUGePf//wUGRPj//wUGRfj//wUGGv3//wUGG/3//wUGOf///wUG Ov///wUG3f///wUG3v///wUG8f///wUG8v///wUCAQAFAAAlBxUAANQVAAAPFgAAEBYAACEWAAAi FgAAMxYAAIUWAADVFgAA/BYAADIXAAB7FwAAxhcAAPgXAAA9GAAAoRgAAOcYAABOGQAAhxkAAMoZ AAAXGgAAQBoAAIkaAACKGgAAixoAALYaAAC3GgAAIhsAAPoAAAAAAAAAAAAAAAD6AAAAAAAAAAAA AAAA9QAAAAAAAAAAAAAAAPUAAAAAAAAAAAAAAAD1AAAAAAAAAAAAAAAA9QAAAAAAAAAAAAAAAPAA AAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA9QAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAA AAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAA APAAAAAAAAAAAAAAAADwAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAPAAAAAAAAAAAAAAAADwAAAA AAAAAAAAAAAA8AAAAAAAAAAAAAAAAO4AAAAAAAAAAAAAAADuAAAAAAAAAAAAAAAA7gAAAAAAAAAA AAAAAO4AAAAAAAAAAAAAAADuAAAAAAAAAAAAAAAA7gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AQAABQAACiYAC0YBAAUAAAomDAtGAAAFAAAKJgALRgIAABv8FgAAMhcAAHsXAADGFwAA+BcAAD0Y AAChGAAA5xgAAE4ZAACHGQAAyhkAABcaAABAGgAAiRoAAIoaAACLGgAAthoAALcaAAAiGwAAJBsA ACUbAAA5GwAAOhsAAHIbAACdGwAAzRsAAP4bAAArHAAALBwAAC0cAABIHAAASRwAAHEcAADBHAAA 2RwAAAIdAAADHQAABB0AACMdAAAkHQAATh0AAGsdAACDHQAAnR0AALkdAADSHQAA6x0AAOwdAADt HQAA/x0AAAAeAAAtHgAAUB4AAGUeAABmHgAAlh4AALkeAADOHgAAzx4AAOMeAAADHwAABB8AAEYf AABHHwAASB8AAGQfAAB4HwAAHiAAAB8gAABNIAAAeSAAAHogAACrIAAAACEAACIhAAAjIQAAJCEA ACUhAAAmIQAAJyEAACghAAD37+ff3Nzc3Nzc3NwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAUIAQAJAQ8GOuz//wgBAAkBCgoAAAAPBoXs//8IAQAJAQoJAAAA DwbO7P//CAEACQEKCAAAAA8GBO3//wgBAAkBCgcAAAAAUCIbAAAkGwAAJRsAADkbAAA6GwAAchsA AJ0bAADNGwAA/hsAACscAAAsHAAALRwAAEgcAABJHAAAcRwAAMEcAADZHAAAAh0AAAMdAAAEHQAA Ix0AACQdAABOHQAAax0AAIMdAACdHQAAuR0AANIdAADrHQAA7B0AAP0AAAAAAAAAAAAAAAD9AAAA AAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAA AAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9 AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAA AAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAA AAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAA AAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAA AAAAAAD9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAd7B0AAO0dAAD/HQAAAB4AAC0eAABQHgAA ZR4AAGYeAACWHgAAuR4AAM4eAADPHgAA4x4AAAMfAAAEHwAARh8AAEcfAABIHwAAZB8AAHgfAAAe IAAAHyAAAE0gAAB5IAAAeiAAAKsgAAAAIQAAIiEAACMhAAAkIQAA/QAAAAAAAAAAAAAAAP0AAAAA AAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAA AAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0A AAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAA AAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAA AP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAA AAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAA AAAAAP0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAB0kIQAAJSEAACYhAAAnIQAAKCEAAP0AAAAA AAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAABCAAHFABAB+wgi4gsMZBIbCJBSKwiQUjkIkF JJCJBSWwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAzwAAAEQAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0Mnqefm6zhGMggCqAEup CwIAAAAXAAAAEwAAAGMAbwBtAHAAcwB0AGEAdABAAGYAYgB1AC4AdQB1AC4AbgBsAAAA4Mnqefm6 zhGMggCqAEupCzQAAABtAGEAaQBsAHQAbwA6AGMAbwBtAHAAcwB0AGEAdABAAGYAYgB1AC4AdQB1 AC4AbgBsAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAEAAKAAEAWwAPAAIAAwAAAAMAOgAAQPH/AgA6AAAACQBT AHQAYQBuAGQAYQBhAHIAZAAAAAIAAAAUAENKFgBPSgAAUUoAAGtIECdtSBMELAABQAEAAgAsAAAA BQBLAG8AcAAgADEAAAAIAAEABiQBQCYABwA1CIFDShgAAAAAAAAAAAAAAAAAAAAAAABEAEFA8v+h AEQAAAAaAFMAdABhAG4AZABhAGEAcgBkAGEAbABpAG4AZQBhAC0AbABlAHQAdABlAHIAdAB5AHAA ZQAAAAAAAAAAAAAAAAAoAFVAogDxACgAAAAJAEgAeQBwAGUAcgBsAGkAbgBrAAAABgA+KgFCKgIA AAAAKB0AAAQAADIAAAAA/////wQAAAAEIP//AQAAAAAAACD//wIAAAAAAAQg//8DAAAAAAAAIP// BAAAAAAAAAAAALYLAACJFgAAAxsAACgdAAAAAGcAAAABAAEAAAACAAEAAAADAAAAAAAABAAAKCEA ABEAAAAABAAABxUAACIbAADsHQAAJCEAACghAAASAAAAFAAAABYAAAAXAAAAGAAAAAAEAAD8FgAA KCEAABMAAAAVAAAAwxwAAOocAAD9HAAAKB0AABNYFP8VgP//FAAAAAMATQBCAFUAHABDADoAXABX AEkATgBEAE8AVwBTAFwAVABFAE0AUABcACQAVwBQAE0ANgAzAEUANQAuAGQAbwBjAAMATQBCAFUA HABDADoAXABXAEkATgBEAE8AVwBTAFwAVABFAE0AUABcACQAVwBQAE0ANgAzAEUANQAuAGQAbwBj AAMATQBCAFUAEgBBADoAXABmAG8AbABkAGUAcgB0AGUAawBzAHQALgBkAG8AYwAJAEQAZQBuACAA RAByAGEAYQBrAC0AQwA6AFwARABPAFMAXABBAHUAdABvAEgAZQByAHMAdABlAGwALQB2AGUAcgBz AGkAZQAgAHYAYQBuACAAZgBvAGwAZABlAHIAdABlAGsAcwB0AC4AYQBzAGQACQBEAGUAbgAgAEQA cgBhAGEAawASAEEAOgBcAGYAbwBsAGQAZQByAHQAZQBrAHMAdAAuAGQAbwBjAAkARABlAG4AIABE AHIAYQBhAGsAEgBBADoAXABmAG8AbABkAGUAcgB0AGUAawBzAHQALgBkAG8AYwAJAEQAZQBuACAA RAByAGEAYQBrABIAQQA6AFwAZgBvAGwAZABlAHIAdABlAGsAcwB0AC4AZABvAGMADQBNAGEAcgBj AG8AIABWAGUAcgBoAGEAYQByADYAXABcAEIAdQByAF8AZgBiAHUAXABTAFkAUwBcAFUAUwBFAFIA UwBcAEMAQgBcAFAAcgBvAGoAZQBjAHQAbABlAGkAZABlAHIAcwBcAEEARABFAFwARgBPAEwARABF AFIAVABFAC4ARABPAEMABwBJAGQAZQBCAG8AbwBtABIAQQA6AFwAZgBvAGwAZABlAHIAdABlAGsA cwB0AC4AZABvAGMABwBJAGQAZQBCAG8AbwBtABQAQQA6AFwAYwBvAG0AcABzAHQAYQB0ACAAMgAw ADAAMAAuAGQAbwBjAAEA/v//////////D/8P/w//D/8P/w//D/8P/w8BAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAABACoAAgAAAP7///8AAAAAZFjoAAEAAAD+////AAAAALhY6AABAAAA//// /3BY6AAgAAAAAQAAABdAAAAAAAAAAAAAAAAAAABoAQAACwgAAA+EaAERhJj+T0oBAFFKAQBvKAAB ALfw/////8RY6AAgAAAAAAAAABdAAAAAAAAAAAAAAAAAAABoAQAACwgAAA+E0AIRhJj+T0oBAFFK AQBvKAABALfw//8BAAAAAAD/QFxcRkJVMDJcQ0IwMUhQSkw0AE5lMDA6AHdpbnNwb29sAEhQIExh c2VySmV0IDQAXFxGQlUwMlxDQjAxSFBKTDQAAAAAAAAAAAAAAAAAAAABBAEDnABwAANjAQABAAkA AAAAAAAAAQAPAFgCAgABAFgCAgAAAEE0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAD///// JQMAAAAAAAD//////////wAAAgAEABEA//8AAP//AAABAP//AQABAAAA//8BAAIA//////////// ////////////////////////////AAAAABgAAAAAABAnECcQJwAAECcAAAAAAAAAAFxcRkJVMDJc Q0IwMUhQSkw0AAAAAAAAAAAAAAAAAAAAAQQBA5wAcAADYwEAAQAJAAAAAAAAAAEADwBYAgIAAQBY AgIAAABBNAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAA/////yUDAAAAAAAA//////////8A AAIABAARAP//AAD//wAAAQD//wEAAQAAAP//AQACAP////////////////////////////////// /////wAAAAAYAAAAAAAQJxAnECcAABAnAAAAAAAAAAAAgAEAAAAAAAAAAACcUegAAQAAAAAAAAAA AAAAAAAAAAAAAAACEAAAAAAAAAAoHQAAQAAACABAAAAEAAAARxaQAQAAAgIGAwUEBQIDBIcCAAAA AAAAAAAAAAAAAACfAAAAAAAAAFQAaQBtAGUAcwAgAE4AZQB3ACAAUgBvAG0AYQBuAAAANRaQAQIA BQUBAgEHBgIFBwAAAAAAAAAQAAAAAAAAAAAAAACAAAAAAFMAeQBtAGIAbwBsAAAAMyaQAQAAAgsG BAICAgICBIcCAAAAAAAAAAAAAAAAAACfAAAAAAAAAEEAcgBpAGEAbAAAADMWkAEAAAICBgMFBAUC AwSHAgAAAAAAAAAAAAAAAAAAnwAAAAAAAABUAEkATQBFAFMAAAAiAAQAAACIGAAAxAIAAKkBAAAA AEaTOiZGkzom8KI4pgIAAAAAADcEAAAKGAAABAAMAAAABACDEDMAAAAAAAAAAAAAAAQAAQAAAAEA AAAAAAAAWQIAAACEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAApQbAB7QAtACAABIwAAAAAAAA AAAAAAAAAACFHQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA9BMA AAAAAAAAAAAAAAAAAAAAAAAAAAIAAABuAf//EgAAAAAAAAANAEMAbwBtAHAAcwB0AGEAdAAgADIA MAAwADAAAAAAAAAACQBCAGUAdABoAGwAZQBoAGUAbQAHAEkAZABlAEIAbwBvAG0AAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAD+/wAABAACAAAAAAAAAAAAAAAAAAAAAAABAAAA4IWf8vlPaBCrkQgAKyez 2TAAAACIAQAAEgAAAAEAAACYAAAAAgAAAKAAAAADAAAAuAAAAAQAAADEAAAABQAAANgAAAAGAAAA 5AAAAAcAAADwAAAACAAAAAABAAAJAAAAEAEAABIAAAAcAQAACgAAADgBAAALAAAARAEAAAwAAABQ AQAADQAAAFwBAAAOAAAAaAEAAA8AAABwAQAAEAAAAHgBAAATAAAAgAEAAAIAAADkBAAAHgAAAA4A AABDb21wc3RhdCAyMDAwAG8AHgAAAAEAAAAAb21wHgAAAAoAAABCZXRobGVoZW0AMDAeAAAAAQAA AABldGgeAAAAAQAAAABldGgeAAAABwAAAE5vcm1hbABlHgAAAAgAAABJZGVCb29tAB4AAAACAAAA MgBlQh4AAAATAAAATWljcm9zb2Z0IFdvcmQgOC4wAABAAAAAAAAAAAAAAABAAAAAAIiXFvHqvgFA AAAAABx2wlgZvwFAAAAAABx2wlgZvwEDAAAABAAAAAMAAAA3BAAAAwAAAAoYAAADAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAA/v8AAAQAAgAAAAAAAAAAAAAAAAAAAAAAAgAAAALVzdWcLhsQk5cIACss+a5EAAAABdXN 1ZwuGxCTlwgAKyz5rjgBAAD0AAAADAAAAAEAAABoAAAADwAAAHAAAAAFAAAAfAAAAAYAAACEAAAA EQAAAIwAAAAXAAAAlAAAAAsAAACcAAAAEAAAAKQAAAATAAAArAAAABYAAAC0AAAADQAAALwAAAAM AAAA1gAAAAIAAADkBAAAHgAAAAQAAABDQlMAAwAAADMAAAADAAAADAAAAAMAAACFHQAAAwAAADEV CAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAB4QAAABAAAADgAAAENvbXBzdGF0IDIw MDAADBAAAAIAAAAeAAAABgAAAFRpdGxlAAMAAAABAAAAKAEAAAQAAAAAAAAAKAAAAAEAAABSAAAA AgAAAFoAAAADAAAAsgAAAAIAAAACAAAACgAAAF9QSURfR1VJRAADAAAADAAAAF9QSURfSExJTktT AAIAAADkBAAAQQAAAE4AAAB7AEMAMwBEADkAMQBDAEEAMAAtADUANgBFAEQALQAxADEARAAzAC0A QQA1ADAAMAAtADQANAA0ADUANQAzADUANAAwADAAMAAwAH0AAAAAAEEAAABsAAAABgAAAAMAAAAd AGkAAwAAAAAAAAADAAAAAAAAAAMAAAAFAAAAHwAAABoAAABtAGEAaQBsAHQAbwA6AGMAbwBtAHAA cwB0AGEAdABAAGYAYgB1AC4AdQB1AC4AbgBsAAAAHwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA AAACAAAAAwAAAAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoAAAALAAAADAAAAA0AAAAOAAAADwAA ABAAAAARAAAAEgAAABMAAAAUAAAAFQAAABYAAAAXAAAAGAAAABkAAAD+////GwAAABwAAAAdAAAA HgAAAB8AAAAgAAAAIQAAAP7///8jAAAAJAAAACUAAAAmAAAAJwAAACgAAAApAAAA/v///ysAAAAs AAAALQAAAC4AAAAvAAAAMAAAADEAAAD+////MwAAADQAAAA1AAAANgAAADcAAAA4AAAAOQAAAP7/ ///9////PAAAAP7////+/////v////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////////////UgBv AG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAABYABQH//////////wMAAAAGCQIAAAAAAMAAAAAAAABGAAAAAAAjqDlYGb8BoKtT51gZvwE+ AAAAgAAAAAAAAABEAGEAdABhAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAACgACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAABoAAAAAEAAAAAAAADEAVABhAGIAbABlAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOAAIAAQAAAP//////////AAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIgAAAAAQAAAAAAAAVwBvAHIAZABEAG8AYwB1AG0A ZQBuAHQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABoAAgEGAAAABQAA AP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIjIAAAAAAAAFAFMA dQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAKAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACoA AAAAEAAAAAAAAAUARABvAGMAdQBtAGUAbgB0AFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0 AGkAbwBuAAAAAAAAAAAAAAA4AAIBBAAAAP//////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAMgAAAAAQAAAAAAAAAQBDAG8AbQBwAE8AYgBqAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgECAAAABwAAAP////8AAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAagAAAAAAAABPAGIAagBlAGMAdABQAG8AbwBs AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFgABAP////////// /////wAAAAAAAAAAAAAAAAAAAAAAAAAAoKtT51gZvwGgq1PnWBm/AQAAAAAAAAAAAAAAAAEAAAD+ //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////////AQD+/wMK AAD/////BgkCAAAAAADAAAAAAAAARhgAAABNaWNyb3NvZnQgV29yZC1kb2N1bWVudAAKAAAATVNX b3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9DmycQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= ------_=_NextPart_000_01BF195A.252CF070-- ========================================================================= Date: Tue, 19 Oct 1999 09:16:00 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Boom, Iris de" Subject: Compstat 2000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Dear Sir / Madame, The COMPSTAT 2000 conference of the ISI International Association for Statistical Computing will take place in Utrecht, the Netherlands from 21 - 25 August 2000. Statistical computing provides the link between statistical theory and applied statistics. As at previous Compstats, the scientific programme will cover all aspects of this link, from the development and implementation of new statistical ideas through to user experiences and software evaluation. The programme should appeal to anyone working in statistics and using computers, whether in universities, industrial companies, government agencies, research institutes or as software developers. The conference will be jointly organised by the Department of Methodology and Statistics of Utrecht University and the Department of Statistical Methods of Statistics Netherlands. Papers may be submitted in any of the following categories: - Statistical research - Development of statistical methodology, especially topics that rely on computers and computing environments. - Computing - Contributions of computer algorithms, tools and environments to the practice of statistics. - Applied statistics - Innovative applications of statistical computing in any area of current interest. Th deadline for submitting abstracts is 8 November 1999. For more information about COMPSTAT 2000, you can consult the attached Word-document, or visit or web site. The address is http://neon.vb.cbs.nl/rsm/compstat. Jelke Bethlehem (Statistics Netherlands) Peter van der Heijden (Utrecht University) Compstat 2000 Local arrangements The Compstat 2000 conference of the ISI International Association for Statistical Computing will take place in Utrecht, the Netherlands from 21 - 25 August 2000. The conference will be jointly organised by the Department of Methodology and Statistics of Utrecht University and the Department of Statistical Methods of Statistics Netherlands. The Department of Methodology and Statistics of Utrecht University has a strong involvement in statistical computing and applied statistics. Statistics Netherlands is also known for its expertise in applied statistics, and for its innovative approach in the application of recent developments of information technology to survey data collection and processing. Approximately 35 kilometres south of Amsterdam Utrecht stands in the heart of the Netherlands. It was founded in 48 by the Romans, who built a military settlement along the shore of the Rhine. In 695 the English Benedictine monk Willibrord came to christianise Francks and Frisians and made Utrecht to a centre of religion, which is still noticeable in present times. For centuries, Utrecht was the largest and only city of importance in the northern part of the Netherlands. Today, Utrecht is an attractive city. With 230,000 inhabitants Utrecht is the fourth largest city in The Netherlands, only Amsterdam, Rotterdam and The Hague having greater populations. With its magnificient cathedral, churches, canals museums and historic buildings dating from the 16th century onwards Utrecht is a city of outstanding culture. As host to the largest University in The Netherlands Utrecht also offers a lively and varied social scene with busy restaurants, cafes, pubs and nightspots. Utrecht is easy reached by road and rail. Delegates flying into Amsterdam Schiphol Airport can take the train from the airport directly to the centre of the city. If you would like to find out more about Utrecht and how to reach it please visit the website. There will be a full programme of social events including a Buffet Reception, Concert, Dinner and excursions, to allow participants to exchange ideas, meet friends and see many of the local attractions. Scientific Programme Statistical computing provides the link between statistical theory and applied statistics. As at previous Compstats, the scientific programme will cover all aspects of this link, from the development and implementation of new statistical ideas through to user experiences and software evaluation. The programme should appeal to anyone working in statistics and using computers, whether in universities, industrial companies, government agencies, research institutes or as software developers. Papers may be submitted in any of the following categories: * Statistical research - Development of statistical methodology, especially topics that rely on computers and computing environments. * Computing - Contributions of computer algorithms, tools and environments to the practice of statistics. * Applied statistics - Innovative applications of statistical computing in any area of current interest. The scientific programme will consist of a variety of sessions, such as parallel and plenary presentations, invited and contributed papers, poster sessions, one or two tutorials, and software demonstrations. The Scientific Programme Committee seeks papers touching on all aspects of computational statistics. This includes theory, applications, and implementations. The Scientific Programme Committee also welcomes papers in the field of Official Statistics, i.e. papers in the field of data collection, data editing, data analysis, and data publications. Papers may be selected by the Scientific Programme Committee as full contributions, short contributions or posters. Selection is based on submitted abstracts of up to two pages. These should include the main results and references, highlighting novel aspects and indicating their relevance to the above mentioned three categories. Further details and sample abstract formats can be found on the website. Full contributions will be refereed and published, with the invited papers, in a volume of Proceedings by Physica Verlag. Short communications and posters will be published in a 2nd volume by Statistics Netherlands and Utrecht university. At the conference, several prices will be awarded: * Three prices, each worth 1000 Dutch Guilders, will be awarded for the best three contributions submitted and presented by young participants (upper age limit 35 years for all authors on August 31, 2000). * A price will be awarded for the best poster presentation. Invited speakers Keynote speakers * Donald Rubin (The broad role for multiple imputation in statistical science), and * Peter Kooiman (Mass imputation versus sequential weighting of a virtual census) At the moment invited speakers include * Noel Cressie (Space-time Kalman filtering and MCMC), * Antoine de Falguerolles (generalized linear models with bilinear terms), * David Draper (Computational issues in MCMC fitting of multilevel models), * David Hand (Methodological issues in data mining) * Georges Hebrail (Practical data mining in a large utility company), * Youngjo Lee (Analysis of correlated non-Gaussian data via hierarchical generalized linear models), * Helmut Luetkepohl (Bootstrapping impulse responses in VAR analyses), * Agustin Maravall (Some applications of the signal extraction technique to socioeconomic time series), * Erich Neuwirth (Spreadsheets in statistical education), * Walter Racugno (Bayes factors for model selection and prediction) * Hans van Houwelingen (Nonproportional hazards models in survival analysis), * Ari Verbyla (Spatio-temporal modelling), Please check our home page for the latest and more detailed information. Software demonstration and book exhibition There will be demonstration stands for software producers to present their products, and book exhibitions. Important deadlines Abstracts received (post or e-mail): 8 November 1999 Notification to authors: 15 December 1999 Contributed paper for refereeing: 11 March 2000 Final versions of contributed papers 1 May 2000 Short communications and posters: 1 May 2000 Local Organising Committee Wim Jansen , Chair (Utrecht University) Douwe van der Sluis (Netherlands Society for Statistics and Operation research) Gerrit Stemerdink (ISI) Leonieke Wijngaards (Utrecht University) Scientific Programme Committee Peter van der Heijden, Netherlands, Chair Jelke Bethlehem, Netherlands Andrej Blejec, Slovenia Wolfgang Haerdle, Germany Roger Payne, United Kingdom Christian Robert, France Roberta Siciliano, Italy Registration fees Early Registration; deadline = 1 April 2000, IASC/ISI/Other Approved NLG 650,00 Others NLG 750,00 Standard Registration; deadline = 21 June 2000, IASC/ISI/Other Approved NLG 750,00 Others NLG 850,00 Late Registration; after 21 June 2000 NLG 950,00 Students (send in document of University Registration) NLG 150,00 Address for correspondence FBU Congress Bureau Utrecht University Attn: Mrs. Marcelle Buma P.O. Box 80125 3508 TC Utrecht The Netherlands Phone: +31 30 253 2728 Fax: +31 30 253 5851 E-mail: compstat@fbu.uu.nl For more information and for registration see website: http://neon.vb.cbs.nl/rsm/compstat To ensure that you receive further information, please send an email to compstat@fbu.uu.nl, or a letter to the address above. ========================================================================= Date: Fri, 22 Oct 1999 00:05:42 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: EPI GLUE DROP DOWN MENU LENGTH LIMITS MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Anyone know whether there's a way in 6.04 to increase the width of drop down menus? I have some options that in Russian that take a bit more space to communicate than in good old computer-abbreviated English and I'm running out of room. The manual doesn't mention this in the epiglue chapter. I have in mind MENUITEM within a POPUP. Thanks for the help. From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9910B" ========================================================================= Date: Tue, 12 Oct 1999 16:16:09 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: OluFemi Ogunbanwo Subject: TYPE command with numbers MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > Dear all, > > I am trying to include a number field in a TYPE command, but Analysis knocks > off any 0s (zeros) at the beginning or end of the number e.g. 06.50 is > printed as 6.5. I need to show the full five digit decimal number, which is > a record of time of contact on my report. > > Does anyone know a way of doing this? > > Thanks in advance. > ========================================================================= Date: Tue, 12 Oct 1999 13:01:31 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kirt Emery Subject: SSS1 Question Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_8FD6B948.4B2A4CA3" This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_8FD6B948.4B2A4CA3 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline I have been attempting to use the SSS1 program to perform Time-Series analysis of health outcomes at a county level (Kern County California). When I go through the manual step-by-step and perform forecasting, I end up with forecasts that have very large upper and lower confidence limits and a series that is a flat line. Many of the models I have attempted look like the sample time-series data set Series 9. When I back cast 12 months on this series and forecast into the future, the pattern is not useful. Is there a minimum sample size per lag that one should use meet before contemplating forecasting? What I believe is happening is that the numbers are too small and there is too much variance in the data to adequately define a model. When I use a complete year of data I do not have forty data points to evaluate--this is the message that SSS1 sends me. When I break down years into quarters or months, the numbers get real small. Since I have not had any experience with Time-Series, is there someone who I can talk to or get advice from? I have included a sample data set to see if I am the problem or if someone else can shed light onto this process. Thank you for your help with this matter. Kirt W. Emery, MPH Kern County Department of Public Health --=_8FD6B948.4B2A4CA3 Content-Type: text/plain Content-Disposition: attachment; filename="DISMNTH.DAT" Monthly Hepatitis A Cases 1989 - 1998 23 29 38 37 47 41 35 28 31 22 12 16 23 17 15 16 15 14 11 15 13 8 9 16 9 6 21 7 10 7 3 9 8 18 9 14 19 14 24 13 11 29 31 21 23 38 28 65 36 28 30 16 28 33 21 24 34 23 28 41 31 38 55 45 62 49 49 63 28 18 25 19 19 18 36 20 18 20 23 19 26 22 14 19 12 20 27 22 9 5 10 8 21 7 16 14 17 9 9 9 6 5 14 9 5 9 10 9 7 25 13 14 18 22 24 32 38 33 41 22 --=_8FD6B948.4B2A4CA3-- ========================================================================= Date: Wed, 13 Oct 1999 08:35:47 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Atrie, Jag" Subject: Re: TYPE command with numbers I am not sure whether there is an option one can set to keep the left and right padded zeroes in output. But there is a way to to do it and that is to convert the number field to an alphanumeric field. For example: DEFINE newvar1 _____ LET newvar1 = oldvar1 Now use the newvar1 for your reports and it should have the padded zeroes. _________________________________ J Atrie Communicable Disease Control Health Department of Western Australia Tel: +61-8-9388 4844 Fax: +61-8-9388 4848 E-Mail: jag.atrie@health.wa.gov.au -----Original Message----- From: OluFemi Ogunbanwo [mailto:femi@OGUNBANWO.FREESERVE.CO.UK] Sent: Tuesday, 12 October 1999 23:16 To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] TYPE command with numbers > Dear all, > > I am trying to include a number field in a TYPE command, but Analysis knocks > off any 0s (zeros) at the beginning or end of the number e.g. 06.50 is > printed as 6.5. I need to show the full five digit decimal number, which is > a record of time of contact on my report. > > Does anyone know a way of doing this? > > Thanks in advance. > ========================================================================= Date: Wed, 13 Oct 1999 09:25:15 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: SSS1 Question MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sorry I can't be much help with particular Time Series models, as this is a subspecialty, even for statisticians, and not all series can be modeled successfully, even at the national level. Small numbers and a lack of repeating patterns add to the difficulty or impossibility of achieving a satisfactory model. Somewhere between "just-try-it" and "take-a-semester-course-with-a-400-page-textbook" , there is a point where you may decide to use moving averages or plain graphs. Of course, if you can find an expert, perhaps at a community technical or business college, a half-hour consultation could be very helpful. -----Original Message----- From: Kirt Emery [mailto:emeryk@CO.KERN.CA.US] Sent: Tuesday, October 12, 1999 4:02 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] SSS1 Question << File: DISMNTH.DAT >> I have been attempting to use the SSS1 program to perform Time-Series analysis of health outcomes at a county level (Kern County California). When I go through the manual step-by-step and perform forecasting, I end up with forecasts that have very large upper and lower confidence limits and a series that is a flat line. Many of the models I have attempted look like the sample time-series data set Series 9. When I back cast 12 months on this series and forecast into the future, the pattern is not useful. Is there a minimum sample size per lag that one should use meet before contemplating forecasting? What I believe is happening is that the numbers are too small and there is too much variance in the data to adequately define a model. When I use a complete year of data I do not have forty data points to evaluate--this is the message that SSS1 sends me. When I break down years into quarters or months, the numbers get real small. Since I have not had any experience with Time-Series, is there someone who I can talk to or get advice from? I have included a sample data set to see if I am the problem or if someone else can shed light onto this process. Thank you for your help with this matter. Kirt W. Emery, MPH Kern County Department of Public Health ========================================================================= Date: Wed, 13 Oct 1999 11:58:46 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: Re: TYPE command with numbers In-Reply-To: <002701bf14c4$b77f9300$ae2f893e@hadoc1> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 16:16 12/10/99 +0100, you wrote: >> Dear all, >> >> I am trying to include a number field in a TYPE command, but Analysis >knocks >> off any 0s (zeros) at the beginning or end of the number e.g. 06.50 is >> printed as 6.5. I need to show the full five digit decimal number, which >is >> a record of time of contact on my report. >> >> Does anyone know a way of doing this? >> >> Thanks in advance. >> > > Time is not a real number.=20 I put hours and minutes in different fields and then performs calculations in analysis. EJ: Field (integer numbers) for hours is "hora" and for minutes is "hora1" DEFINE Hr _____ HR =3D Hora[1,2] + ":" + hora1[1,2] IF hora1 < 10 THEN HR =3D Hora[1,2] + ":" + "0" + hora1[1,1] Perhaps the problem is not that hrs appears without zero, but if minutes appears without zero in calculations 05 min appears like 50 min. Sorry for my bad english! Enrique Finetti Medico Asistente de UCI pedi=E1trica Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9910A" ========================================================================= Date: Fri, 1 Oct 1999 10:22:35 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: suppressing portions of output MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit 6.04b I'm writing a little PGM file to automatically calculate SSI cases per NNIS for Russian hospital epidemiologists. I'm doing some work with how I want to display the information to them directly. Currently I'm just listing all patients with signs/sx that match the diagnosis. Here's my problem: I want to minimize the English text: messages like NOECHO ON, Selection cleared, and Selection = FIELDNAME = only get in the way. I know the use of SET NOECHO=ON/OFF. My problem is that a) setting noecho echos a message to the screen about setting echo (i thought the whole point was to suppress it) b) noecho doesn't seem to affect the first line of LIST which states the record set being evaluated. c)I know I can suppress the Selection cleared notice, but it replaces it with the NOECHO dialogue. Here is the output I currently get: ** Note NOECHO=OFF PATIENTS WITH SUPERFICIAL SSI BY CDC DEFINITIONS ** Current selection: CDCSSSI="Y" SURNAME DEPARTMENT CDCSSSI ------------ ---------- ------- ivanov . Y petrov . Y ** Selection cleared. I want to kill the lines I've marked with **. I want my TITLE to provide the information (because I can russify that). Anyone know how to suppress these things? Thanks much. ========================================================================= Date: Fri, 1 Oct 1999 09:20:49 -0700 Reply-To: gerald.daurat@wanadoo.fr Sender: Epi Info Discussion Group From: Gerald DAURAT Subject: Re: suppressing portions of output MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sam Brown wrote: > > 6.04b > > I'm writing a little PGM file to automatically calculate SSI cases per > NNIS for Russian hospital epidemiologists. I'm doing some work with how > I want to display the information to them directly. Currently I'm just > listing all patients with signs/sx that match the diagnosis. Here's my > problem: > > I want to minimize the English text: messages like NOECHO ON, Selection > cleared, and Selection = FIELDNAME = only get in the way. I know > the use of SET NOECHO=ON/OFF. > > My problem is that > > a) setting noecho echos a message to the screen about setting echo (i > thought the whole point was to suppress it) > b) noecho doesn't seem to affect the first line of LIST which states the > record set being evaluated. > c)I know I can suppress the Selection cleared notice, but it replaces it > with the NOECHO dialogue. > > Here is the output I currently get: > > ** Note NOECHO=OFF > > PATIENTS WITH SUPERFICIAL SSI BY CDC DEFINITIONS > > ** Current selection: CDCSSSI="Y" > > SURNAME DEPARTMENT CDCSSSI > ------------ ---------- ------- > ivanov . Y > petrov . Y > ** Selection cleared. > > I want to kill the lines I've marked with **. I want my TITLE to > provide the information (because I can russify that). Anyone know how > to suppress these things? Thanks much. In order to suppress such lines as Noecho=off just or selection cleared, just send your results to a file rather than to screen. Then you can examine the file with a text editor. A convienient way to do it is to add an item in your epiglue menu such as menuitem "wiew a list of patients with SSI" CDCSSI and make a command block called CDCSSI CDCSSI begin c:\epi6\Analysis c:.........PGM (*ie your PGM file is automaticaly launched) view /noedit (the noedit switch is optional) end You'll find further details in EPI6 manuel within Epiglue chapter. This assumes that your PGM file first erases the txt file and then routes the results to this very file again and that it ends with a QUIT command. A good idea is to begin the pgm file with noecho = on and set split = off so that nothing appears on the screen during data processing. This also speeds up processing. You can remove criteria by adding set criteria = off at the beginning of Pgm files or in config.epi (see manuel for further details). ========================================================================= Date: Fri, 1 Oct 1999 09:24:41 -0700 Reply-To: gerald.daurat@wanadoo.fr Sender: Epi Info Discussion Group From: Gerald DAURAT Subject: Re: suppressing portions of output MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sam Brown wrote: > > 6.04b > > I'm writing a little PGM file to automatically calculate SSI cases per > NNIS for Russian hospital epidemiologists. I'm doing some work with how > I want to display the information to them directly. Currently I'm just > listing all patients with signs/sx that match the diagnosis. Here's my > problem: > > I want to minimize the English text: messages like NOECHO ON, Selection > cleared, and Selection = FIELDNAME = only get in the way. I know > the use of SET NOECHO=ON/OFF. > > My problem is that > > a) setting noecho echos a message to the screen about setting echo (i > thought the whole point was to suppress it) > b) noecho doesn't seem to affect the first line of LIST which states the > record set being evaluated. > c)I know I can suppress the Selection cleared notice, but it replaces it > with the NOECHO dialogue. > > Here is the output I currently get: > > ** Note NOECHO=OFF > > PATIENTS WITH SUPERFICIAL SSI BY CDC DEFINITIONS > > ** Current selection: CDCSSSI="Y" > > SURNAME DEPARTMENT CDCSSSI > ------------ ---------- ------- > ivanov . Y > petrov . Y > ** Selection cleared. > > I want to kill the lines I've marked with **. I want my TITLE to > provide the information (because I can russify that). Anyone know how > to suppress these things? Thanks much. In order to suppress such lines as Noecho=off just or selection cleared, just send your results to a file rather than to screen. Then you can examine the file with a text editor. A convienient way to do it is to add an item in your epiglue menu such as menuitem "wiew a list of patients with SSI" CDCSSI and make a command block called CDCSSI CDCSSI begin c:\epi6\Analysis c:.........PGM (*ie your PGM file is automaticaly launched) view /noedit (the noedit switch is optional) end This command uses the built in Epiinfo text editor, that can display lines longer than 80 caracters. You'll find further details in EPI6 manuel within Epiglue chapter. This assumes that your PGM file first erases the txt file and then routes the results to this very file again and that it ends with a QUIT command. A good idea is to begin the pgm file with noecho = on and set split = off so that nothing appears on the screen during data processing. This also speeds up processing. You can remove criteria by adding set criteria = off at the beginning of Pgm files or in config.epi (see manuel for further details). ========================================================================= Date: Fri, 1 Oct 1999 09:53:29 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Vegard Hogli Subject: Re: suppressing portions of output In-Reply-To: <37F4532B.52E2170F@vecnatech.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm not quite sure if this is what you're looking for, but the command SET SPLIT=3DOFF enters full-screen mode. If you in addition have set NOECHO=3DON, nothing outputs to the screen, output is directed only to the specified output file. (this seems to speed up large processing jobs as well). Then you can construct a hypertext .hlp file that can be called with the HELP .hlp command from an EPIGLUE menu system. By using the freware DOS graphics display program PICEM (Have forgotten if this is on the Epi Info Installation disk or if I have found it elsewhere), you could as well present graphs and maps produced by Epi Info and Epi Map from the same menu system. As you will see from the example below, I'm using the shareware program LIST to display texts. That's because the inborn command VIEW for some reason didn't work on my system. Hope you find these ideas helpful! Vegard Hoegli MD MPH GRUK (Center for QA in Health Care) Skien, Norway EXAMPLE .HPT file (Apology for Norwegian texts - this is from a real application) .topic helse ~+-----------------------------------------------------------------+~ ~=A6 Velg =F8nsket emne med piltast eller og tast = =A6~ ~+-----------------------------------------------------------------+~ =AB01-1 Personell i alt, Leger, Fysioterapeuter|tab01b1=BB =AB01-2 Sykepleiere, Jordm=F8dre, Hjelpepleiere, Annet personell|tab01b2= =BB =AB02 Leger etter stillingstype|tab02b1=BB =AB03 Fysioterapeuter etter stillingsstype|tab03b .TOPIC tab01b1=3DBATCH P:\kht98\program\list P:\kht98\tabeller\tab01b1.txt .TOPIC tab01b2=3DBATCH P:\kht98\program\list P:\kht98\tabeller\tab01b2.txt .TOPIC tab02b1=3DBATCH P:\kht98\program\list P:\kht98\tabeller\tab02b1.txt .TOPIC tab03b1=3DBATCH P:\kht98\program\list P:\kht98\tabeller\tab03b1.txt .topic helsetjenesten ~+-----------------------------------------------------------------+~ ~=A6 Velg =F8nsket emne med piltast eller og tast = =A6~ ~+-----------------------------------------------------------------+~ ~HELSETJENESTEN~ =ABPersonell i alt|dia01a1=BB =ABLeger|dia01a2=BB =ABFysioterapeuter|dia01a3=BB =ABSykepleiere|dia01a4=BB =ABHjelpepleiere|dia01a5=BB =ABAnnet personell|dia01a6=BB , eller for =E5 lukke et grafikkbilde .TOPIC dia01a1=3DBATCH P:\kht98\program\PICEM P:\kht98\eksport\dia01a1.pcx=20 .TOPIC dia01a2=3DBATCH P:\kht98\program\PICEM P:\kht98\eksport\dia01a2.pcx .TOPIC dia01a3=3DBATCH P:\kht98\program\PICEM P:\kht98\eksport\dia01a3.pcx .TOPIC dia01a4=3DBATCH P:\kht98\program\PICEM P:\kht98\eksport\dia01a4.pcx .TOPIC dia01a5=3DBATCH P:\kht98\program\PICEM P:\kht98\eksport\dia01a5.pcx .TOPIC dia01a6=3DBATCH P:\kht98\program\PICEM P:\kht98\eksport\dia01a6.pcx END EXAMPLE. At 10:22 01.10.99 +0400, you wrote: >6.04b > >I'm writing a little PGM file to automatically calculate SSI cases per >NNIS for Russian hospital epidemiologists. I'm doing some work with how >I want to display the information to them directly. Currently I'm just >listing all patients with signs/sx that match the diagnosis. Here's my >problem: > >I want to minimize the English text: messages like NOECHO ON, Selection >cleared, and Selection =3D FIELDNAME =3D only get in the way. I know >the use of SET NOECHO=3DON/OFF. > >My problem is that > >a) setting noecho echos a message to the screen about setting echo (i >thought the whole point was to suppress it) >b) noecho doesn't seem to affect the first line of LIST which states the >record set being evaluated. >c)I know I can suppress the Selection cleared notice, but it replaces it >with the NOECHO dialogue. > >Here is the output I currently get: > > ** Note NOECHO=3DOFF > > PATIENTS WITH SUPERFICIAL SSI BY CDC DEFINITIONS > > >** Current selection: CDCSSSI=3D"Y" > >SURNAME DEPARTMENT CDCSSSI >------------ ---------- ------- >ivanov . Y >petrov . Y >** Selection cleared. > >I want to kill the lines I've marked with **. I want my TITLE to >provide the information (because I can russify that). Anyone know how >to suppress these things? Thanks much. > ========================================================================= Date: Fri, 1 Oct 1999 13:03:50 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: Re: suppressing portions of output MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Thanks for the excellent and rapid advice. I managed to eliminate everything but the Current Selection CDCSSSI="Y" line before giving me the listing of patients. Any ideas about how to eliminate that last line? Here's the example: đÁĂÉĹÎÔŮ Ó ÇĚŐBĎËĎĘ čňé ĐĎ CDCÝÎÉÍ ÓÔŇÁÎÄÁŇÔÎŮÍ ĎĐŇĹÄĹĚĹÎÉŃÍ PATIENTS WITH DEEP SSI BY CDC DEFINITIONS Current selection: CDCDSSI="Y" SURNAME DEPARTMENT CDCDSSI ------------ ---------- ------- ivanov . Y petrov . Y Gerald DAURAT wrote: > Sam Brown wrote: > > > > 6.04b > > > > I'm writing a little PGM file to automatically calculate SSI cases per > > NNIS for Russian hospital epidemiologists. I'm doing some work with how > > I want to display the information to them directly. Currently I'm just > > listing all patients with signs/sx that match the diagnosis. Here's my > > problem: > > > > I want to minimize the English text: messages like NOECHO ON, Selection > > cleared, and Selection = FIELDNAME = only get in the way. I know > > the use of SET NOECHO=ON/OFF. > > > > My problem is that > > > > a) setting noecho echos a message to the screen about setting echo (i > > thought the whole point was to suppress it) > > b) noecho doesn't seem to affect the first line of LIST which states the > > record set being evaluated. > > c)I know I can suppress the Selection cleared notice, but it replaces it > > with the NOECHO dialogue. > > > > Here is the output I currently get: > > > > ** Note NOECHO=OFF > > > > PATIENTS WITH SUPERFICIAL SSI BY CDC DEFINITIONS > > > > ** Current selection: CDCSSSI="Y" > > > > SURNAME DEPARTMENT CDCSSSI > > ------------ ---------- ------- > > ivanov . Y > > petrov . Y > > ** Selection cleared. > > > > I want to kill the lines I've marked with **. I want my TITLE to > > provide the information (because I can russify that). Anyone know how > > to suppress these things? Thanks much. > > In order to suppress such lines as Noecho=off just or selection cleared, > just send your results to a file rather than to screen. Then you can > examine the file with a text editor. A convienient way to do it is to > add an item in your epiglue menu such as > > menuitem "wiew a list of patients with SSI" CDCSSI > > and make a command block called CDCSSI > > CDCSSI > begin > c:\epi6\Analysis c:.........PGM (*ie your PGM file is automaticaly > launched) > view /noedit (the noedit switch is > optional) > end > > This command uses the built in Epiinfo text editor, that can display > lines longer than 80 caracters. > > You'll find further details in EPI6 manuel within Epiglue chapter. > > This assumes that your PGM file first erases the txt file and then > routes the results to this very file again and that it ends with a QUIT > command. > A good idea is to begin the pgm file with noecho = on and set split = > off so that nothing appears on the screen during data processing. This > also speeds up processing. > > You can remove criteria by adding set criteria = off at the beginning > of Pgm files or in config.epi (see manuel for further details). ========================================================================= Date: Fri, 1 Oct 1999 09:52:52 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: suppressing portions of output Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=GNqjBl83ADnI5OsqGwtChjLEg9bCFcJxBwhgAekYEYrb2vxc1wBuPYlA" --0__=GNqjBl83ADnI5OsqGwtChjLEg9bCFcJxBwhgAekYEYrb2vxc1wBuPYlA Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable SET CRITERIA=3DOFF turns off the printing of the current selection criteria (Buried in the manual, but it's there). ---------------------- Jamie Hockin MD,MSc -------------------------- Director, Field Epidemiology _ Directeur, Programme de formation Training Program _|\ en =E9pid=E9miologie d'intervention= LCDC, Health Canada :| \ LLCM, Sant=E9 Canada PL 0602B Tunney's Pasture | LP 0602B Pr=E9 Tunney Ottawa ON K1A 0L2, Canada Ottawa (Ontario) K1A 0L2, Canada Jamie_Hockin@hc-sc.gc.ca 613 957-1764 FAX: 613 941-6028 http://www.hc-sc.gc.ca/hpb/lcdc/survlnce/fetp Sam Brown on 99/10/01 05:03:50 AM Please respond to Epi Info Discussion Group = To: EPI-INFO@LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: Re: [EPI-INFO] suppressing portions of output = --0__=GNqjBl83ADnI5OsqGwtChjLEg9bCFcJxBwhgAekYEYrb2vxc1wBuPYlA Content-type: text/plain; charset=koi8-r Content-Disposition: inline Content-transfer-encoding: quoted-printable Thanks for the excellent and rapid advice. I managed to eliminate ever= ything but the Current Selection CDCSSSI=3D"Y" line before giving me the listing of pa= tients. Any ideas about how to eliminate that last line? Here's the example: =F0=C1=C3=C9=C5=CE=D4=D9 =D3 =C7=CC=D5B=CF=CB=CF=CA =E8=F2=E9= =D0=CF CDC=DD=CE=C9=CD =D3=D4=D2=C1=CE=C4=C1=D2=D4=CE=D9=CD =CF=D0=D2=C5= =C4=C5=CC=C5=CE=C9=D1=CD PATIENTS WITH DEEP SSI BY CDC DEFINITIONS Current selection: CDCDSSI=3D"Y" SURNAME DEPARTMENT CDCDSSI ------------ ---------- ------- ivanov . Y petrov . Y Gerald DAURAT wrote: > Sam Brown wrote: > > > > 6.04b > > > > I'm writing a little PGM file to automatically calculate SSI cases = per > > NNIS for Russian hospital epidemiologists. I'm doing some work wit= h how > > I want to display the information to them directly. Currently I'm = just > > listing all patients with signs/sx that match the diagnosis. Here'= s my > > problem: > > > > I want to minimize the English text: messages like NOECHO ON, Selec= tion > > cleared, and Selection =3D FIELDNAME =3D only get in the way. = I know > > the use of SET NOECHO=3DON/OFF. > > > > My problem is that > > > > a) setting noecho echos a message to the screen about setting echo = (i > > thought the whole point was to suppress it) > > b) noecho doesn't seem to affect the first line of LIST which state= s the > > record set being evaluated. > > c)I know I can suppress the Selection cleared notice, but it replac= es it > > with the NOECHO dialogue. > > > > Here is the output I currently get: > > > > ** Note NOECHO=3DOFF > > > > PATIENTS WITH SUPERFICIAL SSI BY CDC DEFINITIONS > > > > ** Current selection: CDCSSSI=3D"Y" > > > > SURNAME DEPARTMENT CDCSSSI > > ------------ ---------- ------- > > ivanov . Y > > petrov . Y > > ** Selection cleared. > > > > I want to kill the lines I've marked with **. I want my TITLE to > > provide the information (because I can russify that). Anyone know = how > > to suppress these things? Thanks much. > > In order to suppress such lines as Noecho=3Doff just or selection cle= ared, > just send your results to a file rather than to screen. Then you can > examine the file with a text editor. A convienient way to do it is to= > add an item in your epiglue menu such as > > menuitem "wiew a list of patients with SSI" CDCSSI > > and make a command block called CDCSSI > > CDCSSI > begin > c:\epi6\Analysis c:.........PGM (*ie your PGM file is automaticaly > launched) > view /noedit (the noedit switch is > optional) > end > > This command uses the built in Epiinfo text editor, that can display > lines longer than 80 caracters. > > You'll find further details in EPI6 manuel within Epiglue chapter. > > This assumes that your PGM file first erases the txt file and then > routes the results to this very file again and that it ends with a QU= IT > command. > A good idea is to begin the pgm file with noecho =3D on and set split= =3D > off so that nothing appears on the screen during data processing. Thi= s > also speeds up processing. > > You can remove criteria by adding set criteria =3D off at the beginn= ing > of Pgm files or in config.epi (see manuel for further details). = --0__=GNqjBl83ADnI5OsqGwtChjLEg9bCFcJxBwhgAekYEYrb2vxc1wBuPYlA-- ========================================================================= Date: Thu, 7 Oct 1999 08:35:46 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Modifying variables generated and saved in analysis Comments: To: connollc@mrc.ac.za In-Reply-To: <19990914071606969.AAA276.333@mrc.ac.za> MIME-Version: 1.0 Cathy Connolly writes: >How do I modify variables in epi-info that were not in the original .QES file, >that is were >created and saved as part of the analysis as a new rec file? Specifically I >need to: > >a. change a date to make it Y2k compatible and the patch only deals >modifications >for variables appearing in the original *.qes file; > >b. change a variable from a one digit to a two digit format again one that >doesn't >appear in the original *.qes file but in updated rec files? Three steps: Use REC2QES.EXE to create a .QES file Edit the .QES file Use ENTER to restructure the file. Be careful not to change any variable names or types (e.g. ## to seldom works as expected). Mark -- Mark Myatt ========================================================================= Date: Thu, 7 Oct 1999 08:38:59 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Epi-Glue and NT In-Reply-To: MIME-Version: 1.0 Zubieta, Juan writes: >Hi everybody, > >I am having problems using two drives. Epi6 is installed in c:\epi6 but I >also have an Epi-glue menu in d:\menu\ > >It seems that analysis can not execute a .pgm automatically when called from >Epi-glue when on d:\. but it works if the menu is in c:\menu\ It's probably a path problem. Try either: 1. Setting the "Working Directory" on the shortcut properties to D:\ 2. Specifying the path with ANALYSIS: ANALYSIS D:\YOURPROG.PGM Mark -- Mark Myatt ========================================================================= Date: Thu, 7 Oct 1999 08:31:50 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: suppressing portions of output In-Reply-To: <37F478F6.39AC34B4@vecnatech.com> MIME-Version: 1.0 Sam Brown writes: >Thanks for the excellent and rapid advice. I managed to eliminate everything >but the > >Current Selection CDCSSSI="Y" line before giving me the listing of patients. >Any ideas about how to eliminate that last line? SET CRITERIA = OFF CLS -- Mark Myatt From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9909C" ========================================================================= Date: Wed, 15 Sep 1999 15:29:38 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Atrie, Jag" Subject: Importing a boundary file into Epi Map 2 Dear All, I wish to import a boundary map file of Western Australia into Epi Map 2. Then I would like to draw lines in it to demarcate public health regions. Finally I want to be able to mark the distribution of diseases in each of these regions I created. Can someone please explain to me how to go about it. I have only a basic understanding of mapping software and hence, please explain as you would a novice. Our infectious diseases database is in Epi Info. I can get someone to send me a boundary file exported from Map Info. The manual says that Epi Map can import ASCII files from other external programs such as Map Info. "How" is my question. What extension should the file be? What should I inform my colleague when I tell him to send me a boundary file from Map Info? Thank you in advance. Regards, ________________________________ Jag Atrie Communicable Disease Control Branch Health Department of Western Australia Telephone: (08) 9388 4844 Facsimile: (08) 9388 4848 E-Mail: jag.atrie@health.wa.gov.au ________________________________ ========================================================================= Date: Wed, 15 Sep 1999 13:31:23 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Zubieta, Juan" Subject: Epi-Glue and NT MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Hi everybody, I am having problems using two drives. Epi6 is installed in c:\epi6 but I also have an Epi-glue menu in d:\menu\ It seems that analysis can not execute a .pgm automatically when called from Epi-glue when on d:\. but it works if the menu is in c:\menu\ any suggestion? Thanks Juan Carlos Zubieta MD MPH Mail Stop K74 Centers For Disease Control 2877 Brandywine Rd. Williams Building 4th Floor Rm 4803.03 Atlanta, GA 30341 Phone (770) 488 8439 ========================================================================= Date: Wed, 15 Sep 1999 20:20:54 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Pedro Arias Bohigas Subject: Re: Epi-Glue and NT MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Hola Juan, me paso aloga parecido hace unos dias, llamaba a ANALYSIS desde una carpeta (C:\SIVE) donde tenía un menu con su correspondiente CFG, al escribir READ ARCHIVO.REC me decia que no encontraba el archivo en una unidad de red, se resolvió borrando los archivos CFG y volviendolos a crear de nuevo al abrir el menú. Intenta borrar los archivos CFG de la carpeta donde tengas el PGM qu no funciona. Saludos, Pedro ---------- > De: Zubieta, Juan > A: EPI-INFO@LISTSERV.CDC.GOV > Asunto: [EPI-INFO] Epi-Glue and NT > Fecha: miércoles 15 de septiembre de 1999 19:31 > > Hi everybody, > > I am having problems using two drives. Epi6 is installed in c:\epi6 but I > also have an Epi-glue menu in d:\menu\ > > It seems that analysis can not execute a .pgm automatically when called from > Epi-glue when on d:\. but it works if the menu is in c:\menu\ > > any suggestion? > > > Thanks > > Juan Carlos Zubieta MD MPH > Mail Stop K74 > Centers For Disease Control > 2877 Brandywine Rd. Williams Building > 4th Floor Rm 4803.03 > Atlanta, GA 30341 > Phone (770) 488 8439 ========================================================================= Date: Wed, 15 Sep 1999 13:02:23 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kyle Luman Subject: Re: Modifying variables generated and saved in analysi s Comments: To: connollc@mrc.ac.za MIME-Version: 1.0 Content-Type: text/plain It appears others have adequately answered question A. I will answer question B as I understood it to be asked. b. change a variable from a one digit to a two digit format again one that doesn't appear in the original *.qes file but in updated rec files? Let's call the one digit variable VAR1 and assume that it is numeric, the new two digit variable will be VAR2 and also will be numeric. ******************** ***Code in the *.pgm file define VAR2 ## VAR2 = VAR1 ********************* The VAR2 variable contains the exact info in VAR1, but takes up two spaces in the *.rec file. If I misunderstood your question, please forgive ... :-) > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ > > -----Original Message----- > From: Cathy Connolly [SMTP:connollc@MRC.AC.ZA] > Sent: Tuesday, September 14, 1999 12:17 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: [EPI-INFO] Modifying variables generated and saved in > analysis > > How do I modify variables in epi-info that were not in the original .QES > file, that is were > created and saved as part of the analysis as a new rec file? Specifically > I need to: > > a. change a date to make it Y2k compatible and the patch only deals > modifications > for variables appearing in the original *.qes file; > > b. change a variable from a one digit to a two digit format again one > that doesn't > appear in the original *.qes file but in updated rec files? > > Thank you > Cathy Connolly > CATHY CONNOLLY > Senior Scientist > Centre for Epidemiological Research in South Africa > CERSA (Durban) > Medical Research Council > PO Box 17120, Congella 4013 South Africa > Tel +27 (0)31 2051 481 Fax + 27 (0)31 2058 840 ========================================================================= Date: Thu, 16 Sep 1999 07:53:27 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "C. Jon Hinkle" Subject: Re: Epi-Glue and NT Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Be sure both the directory that contains the program file as well as = c:\epi6 are in the path statement in the autoexec.bat file of the machine. = As an alternative, you can issue a new path statement manually. PATH =3D %PATH%; C:\EPI6; The above syntax will add c:\epi6 and the directory of your program file = to your existing path. CJon >>> "Zubieta, Juan" 09/15 12:31 PM >>> Hi everybody, I am having problems using two drives. Epi6 is installed in c:\epi6 but I also have an Epi-glue menu in d:\menu\ It seems that analysis can not execute a .pgm automatically when called = from Epi-glue when on d:\. but it works if the menu is in c:\menu\ any suggestion? Thanks Juan Carlos Zubieta MD MPH Mail Stop K74 Centers For Disease Control 2877 Brandywine Rd. Williams Building 4th Floor Rm 4803.03 Atlanta, GA 30341 Phone (770) 488 8439 ========================================================================= Date: Tue, 21 Sep 1999 14:18:41 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Announcement / Instructional Material on Web MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF045D.B7F1EEFE" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF045D.B7F1EEFE Content-Type: text/plain; charset="iso-8859-1" Good news, Bud. Thanks for doing this!!! -----Original Message----- From: B. Gerstman [mailto:B_Gerstman@COMPUSERVE.COM] Sent: Tuesday, August 24, 1999 12:56 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Announcement / Instructional Material on Web I have posted introductory statistical instructional chapters using Epi Info (v. 6) on the Web for all to use. The work is still in draft form, but perhaps it will be useful to some of you just the same. (Figures do not yet appear in this web document although some are referenced, for instance, and there might be typographical and grammatical errors in the text, since I have not yet had time to proof-read it. For this, I apologize.) The chapter titles are: 1. Epi Info Version 6 Basics 2. Continuous Outcome, Single Group 3. Continuous Outcome, Paired Samples 4. Continuous Outcome, Two Independent Groups 5. Continuous Outcome, Several Independent Groups 6. Continuous Outcome, Continuous Predictor (Correlation and Regression) 7. Continuous Outcome, Multiple Predictors (Multiple Regression) 8. Binary Outcome, Single Group 9. Binary Outcome, Two Independent Groups, Forward-Directional (Cohort) and Adirectional Designs 10. Binary Outcome, Two Independent Groups, Backward-Directional Designs (Case-Control Studies) 11. Stratified Tables (Introduction to Confounding and Interaction) 12. Binary Outcome, Paired (Matched) Samples 13. Logistic Regression 14. Poisson Events 15. Comparison of Rates 16. Multi-categorical Outcome, Single Group 17. Multi-categorical Outcome, Independent Groups Since this site is under development, some chapters may not be available when you sign on. The address for the work is www.sjsu.edu/faculty/gerstman/EpiInfo. (This address is case sensitive.) The title of the work is "Data Analysis with Epi Info." You may use this material freely. The suggested citation is: Gerstman B.B. (1999). Data Analysis with Epi Info. Web document: www.sjsu.edu/faculty/gerstman/EpiInfo. Comments and constructive criticisms are welcome. Bud Gerstman San Jose State University San Jose, California, USA B_Gerstman@compuserve.com ------_=_NextPart_001_01BF045D.B7F1EEFE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [EPI-INFO] Announcement / Instructional Material on = Web

Good news, Bud.  Thanks for doing = this!!! 

      -----Original = Message-----
      From:   B. Gerstman [mailto:B_Gerstman@COMPUSERVE.C= OM]
      Sent:   Tuesday, August 24, 1999 12:56 PM
      To:     EPI-INFO@LISTSERV.CDC.GOV
      Subject:       = [EPI-INFO] Announcement / = Instructional Material on Web

      I have posted introductory statistical = instructional chapters using Epi
      Info (v. 6) on the Web for all to = use. The work is still in draft form, but
      perhaps it will be useful to some of = you just the same. (Figures do not yet
      appear in this web document although = some are referenced, for instance, and
      there might be typographical and = grammatical errors in the text, since I
      have not yet had time to proof-read = it. For this, I apologize.)

      The chapter titles are:

      1.      Epi = Info Version 6 Basics
      2.      = Continuous Outcome, Single Group
      3.      = Continuous Outcome, Paired Samples
      4.      = Continuous Outcome, Two Independent Groups
      5.      = Continuous Outcome, Several Independent Groups
      6.      = Continuous Outcome, Continuous Predictor (Correlation and
      Regression)
      7.      = Continuous Outcome, Multiple Predictors (Multiple Regression)
      8.      = Binary Outcome, Single Group
      9.      = Binary Outcome, Two Independent Groups, Forward-Directional
      (Cohort) and Adirectional = Designs
      10.     Binary = Outcome, Two Independent Groups, Backward-Directional
      Designs (Case-Control Studies)
      11.     = Stratified Tables (Introduction to Confounding and Interaction)
      12.     Binary = Outcome, Paired (Matched) Samples
      13.     Logistic = Regression
      14.     Poisson = Events
      15.     = Comparison of Rates
      16.     = Multi-categorical Outcome, Single Group
      17.     = Multi-categorical Outcome, Independent Groups

      Since this site is under development, = some chapters may not be available
      when you sign on.

      The address for the work is = www.sjsu.edu/faculty/gerstman/EpiInfo. (This
      address is case sensitive.) The title = of the work is "Data Analysis with
      Epi Info." You may use this = material freely. The suggested citation is:

      Gerstman B.B. (1999). Data Analysis = with Epi Info. Web document:
      www.sjsu.edu/faculty/gerstman/EpiInfo.

      Comments and constructive criticisms = are welcome.

      Bud Gerstman
      San Jose State University
      San Jose, California, USA
      B_Gerstman@compuserve.com

------_=_NextPart_001_01BF045D.B7F1EEFE-- From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9909B" ========================================================================= Date: Sat, 11 Sep 1999 16:52:33 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dr. Luis F. Fajardo P. MD M.Sc. Esp. Ped, Esp. Sis" Subject: Domeas progrmam MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Hi Some time ago Dr Dean mentioned the posibility of having "domeas" programa updated so it would run of faster computers. I wonder if any pf the memembers of the list know when this utility will be available Thanks in advance L Fajardo ========================================================================= Date: Tue, 14 Sep 1999 09:16:53 +0200 Reply-To: connollc@mrc.ac.za Sender: Epi Info Discussion Group From: Cathy Connolly Subject: Modifying variables generated and saved in analysis MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT How do I modify variables in epi-info that were not in the original .QES file, that is were created and saved as part of the analysis as a new rec file? Specifically I need to: a. change a date to make it Y2k compatible and the patch only deals modifications for variables appearing in the original *.qes file; b. change a variable from a one digit to a two digit format again one that doesn't appear in the original *.qes file but in updated rec files? Thank you Cathy Connolly CATHY CONNOLLY Senior Scientist Centre for Epidemiological Research in South Africa CERSA (Durban) Medical Research Council PO Box 17120, Congella 4013 South Africa Tel +27 (0)31 2051 481 Fax + 27 (0)31 2058 840 ========================================================================= Date: Tue, 14 Sep 1999 10:10:58 +1 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Merel van Oirschot Organization: Universiteit Utrecht Subject: Information about Compstat 2000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Dear madam/sir, Following you will find the information concerning the XIV Compstat conference of the International Association for Statistical Computing. The conference will take place in Utrecht, The Netherlands from 21-25 August 2000. The scientific programme will consist of a variety of interesting sessions and also a full programme of social events will be offered. We also refer you to the website http://neon.vb.cbs.nl/rsm/compstat We are looking forward to seeing you in Utrecht in 2000! Sincerely, Local Organisation Committee &Scientific Programme Committee Compstat 2000. Compstat 2000 The conference will be jointly organised by the Department of Methodology and Statistics of Utrecht University and the Department of Statistical Methods of Statistics Netherlands. The Department of Methodology and Statistics of Utrecht University has a strong involvement in statistical computing and applied statistics. Statistics Netherlands is also known for its expertise in applied statistics, and for its innovative approach in the application of recent developments of information technology to survey data collection and processing. Approximately 35 kilometres south of Amsterdam Utrecht stands in the heart of the Netherlands. It was founded in 48 by the Romans, who built a military settlement along the shore of the Rhine. In 695 the English Benedictine monk Willibrord came to christianise Francks and Frisians and made Utrecht to a centre of religion, which is still noticeable n present times. For centuries, Utrecht was the largest and only city of importance in the northern part of the Netherlands. Today, Utrecht is an attractive city. With 230,000 inhabitants Utrecht is the fourth largest city in The Netherlands, only Amsterd , Rotterdam and The Hague having greater populations. With its magnificient cathedral, churches, canals museums and historic buildings dating from the 16th century onwards Utrecht is a city of outstanding culture. As host to the largest University in The therlands Utrecht also offers a lively and varied social scene with busy restaurants, cafes, pubs and nightspots. Utrecht is easy reached by road and rail. Delegates flying into Amsterdam Schiphol Airport can take the train from the airport directly to th centre of the city. If you would like to find out more about Utrecht and how to reach it please visit the website. There will be a full programme of social events including a Buffet Reception, Concert, Dinner and excursions, to allow participants to exchange ideas, meet friends and see many of the local attractions. Scientific Programme Statistical computing provides the link between statistical theory and applied statistics. As at previous Compstats, the scientific programme will cover all aspects of this link, from the development and implementation of new statistical ideas through to user experiences and software evaluation. The programme should appeal to anyone working in statistics and using computers, whether in universities, industrial companies, government agencies, research institutes or as software developers. Papers may be submitted in any of the following categories: . Statistical research - Development of statistical methodology, especially topics that rely on computers and computing environments. . Computing - Contributions of computer algorithms, tools and environments to the practice of statistics. . Applied statistics - Innovative applications of statistical computing in any area of current interest. The scientific programme will consist of a variety of sessions, such as parallel and plenary presentations, invited and contributed papers, poster sessions, one or two tutorials, and software demonstrations. The Scientific Programme Committee seeks papers touching on all aspects of computational statistics. This includes theory, applications, and implementations. The Scientific Programme Committee also welcomes papers in the field of Official Statistics, i.e. papers in the field of data collection, data editing, data analysis, and data publications. Papers may be selected by the Scientific Programme Committee as full contributions, short contributions or posters. Selection is based on submitted abstracts of up to two pages. These should include the main results and references, highlighting novel asp ts and indicating their relevance to the above mentioned three categories. Further details and sample abstract formats can be found on the website. Full contributions will be refereed and published, with the invited papers, in a volume of Proceedings by ysica Verlag. Short communications and posters will be published in a 2nd volume by Statistics Netherlands and Utrecht university. At the conference, several prices will be awarded: . Three prices, each worth 1000 Dutch Guilders, will be awarded for the best three contributions submitted and presented by young participants (upper age limit 35 years for all authors on August 31, 2000). . A price will be awarded for the best poster presentation. Invited speakers Keynote speakers . Donald Rubin (The broad role for multiple imputation in statistical science), and . Peter Kooiman (Mass imputation versus sequential weighting of a virtual census) At the moment invited speakers include . Noel Cressie (Space-time Kalman filtering and MCMC), . Antoine de Falguerolles (generalized linear models with bilinear terms), . David Draper (Computational issues in MCMC fitting of multilevel models), . David Hand (Methodological issues in data mining) . Georges Hebrail (Practical data mining in a large utility company), . Youngjo Lee (Analysis of correlated non-Gaussian data via hierarchical generalized linear models), . Helmut Luetkepohl (Bootstrapping impulse responses in VAR analyses), . Agustin Maravall (Some applications of the signal extraction technique to socioeconomic time series), . Erich Neuwirth (Spreadsheets in statistical education), . Walter Racugno (Bayes factors for model selection and prediction) . Hans van Houwelingen (Nonproportional hazards models in survival analysis), . Ari Verbyla (Spatio-temporal modelling), Please check our home page for the latest and more detailed information. Software demonstration and book exhibition There will be demonstration stands for software producers to present their products, and book exhibitions. Important deadlines Abstracts received (post or e-mail): 8 November 1999 Notification to authors: 15 December 1999 Contributed paper for refereeing: 11 March 2000 Final versions of contributed papers 1 May 2000 Short communications and posters: 1 May 2000 Local Organising Committee Wim Jansen , Chair (Utrecht University) Douwe van der Sluis (Netherlands Society for Statistics and Operation research) Gerrit Stemerdink (ISI) Leonieke Wijngaards (Utrecht University) Scientific Programme Committee Peter van der Heijden, Netherlands, Chair Jelke Bethlehem, Netherlands Andrej Blejec, Slovenia Wolfgang Haerdle, Germany Roger Payne, United Kingdom Christian Robert, France Roberta Siciliano, Italy Registration fees Early Registration; deadline = 1 April 2000, IASC/ISI/Other Approved NLG 650,00 Others NLG 750,00 Standard Registration; deadline = 21 June 2000, IASC/ISI/Other Approved NLG 750,00 Others NLG 850,00 Late Registration; after 21 June 2000 NLG 950,00 Students (send in document of University Registration) NLG 150,00 Address for correspondence FBU Congress Bureau Utrecht University Attn: Mrs. Marcelle Buma P.O. Box 80125 3508 TC Utrecht The Netherlands Phone: +31 30 253 2728 Fax: +31 30 253 5851 E-mail: compstat@fbu.uu.nl For more information and for registration see website: http://neon.vb.cbs.nl/rsm/compstat To ensure that you receive further information, please send an email to compstat@fbu.uu.nl, or a letter to the address above. Anouk Denis FBU Congress Bureau University of Utrecht P.O. Box 80125 3508 TC Utrecht The Netherlands Tel: +31.30.2532728 Fax: +31.30.2535851 ========================================================================= Date: Tue, 14 Sep 1999 11:19:25 -0700 Reply-To: gdaurat@club-internet.fr Sender: Epi Info Discussion Group From: Gérald Organization: DAURAT Subject: Re: Modifying variables generated and saved in analysis Comments: To: connollc@mrc.ac.za MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cathy Connolly wrote: > > How do I modify variables in epi-info that were not in the original .QES file, that is were > created and saved as part of the analysis as a new rec file? Specifically I need to: > > a. change a date to make it Y2k compatible and the patch only deals modifications > for variables appearing in the original *.qes file; > > b. change a variable from a one digit to a two digit format again one that doesn't > appear in the original *.qes file but in updated rec files? > > Thank you > Cathy Connolly > CATHY CONNOLLY > Senior Scientist > Centre for Epidemiological Research in South Africa > CERSA (Durban) > Medical Research Council > PO Box 17120, Congella 4013 South Africa > Tel +27 (0)31 2051 481 Fax + 27 (0)31 2058 840 The easier way is to generate a new .QES file using REC2QES.exe file (not accessible from main EPI6 menu, launch it from Dos or file explorer). This file is self documented. Another way would be to modify the original .QES adding appropriate variables to match the Analysis generated files and changes to Y2K. BEWARE of variables names types and lenght. Then you can update your file with the appropriate programs to fit Y2K. By the way, the french EPI6 version has a program called AN2000.EXE witch is really nice (Look for it on www.rnsp-sante.fr). G Daurat Montpellier France ========================================================================= Date: Tue, 14 Sep 1999 11:55:37 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Darwin J. Fedorick" Subject: Re: Modifying variables generated and saved in analysis Comments: To: Cathy Connolly In-Reply-To: <19990914071606969.AAA276.333@mrc.ac.za> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > How do I modify variables in epi-info that were not in the > original .QES file, that is were created and saved as part > of the analysis as a new rec file? Specifically I need to: > > a. change a date to make it Y2k compatible and the patch only deals > modifications for variables appearing in the original *.qes file; Let's see if I first understand the question...I think you have a file that ANALYSIS generated from data in one or more .QES files, and we can call it RESULT.REC for example. Some DATE field in RESULT.REC is defined as DD/MM/YY rather than DD/MM//YYYY so extend to the time period beyond the year 2000. If that is the case, then I would simply use ANALYSIS to recreate the file using a RedoDate.PGM with lines something like - READ RESULT.REC DEFINE NEW_DATE __________ /NOECHO DEFINE DATEFORMAT /NOECHO DEFINE YEARDIGITS #### /NOECHO YEARDIGITS = DATE[7,2] IF YEARDIGITS < 50 THEN YEARDIGITS = YEARDIGITS + 100 (I used 1950 as a cutoff so 00-49 is 2000-2049 and 50-99 is 1950-1999) YEARDIGITS = 1900 + YEARDIGITS NEW_DATE = DATE[1,6] + YEARDIGITS DATEFORMAT = NEW_DATE I'm not certain you need DATEFORMAT at all...it may be superfluous. Then later rewrite the file as ROUTE NEWRESULT.REC WRITE RECFILE NOT NEW_DATE YEARDIGITS So now NEWRESULT.REC contains all the same variables as RESULT.REC plus an added variable DATEFORMAT which is DATE, adjusted into Y2K format. > b. change a variable from a one digit to a two digit format again one > that doesn't appear in the original *.qes file but in updated rec files? Same idea, but the date range/cutoff is more of a problem...how do you know if 9 is 1979, 1989 or 1999? Darwin Fedorick From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9908D" ========================================================================= Date: Tue, 24 Aug 1999 12:56:27 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "B. Gerstman" Subject: Announcement / Instructional Material on Web Comments: To: MPH ListServe MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 I have posted introductory statistical instructional chapters using Epi Info (v. 6) on the Web for all to use. The work is still in draft form, b= ut perhaps it will be useful to some of you just the same. (Figures do not y= et appear in this web document although some are referenced, for instance, a= nd there might be typographical and grammatical errors in the text, since I have not yet had time to proof-read it. For this, I apologize.) = The chapter titles are: 1. Epi Info Version 6 Basics 2. Continuous Outcome, Single Group 3. Continuous Outcome, Paired Samples 4. Continuous Outcome, Two Independent Groups 5. Continuous Outcome, Several Independent Groups = 6. Continuous Outcome, Continuous Predictor (Correlation and Regression) 7. Continuous Outcome, Multiple Predictors (Multiple Regression) = 8. Binary Outcome, Single Group 9. Binary Outcome, Two Independent Groups, Forward-Directional (Cohort) and Adirectional Designs 10. Binary Outcome, Two Independent Groups, Backward-Directional Designs (Case-Control Studies) 11. Stratified Tables (Introduction to Confounding and Interaction) 12. Binary Outcome, Paired (Matched) Samples 13. Logistic Regression 14. Poisson Events 15. Comparison of Rates 16. Multi-categorical Outcome, Single Group = 17. Multi-categorical Outcome, Independent Groups Since this site is under development, some chapters may not be available when you sign on. = The address for the work is www.sjsu.edu/faculty/gerstman/EpiInfo. (This address is case sensitive.) The title of the work is "Data Analysis with Epi Info." You may use this material freely. The suggested citation is: = Gerstman B.B. (1999). Data Analysis with Epi Info. Web document: www.sjsu.edu/faculty/gerstman/EpiInfo. = Comments and constructive criticisms are welcome. Bud Gerstman San Jose State University San Jose, California, USA B_Gerstman@compuserve.com ========================================================================= Date: Thu, 26 Aug 1999 10:12:24 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Heath Harris Subject: Epi-Info 2000 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I attended the Spring Training for EpiInfo 2000, Does Anyone know if a = later beta version has been released since then and how to get it. Some things I have noticed with the latest EpiInfo 2000 beta version is if = you have a Microsoft Access Data Base password protected you can not read = it in EpiInfo 2000 analysis and that EpiInfo 2000 does not treat byte = variables as number variables, you cannot calcualte means on them. Thanks Heath Harris=20 Salt Lake City-County Health Department Bureau of Epidemiology Phone: 801-534-4643 Fax :801-534-4557 E-mail: hharris=40hl6.co.slc.ut.us ========================================================================= Date: Fri, 27 Aug 1999 10:06:10 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "William B. Cissell" Subject: Epi info expert in Texas MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Epi Info Users of Texas: I am the Associate Director of the Texas Statewide Coordinated Statement of Need Project, which developed a plan for assisting providers of services under the Ryan White Care Act funding in gathering and reporting needs assessment data. Currently, we are in the process of developing a client survey instrument and determining the secondary data elements that need to be reported. In anticipation of TDH and/or HRSA requiring service providers to collect data using the client survey instrument and report it along which certain secondary data, we are trying to find a software package that has spreadsheet, data analysis, and summary output capacity that can be used by staff with a wide range of computer and data treatment skills. I would like to hear from some of you who have used Epi Info extensively about whether or not you believe it has potential to meet our needs. We realize that Microsoft Access and Excel can be used in combination to do what we want done. SAS and SPSS are probably much more sophisticated than what we need. Our concern is that some providers may not have staff skilled in use of Microsoft products. Even where the staff are familiar with Microsoft products, they may be unfamiiar with either/both Access and Excel. We are seeking a package that would require the least amount of technical assistance to the end users. Bill Cissell wcissell@twu.edu Professor & Associate Director SCSN Project Texas Woman's University P.O. Box 425499 Denton, TX 76204-5499 940-898-2861 FAX 940-898-2859 ========================================================================= Date: Fri, 27 Aug 1999 18:04:33 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Heath Harris Subject: Re: Epi info expert in Texas Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, Mr. Cissell, I am not from Texas but work in SLC, Utah, and have worked extensively (6 = years of experience) with Epi Info on many different projects and in = different environments including Multi-User Data Entry, My reccomendations are as follows, First of all, at this point EpiInfo is still a Dos Application, so if the = people that will be working with this project are used to windows this may = pose to be a problem. The new Epi 2000 for windows is still in beta = version and not ready to use yet. By far the main strength of Epi-Info is its Statistical Program called = =22Analysis=22. This a user freindly pachage that even though it is in = Dos, you can get some pretty usefull statistical output with out a lot of = programming. Since it is Dos though you will have to reformat the output = if you want to publish it on the WeB. Analysis outputs to ASCI txt only. My reccomendation is to Use Microsoft Access to build your Data Base = around your survey instrument to store the data and create data entry = protocols, Epi-Info is limitted in these area=27s. then output you data = stored in Access to a DBF format and use Epi Info Analysis for data = analysis and output. The windows version of Epi 2000 will read acess = files automatically in the future also. The only other advantage of Epi Info is that it is public domain so it is = free. Hope this helps Heath Harris=20 Salt Lake City-County Health Department Bureau of Epidemiology Phone: 801-534-4643 Fax :801-534-4557 E-mail: hharris=40hl6.co.slc.ut.us >>> =22William B. Cissell=22 08/27 10:06 AM >>> Epi Info Users of Texas: I am the Associate Director of the Texas Statewide Coordinated Statement of Need Project, which developed a plan for assisting providers = of services under the Ryan White Care Act funding in gathering and reporting = needs assessment data. Currently, we are in the process of developing a client survey instrument and determining the secondary data elements that need to = be reported. In anticipation of TDH and/or HRSA requiring service providers = to collect data using the client survey instrument and report it along which certain secondary data, we are trying to find a software package that has spreadsheet, data analysis, and summary output capacity that can be used = by staff with a wide range of computer and data treatment skills. I would like to hear from some of you who have used Epi Info extensively about whether or not you believe it has potential to meet our needs. We realize that Microsoft Access and Excel can be used in = combination to do what we want done. SAS and SPSS are probably much more sophisticated= than what we need. Our concern is that some providers may not have staff skilled in use of Microsoft products. Even where the staff are familiar = with Microsoft products, they may be unfamiiar with either/both Access and = Excel. We are seeking a package that would require the least amount of technical assistance to the end users. Bill Cissell wcissell=40twu.edu=20 Professor & Associate Director SCSN Project Texas Woman=27s University P.O. Box 425499 Denton, TX 76204-5499 940-898-2861 FAX 940-898-2859 ========================================================================= Date: Sat, 28 Aug 1999 11:38:42 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dr. Luis F. Fajardo P. MD M.Sc. Esp. Ped, Esp. Sis" Subject: Domeas program MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi. Some time ago Dr Dean suggest the posibility to have, in the near future,the domeas program updated, so anthropometric calculations could be done in fast computers, within ENTER - CHECK enviroment. I wonder when this usefull tool will be available. Thanks in advance for this information. L. Fajardo MD M.Sc From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9908C" ========================================================================= Date: Sun, 15 Aug 1999 17:12:37 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: STEIN IKDAHL Subject: unsubscribe MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01BEE741.5FAE46E0" This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BEE741.5FAE46E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unsubscribe ------=_NextPart_000_0008_01BEE741.5FAE46E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
unsubscribe
------=_NextPart_000_0008_01BEE741.5FAE46E0-- ========================================================================= Date: Mon, 16 Aug 1999 12:03:55 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Population size N in sample size calculations In-Reply-To: <71364B64597CD211B02800A0C921A213CB4257@psg.ucsf.edu> MIME-Version: 1.0 Estie Hudes writes: >I tried today one of the StatCalc modules: >EpiTable/Sample Size/Single Proportion > >Although the formula has the population size N in it: >N*z^2*p*(1-p)/(d^2*(N-1)+z^2*p*(1-p))) > >The module does not use it. It gives identical sample size for any >value of N. My version works OK. The difference should be apparent with small population sizes (try 200 and then 2000). The BIG problem with the sample size in EpiTable is that it does not work for complex samples from small populations with low prevalence (e.g. from a stratified cluster sampled blindness survey in over 60's in Afghanistan). Try: Size of the population 5000 Desired precision (%) 0.5 Expected prevalence (%) 2 Design effect 3 and get a sample size that is 640 larger than the population! Very silly. If you do complex sample surveys then you can use my SampleXS program to calculate sample sizes (www.myatt.demon.co.uk). Mark -- Mark Myatt ========================================================================= Date: Mon, 16 Aug 1999 10:42:51 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: numeric codes for colors In-Reply-To: <4.2.0.58.19990802200311.009d34c0@tunku.uady.mx> MIME-Version: 1.0 Jose A. Farfan writes: >Dear member of the list: >I would like to know the numeric code for the different colors available in >EpiInfo. I would like to make changes in the colors displayed in my >database, changing the numeric codes in the .rec file. >I will appreciate any help. To see a list of codes start ENTER and press F2. Mark -- Mark Myatt ========================================================================= Date: Mon, 16 Aug 1999 10:46:09 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: starting Analysis in a different directory In-Reply-To: <71364B64597CD211B02800A0C921A213CB420C@psg.ucsf.edu> MIME-Version: 1.0 Estie Hudes writes: >I would like to start EpiInfo in a different directory, say C:\EPIWORK. >I have added this directory to the DOS PATH (in autoexec.bat).. >I can start EpiInfo just fine, but when I try to start ANALYSIS, I get >an error message saying that the help file is not available. >This happens also if I type "analysis" at the DOS command prompt. >In addition, the tutorials and the examples are not available. > >Is the only way do run EpiInfo smoothly is by starting it in the Epi6 >directory, and then use Setup to change the path for data files? No need. I use this batch file to start EpiInfo in any directory. @echo off set oldpath=%path% path c:\epi6;%oldpath% epi6 path %oldpath% cls With some operating systems (older versions of DOS and OS/2) you might need to add an APPEND command: @echo off set oldpath=%path% path c:\epi6;%oldpath% append c:\epi6 /x:on epi6 append ; path %oldpath% cls Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Mon, 16 Aug 1999 10:58:35 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: runtime error with describe /all In-Reply-To: <71364B64597CD211B02800A0C921A213CB422A@psg.ucsf.edu> MIME-Version: 1.0 Estie Hudes writes: >Wow! That's great! > >I have tried describe * not id / all >but that of course doesn't work when there are non-numeric variables in >the file. > >Yes, I agree that the ID variable needs to be checked separately. > >[ I usually do it in Stata. There is a user-written-written command >(these are easy to write in Stata) called -dups- >-dups id, key(id)- ] Here is an EpiInfo equivalent: erase dups.rec route dups.rec output freq idno read dups.rec select count > 1 list Mark -- Mark Myatt ========================================================================= Date: Mon, 16 Aug 1999 10:54:51 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: runtime error with describe /all In-Reply-To: <71364B64597CD211B02800A0C921A213CB4226@psg.ucsf.edu> MIME-Version: 1.0 Estie Hudes writes: >It seems that when the dataset is not small (n=1625, number of variables >15), "describe /all" produces a runtime error. >Although "describe" by itself works just fine, the "/all" switch causes >problems. I did some trial and error, and I think this is caused by the >ID variable. >The ID variable has values from 1 to 3047 (it is stored as integer of >length 4) >I am not sure why computing the 6 additional summary statistics (min, >Q1, median, Q3, max, mode) would cause the problem, but it certainly >does. > >The dataset I am using is onchall.rec, provided by Brixton Books with >the Data Management text written by Mark Myatt and others. > >The message I get is: >Runtime error 202 at o5F5:0DA9 > >Is there a fix for this problem? Nice to see someone using my book :-). I get the same error. A work round is to use the FREQ command with the /N (No tables) option: FREQ * /N or you can drop the IDNO variable from the DESCRIBE command using NOT: DESCRIBE /ALL NOT IDNO Mark -- Mark Myatt ========================================================================= Date: Mon, 16 Aug 1999 13:46:24 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: PEPI for Windows - new test version of WHATIS Comments: To: agd1@cdc.gov, alc@servidor.unam.mx, alkral@itsa.ucsf.edu, andrew.forbes@med.monash.edu.au, antunesc@mono.icb.ufmg.br, bengt.moller@mbox2.swipnet.se, bernt.lindtjorn@cih.uib.no, bmanyame@hqfaus01.unicef.org, bpazva@harare.iafrica.com, bxe2@cdc.gov, castellano.j@mcd.gen.de.us, cdckms@sph.emory.edu, chklein@manguinhos.ensp.fiocruz.br, ck@dynamite.com.au, coflunkc@leonis.nus.sg, consult@tstt.net.tt, coulombi@b3e.jussieu.fr, crmcc@gate.net, d.u.pfeiffer@massey.ac.nz, dnordlund@aol.com, eramalle@goriz.sendanet.es, esterman.adrian@health.sa.gov.au, evan.sergeant@smtpgwy.agric.nsw.gov.au, fmedpct@md2.md.chula.ac.th, fwolfe@msus1.msus.edu, g.hartel@mailbox.uq.edu.au, garst@uvapsy.psy.uva.nl, gomes@lelo.uem.mz, gpatrone@opal.tufts.edu, hans.stenlund@stat.umu.se, heberto@meakins.lan.mcgill.ca, jag.atrie@health.wa.gov.au, james_wood@compuserve.com, jaf@lamar.colostate.edu, jmatute@pronet.net.gt, jucar@cica.es, ljorm@doh.health.nsw.gov.au, lucas@dgsp.scstf.rcanaria.es, mamartinez@mail2.cti.unav.es, martinez_j@a1.rcdp.gov, mccleary@mrrc.bio.uci.edu, medicur1@edu.uch.gr, mikael.aberg@primnet.se, mikal.ustad@ism.uit.no, mulderym@fs7003.pg.tno.nl, pani@ymed.ks.se, per.blanck@mailbox.swipnet.se, pgnetto@ax.apc.org, pierreclaquin@compuserve.com, pmb@mhri.edu.au, promed@riosoft.softex.br, r.fisher@unsw.edu.au, ratti@usa.net, rbk8@cdc.gov, rmccart@epin.ab.umd.edu, rvs3@wonder.em.cdc.gov, sas@ipe.ufg.br, sonia@stat.psu.edu, statcon@ix.netcom.com, stefan.ma@commed.hku.hk, pturri@mail.state.tn.us, gilles@epiconcept.fr, normar01@mcgc16.med.nyu.edu, mcmillan@cc.ucsf.edu, jamie_hockin@inet.hwc.ca, mark_veitch.mdu@muwaye.unimelb.edu.au, jed5@cdc.gov, eramalle@mail.sendanet.es, Koomen.Em@net.HCC.nl, s.ritter@iop.bpmf.ac.uk, Rainer.Muche@medizin.uni-ulm.de, S.S.MASTANA@lboro.AC.UK, TCHUR@doh.health.nsw.gov.au, DDedman@phls.co.uk, jsantos@uec.inta.uchile.cl, Bob@exo.com, BHolden536@aol.com, kannika@cmu.chiangmai.ac.th, waa101@uriacc.uri.edu, ACTUARY@asko.donetsk.ua, EBRENNER@compuserve.com, jzg@cs.bham.ac.uk, FPetschke@t-online.de, wilsonsx@novell2.bham.ac.uk, jmc@med.pitt.edu, EpiMon@aol.com, gxs03@health.state.ny.us, busson@neptune.chu-stlouis.fr, steve.dunn@agric.nsw.gov.au, nbirkett@zeus.med.uottawa.ca, joe@ty-coch.demon.co.uk, JML@dadlnet.dk, damien@jolley.com.au, Epidemiology List , Joe Abramson , bart@hgea.org, jha@vms.huji.ac.il, rjfreund@NewNetra.ensp.fr, sph1804@utsph.sph.uth.tmc.edu, jehrlich@dairyvets.com, bcmiller@biostats.uwo.ca, penamanu@paho.org, chotiwan@who.net, fmedpct@md2.md.chula.ac.th, kclun@nus.edu.sg, ZHUKAK75@ccvax.mmc.edu, nfchu@hsph.harvard.edu, chklein@manguinhos.ensp.fiocruz.br, DANP@CIKC.ORG, jat.sandhu@bristol.ac.uk, Vera.Todorovic@bhcs-tr.trent.nhs.uk, johnf@netaxs.com, fgamboa@hotmail.com, rgempp@werken.ufro.cl, MODAOJUN@epid.lan.mcgill.ca, hegd@servidor.unam.mx, l.gostelow@scfuk.org.uk, jmc@med.pitt.edu, ananda@sunnet.com.br, flogisto@usa.net, N.C.Unwin@newcastle.ac.uk, s.loeffler@vet.uu.nl, jmatute@pronet.net.gt, cdckms@sph.emory.edu, lbautista@multinet.com.co, jchaui@ssdnet.com.ar, pab555@comadrid.es, yv.bonnier@ccisd.org, JML@dadlnet.dk, IOKOSUN@wpo.it.luc.edu, JUNG100W@cdc.gov, kevin_sullivan@oz.ped.emory.edu, marcelo@inf.ufsc.br, lbautista@multinet.com.co, maupome@unixg.ubc.ca, SHIYF@PUBLIC2.ZZ.HA.CN, Lengeler@ubaclu.unibas.ch MIME-Version: 1.0 PEPI users, The PEPI for Windows test page (www.myatt.demon.co.uk) now allows a download of the latest test version of WHATIS (v1.02). The main change is the addition (at the suggestion of an Australian PEPI user) of Armitage and Berry's procedure for estimating confidence intervals for the difference between two correlated proportions. This is an approximate method based on exact Fisher's or mid-P intervals (Armitage and Berry, Statistical Methods in Medical Research, 3rd edn, p. 128). It is now provided in the "CI.. A difference between proportions (paired data)" option, as an alternative to Fleiss's method. Mark -- Mark Myatt ========================================================================= Date: Mon, 16 Aug 1999 10:22:22 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Judith S. Jacobson, Dr.P.H." Subject: Exporting long records MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I now have several epi-info databases with large numbers of variables. I've been trying to export them into SPSS via DBF, but when I do so I get a message that this format will accept only 250 variables. Is there a way to export the whole database? Or is there a way to cut it in half and put it back together again? -- Judith S. Jacobson, Dr.P.H. Division of Epidemiology, PH18-118 Joseph L. Mailman School of Public Health Columbia University 600 West 168th Street New York, NY 10032 (212) 305-7629 (voice) (212) 305-9413 (fax) ========================================================================= Date: Mon, 16 Aug 1999 16:32:38 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Exporting long records In-Reply-To: <37B848CE.2811@columbia.edu> MIME-Version: 1.0 Judith S. Jacobson, Dr.P.H. writes: >I now have several epi-info databases with large numbers of variables. >I've been trying to export them into SPSS via DBF, but when I do so I >get a message that this format will accept only 250 variables. Is there >a way to export the whole database? Or is there a way to cut it in half >and put it back together again? That is a limitation of the DBF file format. Try exporting as LOTUS. I think the .WKS format allows up to 8192 columns. Mark -- Mark Myatt ========================================================================= Date: Tue, 17 Aug 1999 11:47:29 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Zubieta, Juan" Subject: Re: Exporting long records MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Are you exporting from analysis (a .pgm program)? Thanks Juan Carlos Zubieta MD MPH Epi Info Development Team Centers For Disease Control 2877 Brandywine Rd. Williams Building 4th Floor Rm 4803.03 Atlanta, GA 30341 Phone (770) 488 8439 -----Original Message----- From: Judith S. Jacobson, Dr.P.H. [mailto:jsj4@COLUMBIA.EDU] Sent: Monday, August 16, 1999 1:22 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Exporting long records I now have several epi-info databases with large numbers of variables. I've been trying to export them into SPSS via DBF, but when I do so I get a message that this format will accept only 250 variables. Is there a way to export the whole database? Or is there a way to cut it in half and put it back together again? -- Judith S. Jacobson, Dr.P.H. Division of Epidemiology, PH18-118 Joseph L. Mailman School of Public Health Columbia University 600 West 168th Street New York, NY 10032 (212) 305-7629 (voice) (212) 305-9413 (fax) ========================================================================= Date: Thu, 19 Aug 1999 08:55:44 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Conn, Judith" Subject: Re: PEPI for Windows - new test version of WHATIS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Mark- What is PEPI and Whatis?? Judy Conn -----Original Message----- From: Mark Myatt [mailto:mark@MYATT.DEMON.CO.UK] Sent: Monday, August 16, 1999 8:46 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] PEPI for Windows - new test version of WHATIS PEPI users, The PEPI for Windows test page (www.myatt.demon.co.uk) now allows a download of the latest test version of WHATIS (v1.02). The main change is the addition (at the suggestion of an Australian PEPI user) of Armitage and Berry's procedure for estimating confidence intervals for the difference between two correlated proportions. This is an approximate method based on exact Fisher's or mid-P intervals (Armitage and Berry, Statistical Methods in Medical Research, 3rd edn, p. 128). It is now provided in the "CI.. A difference between proportions (paired data)" option, as an alternative to Fleiss's method. Mark -- Mark Myatt ========================================================================= Date: Fri, 20 Aug 1999 09:26:10 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: PEPI for Windows - new test version of WHATIS In-Reply-To: <6B7B0B0E8F2BD111AFE90001FA3751C98108DC@mcdc-atl-62.cdc.gov> MIME-Version: 1.0 Judith Conn wrote: >What is PEPI and Whatis?? PEPI (Programs for EPIdemiologists) is a suite of programs that have been around for many years. It started life as a suite of programs for programmable calculators and then for the PC. It is now being moved to Windows. Most PEPI programs work with pre-tabulated data although some can work with raw data. PEPI provides most of the calculations that an epidemiologist / medical statistician will ever need including some that are hard to find elsewhere. The program "Whatis?" provides: 1) A scientific calculator with memory for constants, results and formulae. 2) Z and chi-square distributions 3) Calculation of confidence intervals for proportion, risk, rate, risk ratio, rate ratio, difference between two proportions, odd ratio (paired data), mean, SD, any Poisson variate, ratio of two Poisson variates, and some more ... 4) Calculations with times and dates. It combines several of the DOS modules into one program. Other PEPI modules are now under development. Mark -- Mark Myatt ========================================================================= Date: Fri, 20 Aug 1999 08:41:25 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Conn, Judith" Subject: Re: PEPI for Windows - new test version of WHATIS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Thanks! How do I get these programs and documentation? Judy Conn -----Original Message----- From: Mark Myatt [mailto:mark@MYATT.DEMON.CO.UK] Sent: Friday, August 20, 1999 4:26 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] PEPI for Windows - new test version of WHATIS Judith Conn wrote: >What is PEPI and Whatis?? PEPI (Programs for EPIdemiologists) is a suite of programs that have been around for many years. It started life as a suite of programs for programmable calculators and then for the PC. It is now being moved to Windows. Most PEPI programs work with pre-tabulated data although some can work with raw data. PEPI provides most of the calculations that an epidemiologist / medical statistician will ever need including some that are hard to find elsewhere. The program "Whatis?" provides: 1) A scientific calculator with memory for constants, results and formulae. 2) Z and chi-square distributions 3) Calculation of confidence intervals for proportion, risk, rate, risk ratio, rate ratio, difference between two proportions, odd ratio (paired data), mean, SD, any Poisson variate, ratio of two Poisson variates, and some more ... 4) Calculations with times and dates. It combines several of the DOS modules into one program. Other PEPI modules are now under development. Mark -- Mark Myatt ========================================================================= Date: Fri, 20 Aug 1999 15:05:47 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: PEPI for Windows - new test version of WHATIS In-Reply-To: <6B7B0B0E8F2BD111AFE90001FA3751C98108E2@mcdc-atl-62.cdc.gov> MIME-Version: 1.0 Conn, Judith writes: >Thanks! How do I get these programs and documentation? Judy Conn DOS versions of PEPI are available from most public FTP sites, Just do a search on PEPI in YAHOO or another search engine. The Windows test version is available only from: www.myatt.demon.co.uk > >-----Original Message----- >From: Mark Myatt [mailto:mark@MYATT.DEMON.CO.UK] >Sent: Friday, August 20, 1999 4:26 AM >To: EPI-INFO@LISTSERV.CDC.GOV >Subject: Re: [EPI-INFO] PEPI for Windows - new test version of WHATIS > > >Judith Conn wrote: > >>What is PEPI and Whatis?? > >PEPI (Programs for EPIdemiologists) is a suite of programs that have >been around for many years. It started life as a suite of programs for >programmable calculators and then for the PC. It is now being moved to >Windows. Most PEPI programs work with pre-tabulated data although some >can work with raw data. PEPI provides most of the calculations that an >epidemiologist / medical statistician will ever need including some that >are hard to find elsewhere. > >The program "Whatis?" provides: > > 1) A scientific calculator with memory for constants, results > and formulae. > > 2) Z and chi-square distributions > > 3) Calculation of confidence intervals for proportion, risk, > rate, risk ratio, rate ratio, difference between two > proportions, odd ratio (paired data), mean, SD, any Poisson > variate, ratio of two Poisson variates, and some more ... > > 4) Calculations with times and dates. > >It combines several of the DOS modules into one program. Other PEPI >modules are now under development. > >Mark > > >-- >Mark Myatt -- Mark Myatt From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9908B" ========================================================================= Date: Mon, 9 Aug 1999 17:49:36 +0200 Reply-To: maugat@ext.jussieu.fr Sender: Epi Info Discussion Group From: Sylvie Maugat Organization: C.CLIN Paris-Nord Subject: linked data files MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------B1F7738C08612BB1C8F9F72C" Content-Transfer-Encoding: 8bit Il s'agit d'un message multivolet au format MIME. --------------B1F7738C08612BB1C8F9F72C Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, Thanks for your help with last problems :"use EPIGLUE" I hope someone'll be able to help me with my new problem ... I built 2 linked data files : Qpat.rec for patients data (n=8) QKT .rec for catheters data (n=14) Each patient record is linked to one or more catheter record by the identifier : CODPAT In analysis, if I'm right, QKT is the main file so I writed : read QKT.rec relate CODPAT Qpat.rec in this case, if I do FREQ sexe I obtain H: 11 anf F:3, and not H:6 and F:2............ I also tried read qpat.rec and relate CODPAT QKT.rec and in this case if I do FREQ typKT I obtain result for only 8 KT and NOT for 14.......... What can I do to obtain the right result ? ONE MORE QUESTION : What can I do in .RPT file ? : Whitch variable'name used behind #USES ?? -- _________________________________________ Sylvie MAUGAT Epidémiologiste CCLIN Paris-Nord 15-21 rue de l'Ecole de Médecine 75006 PARIS Tel : 01 40 46 42 00 --------------B1F7738C08612BB1C8F9F72C Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Carte pour MAUGAT Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: MAUGAT n: ;MAUGAT email;internet: maugat@idf.ext.jussieu.fr x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard --------------B1F7738C08612BB1C8F9F72C-- ========================================================================= Date: Mon, 9 Aug 1999 16:13:18 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: LORI LEE Subject: epi 2000 beta installation problems Mime-Version: 1.0 Content-Type: text/plain I downloaded the 16 files from the ftp site for the epi2000 beta version (which a few hours) and when trying to install gor an I/O error. Is there any way to figure out which file is causing the problem?? Thanks very much. Lori Lee txpro.llee@sdps.org ========================================================================= Date: Mon, 9 Aug 1999 22:15:56 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Darwin J. Fedorick" Subject: Re: linked data files Comments: To: Sylvie Maugat In-Reply-To: <37AEF890.1D135B9C@idf.ext.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > I built 2 linked data files : > Qpat.rec for patients data (n=8) > QKT .rec for catheters data (n=14) > Each patient record is linked to one or more catheter record by the > identifier : CODPAT If, when you ENTER the data, QPAT.CHK does a line like RELATE CODPAT QKT.REC then yes, you need to do it the other way around when you read back the data in ANALYSIS. You would then do a .PGM file with something like these lines which you did: READ QKT.REC PROCESS IMMEDIATE IF (CODPAT = .) THEN GOTO NO_RECORDS RELATE CODPAT QPAT.REC ... PROCESS THE RELATED DATA ETC...ETC (WHEN DEBUGGING, YOU COULD INSERT A STATEMENT LIKE) BROWSE SO YOU CAN EXAMINE WHAT YOUR RELATED RECORDS LOOK LIKE. IF EVERYTHING LOOKS OK, THEN CONTINUE WITH YOUR PROCESSING AS USUAL ... ... ... :NO_RECORDS ECHO !! Unable to proceed because there are NO catheter records at all. ?\nPress any key to Quit ? IMMEDIATE GOTO EXIT_POINT :EXIT_POINT QUIT > In analysis, if I'm right, QKT is the main file so I writed : > read QKT.rec > relate CODPAT Qpat.rec SEEMS OK...I ALWAYS LIKE TO INSERT THE PROCESS LINE FIRST TO CHECK FOR NO RECORDS... > in this case, if I do FREQ sexe I obtain H: 11 anf F:3, and not H:6 and > F:2............ USE THE BROWSE COMMAND TO EXAMINE YOUR RELATED DETAIL RECORDS. > I also tried read qpat.rec and relate CODPAT QKT.rec and in this case > if I do FREQ typKT I obtain result for only 8 KT and NOT for > 14.......... > > What can I do to obtain the right result ? USE THE BROWSE COMMAND TO EXAMINE YOUR RELATED DETAIL RECORDS. Darwin Fedorick Edmonton, Alberta, Canada ========================================================================= Date: Mon, 9 Aug 1999 22:43:16 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Darwin J. Fedorick" Subject: Re: linked data files Comments: To: Sylvie Maugat In-Reply-To: <37AEF890.1D135B9C@idf.ext.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > in this case, if I do FREQ sexe I obtain H: 11 anf F:3, and not H:6 and > F:2............ THIS SOUNDS CORRECT....THERE ARE A TOTAL OF 14 RELATED RECORDS....SAY FOR EXAMPLE, YOU HAD RELATED THE 14 K RECORDS TO SOME SET OF P(H:F) RECORDS LIKE: K01_H1 where QKT.REC(01) RELATES TO QPAT.REC(1) IN WHICH SEX FIELD IS H K02_H2 K03_H3 K04_H4 K05_H5 K06_H6 K07_F1 K08_F2 at this point in this example,every QPAT.REC has been related once K09_H1 so to form the rest of the relations, some must be used again. K10_H3 K11_H5 K12_F1 K13_F2 K14_H2 The K represent the catheter records and they are related to particular patient records. The patient records have either H or F as sex field. So, there MUST be a total of 14 sex fields...the distribution of H and F depends on which QPAT.REC records are related to which QKT.REC records...but the TOTAL of H+F must always = 14. In an extreme case, you might even have only ONE patient record for all 14 catheter records...the you'd have either 14 H or 14 F depending which patient it happened to be. That's why I suggested you BROWSE your data after relating the records. You then will see the reason behind the result you get. Hope this has helped. Darwin Fedorick Edmonton, Alberta, Canada ========================================================================= Date: Tue, 10 Aug 1999 12:22:54 +0200 Reply-To: maugat@ext.jussieu.fr Sender: Epi Info Discussion Group From: Sylvie Maugat Organization: C.CLIN Paris-Nord Subject: Linked data files and .RPT file MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------34BA68BC616FD107570DC70D" Content-Transfer-Encoding: 8bit Il s'agit d'un message multivolet au format MIME. --------------34BA68BC616FD107570DC70D Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, In my last message (yesterday) I Wrote: ONE MORE QUESTION : What can I do in .RPT file ? , Whitch variable'name used behind #USES ?? Sorry about my lack in precission. In fact, I would like to know : what can I do in RPT files with 2 linked data files ..... Whitch kind of results can I obtain ? (If someone have an exemple, It'll be great.......) -- _________________________________________ Sylvie MAUGAT Epidémiologiste CCLIN Paris-Nord 15-21 rue de l'Ecole de Médecine 75006 PARIS Tel : 01 40 46 42 00 --------------34BA68BC616FD107570DC70D Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Carte pour MAUGAT Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: MAUGAT n: ;MAUGAT email;internet: maugat@idf.ext.jussieu.fr x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard --------------34BA68BC616FD107570DC70D-- ========================================================================= Date: Tue, 10 Aug 1999 15:04:07 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: OluFemi Ogunbanwo Subject: Fw: Epi2000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01BEE341.97C4F780" This is a multi-part message in MIME format. ------=_NextPart_000_0017_01BEE341.97C4F780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ----- Original Message -----=20 From: OluFemi Ogunbanwo=20 To: EPI-INFO@LISTSERV.CDC.GOV=20 Cc: EPI Info Helpdesk=20 Sent: 10 August 1999 14:40 Subject: Epi2000 I have been trying for weeks and weeks to download the BETA version of = Epi200 but can not get to the ftp site. Is anyone able to ZIP the files = up and attach them to an email to me please? My address is below. Thank = you very much. =20 femi@nightcentre.freeserve.co.uk or femi@ogunbanwo.freeserve.co.uk ------=_NextPart_000_0017_01BEE341.97C4F780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
----- Original Message -----=20
From: OluFemi Ogunbanwo
Sent: 10 August 1999 14:40
Subject: Epi2000

I have been trying for weeks and weeks = to download the=20 BETA version of Epi200 but can not get to the ftp site. Is anyone able = to ZIP=20 the files up and attach them to an email to me please? My address is = below.=20 Thank you very much.
 
femi@nightcentre.freeser= ve.co.uk
 
or
 
femi@ogunbanwo.freeserve.c= o.uk
 
------=_NextPart_000_0017_01BEE341.97C4F780-- ========================================================================= Date: Tue, 10 Aug 1999 10:26:37 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Richard Lasater Subject: Re: Fw: Epi2000 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I have the files. If no one else sends them in the next few days. I = will. >>> OluFemi Ogunbanwo 08/10/99 09:04AM = >>> ----- Original Message -----=20 From: OluFemi Ogunbanwo=20 To: EPI-INFO@LISTSERV.CDC.GOV=20 Cc: EPI Info Helpdesk=20 Sent: 10 August 1999 14:40 Subject: Epi2000 I have been trying for weeks and weeks to download the BETA version of = Epi200 but can not get to the ftp site. Is anyone able to ZIP the files up = and attach them to an email to me please? My address is below. Thank you = very much. =20 femi@nightcentre.freeserve.co.uk=20 or femi@ogunbanwo.freeserve.co.uk=20 ========================================================================= Date: Tue, 10 Aug 1999 07:55:29 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kyle Luman Subject: Re: Linked data files and .RPT file MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable What I would do with linked (using the relate procedure) data sets if I wanted to run a REPORT is to make a new temporary dataset after the = RELATE command. Then after writing to a temp dataset, I would read in that = temp dataset and run the REPORT that I wanted. When you write to the temp dataset, make sure that you do not have duplicate variables (two ID variables, two CODPAT variables etc.) which can be done by using the = NOT statement. route temp1.rec write recfile NOT dup_var1 dup_var2, etc. ... > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ >=20 > -----Original Message----- > From: Sylvie Maugat [SMTP:maugat@EXT.JUSSIEU.FR] > Sent: Tuesday, August 10, 1999 3:23 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: [EPI-INFO] Linked data files and .RPT file >=20 > Hi, >=20 > In my last message (yesterday) I Wrote: > ONE MORE QUESTION : What can I do in .RPT file ? , Whitch = variable'name > used behind #USES ?? >=20 > Sorry about my lack in precission. > In fact, I would like to know : what can I do in RPT files with 2 = linked > data files ..... > Whitch kind of results can I obtain ? >=20 > (If someone have an exemple, It'll be great.......) >=20 >=20 > -- >=20 > _________________________________________ >=20 > Sylvie MAUGAT > Epid=E9miologiste > CCLIN Paris-Nord > 15-21 rue de l'Ecole de M=E9decine > 75006 PARIS > Tel : 01 40 46 42 00 > << File: Carte pour MAUGAT >>=20 ========================================================================= Date: Tue, 10 Aug 1999 10:45:22 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Darwin J. Fedorick" Subject: Re: Linked data files and .RPT file Comments: To: Sylvie Maugat In-Reply-To: <37AFFD7E.BA1FD7E4@idf.ext.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > In my last message (yesterday) I Wrote: > ONE MORE QUESTION : What can I do in .RPT file ? , Whitch variable'name > used behind #USES ?? I try to avoid the .RPT method because it's a bit more complex to use than straight formatting using the TYPE and WRITE commands like: :SHEET_P1 CLS TYPE "\cSelected Farm Pest/Disease Occurrence/Outbreak Tracking - Column Set 1 of 4" TYPE "\c@FROMDATE - @TODATE - @GETAREA - @GETHOST - @GETDIS" TYPE "\cCORRAL 2.0 Printed on @SYSTEMDATE" TYPE " " TYPE "" TYPE " PRODUCER INSP- INSPECTION HOST ADMIN.SOURCE" TYPE " NAME ECTOR DATE PLANT AREA OF " TYPE " CODE CODE CODE PLANTS" TYPE "" WRITE "\032" NAME "\032" INSPECTCOD "\032" DATEINSPEC "\032\032\032" HOSTPLANT "\032\032\032\032" PRODUCER.AREA "\032\032" SOURCE "" TYPE "" ========================================================================= Date: Tue, 10 Aug 1999 10:57:10 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Darwin J. Fedorick" Subject: Re: Linked data files and .RPT file Comments: To: Sylvie Maugat In-Reply-To: <37AFFD7E.BA1FD7E4@idf.ext.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > (If someone have an exemple, It'll be great.......) This example shows why I stay away from .RPT reports as much as I can. I believe this example works on a file that was related. It took quite a while for me to make it work correctly. Instead you should try to use the simpler WRITE and TYPE formatted statements or the TABLES commands with the /SUM=someVAR if you can. #usessum OUTBREAKS OIECODE DISEASE SPECIES \cOUTBREAKS #foreach oiecode \nOutbreak breakdown for ^oiecode ^disease #foreach species AMONG ^species:3 [^oiecode,,^species]:6 #endfor ______ ALL ^oiecode:4 [^oiecode,,]:6 #endfor ======= OUTBREAKS OF ALL DISEASES [,,]:7 #usessum AFFECTED OIECODE DISEASE SPECIES \cCASES #foreach oiecode \nOutbreak breakdown for ^oiecode ^disease #foreach species AMONG ^species:3 [^oiecode,,^species]:6 #endfor ______ ALL ^oiecode:4 [^oiecode,,]:6 #endfor ======= CASES OF ALL DISEASES [,,]:7 #newpage ========================================================================= Date: Tue, 10 Aug 1999 20:11:35 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: David Newrick Subject: Re: Fw: Epi2000 I have recently set up a site about Epi Info for General Practice/Family Practice. If there are problems with distributing the files then I will be happy to explore the possibility of securing the space to include them on my site so that people in the UK and Europe will have a closer site (i.e. without having to compete on the transatlantic trunk). However, this is a completely free site so there are no funds to purchase space if it can not be obtained by other means. If you would like to have a look at the site then the address is :- http://www.staff.ncl.ac.uk/d.c.newrick/epiinfo/ any comments, suggestions, problems, items for inclusion etc. then let me know - they will all be welcome. If someone could let me know about seeing about more space for including Epi 2000 then please let me know and I will follow it up. Regards, David Newrick. -----Original Message----- From: OluFemi Ogunbanwo [SMTP:femi@OGUNBANWO.FREESERVE.CO.UK] Sent: 10 August 1999 15:04 To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Fw: Epi2000 << File: ATT00000.html >> ----- Original Message ----- From: OluFemi Ogunbanwo To: EPI-INFO@LISTSERV.CDC.GOV Cc: EPI Info Helpdesk Sent: 10 August 1999 14:40 Subject: Epi2000 I have been trying for weeks and weeks to download the BETA version of Epi200 but can not get to the ftp site. Is anyone able to ZIP the files up and attach them to an email to me please? My address is below. Thank you very much. femi@nightcentre.freeserve.co.uk or femi@ogunbanwo.freeserve.co.uk ========================================================================= Date: Thu, 12 Aug 1999 19:37:23 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: Re: Fw: Epi2000 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit oh, and i'm getting a failure to load UAButton class error from my Netscape 4.6 JVM. David Newrick wrote: > I have recently set up a site about Epi Info for General Practice/Family > Practice. If there are problems with distributing the files then I will be > happy to explore the possibility of securing the space to include them on > my site so that people in the UK and Europe will have a closer site (i.e. > without having to compete on the transatlantic trunk). However, this is a > completely free site so there are no funds to purchase space if it can not > be obtained by other means. > > If you would like to have a look at the site then the address is :- > > http://www.staff.ncl.ac.uk/d.c.newrick/epiinfo/ > > any comments, suggestions, problems, items for inclusion etc. then let me > know - they will all be welcome. > > If someone could let me know about seeing about more space for including > Epi 2000 then please let me know and I will follow it up. > > Regards, > David Newrick. > > -----Original Message----- > From: OluFemi Ogunbanwo [SMTP:femi@OGUNBANWO.FREESERVE.CO.UK] > Sent: 10 August 1999 15:04 > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: [EPI-INFO] Fw: Epi2000 > > << File: ATT00000.html >> > ----- Original Message ----- > From: OluFemi Ogunbanwo > To: EPI-INFO@LISTSERV.CDC.GOV > Cc: EPI Info Helpdesk > Sent: 10 August 1999 14:40 > Subject: Epi2000 > > I have been trying for weeks and weeks to download the BETA version of > Epi200 but can not get to the ftp site. Is anyone able to ZIP the files up > and attach them to an email to me please? My address is below. Thank you > very much. > > femi@nightcentre.freeserve.co.uk > > or > > femi@ogunbanwo.freeserve.co.uk -- Yours, Sam Brown sam @ vecnatech.com sambrown @ bigfoot.com http://www.bigfoot.com/~sambrown ========================================================================= Date: Thu, 12 Aug 1999 19:36:16 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: Re: Fw: Epi2000 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Occasionally you can use those silly "free web page" services like geocities or whatever. Put up a dummy web page with their silly advertisements and so on, and then put the software there (you can even link to it from that dummy web page) and link to it from your true web page. That's a relatively painless way to get pretty much free server space. Good luck. David Newrick wrote: > I have recently set up a site about Epi Info for General Practice/Family > Practice. If there are problems with distributing the files then I will be > happy to explore the possibility of securing the space to include them on > my site so that people in the UK and Europe will have a closer site (i.e. > without having to compete on the transatlantic trunk). However, this is a > completely free site so there are no funds to purchase space if it can not > be obtained by other means. > > If you would like to have a look at the site then the address is :- > > http://www.staff.ncl.ac.uk/d.c.newrick/epiinfo/ > > any comments, suggestions, problems, items for inclusion etc. then let me > know - they will all be welcome. > > If someone could let me know about seeing about more space for including > Epi 2000 then please let me know and I will follow it up. > > Regards, > David Newrick. > > -----Original Message----- > From: OluFemi Ogunbanwo [SMTP:femi@OGUNBANWO.FREESERVE.CO.UK] > Sent: 10 August 1999 15:04 > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: [EPI-INFO] Fw: Epi2000 > > << File: ATT00000.html >> > ----- Original Message ----- > From: OluFemi Ogunbanwo > To: EPI-INFO@LISTSERV.CDC.GOV > Cc: EPI Info Helpdesk > Sent: 10 August 1999 14:40 > Subject: Epi2000 > > I have been trying for weeks and weeks to download the BETA version of > Epi200 but can not get to the ftp site. Is anyone able to ZIP the files up > and attach them to an email to me please? My address is below. Thank you > very much. > > femi@nightcentre.freeserve.co.uk > > or > > femi@ogunbanwo.freeserve.co.uk -- Yours, Sam Brown sam @ vecnatech.com sambrown @ bigfoot.com http://www.bigfoot.com/~sambrown ========================================================================= Date: Fri, 13 Aug 1999 02:07:33 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: David Newrick Subject: Re: Fw: Epi2000 Aha ! Thanks for the tip !! I know what you mean about all the ads - I would definitely not like to see them on my own site - but then I hadn't thought of just using the free sites as a kind of extended server space. In your other message you mentioned a problem with Netscape 4.6. I haven't tested the site with the newer version of Netscape - but I have with Netscape 4, Internet Explorer 4 and Internet Explorer 5. It is difficult to keep up with different versions. However, I will be implementing a non-frames, non-Java version to help developing countries visitors who will not have the luxury of our fast, up to date machines. But as soon as possible I will get my hands on the newer Netscape and test the pages again. Many thanks again - and keep in touch ! Regards, David Newrick. -----Original Message----- From: Sam Brown [SMTP:sam@VECNATECH.COM] Sent: 12 August 1999 16:36 To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] Fw: Epi2000 << File: ATT00002.txt; charset = koi8-r >> ========================================================================= Date: Fri, 13 Aug 1999 17:54:48 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Estie Hudes Subject: Population size N in sample size calculations Comments: To: epiinfo@cdc.gov MIME-Version: 1.0 Content-Type: text/plain I tried today one of the StatCalc modules: EpiTable/Sample Size/Single Proportion Although the formula has the population size N in it: N*z^2*p*(1-p)/(d^2*(N-1)+z^2*p*(1-p))) The module does not use it. It gives identical sample size for any value of N. I have not checked other modules for sample size calculation which use N. --Estie Hudes. ------------------------------------------------------------------------ ------------ Estie Sid Hudes University of California Prevention Sciences Group & Center for AIDS Prevention Studies 74 New Montgomery Street, Suite 600 S.F. CA 94105 phone: 415.597.9126 fax: 415.597.9125 email: ehudes@psg.ucsf.edu Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html ------------------------------------------------------------------------ ------------ ========================================================================= Date: Sat, 14 Aug 1999 12:15:02 +0200 Reply-To: "d.coulombier@rnsp-sante.fr" Sender: Epi Info Discussion Group From: Denis COULOMBIER Subject: Re: Population size N in sample size calculations MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Epitable does use the population size in sample size calculation, but the population size may affect the sample size result only when N is not too large. The default value for N is 999999. The returned value may be affected for population size of 5000 or less. I tried today one of the StatCalc modules: EpiTable/Sample Size/Single Proportion Although the formula has the population size N in it: N*z^2*p*(1-p)/(d^2*(N-1)+z^2*p*(1-p))) From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9908A" ========================================================================= Date: Mon, 2 Aug 1999 20:07:14 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jose A. Farfan" Subject: numeric codes for colors Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Dear member of the list: I would like to know the numeric code for the different colors available in EpiInfo. I would like to make changes in the colors displayed in my database, changing the numeric codes in the .rec file. I will appreciate any help. Jose A. Farfan. Universidad Autonoma de Yucatan ========================================================================= Date: Tue, 3 Aug 1999 09:26:49 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Pedro Arias Bohigas Subject: Re: numeric codes for colors MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Jose A. Farfan escribió: > Dear member of the list: > I would like to know the numeric code for the different colors available in > EpiInfo. I would like to make changes in the colors displayed in my > database, changing the numeric codes in the .rec file. > I will appreciate any help. > > Jose A. Farfan. > Universidad Autonoma de Yucatan Estimado Jose A. Puedes conseguir los códigos de los colores de fondo, texto y espacio para la pregunta usando la tecla F2 en ENTER. Cuando estes en la primera pantalla de ENTER (antes de ver la base de datos), veras una opción de configuración, allí podrás seleccionar los colores que utilizará EpiInfo para definir un nuevo cuestionario o para revisar uno viejo a partir de un QES. La paleta de colores identifica el número con un color de fondo y uno de primer plano (hay 7 u 8 posibilidades de colores de fondo y varias más de colores de primer plano). Si apuntas los códigos que te interesan tambien puedes modificar el aspecto de la base de datos usando algunas órdenes dentro de un archivo .CHK (COLOR QUESTION, COLOR DATA y COLOR BACKGROUND). Espero que te ayude, Pedro Arias Bohigas Servicio de Epidemiología Comunidad de Madrid Espańa p.arias@comadrid.es www.comadrid.es ========================================================================= Date: Tue, 3 Aug 1999 12:52:34 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: Re: numeric codes for colors In-Reply-To: <37A699B9.148C1225@comadrid.es> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 09:26 3/08/99 +0200, Pedro Arias Bohigas wrote: >Jose A. Farfan escribi=F3: > >> Dear member of the list: >> I would like to know the numeric code for the different colors available= in >> >> Jose A. Farfan. >> Universidad Autonoma de Yucatan > >Estimado Jose A. Puedes conseguir los c=F3digos de los colores de fondo, texto y >imer plano). >Si apuntas los c=F3digos que te interesan tambien puedes modificar el aspecto de >la base de datos usando algunas =F3rdenes dentro de un archivo .CHK (COLOR >QUESTION, COLOR DATA y COLOR BACKGROUND). > >Espero que te ayude, > >Pedro Arias Bohigas >Servicio de Epidemiolog=EDa >Comunidad de Madrid >Espa=F1a >p.arias@comadrid.es >www.comadrid.es > > Otra forma, pero hay que tener un poco de practica y cuidado, es editar el archivo .rec directamente con eped, y modificarlo. Esto permite crear diferentes colores para cada campo, hay que cambiar algunos n=FAmeros, e ir viendo que pasa. Los n=FAmeros que indican el color son por ejemplo el archivo rec que esta abajo, en la primera linea, el segundo n=FAmero, en este caso "1", indica el color del fondo de la pantalla. En las columnas de n=FAmeros, la tercera y la octava, en este caso las que tienen los valores "30" y "15" son los que indican el color y el fondo para cada campo, puedes modificar cada linea con diferentes n=FAmeros e ir viendo los resultados. Hay un monton de variantes, incluso hay una que produce un color intermitente. Hay que tener cuidado que las columnas queden alineadas, si no no anda. Si en el archivo .chk se indican los colores, se anulan los cambios que hayas hecho en el archivo rec y aparecen con los colores que indica el .chk. 39 1 FICHDEINTE 7 2 30 73 2 0 0 15=20 CU2 3 3 30 7 3 3 13 15 CU2 CU 21 3 30 24 3 3 10 15 CU NOMBRE 6 4 30 13 4 3 25 15 Nombre EDAD 59 4 30 65 4 102 6 15 Edad MESES 72 4 30 77 4 0 0 15 meses DOMICILIO 3 5 30 13 5 1 30 15 Domicilio AREA 59 5 30 65 5 3 3 15 Area ING 3 7 30 24 7 11 8 15 Fecha de internaci=A2n HORA 38 7 30 43 7 0 2 15 Hora HORA1 46 7 30 46 7 0 2 15 PROCEDENCI 53 7 30 65 7 3 3 15 Procedencia SALA 3 8 30 8 8 3 10 15 Sala CAMA 19 8 30 20 8 0 2 15 C MEDICO 23 8 30 38 8 3 20 15 M=82dico a cargo MP 61 8 30 65 8 3 4 15 MP DIAGING 2 10 30 36 10 1 34 15 Diagn=A2stico que motiva el= ingreso C 71 10 30 73 10 3 5 15 C EGRESO1 13 11 30 36 11 1 34 15 Diagn=A2stico de egreso1 C01 71 11 30 73 11 3 5 15 C EGRESO2 13 12 30 36 12 1 34 15 Diagn=A2stico de egreso2 C02 71 12 30 73 12 3 5 15 C EGRESO3 13 13 30 36 13 1 34 15 Diagn=A2stico de egreso3 C03 71 13 30 73 13 3 5 15 C EGRESO4 13 14 30 36 14 1 34 15 Diagn=A2stico de egreso4 C04 71 14 30 73 14 3 5 15 C ANTRO 4 16 30 17 16 3 1 15 Antopometr=A1a PRISM 22 16 30 28 16 3 1 15 PRISM ARM 32 16 30 36 16 3 1 15 ARM CIRUGIA 41 16 30 49 16 3 1 15 Cirug=A1a OTRO2 51 16 30 57 16 3 1 15 Otro2 OTRO3 61 16 30 67 16 3 1 15 Otro3 EGR 4 18 30 20 18 11 8 15 Fecha de egreso HORA01 39 18 30 44 18 0 2 15 Hora HORA21 47 18 30 47 18 0 2 15 DIAS 4 19 30 24 19 0 3 15 D=A1as de internaci=A2n PASAA 37 19 30 44 19 3 3 15 Pasa a DATOSCORRE 31 21 30 47 21 3 1 15 Datos correctos COMED 56 21 30 62 21 1 10 15 comed=1A Suerte Enrique Finetti Medico Asistente de UCI pedi=E1trica Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Tue, 3 Aug 1999 15:42:57 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: Re: numeric codes for colors In-Reply-To: <37A699B9.148C1225@comadrid.es> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 09:26 3/08/99 +0200, you wrote: >Jose A. Farfan escribi=F3: > >> Dear member of the list: >> I would like to know the numeric code for the different colors available= in >> EpiInfo. I would like to make changes in the colors displayed in my >> database, changing the numeric codes in the .rec file. >> I will appreciate any help. >> >> Jose A. Farfan. >> Universidad Autonoma de Yucatan > >Estimado Jose A. Puedes conseguir los c=F3digos de los colores de fondo, texto y >espacio para la pregunta usando la tecla F2 en ENTER. Cuando estes en la >primera pantalla de ENTER (antes de ver la base de datos), veras una opci=F3n de >configuraci=F3n, all=ED podr=E1s seleccionar los colores que utilizar=E1= EpiInfo para >definir un nuevo cuestionario o para revisar uno viejo a partir de un QES. >La paleta de colores identifica el n=FAmero con un color de fondo y uno de primer >plano (hay 7 u 8 posibilidades de colores de fondo y varias m=E1s de= colores de >primer plano). >Si apuntas los c=F3digos que te interesan tambien puedes modificar el aspecto de >la base de datos usando algunas =F3rdenes dentro de un archivo .CHK (COLOR >QUESTION, COLOR DATA y COLOR BACKGROUND). > >Espero que te ayude, > >Pedro Arias Bohigas >Servicio de Epidemiolog=EDa >Comunidad de Madrid >Espa=F1a >p.arias@comadrid.es >www.comadrid.es > > Enrique Finetti Medico Asistente de UCI pedi=E1trica Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Tue, 3 Aug 1999 20:09:22 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Estie Hudes Subject: starting Analysis in a different directory MIME-Version: 1.0 Content-Type: text/plain I would like to start EpiInfo in a different directory, say C:\EPIWORK. I have added this directory to the DOS PATH (in autoexec.bat).. I can start EpiInfo just fine, but when I try to start ANALYSIS, I get an error message saying that the help file is not available. This happens also if I type "analysis" at the DOS command prompt. In addition, the tutorials and the examples are not available. Is the only way do run EpiInfo smoothly is by starting it in the Epi6 directory, and then use Setup to change the path for data files? Thanks, --Estie. ------------------------------------------------------------------------ ------------ Estie Sid Hudes University of California Prevention Sciences Group & Center for AIDS Prevention Studies 74 New Montgomery Street, Suite 600 S.F. CA 94105 phone: 415.597.9126 fax: 415.597.9125 email: ehudes@psg.ucsf.edu Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html ------------------------------------------------------------------------ ------------ ========================================================================= Date: Wed, 4 Aug 1999 15:05:23 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: OluFemi Ogunbanwo Subject: Re: starting Analysis in a different directory MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit If you simply need to go directly to analysis, you can add c:\epi6\analysis.exe DOS Path. This should take you right to analysis. Or if you would like to be presented with a list of your .REC files to choose from, then add c:\epi6\analysis.exe c:\epiwork\*.rec to your DOS Path. (epiwork=datafile folder) Hope this helps. ----- Original Message ----- From: Estie Hudes To: Sent: 04 August 1999 04:09 Subject: [EPI-INFO] starting Analysis in a different directory > I would like to start EpiInfo in a different directory, say C:\EPIWORK. > I have added this directory to the DOS PATH (in autoexec.bat).. > I can start EpiInfo just fine, but when I try to start ANALYSIS, I get > an error message saying that the help file is not available. > This happens also if I type "analysis" at the DOS command prompt. > In addition, the tutorials and the examples are not available. > > Is the only way do run EpiInfo smoothly is by starting it in the Epi6 > directory, and then use Setup to change the path for data files? > > Thanks, > --Estie. > > > ------------------------------------------------------------------------ > ------------ > Estie Sid Hudes > University of California > Prevention Sciences Group & > Center for AIDS Prevention Studies > 74 New Montgomery Street, Suite 600 > S.F. CA 94105 > phone: 415.597.9126 > fax: 415.597.9125 > email: ehudes@psg.ucsf.edu > Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html > ------------------------------------------------------------------------ > ------------ > ========================================================================= Date: Wed, 4 Aug 1999 14:40:54 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: OluFemi Ogunbanwo Subject: Re: numeric codes for colors MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit You can find detailed instructions for this in the manual chapter 35 page 462. The command needs to be placed in the .CHK file to affect any of the areas of the questionaire. COLOR question this will affect all your field descriptions. COLOR data this will affect all your data areas COLOR background this will affect the whole background COLOR this will affect a specific data area & description. Definitions: COLOR: command colorno: the number that corresponds to the colour you require. You may need to try a few. question: is the text area describing the data field data: is the data area background: is the background fieldname: is a specific field I hope this helps. ----- Original Message ----- From: Enrique Finetti To: Sent: 03 August 1999 19:42 Subject: Re: [EPI-INFO] numeric codes for colors At 09:26 3/08/99 +0200, you wrote: >Jose A. Farfan escribió: > >> Dear member of the list: >> I would like to know the numeric code for the different colors available in >> EpiInfo. I would like to make changes in the colors displayed in my >> database, changing the numeric codes in the .rec file. >> I will appreciate any help. >> >> Jose A. Farfan. >> Universidad Autonoma de Yucatan > >Estimado Jose A. Puedes conseguir los códigos de los colores de fondo, texto y >espacio para la pregunta usando la tecla F2 en ENTER. Cuando estes en la >primera pantalla de ENTER (antes de ver la base de datos), veras una opción de >configuración, allí podrás seleccionar los colores que utilizará EpiInfo para >definir un nuevo cuestionario o para revisar uno viejo a partir de un QES. >La paleta de colores identifica el número con un color de fondo y uno de primer >plano (hay 7 u 8 posibilidades de colores de fondo y varias más de colores de >primer plano). >Si apuntas los códigos que te interesan tambien puedes modificar el aspecto de >la base de datos usando algunas órdenes dentro de un archivo .CHK (COLOR >QUESTION, COLOR DATA y COLOR BACKGROUND). > >Espero que te ayude, > >Pedro Arias Bohigas >Servicio de Epidemiología >Comunidad de Madrid >Espańa >p.arias@comadrid.es >www.comadrid.es > > Enrique Finetti Medico Asistente de UCI pediátrica Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Thu, 5 Aug 1999 09:54:16 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Richard Lasater Subject: Re: starting Analysis in a different directory Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Stick this on the end of you dos path statement in autoexec.bat c:\epi6;=20 (This assumes of course that you epiinfo program files are in c:\epi6). Use eped or a text only mode of whatever word processor you have Then reboot. The os should then be able to find the epiinfo commands in = whatever directoyr you find yourself. =20 >>> Estie Hudes 08/03/99 10:09PM >>> I would like to start EpiInfo in a different directory, say C:\EPIWORK. I have added this directory to the DOS PATH (in autoexec.bat).. I can start EpiInfo just fine, but when I try to start ANALYSIS, I get an error message saying that the help file is not available. This happens also if I type "analysis" at the DOS command prompt. In addition, the tutorials and the examples are not available. Is the only way do run EpiInfo smoothly is by starting it in the Epi6 directory, and then use Setup to change the path for data files? Thanks, --Estie. ------------------------------------------------------------------------ ------------ Estie Sid Hudes University of California Prevention Sciences Group & Center for AIDS Prevention Studies 74 New Montgomery Street, Suite 600 S.F. CA 94105 phone: 415.597.9126 fax: 415.597.9125 email: ehudes@psg.ucsf.edu=20 Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html=20 ------------------------------------------------------------------------ ------------ ========================================================================= Date: Thu, 5 Aug 1999 13:50:38 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: starting Analysis in a different directory Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=oR2QWxnoPgNVBIHLlAuyvgBuGj2PuFeSVSiW5PhNTKXgT4r2TMguXYCZ" --0__=oR2QWxnoPgNVBIHLlAuyvgBuGj2PuFeSVSiW5PhNTKXgT4r2TMguXYCZ Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable The problem is that ANALYSIS does not use the EPI6 setup path in the sa= me way as Enter. The manual suggests (and I know this works): If EPI6.EXE is not in C:\EPI6, then you need to do two things in AUTOEX= EC.BAT 1. add a line: SET EIDIR=3DC:\path where EpiInfo is in C:\path\EPI6 2. add to your path statement (at the end) C:\EPI6 or C:\path\EPI6 If you are using DOS, then you start EPI6 from the directory which has = your data. The DOS prompt COULD look like this: C:\EPIWORK> and you type EPI6 Then Analysis will find your .REC files and all the EPI6 functions will= be available. I use Windows95 and made a batch file to start up EPI6. This is in the = EPI6 directory. The .BAT file is called EPISTART.BAT and looks like this: set eidir=3Dc:\dosapp path %path%;c:\dosapp\epi6 Then I create a shortcut which has the following in the 'Program' tab: Cmd line: c:\dosapp\epi6\epi6.exe Working: d:\epiwork Batch file: c:\dosapp\epi6\epistart.bat I can change the Working directory when I change projects. ---------------------- Jamie Hockin MD,MSc -------------------------- Director, Field Epidemiology _ Directeur, Programme de formation Training Program _|\ en =E9pid=E9miologie d'intervention= LCDC, Health Canada :| \ LLCM, Sant=E9 Canada PL 0602B Tunney's Pasture | LP 0602B Pr=E9 Tunney Ottawa ON K1A 0L2, Canada Ottawa (Ontario) K1A 0L2, Canada Jamie_Hockin@hc-sc.gc.ca 613 957-1764 FAX: 613 941-6028 http://www.hc-sc.gc.ca/hpb/lcdc/survlnce/fetp Estie Hudes on 99/08/03 11:09:22 PM Please respond to Epi Info Discussion Group = To: EPI-INFO@LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: [EPI-INFO] starting Analysis in a different directory = --0__=oR2QWxnoPgNVBIHLlAuyvgBuGj2PuFeSVSiW5PhNTKXgT4r2TMguXYCZ Content-type: text/plain; charset=us-ascii Content-Disposition: inline I would like to start EpiInfo in a different directory, say C:\EPIWORK. I have added this directory to the DOS PATH (in autoexec.bat).. I can start EpiInfo just fine, but when I try to start ANALYSIS, I get an error message saying that the help file is not available. This happens also if I type "analysis" at the DOS command prompt. In addition, the tutorials and the examples are not available. Is the only way do run EpiInfo smoothly is by starting it in the Epi6 directory, and then use Setup to change the path for data files? Thanks, --Estie. ------------------------------------------------------------------------ ------------ Estie Sid Hudes University of California Prevention Sciences Group & Center for AIDS Prevention Studies 74 New Montgomery Street, Suite 600 S.F. CA 94105 phone: 415.597.9126 fax: 415.597.9125 email: ehudes@psg.ucsf.edu Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html ------------------------------------------------------------------------ ------------ --0__=oR2QWxnoPgNVBIHLlAuyvgBuGj2PuFeSVSiW5PhNTKXgT4r2TMguXYCZ-- ========================================================================= Date: Fri, 6 Aug 1999 10:16:46 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Estie Hudes Subject: runtime error with describe /all MIME-Version: 1.0 Content-Type: text/plain It seems that when the dataset is not small (n=1625, number of variables 15), "describe /all" produces a runtime error. Although "describe" by itself works just fine, the "/all" switch causes problems. I did some trial and error, and I think this is caused by the ID variable. The ID variable has values from 1 to 3047 (it is stored as integer of length 4) I am not sure why computing the 6 additional summary statistics (min, Q1, median, Q3, max, mode) would cause the problem, but it certainly does. The dataset I am using is onchall.rec, provided by Brixton Books with the Data Management text written by Mark Myatt and others. The message I get is: Runtime error 202 at o5F5:0DA9 Is there a fix for this problem? Thanks, --Estie. ------------------------------------------------------------------------ ------------ Estie Sid Hudes University of California Prevention Sciences Group & Center for AIDS Prevention Studies 74 New Montgomery Street, Suite 600 S.F. CA 94105 phone: 415.597.9126 fax: 415.597.9125 email: ehudes@psg.ucsf.edu Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html ------------------------------------------------------------------------ ------------ ========================================================================= Date: Fri, 6 Aug 1999 19:08:07 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Benoit Subject: EPI 2000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Can you say me where and how can i get Epi Info 2000 (beta) ? Thanks. Benoit SALLES Statistician ========================================================================= Date: Fri, 6 Aug 1999 13:32:40 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: runtime error with describe /all Comments: cc: ehudes@psg.ucsf.edu Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Estie: You can use the command: describe /all not id to exclude ID from the computation. Maybe this will solve your problem. For ID you really need to do a FREQ anyway to look for duplicates. Jamie Estie Hudes on 99/08/06 01:16:46 PM Please respond to Epi Info Discussion Group To: EPI-INFO@LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: [EPI-INFO] runtime error with describe /all It seems that when the dataset is not small (n=1625, number of variables 15), "describe /all" produces a runtime error. Although "describe" by itself works just fine, the "/all" switch causes problems. I did some trial and error, and I think this is caused by the ID variable. The ID variable has values from 1 to 3047 (it is stored as integer of length 4) I am not sure why computing the 6 additional summary statistics (min, Q1, median, Q3, max, mode) would cause the problem, but it certainly does. The dataset I am using is onchall.rec, provided by Brixton Books with the Data Management text written by Mark Myatt and others. The message I get is: Runtime error 202 at o5F5:0DA9 Is there a fix for this problem? Thanks, --Estie. ------------------------------------------------------------------------ ------------ Estie Sid Hudes University of California Prevention Sciences Group & Center for AIDS Prevention Studies 74 New Montgomery Street, Suite 600 S.F. CA 94105 phone: 415.597.9126 fax: 415.597.9125 email: ehudes@psg.ucsf.edu Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html ------------------------------------------------------------------------ ------------ ========================================================================= Date: Fri, 6 Aug 1999 10:59:16 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Estie Hudes Subject: Re: runtime error with describe /all MIME-Version: 1.0 Content-Type: text/plain Wow! That's great! I have tried describe * not id / all but that of course doesn't work when there are non-numeric variables in the file. Yes, I agree that the ID variable needs to be checked separately. [ I usually do it in Stata. There is a user-written-written command (these are easy to write in Stata) called -dups- -dups id, key(id)- ] will list all duplicated ids, if there are any. BTW, the screen resizing didn't work with NT. Thanks again for your help. (I still haven't received my original posting to the list). > -----Original Message----- > From: Jamie Hockin [SMTP:Jamie_Hockin@HC-SC.GC.CA] > Sent: Friday, August 06, 1999 10:33 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: [EPI-INFO] runtime error with describe /all > > Estie: > > You can use the command: > > describe /all not id > > to exclude ID from the computation. Maybe this will solve your > problem. For ID > you really need to do a FREQ anyway to look for duplicates. > > Jamie > > > > > Estie Hudes on 99/08/06 01:16:46 PM > > Please respond to Epi Info Discussion Group > > > To: EPI-INFO@LISTSERV.CDC.GOV > cc: (bcc: Jamie Hockin) > > Subject: [EPI-INFO] runtime error with describe /all > > > > > It seems that when the dataset is not small (n=1625, number of > variables > 15), "describe /all" produces a runtime error. > Although "describe" by itself works just fine, the "/all" switch > causes > problems. I did some trial and error, and I think this is caused by > the > ID variable. > The ID variable has values from 1 to 3047 (it is stored as integer of > length 4) > I am not sure why computing the 6 additional summary statistics (min, > Q1, median, Q3, max, mode) would cause the problem, but it certainly > does. > > The dataset I am using is onchall.rec, provided by Brixton Books with > the Data Management text written by Mark Myatt and others. > > The message I get is: > Runtime error 202 at o5F5:0DA9 > > Is there a fix for this problem? > > Thanks, > --Estie. > > > ---------------------------------------------------------------------- > -- > ------------ > Estie Sid Hudes > University of California > Prevention Sciences Group & > Center for AIDS Prevention Studies > 74 New Montgomery Street, Suite 600 > S.F. CA 94105 > phone: 415.597.9126 > fax: 415.597.9125 > email: ehudes@psg.ucsf.edu > Web: http://www.epibiostat.ucsf.edu/capsweb/people/hudesbio.html > ---------------------------------------------------------------------- > -- > ------------ ========================================================================= Date: Fri, 6 Aug 1999 16:10:36 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: EPI 2000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We put up improved versions from time to time. Here is the information on how to get the latest one, dating from mid July. The next improvements will be in about 2 weeks. Epi Info 2000 BETA Version Available A BETA version of Epi Info 2000 is available to a limited number of interested persons. Instructions are given below for downloading it by FTP, with a password. The BETA version is primarily for testing. It has many more features than the ALPHA version of September 98, but still lacks a few of the functions that the RELEASE versions will have. Please see the "GUIDED TOUR" from the main menu for an introduction to the system. A list of features not yet implemented is provided below. The following are required to run the BETA: 1. Windows 95, 98, or NT 2. A reasonably fast computer, with at least 32 meg of RAM The Microsoft Internet Explorer IS NO LONGER REQUIRED, as Epi Info provides a small, off-line browser. The BETA should not be relied upon for serious epidemiologic work, and should not be distributed to others for that purpose. To see the features of the system under development, install the BETA as recommended, and run the main menu, EPI2000.EXE. Click on the GUIDED TOUR button and then print the document that appears. The TOUR outlines the features that currently work. Please do not post the BETA or password on WWW sites or through other public channels, although we are making the password available through this e-mail. Out intention is to limit distribution of the BETA to those seriously interested in a first look at the Epi 2000 technology, but who can tolerate partial features and the bugs associated with development. Bug reports should be sent to epiinfo@cdc.gov . Since this is a BETA test, we are asking for bug reports, and a questionnaire is provided for this purpose via the button called BETA RESULTS on the main menu. The Epi Info HelpLine will receive comments about the system or resolve specific problems about installation, but cannot provide help in developing applications with the new system until it is released. Comments of a general nature or suggestions can be sent to Dr. Andy Dean at agd1@cdc.gov Instructions for Downloading the BETA Version of Epi Info 2000 (Realizing that it is incomplete and not ready for serious work) To download the Epi2000 BETA files you can use a Web browser like the Microsoft Internet Explorer or Netscape, or an FTP software package like WS_FTP or Rapid Filer. To use the Netscape or Internet Explorer browsers, click on the following address, which includes the password: ftp://epidemo:meds1998@sftp.cdc.gov/ftp/epidemo/pub/epi2000/ If this does not bring up your web browser, you can copy the address (URL) to the address window in the browser and press enter. As always, with the Internet, if the first attempt does not work, try again. This transmits the userid, the password, the ftp site, and the correct directory all in one line, and should bring up a list of 13 SETUP files that can be downloaded by clicking on one at a time. Be sure that they arrive on your system with the same names they have in the ftp site. The Internet Explorer sometimes appends "(1)" or "(2)" to SETUP. Change the filenames back to SETUP when you are asked to designate the filename. Netscape displays portions of downloaded files having a W0? extension as text that resembles garbage. Ignore this, click on "SAVE AS" (under the "FILE" menu) and click OK and Netscape will save the file correctly. If you are using FTP software other than a browser, the information needed is: NAME: sftp.cdc.gov USERID: epidemo PASSWORD: meds1998 After the files are in a temporary directory on your hard disk or on diskettes, install the BETA system as follows: Installing Epi Info 2000 These instructions assume that the program called SETUP and the necessary files are either on diskettes or on your hard disk. From the STARTUP menu in Windows 95 or Windows NT, choose RUN and enter the location of your setup file and its name, as in "C:\TEMP\SETUP.EXE", or use the browse button on the RUN dialog to find and select the same file and then click OK. The password for installation is DEMOONLY After experimenting with the BETA, you will be able to UNINSTALL it by running the UNINSTAL.EXE program found in the same directory with Epi Info 2000. Running Epi Info 2000 After installation, use the Epi Info 2000 icon on the DESKTOP, the PROGRAMS menu under START, or the Windows Explorer to run EPI2000.EXE. Getting Acquainted When you see the menu of Epi Info 2000, click on the button called GUIDED TOUR. The GUIDED.HTM file that appears gives specific instructions for the most efficient way to get acqainted with the programs. We strongly recommend that you print the GUIDED TOUR document, using the PRINT button at the top of the screen, and then use the printed document as your guide through the system. Features not yet implemented 1. The CFREQ, CTABLES, and CMEANS statistics for complex samples 2. The ability to change field or variable names or data types after a data table has been created and data have been entered. 3. Access to ODBC databases 4. A RELATE command in Analysis 5. Analytic features for nutritional databases 6. A program for entering data from the screen for statistical calculations (like STATCALC from Epi Info for DOS) 7. Several features of Epi Map 8. Printing of questionnaires 9. A report generator for Analysis 10. Changes in the way Views are linked to data tables We hope that you enjoy testing the BETA version of Epi Info 2000, and look forward to receiving you detailed findings, either by email or by sending the database BETATEST.MDB file containing comments entered from the BETA RESULTS button on the main screen. -----Original Message----- From: Benoit [mailto:Benoit.Salles@WANADOO.FR] Sent: Friday, August 06, 1999 1:08 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] EPI 2000 Can you say me where and how can i get Epi Info 2000 (beta) ? Thanks. Benoit SALLES Statistician From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9907E" ========================================================================= Date: Thu, 29 Jul 1999 10:26:09 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Use epiglue Comments: To: maugat@ext.jussieu.fr In-Reply-To: <379F1E49.20035818@idf.ext.jussieu.fr> MIME-Version: 1.0 Sylvie Maugat writes: >I would like to generate a new application with EPIGLUE but I don't >remember ways to do it. Especialy the early begining. It's important to remember that you need two files for an Epiglue application. These are the .EXE file and the .MNU file. The .EXE file is easy as you just make a copy of EPI6.EXE with the name of the application (in fact you don't even have to do this as you can instruct EPI6.EXE to read a specific .MNU file when you start it. For example: EPI6 MYMENU.MNU will start EPI6.EXE with the new menu file MYMENU.MNU. It is in the .MNU file that the bulk of the work needs to be done. The .MNU file has three main sections: MENU section :- This is where you define the menus. COMMAND section :- This is where you define the actions associated with each item in the MENU section. STRINGTABLE section :- Hints for each menu item that appear on the bottom line of the screen when a menu item is selected. Here is a quick .MNU with an item to enter data and produce a report using ANALYSIS: MYMENU MENU BEGIN POPUP "&Actions" BEGIN MENUITEM "&Enter Data", ENTERDATA MENUITEM "Produce &Report", DOREPORT MENUITEM SEPARATOR MENUITEM "&Quit", IDQUIT END END ENTERDATA BEGIN ENTER MYDATA.REC END DOREPORT BEGIN ANALYSIS MYREPORT.PGM END STRINGTABLE BEGIN ENTERDATA "Enter data for subsequent reporting" DOREPORT "Produce report for entered data" END Looking at this line by line: MYMENU MENU <- Start of MENU section BEGIN <- Menu definition starts POPUP "&Actions" <- Top-level menu BEGIN <- Items of drop-don menu MENUITEM "&Enter Data", ENTERDATA <- An item to enter data. The label "ENTERDATA" points to an item in the command block. MENUITEM "Produce &Report", DOREPORT <- An item to produce a report. The label "ENTERDATA" points to an item in the command block. MENUITEM SEPARATOR <- A separating line MENUITEM "&Quit", IDQUIT <- QUIT item. "IDQUIT" is an internal EPIGLUE command. END <- That's the end of that drop-down menu. END <- End of menu definition ENTERDATA <- Commands for the ENTERDATA menu item follow. BEGIN <- Start of command block ENTER MYDATA.REC <- Start ENTER END <- No more commands DOREPORT <- Commands for the DOREPORT menu item follow. BEGIN <- Start of command block ANALYSIS MYREPORT.PGM <- Run MYREPORT.PGM END <- No more commands STRINGTABLE <- STRINGTABLE block BEGIN <- Hints follow ENTERDATA "Enter data" <- Hint for EMTERDATA DOREPORT "Produce report for entered data" <- Hint for DOREPORT END <- No more hints. The command block can contain anything you could put in an MSDOS batch file as well as some internal EPIGLUE commands (dialog boxes &c.). In addition you could also have a .SCR file (same name as .MNU file but with .SCR exension). This acts as the background screen for the menu system. A good place to start is to examine some of the .MNU files in the \EPI6 directory. Chapter 20 in the manual gives a decent introduction to all of this. Hope that helps. Mark -- Mark Myatt From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9907D" ========================================================================= Date: Thu, 22 Jul 1999 09:11:49 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Denis COULOMBIER Organization: In.V.S. Subject: Re: Min and/or Max values MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To select MIN and MAX values, you need to use GLOBAL variables. The following program let you capture MIN and MAX values in global variables, and use them to select : READ YOURFILE DEFINE MINVAL ##### GLOB 999999 DEFINE MAXVAL ##### GLOB 0 SELECT YOURVAR <> . IF YOURVAR < MINVAL THEN MINVAL = YOURVAR IF YOURVAR > MAXVAL THEN MAXVAL = YOURVAR PROCESS SELECT * Then you can use MINVAR AND MAXVAR to do whatever you want, such as : SELECT YOURVAR=MINVAL TYPE "Minimum value is @MINVAL, range : @MINVAL .. @MAXVAL" Note that MINVAL is initialized with 999999, the maximum value and MAXVAL with 0, the minimum value. The SELECT YOURVAR <> . is needed if there are missing value in the dataset Such approach is often used in automated surveillance system to get the most recent report. For example in a weekly notification system, you can get the the most recent WEEKNUMBER and select the data for this week in order to produce the report. ========================================================================= Date: Thu, 22 Jul 1999 03:28:56 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: Min and/or Max values In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" If you want the minimum, why do you have to select also age > 5 (perhaps to exclude missing?)) I don't have big data sets, so I usually sort first and then look at the extremes; I then know what values to select on. One could also do frequency tables, or as someone else mentioned, means. The most efficient is the program that uses global values. Looking at the extremes is a good idea for data cleaning anyway (even though "plausible" errors can and do in the middle of the range). Leona Bassein At 17:37 21/07/99 -0500, you wrote: >Another idea is to use >Select age >5 and age <7 >what you get is all the 6 year olds >this if you have a certain minimum value in mind > >>>> OluFemi Ogunbanwo 07/21/99 12:00PM >>> >Is there any way of SELECTing a minimum or maximum data value of a variable. I have only been able to use FREQ, but I want just the single min or single max value(s) > >Thank you for your help. > > ========================================================================= Date: Thu, 22 Jul 1999 05:06:35 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Tom & Edie Welty Subject: Removal request MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Please remove me from the Epiinfo distribution list. Tom Welty ========================================================================= Date: Thu, 22 Jul 1999 11:25:10 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Steve Peters Subject: Z score & Flag value MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" I am interested in using the Z score in EpiInfo to check data integrity during the patient weight and height entry process for our clinical information system. Can you help me with some of the formulas on how the Z score is derived on weight & height values??? More specifically> In the file Measure.pas , I need a little help with the declaration of variables and calculation of the Flag value with the Z score. ALSO - Does anyone have an e-mail address for Ray Smith or Keith Sullivan?? Thanks Steve Stephen G. Peters, RPh., MBA Pharmacy Director Children's Hospital 1600 7th Avenue South Birmingham, Al 35233 E-Mail Hyperlink --> Phone (205) 939-9721 Fax (205) 939-9934 ========================================================================= Date: Thu, 22 Jul 1999 16:49:43 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Z score & Flag value MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Kevin Sullivan's email is cdckms@sph.emory.edu I do not know more about the derivations than is in the Chapter in the Epi Info manual on Nutritional Anthropometry, the references in the chapter, and the Pascal source code. Kevin may be able to help. -----Original Message----- From: Steve Peters [mailto:steve.peters@CHSYS.ORG] Sent: Thursday, July 22, 1999 12:25 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Z score & Flag value I am interested in using the Z score in EpiInfo to check data integrity during the patient weight and height entry process for our clinical information system. Can you help me with some of the formulas on how the Z score is derived on weight & height values??? More specifically> In the file Measure.pas , I need a little help with the declaration of variables and calculation of the Flag value with the Z score. ALSO - Does anyone have an e-mail address for Ray Smith or Keith Sullivan?? Thanks Steve Stephen G. Peters, RPh., MBA Pharmacy Director Children's Hospital 1600 7th Avenue South Birmingham, Al 35233 E-Mail Hyperlink --> Phone (205) 939-9721 Fax (205) 939-9934 ========================================================================= Date: Sat, 24 Jul 1999 18:21:10 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kevin Sullivan Subject: Re: IMPORTANT NOTICE - EPI INFO HAS MOVED In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Be sure to update the website at http://www.cdc.gov/epo/epi/techsupp.htm with the new info. I checked it on July 24 and it had the old info. Kevin At 09:10 AM 7/12/99 -0400, you wrote: >> PLEASE BE ADVISED THAT THE EPI INFO HELPDESK HAS RELOCATED. THE >> INFORMATION FOR THE NEW LOCATION IS: >> >> >> NEW PHONE NUMBER: 770.488.8440 >> NEW FAX NUMBER: 770.488.8456 >> EMAIL: EPIINFO@CDC.GOV >> EPIWWW@CDC.GOV >> >> ADDRESS: 2877 BRANDYWINE ROAD >> WILLIAMS BLDG, 4TH FL. M/S K74 >> ATLANTA, GA 30341 >> >> PLEASE INFORM YOUR COLLEAGUES OF THESE CHANGES. >> >> (NOTE: PLEASE DO NOT LEAVE VOICE MAIL MESSAGES AT THE OLD HELPDESK PHONE >> NUMBER, AS WE ARE UNABLE TO RETRIEVE MESSAGES). THE NEW PHONE NUMBER WILL >> BE AVAILABLE BEGINNING MONDAY, JULY 12TH AFTER 1200. >THANK YOU FOR YOUR PATIENCE, AND WE APOLOGIZE FOR THE LATE NOTICE. > >> Thanks >> Epi Info Helpdesk >> >> > > -------------------------------- Kevin M. Sullivan, PhD, MPH, MHA, Assistant Professor Department of Epidemiology Emory University 1518 Clifton Road, NE, Room 448 Atlanta, GA 30322 USA Phone number: 404-727-5846 Fax number: 404-727-5369 Pager number: 770-348-4985 e-mail: cdckms@sph.emory.edu ========================================================================= Date: Wed, 28 Jul 1999 17:14:17 +0200 Reply-To: maugat@ext.jussieu.fr Sender: Epi Info Discussion Group From: Sylvie Maugat Organization: C.CLIN Paris-Nord Subject: Use epiglue MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------438CCAC75E1C34BCBE6165FB" Content-Transfer-Encoding: 8bit Il s'agit d'un message multivolet au format MIME. --------------438CCAC75E1C34BCBE6165FB Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I would like to generate a new application with EPIGLUE but I don't remember ways to do it. Especialy the early begining. Is it someone for help me ??....... Thanks a lot for your help. -- _________________________________________ Sylvie MAUGAT Epidémiologiste CCLIN Paris-Nord 15-21 rue de l'Ecole de Médecine 75006 PARIS Tel : 01 40 46 42 00 --------------438CCAC75E1C34BCBE6165FB Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Carte pour MAUGAT Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: MAUGAT n: ;MAUGAT email;internet: maugat@idf.ext.jussieu.fr x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard --------------438CCAC75E1C34BCBE6165FB-- From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9907C" ========================================================================= Date: Thu, 15 Jul 1999 08:58:06 -0700 Reply-To: gdaurat@club-internet.fr Sender: Epi Info Discussion Group From: Gérald DAURAT Subject: Re: color scheme in EI6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sam Brown wrote: > > Sorry to bother with this trivial question, but I can't seem to find the > screen mentioned in the manual for seeing which colors correspond to > which COLOR designation. If functionality isn't in EpiInfo 6, if > someone could point me to a freeware color palette that matches the > scheme used there, that would be excellent. Thanks much. From main Epi6 menu chose Program then EnterX (or ENTER) then press F2 and follow instructions. G Daurat Montpellier France ========================================================================= Date: Thu, 15 Jul 1999 14:26:28 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: OluFemi Ogunbanwo Subject: Printing from ENTER(X) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Does anyone know if there is a way of invoking ANALYSIS from ENTER, by perharps including a command in the CHK file? At a certain stage of completing a data form, I need to print off only some of the fields in a particular arrangement (to fit onto a small multipart form). I have managed to do this using ANALYSIS but have to exit ENTER each time to run the .PGM file, using the . Is there a more efficient or effective way of doing this please? Thank you very much. ========================================================================= Date: Fri, 16 Jul 1999 17:13:57 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Problems with EpiTable and EpiNut on Fast Machines Fixed MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Not that we've heard about. The fix was only a small patch for the compiler-it should not have had serious side effects. -----Original Message----- From: Kaufmann, Rachel [mailto:rbk8@CDC.GOV] Sent: Monday, July 05, 1999 5:21 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] Problems with EpiTable and EpiNut on Fast Machines Fixed Have any problems been noted with these? Thanks. > -----Original Message----- > From: Dean, Andrew G. [SMTP:agd1@CDC.GOV] > Sent: Friday, January 22, 1999 10:23 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Problems with EpiTable and EpiNut on Fast Machines Fixed > > EpiNut and EpiTable in version 6.04 b-to-c and 6.04b fail to run on some > fast Pentium machines due to an error in the compiler that causes a timing > loop to exceed the allowed value for an integer. The telltale symptom is > an > Error 200 message immediately on attempting to run the programs. > > We have been able to fix this problem with the aid of a compiler patch > obtained from the Internet, but we would like a few people to test the > programs and make sure that they give the same results as the previous > versions and that all functions work. If you would like to test copies of > the corrected programs and give us your conclusions, please send me an > email: > > Agd1@cdc.gov > > Andy Dean > Epi Info Development Team ========================================================================= Date: Sun, 18 Jul 1999 16:44:52 +0530 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Alison Anderson Subject: Problems with write to recfile MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear Colleagues, I've tried this query on the EPI help desk without success. Does anyone on the EPI list have any suggestions? I've already tried starting EPI from DOS etc and other simple troubleshooting; neither is it a problem with the date conversion itself... that code looks odd, but it works because of the way our variable regdate is defined. The biggest concern is that I dont get any error messages, just faulty files. Thanks in anticipation Alison ---------- > From: Alison Anderson > To: EPIINFO@CDC.GOV > Subject: Help wanted from epi info help desk > Date: 13 July 1999 13:29 > > Dear Colleagues > > I'm working with EPI info 6.04b to c (with the Y2k patch) and having > trouble correctly writing to a recfile. > Code as follows: > > erase c:\trials\analy1\dlcp_1.rec > read c:\trials\dlcp\tripod1.rec > > ******************************************************** > *Merge with the code file (1 extra variable, treatment)* > ******************************************************** > > relate tripodno c:\trials\analy1\codez.rec > > ******************************************************** > * redefine string format dates back to dates (Y2K) * > ******************************************************** > define regd > regd=regdate[6,3]+regdate[9,2]+"/"+regdate[1,4] > > route c:\trials\analy1\dlcp_1.rec > write recfile > read c:\trials\analy1\dlcp_1.rec > browse tripodno treatment regdate regd > > > > EPI doesn't give any error messages, but doesnt write to file dlcp_1.rec. > It produces a zreo byte file only. > It doesn't appear to see the read statement, and browses incorrectly from > the parent file tripod1.rec. It therefore gives an error message that > treatment and regd are not found. > > > Can you give me any idea what might be going wrong? > I thought it might be memory (although I have 32Mb installed) as I don't > know how to send more for use of EPI.But the error doesn't seem to change > however small I cut the files. > > The parent file (TRIPOD1.rec is 280 variables x 51 records, the relate file > is 2 variables x 1800 records) > > > > > > Alison M Anderson > Biostatistician > INF RELEASE Project - POKHARA NEPAL > anderson@mos.com.np > > ========================================================================= Date: Sun, 18 Jul 1999 15:41:23 +0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "FOUAD, MUSTAFA" Subject: Re: Problems with write to recfile MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Let me try with that: If the coding for redefine string format to dates back is ok to you -because it does not to me, it looks missing "+/"-, then Try exiting from analysis -press F10- after writing to a recfile, restart analysis, read the file. Hope this works DR MOUSTAFA FOUAD SABIC R&D P.O.BOX 42503 RIYADH 11551 KINGDOM OF SAUDI ARABIA TEL: 966 1 2653333 EXT 5077 FAX: 966 1 2651101 -----Original Message----- From: Alison Anderson [SMTP:anderson@MOS.COM.NP] Sent: Sun, July 18, 1999 2:15 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Problems with write to recfile Dear Colleagues, I've tried this query on the EPI help desk without success. Does anyone on the EPI list have any suggestions? I've already tried starting EPI from DOS etc and other simple troubleshooting; neither is it a problem with the date conversion itself... that code looks odd, but it works because of the way our variable regdate is defined. The biggest concern is that I dont get any error messages, just faulty files. Thanks in anticipation Alison ---------- > From: Alison Anderson > To: EPIINFO@CDC.GOV > Subject: Help wanted from epi info help desk > Date: 13 July 1999 13:29 > > Dear Colleagues > > I'm working with EPI info 6.04b to c (with the Y2k patch) and having > trouble correctly writing to a recfile. > Code as follows: > > erase c:\trials\analy1\dlcp_1.rec > read c:\trials\dlcp\tripod1.rec > > ******************************************************** > *Merge with the code file (1 extra variable, treatment)* > ******************************************************** > > relate tripodno c:\trials\analy1\codez.rec > > ******************************************************** > * redefine string format dates back to dates (Y2K) * > ******************************************************** > define regd > regd=regdate[6,3]+regdate[9,2]+"/"+regdate[1,4] > > route c:\trials\analy1\dlcp_1.rec > write recfile > read c:\trials\analy1\dlcp_1.rec > browse tripodno treatment regdate regd > > > > EPI doesn't give any error messages, but doesnt write to file dlcp_1.rec. > It produces a zreo byte file only. > It doesn't appear to see the read statement, and browses incorrectly from > the parent file tripod1.rec. It therefore gives an error message that > treatment and regd are not found. > > > Can you give me any idea what might be going wrong? > I thought it might be memory (although I have 32Mb installed) as I don't > know how to send more for use of EPI.But the error doesn't seem to change > however small I cut the files. > > The parent file (TRIPOD1.rec is 280 variables x 51 records, the relate file > is 2 variables x 1800 records) > > > > > > Alison M Anderson > Biostatistician > INF RELEASE Project - POKHARA NEPAL > anderson@mos.com.np > > ========================================================================= Date: Sun, 18 Jul 1999 18:52:02 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Thierry Matton Organization: SSA France Subject: Re: Problems with write to recfile MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Dear Colleague, I already had to cope with this kind of problem. Just try to close the dlcp_1.rec file before erasing it. Hope it helps. Thierry Alison Anderson a écrit : > Dear Colleagues, > I've tried this query on the EPI help desk without success. Does anyone on > the EPI list have any suggestions? > I've already tried starting EPI from DOS etc and other simple > troubleshooting; neither is it a problem with the date conversion itself... > that code looks odd, but it works because of the way our variable regdate > is defined. > The biggest concern is that I dont get any error messages, just faulty > files. > > Thanks in anticipation > > Alison > ---------- > > From: Alison Anderson > > To: EPIINFO@CDC.GOV > > Subject: Help wanted from epi info help desk > > Date: 13 July 1999 13:29 > > > > Dear Colleagues > > > > I'm working with EPI info 6.04b to c (with the Y2k patch) and having > > trouble correctly writing to a recfile. > > Code as follows: > > > > erase c:\trials\analy1\dlcp_1.rec > > read c:\trials\dlcp\tripod1.rec > > > > ******************************************************** > > *Merge with the code file (1 extra variable, treatment)* > > ******************************************************** > > > > relate tripodno c:\trials\analy1\codez.rec > > > > ******************************************************** > > * redefine string format dates back to dates (Y2K) * > > ******************************************************** > > define regd > > regd=regdate[6,3]+regdate[9,2]+"/"+regdate[1,4] > > > > route c:\trials\analy1\dlcp_1.rec > > write recfile > > read c:\trials\analy1\dlcp_1.rec > > browse tripodno treatment regdate regd > > > > > > > > EPI doesn't give any error messages, but doesnt write to file dlcp_1.rec. > > It produces a zreo byte file only. > > It doesn't appear to see the read statement, and browses incorrectly from > > the parent file tripod1.rec. It therefore gives an error message that > > treatment and regd are not found. > > > > > > Can you give me any idea what might be going wrong? > > I thought it might be memory (although I have 32Mb installed) as I don't > > know how to send more for use of EPI.But the error doesn't seem to change > > however small I cut the files. > > > > The parent file (TRIPOD1.rec is 280 variables x 51 records, the relate > file > > is 2 variables x 1800 records) > > > > > > > > > > > > Alison M Anderson > > Biostatistician > > INF RELEASE Project - POKHARA NEPAL > > anderson@mos.com.np > > > > -- Thierry Matton, 5A Résidence du Pharo, Esplanade du Pharo, 13007 Marseille # +33 (0)4 91 314 354 ========================================================================= Date: Mon, 19 Jul 1999 11:49:34 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leslie Daly Organization: UCD Subject: Re: Warning - Pilot MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Tony Stewart wrote: > > Sorry this Question is a bit off topic for this list, but as it is read by > some of the greatest epi minds it seems like a fair thing.... > > Does anyone know of/recommend a stats calculator that can run on the Palm > Pilot III? (CIs, 2x2s, sample sizes, you know the Statcalc type of > functions. Great to see another epidemiologist using a Pilot (I got one of the originals way back and wouldn't be without it!) At this stage I have an 8mg board on it! Two solutions - write your own in Basic - I have a suite for chisquare, relative risks etc etc for 2x2 tables and CI for proporions and sample sizes. Contact me if you are interested. Other: a nice suite of programs written by a Chilian Epidemiologist. It is called PalmStat and I have version 1.0 It is available on PilotGear or his email is lvilla@med.puc.cl (all 'L's not 'one's) -- Leslie Daly Associate Professor Dept of Public Health Medicine and Epidemiology, University College Dublin, Earlsfort Terrace Dublin 2 IRELAND Tel: + 353 1 7067315 Fax: + 353 1 7067407 Email: Leslie.Daly@ucd.ie or ldaly@iveagh.ucd.ie ========================================================================= Date: Mon, 19 Jul 1999 09:39:55 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Pinzon, Ms. Milena" Subject: Hantavirus MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Dear colleages: I think this information might be of special interest: The Pan American Health Organization, Regional office of the World Health Organization, has published recently: Hantavirus in the Americas: Guidelines for Diagnosis, Treatment, Prevention, and Control In 1993, the outbreak of a mysterious, deadly respiratory illness in the southwestern United States made national headlines. When a hantavirus was found to be the culprit, other governments in the Region began to focus greater attention on the presence and effects of hantavirus in their countries. This publication presents an extensive view of what came to be known as hantavirus pulmonary syndrome (HPS), its clinical manifestations, methods of preventing infection, and measures taken by governments in the Region to monitor hanta-viruses and educate health professionals and the general public about the disease. This comprehensive manual begins by describing the different hanta-viruses known in the Americas and their reservoirs, rodent ecology and zoology, and the epidemiology of human disease in the Region. Upon this foundation, the manual describes the disease's clinical manifestation and diagnosis and presents guidelines for HPS surveillance, treatment, and case management. It also provides detailed, easy-to-follow instructions for preventing infection in the home, hospital, and laboratory, as well for cleaning rodent-infested areas. The importance of educating health professionals and the general public about the disease is stressed through examples of communication strategies used in different countries of the Region. The publication also provides an overview of communication tools that can be adapted to educate diverse populations about HPS and other communicable diseases. An essential tool for anyone involved in hantavirus prevention, control, treatment, or health education activities, Hantavirus in the Americas: Guidelines for Diagnosis, Treatment, Prevention, and Control contains useful, stand-alone annexes, such as sample case report forms, guidelines for safe handling and transfer of specimens, educational resources, and descriptions of prevention campaigns undertaken by countries in the Region. The book's handy format allows for quick reproduction and distribution of the annexes and infection prevention and control measures. 1999, 80 pp. est., ISBN 92 75 13047 7 US$ 14.00. Order code: TP 47 Spanish version forthcoming, order code: CT 47 If you want more information on how to get this publication, please e-mail me at: pinzomi@paho.org Mylena Pinzon ========================================================================= Date: Mon, 19 Jul 1999 10:23:15 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: FW: Performing calculations on dates In-Reply-To: MIME-Version: 1.0 Dan Pearson writes: >I am having trouble performing a calculation based on a user-defined date. >I am trying to determine the percentage of records that have been updated in >the past year, and I am using the following commands: > >DEFINE DATE1 >IMMEDIATE IF 1=1 THEN DATE1 = "?Please enter the date you wish to use: ?" >DEFINE UPDATED >IF (DATE1 - LASTFULL) <= 365 THEN UPDATED = "Y" >IF (DATE1 - LASTFULL) > 365 THEN UPDATED = "N" >FREQ UPDATED > >Unfortunately, I am coming out with 100% of the records updated, because the >DATE1 field is blank regardless of the date entered. Is there a way to >allow user definition of a date field? This works for me DEFINE DATE1 DATE1 = "?Please enter the date you wish to use: ?" DEFINE UPDATED IF (DATE1 - LASTFULL) <= 365 THEN UPDATED = "Y" IF (DATE1 - LASTFULL) > 365 THEN UPDATED = "N" FREQ UPDATED but it might be a version problem. Try this: DEFINE DATE1 GLOBAL DATE1 = "?Please enter the date you wish to use: ?" WRITE DATE1 /NOECHO DEFINE UPDATED IF (DATE1 - LASTFULL) <= 365 THEN UPDATED = "Y" IF (DATE1 - LASTFULL) > 365 THEN UPDATED = "N" FREQ UPDATED I have found the WRITE command essential with early versions of ANALYSIS. Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Mon, 19 Jul 1999 10:27:28 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Printing from ENTER(X) In-Reply-To: <000001beced8$5552cc60$7719883e@hadoc1> MIME-Version: 1.0 OluFemi Ogunbanwo writes: >Does anyone know if there is a way of invoking ANALYSIS from ENTER, by >perharps including a command in the CHK file? At a certain stage of >completing a data form, I need to print off only some of the fields in a >particular arrangement (to fit onto a small multipart form). I have managed >to do this using ANALYSIS but have to exit ENTER each time to run the .PGM >file, using the . It should be possible to do this using a TSR (details in the EpIInfo manual and example code and headers installed in the EPI6 directory). My guess, however, is that ANALYSIS will require too much memory to be able to run with ENTER resident in memory. I think you might be better off writing a TSR to pick the data from the screen or from the .REC file and print it directly. Mark -- Mark Myatt ========================================================================= Date: Wed, 21 Jul 1999 18:00:43 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: OluFemi Ogunbanwo Subject: Min and/or Max values Comments: To: EPI Info Helpdesk MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01BED3A2.F3838CC0" This is a multi-part message in MIME format. ------=_NextPart_000_0018_01BED3A2.F3838CC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Is there any way of SELECTing a minimum or maximum data value of a = variable. I have only been able to use FREQ, but I want just the single = min or single max value(s) Thank you for your help.=20 ------=_NextPart_000_0018_01BED3A2.F3838CC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Is there any way of SELECTing a minimum or = maximum data=20 value of a variable. I have only been able to use FREQ, but I want just = the=20 single min or single max value(s)
 
Thank you for your = help. 
------=_NextPart_000_0018_01BED3A2.F3838CC0-- ========================================================================= Date: Wed, 21 Jul 1999 20:55:50 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: David Barton Subject: remove MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Please remove me from distribution list. I have no interest in EPI info. ========================================================================= Date: Wed, 21 Jul 1999 20:13:39 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: David Newrick Subject: Re: Min and/or Max values There is no direct way to select out of a REC file the minimum or maximum values of a variable with one SELECT command. However, if you have a good idea of the *shape* of your data then you can try to shortcut by using SELECT on an educated guess, i.e. (taking an AGE variable as an example) SELECT AGE< 5 In other words - you have a good idea that subjects are probably as young as 4 years old, possibly younger, when you do a frequency on AGE after issuing this SELECT command you will get a very different result. If you get a surprise result, say there is a subject as young as 2, then you can select again by issuing the SELECT AGE=2 command. The same applies to the maximum. It would be useful to have MIN, MAX, MEAN commands etc. but even then they would need to be issued as separate commands before the SELECT command (possibly storing to a new variable if in a program file, then issued on the next line with SELECT on the new variable value). Hope this helps. Regards, David Newrick. http://www.staff.ncl.ac.uk/d.c.newrick/epiinfo/ http://www.ncl.ac.uk/~npol/ -----Original Message----- From: OluFemi Ogunbanwo [SMTP:femi@OGUNBANWO.FREESERVE.CO.UK] Sent: 21 July 1999 18:01 To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Min and/or Max values << File: ATT00000.html >> Is there any way of SELECTing a minimum or maximum data value of a variable. I have only been able to use FREQ, but I want just the single min or single max value(s) Thank you for your help. ========================================================================= Date: Wed, 21 Jul 1999 17:08:54 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: remove MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We will do so, with apologies. Do you have an idea how you got on the list? -----Original Message----- From: David Barton [mailto:barton@ONLINE.NO] Sent: Wednesday, July 21, 1999 2:56 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] remove Please remove me from distribution list. I have no interest in EPI info. ========================================================================= Date: Wed, 21 Jul 1999 17:37:47 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Richard Lasater Subject: Re: Min and/or Max values Comments: To: femi@ogunbanwo.freeserve.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Another idea is to use Select age >5 and age <7 what you get is all the 6 year olds this if you have a certain minimum value in mind >>> OluFemi Ogunbanwo 07/21/99 12:00PM = >>> Is there any way of SELECTing a minimum or maximum data value of a = variable. I have only been able to use FREQ, but I want just the single = min or single max value(s) Thank you for your help.=20 ========================================================================= Date: Thu, 22 Jul 1999 02:06:43 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Dimitri E Zylberstein Subject: Re: Min and/or Max values In-Reply-To: <000001bed39b$0d3325c0$7983883e@hadoc1> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 18:00 1999-07-21 +0100, you wrote: > SELECTing a minimum or maximum data value of a variable. I have only >been able to use FREQ, but I want just the single min or single max >value(s) Thank you for your help. =20 You can use a command >means<. For example You have variables "triglyc" (must be numeric) and a variable "sex", then You write: means triglyc sex An anova test is performed and several values are listed like mean, median, min, max splitted for each sex. With regards Dimitri Zylberstein GP Sweden, M=F6lndal From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9907B" ========================================================================= Date: Fri, 9 Jul 1999 02:03:47 PDT Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Nicolae Bedescu Subject: Re: Problems with EpiTable and EpiNut on Fast Machines Fixed Mime-Version: 1.0 Content-Type: text/plain; format=flowed Yes, I have the same problem with the same error mesage when I am running Epi Info under Win98 or WinNT. If I made special icon to run directly epitable, sometime is working and sometime not. >From: "Kaufmann, Rachel" >Reply-To: Epi Info Discussion Group >To: EPI-INFO@LISTSERV.CDC.GOV >Subject: Re: [EPI-INFO] Problems with EpiTable and EpiNut on Fast Machines > Fixed >Date: Mon, 5 Jul 1999 17:21:24 -0400 > >Have any problems been noted with these? Thanks. > > > -----Original Message----- > > From: Dean, Andrew G. [SMTP:agd1@CDC.GOV] > > Sent: Friday, January 22, 1999 10:23 AM > > To: EPI-INFO@LISTSERV.CDC.GOV > > Subject: Problems with EpiTable and EpiNut on Fast Machines Fixed > > > > EpiNut and EpiTable in version 6.04 b-to-c and 6.04b fail to run on some > > fast Pentium machines due to an error in the compiler that causes a >timing > > loop to exceed the allowed value for an integer. The telltale symptom >is > > an > > Error 200 message immediately on attempting to run the programs. > > > > We have been able to fix this problem with the aid of a compiler patch > > obtained from the Internet, but we would like a few people to test the > > programs and make sure that they give the same results as the previous > > versions and that all functions work. If you would like to test copies >of > > the corrected programs and give us your conclusions, please send me an > > email: > > > > Agd1@cdc.gov > > > > Andy Dean > > Epi Info Development Team ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com ========================================================================= Date: Mon, 12 Jul 1999 09:10:13 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Discussion Group Subject: IMPORTANT NOTICE - EPI INFO HAS MOVED MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" > PLEASE BE ADVISED THAT THE EPI INFO HELPDESK HAS RELOCATED. THE > INFORMATION FOR THE NEW LOCATION IS: > > > NEW PHONE NUMBER: 770.488.8440 > NEW FAX NUMBER: 770.488.8456 > EMAIL: EPIINFO@CDC.GOV > EPIWWW@CDC.GOV > > ADDRESS: 2877 BRANDYWINE ROAD > WILLIAMS BLDG, 4TH FL. M/S K74 > ATLANTA, GA 30341 > > PLEASE INFORM YOUR COLLEAGUES OF THESE CHANGES. > > (NOTE: PLEASE DO NOT LEAVE VOICE MAIL MESSAGES AT THE OLD HELPDESK PHONE > NUMBER, AS WE ARE UNABLE TO RETRIEVE MESSAGES). THE NEW PHONE NUMBER WILL > BE AVAILABLE BEGINNING MONDAY, JULY 12TH AFTER 1200. THANK YOU FOR YOUR PATIENCE, AND WE APOLOGIZE FOR THE LATE NOTICE. > Thanks > Epi Info Helpdesk > > ========================================================================= Date: Tue, 13 Jul 1999 09:22:54 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: generating values for variables by concatenating strings In-Reply-To: <3783610A.7B0D53F4@vecnatech.com> MIME-Version: 1.0 Sam Brown writes: >I'm new to Epi Info, accustomed to Perl. > >I'm working on an ICU infection control surveillance database for some >Russian hospitals. We would like to generate a case_ID, which would >reflect a given infection in a given patient. At this point (thinking >Perl), I thought it would be easiest to have a subroutine in a .CHK file >that automatically concatenates MEDICAL_RECORD_NUMBER, SYSTEMDATE, and >INFECTION_CODE when a particular infection is observed in the patient. > >Basic idea is something like > >SSI > IF SSI = "Y" THEN SET CASE_ID = ??? > >In Perl, I'd do something like $medical_record . $date . >$infection_code. I'm not sure how to do it in Epi Info. Try something like: IF SSI = "Y" THEN LET ID = MEDRECNO + SYSTEMDATE + INFCODE ENDIF The '+' is a concatenation operator with string / date variables. Mark -- Mark Myatt ========================================================================= Date: Tue, 13 Jul 1999 13:06:52 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Dan Pearson Subject: FW: Performing calculations on dates MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I am having trouble performing a calculation based on a user-defined date. I am trying to determine the percentage of records that have been updated in the past year, and I am using the following commands: DEFINE DATE1 IMMEDIATE IF 1=1 THEN DATE1 = "?Please enter the date you wish to use: ?" DEFINE UPDATED IF (DATE1 - LASTFULL) <= 365 THEN UPDATED = "Y" IF (DATE1 - LASTFULL) > 365 THEN UPDATED = "N" FREQ UPDATED Unfortunately, I am coming out with 100% of the records updated, because the DATE1 field is blank regardless of the date entered. Is there a way to allow user definition of a date field? Thanks in advance for any advice. Dan Pearson ========================================================================= Date: Tue, 13 Jul 1999 17:58:11 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: FW: Performing calculations on dates Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Try DEFINE DATE1 GLOBAL Then DATE1 is treated as a constant rather than a variable. Jamie Hockin Dan Pearson on 99/07/13 02:06:52 PM Please respond to Epi Info Discussion Group To: EPI-INFO@LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: [EPI-INFO] FW: Performing calculations on dates I am having trouble performing a calculation based on a user-defined date. I am trying to determine the percentage of records that have been updated in the past year, and I am using the following commands: DEFINE DATE1 IMMEDIATE IF 1=1 THEN DATE1 = "?Please enter the date you wish to use: ?" DEFINE UPDATED IF (DATE1 - LASTFULL) <= 365 THEN UPDATED = "Y" IF (DATE1 - LASTFULL) > 365 THEN UPDATED = "N" FREQ UPDATED Unfortunately, I am coming out with 100% of the records updated, because the DATE1 field is blank regardless of the date entered. Is there a way to allow user definition of a date field? Thanks in advance for any advice. Dan Pearson ========================================================================= Date: Wed, 14 Jul 1999 11:10:09 +1100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Tony Stewart Subject: Warning - Off topic question. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sorry this Question is a bit off topic for this list, but as it is read by some of the greatest epi minds it seems like a fair thing.... Does anyone know of/recommend a stats calculator that can run on the Palm Pilot III? (CIs, 2x2s, sample sizes, you know the Statcalc type of functions. ========================================================================= Date: Wed, 14 Jul 1999 08:17:03 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: color scheme in EI6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sorry to bother with this trivial question, but I can't seem to find the screen mentioned in the manual for seeing which colors correspond to which COLOR designation. If functionality isn't in EpiInfo 6, if someone could point me to a freeware color palette that matches the scheme used there, that would be excellent. Thanks much. From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9907A" ========================================================================= Date: Fri, 2 Jul 1999 11:46:02 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: PEPI For Windows Comments: To: agd1@cdc.gov, alc@servidor.unam.mx, alkral@itsa.ucsf.edu, andrew.forbes@med.monash.edu.au, antunesc@mono.icb.ufmg.br, bengt.moller@mbox2.swipnet.se, bernt.lindtjorn@cih.uib.no, bmanyame@hqfaus01.unicef.org, bpazva@harare.iafrica.com, bxe2@cdc.gov, castellano.j@mcd.gen.de.us, cdckms@sph.emory.edu, chklein@manguinhos.ensp.fiocruz.br, ck@dynamite.com.au, coflunkc@leonis.nus.sg, consult@tstt.net.tt, coulombi@b3e.jussieu.fr, crmcc@gate.net, d.u.pfeiffer@massey.ac.nz, djolley@ariel.ucs.unimelb.edu.au, dnordlund@aol.com, eramalle@goriz.sendanet.es, esterman.adrian@health.sa.gov.au, evan.sergeant@smtpgwy.agric.nsw.gov.au, fmedpct@md2.md.chula.ac.th, fwolfe@msus1.msus.edu, g.hartel@mailbox.uq.edu.au, garst@uvapsy.psy.uva.nl, gomes@lelo.uem.mz, gpatrone@opal.tufts.edu, hans.stenlund@stat.umu.se, heberto@meakins.lan.mcgill.ca, jag.atrie@health.wa.gov.au, james_wood@compuserve.com, jaf@lamar.colostate.edu, jmatute@pronet.net.gt, jucar@cica.es, ljorm@doh.health.nsw.gov.au, lucas@dgsp.scstf.rcanaria.es, mamartinez@mail2.cti.unav.es, martinez_j@a1.rcdp.gov, mccleary@mrrc.bio.uci.edu, medicur1@edu.uch.gr, mikael.aberg@primnet.se, mikal.ustad@ism.uit.no, mulderym@fs7003.pg.tno.nl, pani@ymed.ks.se, per.blanck@mailbox.swipnet.se, pgnetto@ax.apc.org, pierreclaquin@compuserve.com, pmb@mhri.edu.au, promed@riosoft.softex.br, r.fisher@unsw.edu.au, ratti@usa.net, rbk8@cdc.gov, rmccart@epin.ab.umd.edu, rvs3@wonder.em.cdc.gov, sas@ipe.ufg.br, sonia@stat.psu.edu, statcon@ix.netcom.com, stefan.ma@commed.hku.hk, pturri@mail.state.tn.us, gilles@epiconcept.fr, normar01@mcgc16.med.nyu.edu, mcmillan@cc.ucsf.edu, jamie_hockin@inet.hwc.ca, mark_veitch.mdu@muwaye.unimelb.edu.au, jed5@cdc.gov, eramalle@mail.sendanet.es, Koomen.Em@net.HCC.nl, s.ritter@iop.bpmf.ac.uk, Rainer.Muche@medizin.uni-ulm.de, S.S.MASTANA@lboro.AC.UK, TCHUR@doh.health.nsw.gov.au, DDedman@phls.co.uk, jsantos@uec.inta.uchile.cl, Bob@exo.com, BHolden536@aol.com, kannika@cmu.chiangmai.ac.th, waa101@uriacc.uri.edu, ACTUARY@asko.donetsk.ua, EBRENNER@compuserve.com, jzg@cs.bham.ac.uk, FPetschke@t-online.de, wilsonsx@novell2.bham.ac.uk, jmc@med.pitt.edu, EpiMon@aol.com, gxs03@health.state.ny.us, busson@neptune.chu-stlouis.fr, steve.dunn@agric.nsw.gov.au, nbirkett@zeus.med.uottawa.ca, joe@ty-coch.demon.co.uk, JML@dadlnet.dk, Epidemiology List , rjfreund@NewNetra.ensp.fr, sph1804@utsph.sph.uth.tmc.edu, jehrlich@dairyvets.com, bcmiller@biostats.uwo.ca, penamanu@paho.org, chotiwan@who.net, fmedpct@md2.md.chula.ac.th, kclun@nus.edu.sg, ZHUKAK75@ccvax.mmc.edu, nfchu@hsph.harvard.edu, chklein@manguinhos.ensp.fiocruz.br, DANP@CIKC.ORG, jat.sandhu@bristol.ac.uk, Vera.Todorovic@bhcs-tr.trent.nhs.uk, johnf@netaxs.com, fgamboa@hotmail.com, rgempp@werken.ufro.cl, MODAOJUN@epid.lan.mcgill.ca, hegd@servidor.unam.mx, l.gostelow@scfuk.org.uk, jmc@med.pitt.edu, ananda@sunnet.com.br, flogisto@usa.net, N.C.Unwin@newcastle.ac.uk, s.loeffler@vet.uu.nl, jmatute@pronet.net.gt, cdckms@sph.emory.edu, lbautista@multinet.com.co, jchaui@ssdnet.com.ar, pab555@comadrid.es, yv.bonnier@ccisd.org, JML@dadlnet.dk, IOKOSUN@wpo.it.luc.edu, JUNG100W@cdc.gov, kevin_sullivan@oz.ped.emory.edu, marcelo@inf.ufsc.br, lbautista@multinet.com.co, maupome@unixg.ubc.ca, SHIYF@PUBLIC2.ZZ.HA.CN, Lengeler@ubaclu.unibas.ch MIME-Version: 1.0 PEPI for Windows - Test Version Available -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joe Abramson is currently working on producing a Windows version of the renowned PEPI suite of programs. Although the present DOS-based PEPI programs can be run under Windows, the Windows format improves their integration, flexibility, ease-of-use, and appearance. During the development phase this site: http://www.myatt.demon.co.uk will act as the distribution site for PEPI modules as they become available. At present the package consists of WHATIS.EXE, which provides a calculator (an expression evaluator with 24 memory registers for constants, interim results, and formulae) and computes probability values (and their inverse), confidence intervals, and time spans. PEPI for Windows is a 16-bit Microsoft Windows application and will run under Microsoft Windows 3.1x, '95, '98, and NT 3.51 or later. PEPI for Windows is currently available only as a test version. Please report any problems you experience or any suggestions you may have to improve the package. Mark -- Mark Myatt ========================================================================= Date: Fri, 2 Jul 1999 10:38:04 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Pat Salt, Ph.D." Organization: Judge Baker Children's Center Subject: changing directories for ANALYSIS MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Looking for help from the experts: I want to change the default directory that EPI looks in for data files. I changed it in setup, and it works for 'enter' but not for 'analysis' (which continues to look in the old place). How do I get the change to apply in 'analysis' too? TIA, Pat Salt ************ Pat Salt, Ph.D. Judge Baker Children's Center 3 Blackfan Circle Boston, MA 02115 617-232-8390, ext. 2223 psalt@jbcc.harvard.edu ========================================================================= Date: Fri, 2 Jul 1999 17:13:43 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert-Jean FREUND Subject: Re: changing directories for ANALYSIS In-Reply-To: <199907021444.KAA17759@ackroyd.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 1 define a new directory, let say study1 as c:\study1 using the Windows explorer 2 on the desk of the computer define an icon of EpiInfo by duplicating the original one and in properties (right click of the mouse) choose program and define the working directory as c:\study1 3 start Epi6 with this icon this results in defining c:\study1 as the default directory in most of the epiinfo programs (Eped, Enter, Check, Analysis) Hope that helps Robert A 10:38 02/07/1999 -0400, vous avez =E9crit : >Looking for help from the experts: > I want to change the default directory that EPI looks in for data >files. I changed it in setup, and it works for 'enter' but not for >'analysis' (which continues to look in the old place). How do I get >the change to apply in 'analysis' too? > TIA, > Pat Salt >************ >Pat Salt, Ph.D. >Judge Baker Children's Center >3 Blackfan Circle >Boston, MA 02115 >617-232-8390, ext. 2223 >psalt@jbcc.harvard.edu > \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Fri, 2 Jul 1999 11:16:06 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Douglas Dodson Subject: Re: changing directories for ANALYSIS Mime-Version: 1.0 Content-Type: text/plain Pat, I'm no expert, and this is probably the wrong way to do it. But I have included the following statement in my config.epi file: read c:\myfile\*.rec Douglas Dodson Missouri Department of Health dodsod@mail.health.state.mo.us >>> "Pat Salt, Ph.D." 7/2/99 >>> Looking for help from the experts: I want to change the default directory that EPI looks in for data files. I changed it in setup, and it works for 'enter' but not for 'analysis' (which continues to look in the old place). How do I get the change to apply in 'analysis' too? TIA, Pat Salt ************ Pat Salt, Ph.D. Judge Baker Children's Center 3 Blackfan Circle Boston, MA 02115 617-232-8390, ext. 2223 psalt@jbcc.harvard.edu ! ========================================================================= Date: Fri, 2 Jul 1999 10:42:12 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kyle Luman Subject: Data Analysis MIME-Version: 1.0 Content-Type: text/plain I have a relational database for immunizations that looks like the sample below. It has a date for when the IZ was given and then a place to describe the antigen. The way you know if it is MMR1 or MMR2 is by counting the number of MMRs there are total, there is not a variable name MMR1 and another one MMR2. For analysis purposes, I would like to create a dataset that does have variable names for each antigen given in the series. I would like to have an MMR1 and an MMR2, etc., but I am not sure how EpiInfo can accomplish this. Thanks. PrimaryKey UniqueID Name Date Antigen 9724 115968 NAME 1 9/15/98 DTP 9709 115968 NAME 1 10/22/97 IPV 9723 115968 NAME 1 9/9/98 HEP B 9727 115968 NAME 1 11/30/98 IPV 9706 115968 NAME 1 9/18/97 DTP 9708 115968 NAME 1 9/25/97 HIB 9705 115968 NAME 1 9/15/97 HEP B 9720 115968 NAME 1 7/7/98 MMR 9711 115968 NAME 1 1/13/98 IPV 9717 115968 NAME 1 8/6/98 MMR 9704 115968 NAME 1 8/27/97 DTP 9707 115968 NAME 1 11/20/97 MMR 49132 337128 NAME 2 5/11/98 HEP B 8895 107399 NAME 3 8/7/97 IPV 90525 435798 NAME 4 3/12/99 HEP B 90523 435798 NAME 4 12/30/97 DTP 90526 435798 NAME 4 3/12/99 HEP B 90524 435798 NAME 4 9/1/98 DTP 90522 435798 NAME 4 8/19/97 HIB 90521 435798 NAME 4 7/8/97 HIB 77237 410904 NAME 5 7/15/97 HIB 77239 410904 NAME 5 3/12/99 HEP B > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ > ========================================================================= Date: Fri, 2 Jul 1999 14:15:28 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Maldonado, Mr. Omar" Subject: Re: changing directories for ANALYSIS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable If yor AUTOEXEC.BAT file has been modified by the installling program, try this: 1. Open a DOS session and go to your directory (IE. C:\DATA) 2. In this prompt C:\DATA type ANALYSIS (You don't need the Epi Menu) 3. All the process will work in this directory Hope this help Omar Maldonado A. Consultor Sistemas de Informaci=F3n OPS - OMS Chile -----Mensaje original----- De: Pat Salt, Ph.D. [mailto:psalt@JBCC.HARVARD.EDU] Enviado el: Viernes 2 de Julio de 1999 10:38 AM Para: EPI-INFO@LISTSERV.CDC.GOV Asunto: [EPI-INFO] changing directories for ANALYSIS Looking for help from the experts: I want to change the default directory that EPI looks in for data files. I changed it in setup, and it works for 'enter' but not for 'analysis' (which continues to look in the old place). How do I get the change to apply in 'analysis' too? TIA, Pat Salt ************ Pat Salt, Ph.D. Judge Baker Children's Center 3 Blackfan Circle Boston, MA 02115 617-232-8390, ext. 2223 psalt@jbcc.harvard.edu ========================================================================= Date: Fri, 2 Jul 1999 15:14:54 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Maldonado, Mr. Omar" Subject: Re: Data Analysis Comments: cc: "kluman@SCHSA.ORG" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable You should define some new variables, as many as ANTIGEN you wanto to count. Asign the values to the new variables with this commands: DEFINE MMR1 DEFINE MMR2 DEFINE DTP etc.... IF ANTIGEN=3D"MMR1" THEN MMR1=3D"Y" IF ANTIGEN=3D"MMR2" THEN MMR2=3D"Y" IF ANTIGEN=3D"DTP" THEN DTP=3D"Y" etc. etc. Hope this help Omar Maldonado A. Consultor Sistemas de Informaci=F3n OPS - OMS Chile -----Mensaje original----- De: Kyle Luman [mailto:kluman@SCHSA.ORG] Enviado el: Viernes 2 de Julio de 1999 01:42 PM Para: EPI-INFO@LISTSERV.CDC.GOV Asunto: [EPI-INFO] Data Analysis I have a relational database for immunizations that looks like the sample below. It has a date for when the IZ was given and then a place to describe the antigen. The way you know if it is MMR1 or MMR2 is by counting the number of MMRs there are total, there is not a variable name MMR1 and another one MMR2. For analysis purposes, I would like to create a dataset that does have variable names for each antigen given in the series. I would like to have an MMR1 and an MMR2, etc., but I am not sure how EpiInfo can accomplish this. Thanks. PrimaryKey UniqueID Name Date Antigen 9724 115968 NAME 1 9/15/98 DTP 9709 115968 NAME 1 10/22/97 IPV 9723 115968 NAME 1 9/9/98 HEP B 9727 115968 NAME 1 11/30/98 IPV 9706 115968 NAME 1 9/18/97 DTP 9708 115968 NAME 1 9/25/97 HIB 9705 115968 NAME 1 9/15/97 HEP B 9720 115968 NAME 1 7/7/98 MMR 9711 115968 NAME 1 1/13/98 IPV 9717 115968 NAME 1 8/6/98 MMR 9704 115968 NAME 1 8/27/97 DTP 9707 115968 NAME 1 11/20/97 MMR 49132 337128 NAME 2 5/11/98 HEP B 8895 107399 NAME 3 8/7/97 IPV 90525 435798 NAME 4 3/12/99 HEP B 90523 435798 NAME 4 12/30/97 DTP 90526 435798 NAME 4 3/12/99 HEP B 90524 435798 NAME 4 9/1/98 DTP 90522 435798 NAME 4 8/19/97 HIB 90521 435798 NAME 4 7/8/97 HIB 77237 410904 NAME 5 7/15/97 HIB 77239 410904 NAME 5 3/12/99 HEP B > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ > ========================================================================= Date: Fri, 2 Jul 1999 15:10:08 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "C. Jon Hinkle" Subject: Re: Data Analysis Mime-Version: 1.0 Content-Type: text/plain Depending on the size of the dataset, the easiest thing might be to sort by uniqueID then antigen then date and manually edit the antigen names with update. This is not elegant, but if the dataset is only a few hundred records, it might actually be easier. I say this as someone who just spent a couple hundred hours cleaning 24000 records for inclusion in a data warehouse. When I got down to the short rows, it became apparent that it was easier to do it manually than program it. >>> Kyle Luman 07/02 12:42 PM >>> I have a relational database for immunizations that looks like the sample below. It has a date for when the IZ was given and then a place to describe the antigen. The way you know if it is MMR1 or MMR2 is by counting the number of MMRs there are total, there is not a variable name MMR1 and another one MMR2. For analysis purposes, I would like to create a dataset that does have variable names for each antigen given in the series. I would like to have an MMR1 and an MMR2, etc., but I am not sure how EpiInfo can accomplish this. Thanks. PrimaryKey UniqueID Name Date Antigen 9724 115968 NAME 1 9/15/98 DTP 9709 115968 NAME 1 10/22/97 IPV 9723 115968 NAME 1 9/9/98 HEP B 9727 115968 NAME 1 11/30/98 IPV 9706 115968 NAME 1 9/18/97 DTP 9708 115968 NAME 1 9/25/97 HIB 9705 115968 NAME 1 9/15/97 HEP B 9720 115968 NAME 1 7/7/98 MMR 9711 115968 NAME 1 1/13/98 IPV 9717 115968 NAME 1 8/6/98 MMR 9704 115968 NAME 1 8/27/97 DTP 9707 115968 NAME 1 11/20/97 MMR 49132 337128 NAME 2 5/11/98 HEP B 8895 107399 NAME 3 8/7/97 IPV 90525 435798 NAME 4 3/12/99 HEP B 90523 435798 NAME 4 12/30/97 DTP 90526 435798 NAME 4 3/12/99 HEP B 90524 435798 NAME 4 9/1/98 DTP 90522 435798 NAME 4 8/19/97 HIB 90521 435798 NAME 4 7/8/97 HIB 77237 410904 NAME 5 7/15/97 HIB 77239 410904 NAME 5 3/12/99 HEP B > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ > ! ! ========================================================================= Date: Mon, 5 Jul 1999 10:48:14 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: Data Analysis Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Here is part of the program you need. This has only the logic for MMR1 and MMR2, but you can add all the other variables. I have assumed you want dates of each dose. The key here is to create a related file with one record per person on the fly and then fill in the variables based on the antigens in your IZ file. Jamie Hockin Director, FETP Canada ======== IZ.PGM ========= * Program to generate .rec file with one record per person and variables * giving dates of each immunization - process shown for MMR1 and MMR2 only * assumes that the working directory for analysis contains all files. * If not, add path to all file names * get rid of temporary files erase mmrtemp.rec erase mmrtem2.rec * get rid of any copy of the final file with MMR1 and MMR2 erase mmr.rec * Read the original file with one record per immunization given read iz * create mmrtemp.rec with one record per person route mmrtemp.rec output freq id * read the temp file and add variables MMR1 and MMR2 as dates read mmrtemp define mmr1 define mmr2 * create 2nd temp file with ID, MMR1 and MMR2 only route mmrtem2.rec write recfile * back to original file read d:iz * relate brings in MMR1 and MMR2 variables relate id d:mmrtem2 * sort file to get all records together and in date order sort id antigen DATE * temporary variable to hold ID variable over to next record * you need this to allow final write of only one record per ID define previd ###### cumulative * temporary variable to hold number of records for this ID * so only the last record is saved in final write define reccnt ### cumulative * when ID changes, reset counting number of records, otherwise add one if id <> previd then reccnt = 0 reccnt = reccnt + 1 * PREVID starts off as . but now should hold ID from the current record previd = id * fill MMR1 and MMR2 variables * for other antigens, you would have DPT1 ... DPT5 or more * just keep adding if statements, with the final one using <> . instead of = . if antigen = "MMR" and MMR1 = . then MMR1 = date if antigen = "MMR" and MMR1 <> . then MMR2 = date * save everything to fix the values of reccnt and read it back in erase mmrtemp.rec route mmrtemp.rec write recfile read mmrtemp * now just save one record per ID, using the record in IZ which is last for this ID select reccnt = count route d:mmr.rec * save the variables of interest from IZ plus the new ones created write recfile key id name mmr1 mmr2 Kyle Luman on 99/07/02 01:42:12 PM Please respond to Epi Info Discussion Group To: EPI-INFO@LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: [EPI-INFO] Data Analysis I have a relational database for immunizations that looks like the sample below. It has a date for when the IZ was given and then a place to describe the antigen. The way you know if it is MMR1 or MMR2 is by counting the number of MMRs there are total, there is not a variable name MMR1 and another one MMR2. For analysis purposes, I would like to create a dataset that does have variable names for each antigen given in the series. I would like to have an MMR1 and an MMR2, etc., but I am not sure how EpiInfo can accomplish this. Thanks. PrimaryKey UniqueID Name Date Antigen 9724 115968 NAME 1 9/15/98 DTP 9709 115968 NAME 1 10/22/97 IPV 9723 115968 NAME 1 9/9/98 HEP B 9727 115968 NAME 1 11/30/98 IPV 9706 115968 NAME 1 9/18/97 DTP 9708 115968 NAME 1 9/25/97 HIB 9705 115968 NAME 1 9/15/97 HEP B 9720 115968 NAME 1 7/7/98 MMR 9711 115968 NAME 1 1/13/98 IPV 9717 115968 NAME 1 8/6/98 MMR 9704 115968 NAME 1 8/27/97 DTP 9707 115968 NAME 1 11/20/97 MMR 49132 337128 NAME 2 5/11/98 HEP B 8895 107399 NAME 3 8/7/97 IPV 90525 435798 NAME 4 3/12/99 HEP B 90523 435798 NAME 4 12/30/97 DTP 90526 435798 NAME 4 3/12/99 HEP B 90524 435798 NAME 4 9/1/98 DTP 90522 435798 NAME 4 8/19/97 HIB 90521 435798 NAME 4 7/8/97 HIB 77237 410904 NAME 5 7/15/97 HIB 77239 410904 NAME 5 3/12/99 HEP B > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ > ========================================================================= Date: Mon, 5 Jul 1999 17:21:24 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Kaufmann, Rachel" Subject: Re: Problems with EpiTable and EpiNut on Fast Machines Fixed MIME-Version: 1.0 Content-Type: text/plain Have any problems been noted with these? Thanks. > -----Original Message----- > From: Dean, Andrew G. [SMTP:agd1@CDC.GOV] > Sent: Friday, January 22, 1999 10:23 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Problems with EpiTable and EpiNut on Fast Machines Fixed > > EpiNut and EpiTable in version 6.04 b-to-c and 6.04b fail to run on some > fast Pentium machines due to an error in the compiler that causes a timing > loop to exceed the allowed value for an integer. The telltale symptom is > an > Error 200 message immediately on attempting to run the programs. > > We have been able to fix this problem with the aid of a compiler patch > obtained from the Internet, but we would like a few people to test the > programs and make sure that they give the same results as the previous > versions and that all functions work. If you would like to test copies of > the corrected programs and give us your conclusions, please send me an > email: > > Agd1@cdc.gov > > Andy Dean > Epi Info Development Team ========================================================================= Date: Tue, 6 Jul 1999 11:32:25 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: David Barton Subject: remove MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01BEC7A3.38B5FC80" This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BEC7A3.38B5FC80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0008_01BEC7A3.38B5FC80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0008_01BEC7A3.38B5FC80-- ========================================================================= Date: Wed, 7 Jul 1999 18:15:39 +0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: generating values for variables by concatenating strings MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm new to Epi Info, accustomed to Perl. I'm working on an ICU infection control surveillance database for some Russian hospitals. We would like to generate a case_ID, which would reflect a given infection in a given patient. At this point (thinking Perl), I thought it would be easiest to have a subroutine in a .CHK file that automatically concatenates MEDICAL_RECORD_NUMBER, SYSTEMDATE, and INFECTION_CODE when a particular infection is observed in the patient. Basic idea is something like SSI IF SSI = "Y" THEN SET CASE_ID = ??? In Perl, I'd do something like $medical_record . $date . $infection_code. I'm not sure how to do it in Epi Info. Thanks millions in advance. -- Yours, Sam Brown sam @ vecnatech.com sambrown @ bigfoot.com http://www.bigfoot.com/~sambrown ========================================================================= Date: Wed, 7 Jul 1999 09:01:32 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kyle Luman Subject: Re: generating values for variables by concatenating s trings MIME-Version: 1.0 Content-Type: text/plain Unfortunately, you can't use the underscore for variable names when you are using EpiInfo for data entry. Because the underscore is actually a way to tell the computer you want to have an alphanumeric variable. In order for the check file to concatenate the medical record number, infection code and the date, I had to tell it to substring the variables, although I started with the the first digit and took all of the digits. ( for MEDRECNUM, [1,6] stands for start with digit one and take 6 digits which is all of the digits there are in what I defined.) Unfortunately, it does not look to me like SYSTEMDATE is an available variable in data entry, although there are variables with are actually the date of last update. So if you only enter data once, then it will remain the same, but it you keep going back into the record day after day, then the CASEID will change as the DATE variable (below) changes. The other way to do this is to hand enter the date and not have it as a formatted variable. CHECK FILE SSI AFTER ENTRY IF SSI = "Y" THEN LET CASEID = MEDRECNUM [1,6] + DATE [1,10] + INFCODE [1,6] ENDIF END END QUESTIONNAIRE MEDRECNUM ###### INFCODE DATE SSI CASEID ______________________ Hope this helps. > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ > > -----Original Message----- > From: Sam Brown [SMTP:sam@VECNATECH.COM] > Sent: Wednesday, July 07, 1999 7:16 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: [EPI-INFO] generating values for variables by concatenating > strings > > I'm new to Epi Info, accustomed to Perl. > > I'm working on an ICU infection control surveillance database for some > Russian hospitals. We would like to generate a case_ID, which would > reflect a given infection in a given patient. At this point (thinking > Perl), I thought it would be easiest to have a subroutine in a .CHK file > that automatically concatenates MEDICAL_RECORD_NUMBER, SYSTEMDATE, and > INFECTION_CODE when a particular infection is observed in the patient. > > Basic idea is something like > > SSI > IF SSI = "Y" THEN SET CASE_ID = ??? > > In Perl, I'd do something like $medical_record . $date . > $infection_code. I'm not sure how to do it in Epi Info. > > > Thanks millions in advance. > -- > Yours, > > Sam Brown > sam @ vecnatech.com > sambrown @ bigfoot.com > http://www.bigfoot.com/~sambrown ========================================================================= Date: Thu, 8 Jul 1999 01:41:19 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Sam Brown Subject: Re: generating values for variables by concatenating s trings MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Thanks for the tip. I'll do some fiddling and let you know how it turns out. Thanks again. From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9906E" ========================================================================= Date: Wed, 30 Jun 1999 09:07:53 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Problems with Epi info and Windows NT In-Reply-To: <01BEC199.09C62450.d.coulombier@rnsp-sante.fr> MIME-Version: 1.0 Denis COULOMBIER writes: >I have recently upgraded my computer to a Pentium II, 400 MHZ, running >Windows NT 4.00. > >I cannot load Epi info in full screen mode. If I load Epi info in a Dos >window, I get it. When starting Analysis, it switches automatically to full >screen. When quitting Epi info, I get an error message : UC NTVDM has >encountered an illegal instruction CS:5b5f IP:0e 57 bf de 4d. > >Has anyone encountered such a problem, and is there a solution ? Contact Phil Atkinson (P.Atkinson@cdsc.nthames.nhs.uk) as he has muxh experience running EpiInfo under NT. I think this may be a problem with the way NT locks out control of hardware. Try moving the .BGI files out of the EpiInfo directory to somewhere not on any search path and see it ANALYSIS will work then. If so, I think NT is blocking access to video hardware that ANALYSIS uses to detect which .BGI file to use when displaying graphs. Mark -- Mark Myatt From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9906D" ========================================================================= Date: Mon, 28 Jun 1999 06:11:52 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: deleted records in dbf and epi-info Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi everybody, A curiosity: what does epi-info do when it reads a dbf file with deleted records? a) leaves them out completely? b) imports them as deleted? c) imports them as usual data? Thank you very much. Leona Bassein, Hospital Statistician in Italy ========================================================================= Date: Mon, 28 Jun 1999 13:25:23 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: deleted records in dbf and epi-info In-Reply-To: <3.0.5.16.19990628120237.2a3f7ada@pop> MIME-Version: 1.0 Leona Bassein writes: >Hi everybody, > >A curiosity: what does epi-info do when it reads a dbf file with deleted >records? > >a) leaves them out completely? >b) imports them as deleted? >c) imports them as usual data? > >Thank you very much. Two questions really: ANALYSIS (READ FILENAME.DBF) -=-=-=-=-=-=-=-=-=-=-=-=-=-= Deleted records are imported but do not appear in any tables, lists, &c. UPDATE does not work so records cannot be undeleted. SET PROCESS = DELETED / UNDELETED / BOTH works as expected. IMPORT -=-=-= Deleted records are imported as 'DELETED' UPDATE works fine. SET PROCESS = DELETED / UNDELETED / BOTH works as expected. Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Mon, 28 Jun 1999 19:04:24 +0200 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Denis COULOMBIER Organization: In.V.S. Subject: Problems with Epi info and Windows NT MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I have recently upgraded my computer to a Pentium II, 400 MHZ, running Windows NT 4.00. I cannot load Epi info in full screen mode. If I load Epi info in a Dos window, I get it. When starting Analysis, it switches automatically to full screen. When quitting Epi info, I get an error message : UC NTVDM has encountered an illegal instruction CS:5b5f IP:0e 57 bf de 4d. Has anyone encountered such a problem, and is there a solution ? Thanks. From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9906C" ========================================================================= Date: Tue, 15 Jun 1999 12:09:55 +0200 Reply-To: Patrick Goeman Sender: Epi Info Discussion Group From: Patrick Goeman Subject: 2000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit When will it be possible to get Epi-Info 2000 ? http://perso.wanadoo.fr/smsie ========================================================================= Date: Sat, 19 Jun 1999 21:49:35 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group Comments: Authenticated sender is From: Louk Meertens Subject: (Fwd) Re: Fw: Attention: New Virus Comments: To: ANDREW.G.DEAN.Epi.Info.Organiasatie@ultra.multiweb.net Comments: cc: Koomen.Em@net.HCC.nl, mark@myatt.demon.co.uk, "Ess, Ingeborg van" , cima@xs4all.nl, info@noordwest12.nl, info@noordwest12.nl, Bruce Williams , j.mintjes@cbo.nl MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Heemskerk 19/06/1999 Dear Andrew Dean, I just received this rather allarming message, maybe you know already about it, better be carefull. Yours ,Louk Meertens, The Netherlands. > >>>>> >>> ---------- > >>>>> >>> From: Reinhard H. Wohlbier[SMTP:r.wohlbier@bulk-online.com] > >>>>> >>> Sent: woensdag 24 maart 1999 11:04 > >>>>> >>> To: trans.tech.publications@bulk-online.com > >>>>> >>> Cc: mailing.list@bulk-online.com > >>>>> >>> Subject: Attention: New Virus > >>>>> >>> > >>>>> >>> Ladies and Gentlemen, dear Friends, > >>>>> >>> > >>>>> >>> We have just been informed about the following: > >>>>> >>> > >>>>> >>> >> Please note this carefully! > >>>>> >>> >> If you receive an email titled "It Takes Guts to Say ,Jesus'" > >>>>> >>> >> DO NOT OPEN IT. > >>>>> >>> >> It will erase everything on your hard drive. Forward this > >>>>> >>> >> letter out to as many people as you can. This is a new, very > >>>>> >>> >> malicious virus and not many people know about it. > >>>>> >>> > >>>>> >>> >> This information was announced yesterday morning from IBM; > >>>>> >>> >> please share it with everyone that might access the internet. > >>>>> >>> >> > >>>>> >>> >> Once again, pass this along to EVERYONE in your > address book so > >>>>> >>> >> that this may be stopped. > >>>>> >>> >> > >>>>> >>> >> AOL has said that this is a very dangerous virus and > that there > >>>>>is > >>>>> >>> >> NO remedy for it at this time. Please practice cautionary > >>>>>measures > >>>>> >>> >> and forward this to all your online friends ASAP. > >>>>> >>> >> > >>>>> >>> >> > >>>>> >>> >> Kind regards, > >>>>> >>> > >>>>> >>> Dr.-Ing. Reinhard H. Wohlbier > >>>>> >>> Publisher & Editor-in-Chief > >>>>> >>> Trans Tech Publications Germany > >>>>> >>> > >>>>> >>> http://www.bulk-online.com > >>>>> >>> r.wohlbier@bulk-online.com > >>>>> >>> fax: +49 53 23 96 97 99 > >>>>> >>> tel.: +49 53 23 96 97 0 > >>>>> >>> > >>>>> >>> Kind regards, > >>>>> >>> > >>>>> >>> Dr. Reinhard H. Wohlbier > >>>>> >>> Publisher, Trans Tech Publications > >>>>> >>> http://www.bulk-online.com > >>>>> >>> > >>>>> >>> email: r.wohlbier@bulk-online.com > >>>>> >>> fax: +49 (0) 53 23 96 97 99 > >>>>> >>> tel.: +49 (0) 53 23 96 97 0 REDFLAMINGO ========================================================================= Date: Sat, 19 Jun 1999 21:55:47 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Greg Fegan Subject: This is a hoax MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Dear All, As someone who has previously and unwittingly propagated one of these I would like to let you know that this is a hoax. See http://vil.mcafee.com/villib/dispHoax.asp?id=vh10053 for info best wishes Greg ----- Original Message ----- From: Louk Meertens To: Sent: Saturday, June 19, 1999 4:49 PM Subject: [EPI-INFO] (Fwd) Re: Fw: Attention: New Virus > Heemskerk 19/06/1999 > Dear Andrew Dean, > I just received this rather allarming message, maybe you know already > about it, better be carefull. > > Yours ,Louk Meertens, The Netherlands. > > > >>>>> >>> ---------- > > >>>>> >>> From: Reinhard H. Wohlbier[SMTP:r.wohlbier@bulk-online.com] > > >>>>> >>> Sent: woensdag 24 maart 1999 11:04 > > >>>>> >>> To: trans.tech.publications@bulk-online.com > > >>>>> >>> Cc: mailing.list@bulk-online.com > > >>>>> >>> Subject: Attention: New Virus > > >>>>> >>> > > >>>>> >>> Ladies and Gentlemen, dear Friends, > > >>>>> >>> > > >>>>> >>> We have just been informed about the following: > > >>>>> >>> > > >>>>> >>> >> Please note this carefully! > > >>>>> >>> >> If you receive an email titled "It Takes Guts to Say ,Jesus'" > > >>>>> >>> >> DO NOT OPEN IT. > > >>>>> >>> >> It will erase everything on your hard drive. Forward this > > >>>>> >>> >> letter out to as many people as you can. This is a new, very > > >>>>> >>> >> malicious virus and not many people know about it. > > >>>>> >>> > > >>>>> >>> >> This information was announced yesterday morning from IBM; > > >>>>> >>> >> please share it with everyone that might access the internet. > > >>>>> >>> >> > > >>>>> >>> >> Once again, pass this along to EVERYONE in your > > address book so > > >>>>> >>> >> that this may be stopped. > > >>>>> >>> >> > > >>>>> >>> >> AOL has said that this is a very dangerous virus and > > that there > > >>>>>is > > >>>>> >>> >> NO remedy for it at this time. Please practice cautionary > > >>>>>measures > > >>>>> >>> >> and forward this to all your online friends ASAP. > > >>>>> >>> >> > > >>>>> >>> >> > > >>>>> >>> >> Kind regards, > > >>>>> >>> > > >>>>> >>> Dr.-Ing. Reinhard H. Wohlbier > > >>>>> >>> Publisher & Editor-in-Chief > > >>>>> >>> Trans Tech Publications Germany > > >>>>> >>> > > >>>>> >>> http://www.bulk-online.com > > >>>>> >>> r.wohlbier@bulk-online.com > > >>>>> >>> fax: +49 53 23 96 97 99 > > >>>>> >>> tel.: +49 53 23 96 97 0 > > >>>>> >>> > > >>>>> >>> Kind regards, > > >>>>> >>> > > >>>>> >>> Dr. Reinhard H. Wohlbier > > >>>>> >>> Publisher, Trans Tech Publications > > >>>>> >>> http://www.bulk-online.com > > >>>>> >>> > > >>>>> >>> email: r.wohlbier@bulk-online.com > > >>>>> >>> fax: +49 (0) 53 23 96 97 99 > > >>>>> >>> tel.: +49 (0) 53 23 96 97 0 > > REDFLAMINGO > ========================================================================= Date: Sun, 20 Jun 1999 11:48:16 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Tom & Edie Welty Subject: Hospital data base and TB registry MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear Epilist, I am EIS alumnus (1982) who recently retired from the Indian Health Service and have been providing volunteer service for the Cameroonian Baptist Medical Program. I used Epi Info to set up a TB register and now hope to help them in setting up a simple affordable information system on hospital admissions. I have the following questions: 1. Has anyone used EpiInfo for this purpose using ICD-9 coding? If so I would like to buy or borrow their program. It would also be helpful to include some financial data. Would you recommend Epi Info for such a purpose? Or perhaps you could recommend another software program for use in developing countries. 2. Has anyone developed a TB register on Epi Info? I would be happy to share mine but it's pretty rudimentary. There are over 100 cases of TB per year at each of 2 hospitals. Any suggestions regarding this would be apprectiated. Thanks. Tom Welty ========================================================================= Date: Mon, 21 Jun 1999 06:14:36 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: New Virus that works thru e-mail In-Reply-To: <199906191954.VAA03080@ultra.multiweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I have seen this before (see below) and I think that it was mentioned as a hoax. However, there are other recent dangers: after Melissa another more dangerous virus has been found which works on the same principle. If you use outlook or outlook express you can spread it, otherwise you will just get infected. You receive an e-mail from someone you know (so far in English only I think, but of course this too will change with time) as an answer to something you have written (it keeps the subject). The message says something to the effect that you are not yet receiving what you asked for, but in the meantime look at these (zipped) files. When you go to unzip, it doesn't work, but by that time you are infected. As epidemiologists, you know you should go beyond today's problems and be ready for tomorrow's: the latest trend is to attempt to have you infect your friends and colleagues by e-mail. Some e-mail programs open attachments automatically and these should be avoided. If someone sends you an attachment you did not expect in that form, maybe it's better to ask confirmation (perhaps in another language or with a secret code). With these new viruses it is more probable that someone you have already written to will give it to you. Anyway, if an e-mail program does not automatically open attachments so far you cannot get infected through ascii e-mail. Does anyone know about rtf (rich text format) or html? Good luck, Leona Bassein At 21:49 19/06/99 +0000, you wrote: >Heemskerk 19/06/1999 >Dear Andrew Dean, >I just received this rather allarming message, maybe you know already >about it, better be carefull. > >Yours ,Louk Meertens, The Netherlands. > >> >>>>> >>> ---------- >> >>>>> >>> From: Reinhard H. Wohlbier[SMTP:r.wohlbier@bulk-online.com] >> >>>>> >>> Sent: woensdag 24 maart 1999 11:04 >> >>>>> >>> To: trans.tech.publications@bulk-online.com >> >>>>> >>> Cc: mailing.list@bulk-online.com >> >>>>> >>> Subject: Attention: New Virus >> >>>>> >>> >> >>>>> >>> Ladies and Gentlemen, dear Friends, >> >>>>> >>> >> >>>>> >>> We have just been informed about the following: >> >>>>> >>> >> >>>>> >>> >> Please note this carefully! >> >>>>> >>> >> If you receive an email titled "It Takes Guts to Say ,Jesus'" >> >>>>> >>> >> DO NOT OPEN IT. >> >>>>> >>> >> It will erase everything on your hard drive. Forward this >> >>>>> >>> >> letter out to as many people as you can. This is a new, very >> >>>>> >>> >> malicious virus and not many people know about it. >> >>>>> >>> >> >>>>> >>> >> This information was announced yesterday morning from IBM; >> >>>>> >>> >> please share it with everyone that might access the internet. >> >>>>> >>> >> >> >>>>> >>> >> Once again, pass this along to EVERYONE in your >> address book so >> >>>>> >>> >> that this may be stopped. >> >>>>> >>> >> >> >>>>> >>> >> AOL has said that this is a very dangerous virus and >> that there >> >>>>>is >> >>>>> >>> >> NO remedy for it at this time. Please practice cautionary >> >>>>>measures >> >>>>> >>> >> and forward this to all your online friends ASAP. >> >>>>> >>> >> >> >>>>> >>> >> >> >>>>> >>> >> Kind regards, >> >>>>> >>> >> >>>>> >>> Dr.-Ing. Reinhard H. Wohlbier >> >>>>> >>> Publisher & Editor-in-Chief >> >>>>> >>> Trans Tech Publications Germany >> >>>>> >>> >> >>>>> >>> http://www.bulk-online.com >> >>>>> >>> r.wohlbier@bulk-online.com >> >>>>> >>> fax: +49 53 23 96 97 99 >> >>>>> >>> tel.: +49 53 23 96 97 0 >> >>>>> >>> >> >>>>> >>> Kind regards, >> >>>>> >>> >> >>>>> >>> Dr. Reinhard H. Wohlbier >> >>>>> >>> Publisher, Trans Tech Publications >> >>>>> >>> http://www.bulk-online.com >> >>>>> >>> >> >>>>> >>> email: r.wohlbier@bulk-online.com >> >>>>> >>> fax: +49 (0) 53 23 96 97 99 >> >>>>> >>> tel.: +49 (0) 53 23 96 97 0 > >REDFLAMINGO > > From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9906A" ========================================================================= Date: Tue, 1 Jun 1999 17:12:09 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Nelson, Robert" Subject: problems with merge/relate Comments: cc: "Bock, Stephanie" MIME-Version: 1.0 Content-Type: text/plain We are working with a 79 variable clinic visit database and would like to request your help in creating an "ASCII" output file. The data entry screens reflect the medical record, while the output file must conform to a specific study format - therefore, a substantial amount of recoding and reordering of variables is necessary. The ID variable in the dataset is unique to the individual patient, but multiple visits are allowed. Therefore, ID is not necessarily unique to an individual record. When the following merge (join) is attempted using ID and date of visit, matching is unsucessful, and produces a final file with more records than anticipated (expecting 124, getting 425). We have also tried to use the relate command. While we were able to keep the final number of records to 124, the variable visit date is repeated at the beginning of each related block. Any suggestions? Thanks, Rob Nelson Stephanie Bock ========================================================================= Date: Wed, 2 Jun 1999 16:04:04 -0700 Reply-To: gdaurat@club-internet.fr Sender: Epi Info Discussion Group From: Gérald DAURAT Subject: Re: problems with merge/relate MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Nelson, Robert wrote: > > We are working with a 79 variable clinic visit database and would like to > request your help in creating an "ASCII" output file. The data entry > screens reflect the medical record, while the output file must conform to a > specific study format - therefore, a substantial amount of recoding and > reordering of variables is necessary. > The ID variable in the dataset is unique to the individual patient, but > multiple visits are allowed. Therefore, ID is not necessarily unique to an > individual record. When the following merge (join) is attempted using ID > and date of visit, matching is unsucessful, and produces a final file with > more records than anticipated (expecting 124, getting 425). > We have also tried to use the relate command. While we were able to keep > the final number of records to 124, the variable visit date is repeated at > the beginning of each related block. > Any suggestions? > Thanks, > Rob Nelson > Stephanie Bock In order to answer you properly, I'd need some more information. Do you have 2 related files (one for individual patients and one for visits) or only one with variables such as visit1 visit2 etc. (this is not the better way)? Do you want to extract data from these files? (eventually after proceeding some calculations) Wich format do you want: ASCII delimited, ASCII fixed lenght..... May be you used the COMBINE command and got 425 records. This would mean there are 425 visits and 124 individuals. I suggest you send me a copy of the .qes and .pgm and .chk files if you can't answer these questions. G Daurat Montpellier France ========================================================================= Date: Thu, 3 Jun 1999 08:44:28 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Nelson, Robert" Subject: Re: problems with merge/relate MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Thanks for your replies. We are working with one recfile. Our layout is, with a layout similar to the following: rcd_date (date entered into database), ID (participant ID), visit date, test result 1, test result 2, etc. So, the first five observations in the dataset might look like this: 05/05/1999 0001 01/01/1999 Negative Negative ... 06/06/1999 0001 03/03/1999 Negative Positive ... 06/06/1999 0001 04/04/1999 Positive Positive ... 05/05/1999 0002 01/04/1999 Negative Negative ... 05/05/1999 0003 01/02/1999 Negative Negative ... We begin by sorting by ID and visit date. We next tried using both JOIN and RELATE. With JOIN, records for which ID is repeated did not merge correctly (but the others did). Again, ID is unique to participants, but not unique to records. With RELATE, we sorted by ID and visit date. The correct number of records was created. However, visit date was then somehow included at the beginning of each related block (9 times in each record!!). I see two possible ways to fix this. First, find a way to get JOIN to work. Second, simply constructing a temporary record ID (RECID) for merging - using ID and visit date - which could then be dropped. In summary, if we could solve either of two problems, we would be able to create the desired output file: 1) Getting Epi Info to successfully merge by two variables - neither of which is unique alone, but which are unique in combination. 2) Being able to write all 78 database variables to a recfile in one write statement (this would allow us to create and then drop a temporary RECID). I have included a sample of our code (with recoding removed, as it is not relevant). erase d:\data\mar1.rec read d:\data\pr_samp2.rec recode race=1 to race=3 recode race=2 to race=8 route d:\data\mar1.rec write recfile RCD_DATE ID AREA SITENUM VISIT_DT HIV_TEST PREV_TST ST \ COUNTY DOB SEX RACE RV_KNOWN RV_HIV99 RV_HIVO read d:\data\mar1.rec sort id visit_dt route d:\data\mar1a.rec write recfile read d:\data\pr_samp2.rec define RV_STD _ RV_STD=referred define rv_oth _ rv_oth=otherr route d:\data\mar2.rec write recfile ID VISIT_DT RV_SYMP RV_ASYMP RV_F_UP RV_CONT RV_STD RV_OTH read d:\data\mar2.rec sort id visit_dt route d:\data\mar2a.rec write recfile read d:\data\pr_samp2.rec route d:\data\mar3.rec write recfile ID VISIT_DT RG_SXMAN RG_SXWMN RG_IDU RG_COKE RG_O_DRG \ RG_XDRG RG_SXIDU RG_SXHIV RG_SXMSM HX_STD read d:\data\mar3.rec sort id visit_dt route d:\data\mar3a.rec write recfile *RELATE ATTEMPT *read d:\data\mar1a.rec *relate id d:\data\mar2a.rec *route d:\data\marA.rec *write recfile *read d:\data\marA.rec *relate id d:\data\mar3a.rec *route d:\data\marB.rec *write recfile *MERGE ATTEMPT dos d:\epi6\merge d:\data\mar1a.rec d:\data\mar2a.rec d:\data\marA.rec 2 id visit_dt n dos d:\epi6\merge d:\data\marA.rec d:\data\mar3a.rec d:\data\marB.rec 2 id visit_dt n dos d:\epi6\export d:\data\martot.rec d:\data\martot.asc 2 Thanks, Rob Nelson Stephanie Bock > -----Original Message----- > From: Girald DAURAT [SMTP:gdaurat@CLUB-INTERNET.FR] > Sent: Wednesday, June 02, 1999 7:04 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: [EPI-INFO] problems with merge/relate > > Nelson, Robert wrote: > > > > We are working with a 79 variable clinic visit database and would like > to > > request your help in creating an "ASCII" output file. The data entry > > screens reflect the medical record, while the output file must conform > to a > > specific study format - therefore, a substantial amount of recoding and > > reordering of variables is necessary. > > The ID variable in the dataset is unique to the individual patient, but > > multiple visits are allowed. Therefore, ID is not necessarily unique to > an > > individual record. When the following merge (join) is attempted using > ID > > and date of visit, matching is unsucessful, and produces a final file > with > > more records than anticipated (expecting 124, getting 425). > > We have also tried to use the relate command. While we were able to > keep > > the final number of records to 124, the variable visit date is repeated > at > > the beginning of each related block. > > Any suggestions? > > Thanks, > > Rob Nelson > > Stephanie Bock > > In order to answer you properly, I'd need some more information. > > Do you have 2 related files (one for individual patients and one for > visits) or only one with variables such as visit1 visit2 etc. (this is > not the better way)? > > Do you want to extract data from these files? (eventually after > proceeding some calculations) > Wich format do you want: ASCII delimited, ASCII fixed lenght..... > > May be you used the COMBINE command and got 425 records. This would mean > there are 425 visits and 124 individuals. > > I suggest you send me a copy of the .qes and .pgm and .chk files if you > can't answer these questions. > > G Daurat > > Montpellier > France ========================================================================= Date: Thu, 3 Jun 1999 08:16:24 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "C. Jon Hinkle" Subject: Re: problems with merge/relate Comments: cc: rxn1@CDC.gov Mime-Version: 1.0 Content-Type: text/plain If I follow correctly, your thought about creating a variable that contained the concatinated variables ID and visit date and then writing a new recfile should be the simplest. Remember that you do not need to list all 79 (now 80) fields if you want to write them all, simply ROUTE NEWFILENAME.REC and then WRITE RECFILE. You can sort on whatever field(s) you choose prior to writing the recfile and the new recfile will be sorted in that order. Merging the two variables is not difficult, even if the ID is a number variable. Remember that the date is simply a special type of string. Therefore, your new variable must be a string as well. Something like this should work: DEFINE sortstr _______________ LET sortstr = visitdate+id ROUTE newrec.rec WRITE recfile That will give you a recfile with a unique identifier for each record (sortstr). In this instance, sorting on that identifier will sort by visit date and then by id number. If you want to sort by id and then by date, reverse the order in the LET statement above. As an alternative, you could SELECT for each visit date and write recfiles for all the patients who visited on that date and then work with the different sets separately, but I'm not sure what that would accomplish. As has been pointed out elsewhere, exporting to an ASCII file (as well as many other formats) is a function built in to Epi 6. Hope this is helpful C. Jon Hinkle >>> "Nelson, Robert" 06/03 7:44 AM >>> Thanks for your replies. We are working with one recfile. Our layout is, with a layout similar to the following: rcd_date (date entered into database), ID (participant ID), visit date, test result 1, test result 2, etc. So, the first five observations in the dataset might look like this: 05/05/1999 0001 01/01/1999 Negative Negative ... 06/06/1999 0001 03/03/1999 Negative Positive ... 06/06/1999 0001 04/04/1999 Positive Positive ... 05/05/1999 0002 01/04/1999 Negative Negative ... 05/05/1999 0003 01/02/1999 Negative Negative ... We begin by sorting by ID and visit date. We next tried using both JOIN and RELATE. With JOIN, records for which ID is repeated did not merge correctly (but the others did). Again, ID is unique to participants, but not unique to records. With RELATE, we sorted by ID and visit date. The correct number of records was created. However, visit date was then somehow included at the beginning of each related block (9 times in each record!!). I see two possible ways to fix this. First, find a way to get JOIN to work. Second, simply constructing a temporary record ID (RECID) for merging - using ID and visit date - which could then be dropped. In summary, if we could solve either of two problems, we would be able to create the desired output file: 1) Getting Epi Info to successfully merge by two variables - neither of which is unique alone, but which are unique in combination. 2) Being able to write all 78 database variables to a recfile in one write statement (this would allow us to create and then drop a temporary RECID). I have included a sample of our code (with recoding removed, as it is not relevant). erase d:\data\mar1.rec read d:\data\pr_samp2.rec recode race=1 to race=3 recode race=2 to race=8 route d:\data\mar1.rec write recfile RCD_DATE ID AREA SITENUM VISIT_DT HIV_TEST PREV_TST ST \ COUNTY DOB SEX RACE RV_KNOWN RV_HIV99 RV_HIVO read d:\data\mar1.rec sort id visit_dt route d:\data\mar1a.rec write recfile read d:\data\pr_samp2.rec define RV_STD _ RV_STD=referred define rv_oth _ rv_oth=otherr route d:\data\mar2.rec write recfile ID VISIT_DT RV_SYMP RV_ASYMP RV_F_UP RV_CONT RV_STD RV_OTH read d:\data\mar2.rec sort id visit_dt route d:\data\mar2a.rec write recfile read d:\data\pr_samp2.rec route d:\data\mar3.rec write recfile ID VISIT_DT RG_SXMAN RG_SXWMN RG_IDU RG_COKE RG_O_DRG \ RG_XDRG RG_SXIDU RG_SXHIV RG_SXMSM HX_STD read d:\data\mar3.rec sort id visit_dt route d:\data\mar3a.rec write recfile *RELATE ATTEMPT *read d:\data\mar1a.rec *relate id d:\data\mar2a.rec *route d:\data\marA.rec *write recfile *read d:\data\marA.rec *relate id d:\data\mar3a.rec *route d:\data\marB.rec *write recfile *MERGE ATTEMPT dos d:\epi6\merge d:\data\mar1a.rec d:\data\mar2a.rec d:\data\marA.rec 2 id visit_dt n dos d:\epi6\merge d:\data\marA.rec d:\data\mar3a.rec d:\data\marB.rec 2 id visit_dt n dos d:\epi6\export d:\data\martot.rec d:\data\martot.asc 2 Thanks, Rob Nelson Stephanie Bock > -----Original Message----- > From: Girald DAURAT [SMTP:gdaurat@CLUB-INTERNET.FR] > Sent: Wednesday, June 02, 1999 7:04 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: [EPI-INFO] problems with merge/relate > > Nelson, Robert wrote: > > > > We are working with a 79 variable clinic visit database and would like > to > > request your help in creating an "ASCII" output file. The data entry > > screens reflect the medical record, while the output file must conform > to a > > specific study format - therefore, a substantial amount of recoding and > > reordering of variables is necessary. > > The ID variable in the dataset is unique to the individual patient, but > > multiple visits are allowed. Therefore, ID is not necessarily unique to > an > > individual record. When the following merge (join) is attempted using > ID > > and date of visit, matching is unsucessful, and produces a final file > with > > more records than anticipated (expecting 124, getting 425). > > We have also tried to use the relate command. While we were able to > keep > > the final number of records to 124, the variable visit date is repeated > at > > the beginning of each related block. > > Any suggestions? > > Thanks, > > Rob Nelson > > Stephanie Bock > > In order to answer you properly, I'd need some more information. > > Do you have 2 related files (one for individual patients and one for > visits) or only one with variables such as visit1 visit2 etc. (this is > not the better way)? > > Do you want to extract data from these files? (eventually after > proceeding some calculations) > Wich format do you want: ASCII delimited, ASCII fixed lenght..... > > May be you used the COMBINE command and got 425 records. This would mean > there are 425 visits and 124 individuals. > > I suggest you send me a copy of the .qes and .pgm and .chk files if you > can't answer these questions. > > G Daurat > > Montpellier > France ! ! ! ! ! ! ========================================================================= Date: Thu, 3 Jun 1999 16:06:08 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Nelson, Robert" Subject: Re: problems with merge/relate MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Thanks for your reply. The problem lies with the output file specifications: it must have only the 78 study variables, and they must be in the correct order. I agree that creating a unique record ID would allow me to merge without problem. However, how would I remove this new variable from my final recfile? > -----Original Message----- > From: C. Jon Hinkle [SMTP:HinklC@MAIL.HEALTH.STATE.MO.US] > Sent: Thursday, June 03, 1999 9:16 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: [EPI-INFO] problems with merge/relate > > If I follow correctly, your thought about creating a variable that > contained the concatinated variables ID and visit date and then writing a > new recfile should be the simplest. Remember that you do not need to list > all 79 (now 80) fields if you want to write them all, simply ROUTE > NEWFILENAME.REC and then WRITE RECFILE. You can sort on whatever field(s) > you choose prior to writing the recfile and the new recfile will be sorted > in that order. > > Merging the two variables is not difficult, even if the ID is a number > variable. Remember that the date is simply a special type of string. > Therefore, your new variable must be a string as well. Something like > this should work: > > DEFINE sortstr _______________ > LET sortstr = visitdate+id > ROUTE newrec.rec > WRITE recfile > > That will give you a recfile with a unique identifier for each record > (sortstr). In this instance, sorting on that identifier will sort by > visit date and then by id number. If you want to sort by id and then by > date, reverse the order in the LET statement above. > > As an alternative, you could SELECT for each visit date and write recfiles > for all the patients who visited on that date and then work with the > different sets separately, but I'm not sure what that would accomplish. > > As has been pointed out elsewhere, exporting to an ASCII file (as well as > many other formats) is a function built in to Epi 6. > > Hope this is helpful > C. Jon Hinkle > > >>> "Nelson, Robert" 06/03 7:44 AM >>> > Thanks for your replies. We are working with one recfile. Our layout is, > with a layout similar to the following: rcd_date (date entered into > database), ID (participant ID), visit date, test result 1, test result 2, > etc. So, the first five observations in the dataset might look like this: > 05/05/1999 0001 01/01/1999 Negative Negative ... > 06/06/1999 0001 03/03/1999 Negative Positive ... > 06/06/1999 0001 04/04/1999 Positive Positive ... > 05/05/1999 0002 01/04/1999 Negative Negative ... > 05/05/1999 0003 01/02/1999 Negative Negative ... > We begin by sorting by ID and visit date. We next tried using both JOIN > and > RELATE. With JOIN, records for which ID is repeated did not merge > correctly > (but the others did). Again, ID is unique to participants, but not unique > to records. With RELATE, we sorted by ID and visit date. The correct > number of records was created. However, visit date was then somehow > included at the beginning of each related block (9 times in each > record!!). > > I see two possible ways to fix this. First, find a way to get JOIN to > work. > Second, simply constructing a temporary record ID (RECID) for merging - > using ID and visit date - which could then be dropped. > In summary, if we could solve either of two problems, we would be able to > create the desired output file: > 1) Getting Epi Info to successfully merge by two variables - neither of > which is unique alone, but which are unique in combination. > 2) Being able to write all 78 database variables to a recfile in one write > statement (this would allow us to create and then drop a temporary RECID). > > I have included a sample of our code (with recoding removed, as it is not > relevant). > > erase d:\data\mar1.rec > read d:\data\pr_samp2.rec > recode race=1 to race=3 > recode race=2 to race=8 > route d:\data\mar1.rec > write recfile RCD_DATE ID AREA SITENUM VISIT_DT HIV_TEST PREV_TST ST \ > COUNTY DOB SEX RACE RV_KNOWN RV_HIV99 RV_HIVO > > read d:\data\mar1.rec > sort id visit_dt > route d:\data\mar1a.rec > write recfile > > read d:\data\pr_samp2.rec > define RV_STD _ > RV_STD=referred > define rv_oth _ > rv_oth=otherr > route d:\data\mar2.rec > write recfile ID VISIT_DT RV_SYMP RV_ASYMP RV_F_UP RV_CONT RV_STD RV_OTH > > read d:\data\mar2.rec > sort id visit_dt > route d:\data\mar2a.rec > write recfile > > read d:\data\pr_samp2.rec > route d:\data\mar3.rec > write recfile ID VISIT_DT RG_SXMAN RG_SXWMN RG_IDU RG_COKE RG_O_DRG \ > RG_XDRG RG_SXIDU RG_SXHIV RG_SXMSM HX_STD > > read d:\data\mar3.rec > sort id visit_dt > route d:\data\mar3a.rec > write recfile > > *RELATE ATTEMPT > > *read d:\data\mar1a.rec > *relate id d:\data\mar2a.rec > *route d:\data\marA.rec > *write recfile > > *read d:\data\marA.rec > *relate id d:\data\mar3a.rec > *route d:\data\marB.rec > *write recfile > > *MERGE ATTEMPT > dos d:\epi6\merge d:\data\mar1a.rec d:\data\mar2a.rec d:\data\marA.rec 2 > id > visit_dt n > dos d:\epi6\merge d:\data\marA.rec d:\data\mar3a.rec d:\data\marB.rec 2 > id > visit_dt n > > dos d:\epi6\export d:\data\martot.rec d:\data\martot.asc 2 > > Thanks, > Rob Nelson > Stephanie Bock > > > -----Original Message----- > > From: Girald DAURAT [SMTP:gdaurat@CLUB-INTERNET.FR] > > Sent: Wednesday, June 02, 1999 7:04 PM > > To: EPI-INFO@LISTSERV.CDC.GOV > > Subject: Re: [EPI-INFO] problems with merge/relate > > > > Nelson, Robert wrote: > > > > > > We are working with a 79 variable clinic visit database and would like > > to > > > request your help in creating an "ASCII" output file. The data entry > > > screens reflect the medical record, while the output file must conform > > to a > > > specific study format - therefore, a substantial amount of recoding > and > > > reordering of variables is necessary. > > > The ID variable in the dataset is unique to the individual patient, > but > > > multiple visits are allowed. Therefore, ID is not necessarily unique > to > > an > > > individual record. When the following merge (join) is attempted using > > ID > > > and date of visit, matching is unsucessful, and produces a final file > > with > > > more records than anticipated (expecting 124, getting 425). > > > We have also tried to use the relate command. While we were able to > > keep > > > the final number of records to 124, the variable visit date is > repeated > > at > > > the beginning of each related block. > > > Any suggestions? > > > Thanks, > > > Rob Nelson > > > Stephanie Bock > > > > In order to answer you properly, I'd need some more information. > > > > Do you have 2 related files (one for individual patients and one for > > visits) or only one with variables such as visit1 visit2 etc. (this is > > not the better way)? > > > > Do you want to extract data from these files? (eventually after > > proceeding some calculations) > > Wich format do you want: ASCII delimited, ASCII fixed lenght..... > > > > May be you used the COMBINE command and got 425 records. This would mean > > there are 425 visits and 124 individuals. > > > > I suggest you send me a copy of the .qes and .pgm and .chk files if you > > can't answer these questions. > > > > G Daurat > > > > Montpellier > > France > > ! > > ! > > ! > > ! > > ! > > ! ========================================================================= Date: Thu, 3 Jun 1999 13:17:57 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kyle Luman Subject: Re: problems with merge/relate MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Possibly the last time you wrote to the recfile, you could use the NOT syntax write recfile not uniqueID This will write all variables to the file excluding that one (or others if you list them). As far as having the variables in a certain order, it might be easiest to export to some other application (like Excel or Access) and move the variables around there. > Kyle Luman, MPH > Epidemiologist > Stanislaus County, Health Services Agency > 820 Scenic Drive, Modesto, CA 95350 > Ph: (209) 558-7526 Fx: (209) 558-7286 E-mail: kluman@schsa.org > Personal WebPage: http://www.geocities.com/Tokyo/Flats/4550/ > > -----Original Message----- > From: Nelson, Robert [SMTP:rxn1@CDC.GOV] > Sent: Thursday, June 03, 1999 1:06 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: [EPI-INFO] problems with merge/relate > > Thanks for your reply. The problem lies with the output file > specifications: it must have only the 78 study variables, and they must be > in the correct order. I agree that creating a unique record ID would > allow > me to merge without problem. However, how would I remove this new > variable > from my final recfile? > > > -----Original Message----- > > From: C. Jon Hinkle [SMTP:HinklC@MAIL.HEALTH.STATE.MO.US] > > Sent: Thursday, June 03, 1999 9:16 AM > > To: EPI-INFO@LISTSERV.CDC.GOV > > Subject: Re: [EPI-INFO] problems with merge/relate > > > > If I follow correctly, your thought about creating a variable that > > contained the concatinated variables ID and visit date and then writing > a > > new recfile should be the simplest. Remember that you do not need to > list > > all 79 (now 80) fields if you want to write them all, simply ROUTE > > NEWFILENAME.REC and then WRITE RECFILE. You can sort on whatever > field(s) > > you choose prior to writing the recfile and the new recfile will be > sorted > > in that order. > > > > Merging the two variables is not difficult, even if the ID is a number > > variable. Remember that the date is simply a special type of string. > > Therefore, your new variable must be a string as well. Something like > > this should work: > > > > DEFINE sortstr _______________ > > LET sortstr = visitdate+id > > ROUTE newrec.rec > > WRITE recfile > > > > That will give you a recfile with a unique identifier for each record > > (sortstr). In this instance, sorting on that identifier will sort by > > visit date and then by id number. If you want to sort by id and then by > > date, reverse the order in the LET statement above. > > > > As an alternative, you could SELECT for each visit date and write > recfiles > > for all the patients who visited on that date and then work with the > > different sets separately, but I'm not sure what that would accomplish. > > > > As has been pointed out elsewhere, exporting to an ASCII file (as well > as > > many other formats) is a function built in to Epi 6. > > > > Hope this is helpful > > C. Jon Hinkle > > > > >>> "Nelson, Robert" 06/03 7:44 AM >>> > > Thanks for your replies. We are working with one recfile. Our layout > is, > > with a layout similar to the following: rcd_date (date entered into > > database), ID (participant ID), visit date, test result 1, test result > 2, > > etc. So, the first five observations in the dataset might look like > this: > > 05/05/1999 0001 01/01/1999 Negative Negative ... > > 06/06/1999 0001 03/03/1999 Negative Positive ... > > 06/06/1999 0001 04/04/1999 Positive Positive ... > > 05/05/1999 0002 01/04/1999 Negative Negative ... > > 05/05/1999 0003 01/02/1999 Negative Negative ... > > We begin by sorting by ID and visit date. We next tried using both JOIN > > and > > RELATE. With JOIN, records for which ID is repeated did not merge > > correctly > > (but the others did). Again, ID is unique to participants, but not > unique > > to records. With RELATE, we sorted by ID and visit date. The correct > > number of records was created. However, visit date was then somehow > > included at the beginning of each related block (9 times in each > > record!!). > > > > I see two possible ways to fix this. First, find a way to get JOIN to > > work. > > Second, simply constructing a temporary record ID (RECID) for merging - > > using ID and visit date - which could then be dropped. > > In summary, if we could solve either of two problems, we would be able > to > > create the desired output file: > > 1) Getting Epi Info to successfully merge by two variables - neither of > > which is unique alone, but which are unique in combination. > > 2) Being able to write all 78 database variables to a recfile in one > write > > statement (this would allow us to create and then drop a temporary > RECID). > > > > I have included a sample of our code (with recoding removed, as it is > not > > relevant). > > > > erase d:\data\mar1.rec > > read d:\data\pr_samp2.rec > > recode race=1 to race=3 > > recode race=2 to race=8 > > route d:\data\mar1.rec > > write recfile RCD_DATE ID AREA SITENUM VISIT_DT HIV_TEST PREV_TST ST \ > > COUNTY DOB SEX RACE RV_KNOWN RV_HIV99 RV_HIVO > > > > read d:\data\mar1.rec > > sort id visit_dt > > route d:\data\mar1a.rec > > write recfile > > > > read d:\data\pr_samp2.rec > > define RV_STD _ > > RV_STD=referred > > define rv_oth _ > > rv_oth=otherr > > route d:\data\mar2.rec > > write recfile ID VISIT_DT RV_SYMP RV_ASYMP RV_F_UP RV_CONT RV_STD RV_OTH > > > > read d:\data\mar2.rec > > sort id visit_dt > > route d:\data\mar2a.rec > > write recfile > > > > read d:\data\pr_samp2.rec > > route d:\data\mar3.rec > > write recfile ID VISIT_DT RG_SXMAN RG_SXWMN RG_IDU RG_COKE RG_O_DRG \ > > RG_XDRG RG_SXIDU RG_SXHIV RG_SXMSM HX_STD > > > > read d:\data\mar3.rec > > sort id visit_dt > > route d:\data\mar3a.rec > > write recfile > > > > *RELATE ATTEMPT > > > > *read d:\data\mar1a.rec > > *relate id d:\data\mar2a.rec > > *route d:\data\marA.rec > > *write recfile > > > > *read d:\data\marA.rec > > *relate id d:\data\mar3a.rec > > *route d:\data\marB.rec > > *write recfile > > > > *MERGE ATTEMPT > > dos d:\epi6\merge d:\data\mar1a.rec d:\data\mar2a.rec d:\data\marA.rec 2 > > id > > visit_dt n > > dos d:\epi6\merge d:\data\marA.rec d:\data\mar3a.rec d:\data\marB.rec 2 > > id > > visit_dt n > > > > dos d:\epi6\export d:\data\martot.rec d:\data\martot.asc 2 > > > > Thanks, > > Rob Nelson > > Stephanie Bock > > > > > -----Original Message----- > > > From: Girald DAURAT [SMTP:gdaurat@CLUB-INTERNET.FR] > > > Sent: Wednesday, June 02, 1999 7:04 PM > > > To: EPI-INFO@LISTSERV.CDC.GOV > > > Subject: Re: [EPI-INFO] problems with merge/relate > > > > > > Nelson, Robert wrote: > > > > > > > > We are working with a 79 variable clinic visit database and would > like > > > to > > > > request your help in creating an "ASCII" output file. The data > entry > > > > screens reflect the medical record, while the output file must > conform > > > to a > > > > specific study format - therefore, a substantial amount of recoding > > and > > > > reordering of variables is necessary. > > > > The ID variable in the dataset is unique to the individual patient, > > but > > > > multiple visits are allowed. Therefore, ID is not necessarily > unique > > to > > > an > > > > individual record. When the following merge (join) is attempted > using > > > ID > > > > and date of visit, matching is unsucessful, and produces a final > file > > > with > > > > more records than anticipated (expecting 124, getting 425). > > > > We have also tried to use the relate command. While we were able to > > > keep > > > > the final number of records to 124, the variable visit date is > > repeated > > > at > > > > the beginning of each related block. > > > > Any suggestions? > > > > Thanks, > > > > Rob Nelson > > > > Stephanie Bock > > > > > > In order to answer you properly, I'd need some more information. > > > > > > Do you have 2 related files (one for individual patients and one for > > > visits) or only one with variables such as visit1 visit2 etc. (this is > > > not the better way)? > > > > > > Do you want to extract data from these files? (eventually after > > > proceeding some calculations) > > > Wich format do you want: ASCII delimited, ASCII fixed lenght..... > > > > > > May be you used the COMBINE command and got 425 records. This would > mean > > > there are 425 visits and 124 individuals. > > > > > > I suggest you send me a copy of the .qes and .pgm and .chk files if > you > > > can't answer these questions. > > > > > > G Daurat > > > > > > Montpellier > > > France > > > > ! > > > > ! > > > > ! > > > > ! > > > > ! > > > > ! ========================================================================= Date: Thu, 3 Jun 1999 15:37:32 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "C. Jon Hinkle" Subject: Re: problems with merge/relate Comments: cc: rxn1@CDC.gov Mime-Version: 1.0 Content-Type: text/plain If you are daring, you can use a text editor to cut & paste the header lines into the order you desire. Note that this is a dangerous practice. Start by opening your original recfile and selecting something that doesn't exist. SELECT ID = "ZZZ" (when ID is a number). Then route to a new recfile (Empty.rec) and WRITE RECFILE. This will create an empty recfile. (Likely there are other ways to accomplish this as well. For instance, you could open the recfile with a text editor, highlight the header but none of the data, and copy and paste the header into an new file called Empty.rec) You can then open the new recfile (Empty.rec) with your text editor and sort the order of the variables however you want them. Then merge the recfile with the extra variable (Extravar.rec) to the sorted recfile in the update mode. (Sorry, I never do this except from the DOS prompt so I don't know the steps from the menu.) The DOS command line is: MERGE Empty.rec Extravar.rec Corrected.rec 4 The resulting CORRECTED.REC will have the variables from your original recfile in the order you sorted them. It will appear on the screen to be identical to the original, but if you sorted the lines, the cursor will jump around as you enter data because the DATA (and the entry order) is now in the order of the sorted header. (Clear as mud?) Note that you don't need to do the sort trick if the original recfile is in the order you desire. You need only to write an empty recfile and then merge Extravar.rec to it. If Extravar.rec is in the correct order except for the extra variable, you can simply read it in analysis, route to a new recname, and WRITE RECFILE NOT EXTRAVAR (where extravar is the name of the extra variable). I stress again that hacking around on the header is a really great to screw up your database. ONLY DO IT TO A BACKUP COPY. NEVER, NEVER, NEVER TO THE ORIGINAL. (Sound like the voice of experience?) GLuk, C. Jon >>> "Nelson, Robert" 06/03 3:06 PM >>> Thanks for your reply. The problem lies with the output file specifications: it must have only the 78 study variables, and they must be in the correct order. I agree that creating a unique record ID would allow me to merge without problem. However, how would I remove this new variable from my final recfile? ! ========================================================================= Date: Fri, 4 Jun 1999 02:12:16 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: problems with merge/relate In-Reply-To: <0E21AA045067D211A2F300A02461F7A01E0A1F@mcdc-atl-51.cdc.gov > Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Write recfile has a "not" option, you can specify the variables you write or those you exclude. I have used it but not recently and can't remember exactly, but you can find it in the manual. Hope this helps, Leona Bassein Hospital Statistician in Italy At 16:06 03/06/99 -0400, you wrote: >Thanks for your reply. The problem lies with the output file >specifications: it must have only the 78 study variables, and they must be >in the correct order. I agree that creating a unique record ID would allow >me to merge without problem. However, how would I remove this new variable >from my final recfile? From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9905D" ========================================================================= Date: Sat, 22 May 1999 18:55:57 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Searching the Epi Info Discussion Group Archive Comments: cc: EPI Info Helpdesk MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" You can retrieve emails from previous discussions by searching the archives of the Epi-Info LSERVE. To do so, send an email to LISTSERV@LISTSERV.CDC.GOV with a SEACH message in the body of the message. Some sample search messages are (in capital letters): (1) Keyword Search: SEARCH 'ANALYSIS' IN EPI-INFO SINCE 97/01/01 (This command will search for emails since January 1, 1997 to the present containing the keyword "analysis". The Date must be in yy/mm/dd format.) (2) Subject Search: SEARCH * IN EPI-INFO WHERE SUBJECT CONTAINS 'EPITABLE' (This command will search for all emails where the subject or header contained the word EPITABLE. Note: The * sign designates all emails as opposed to restricting the search to a particular date or subject.) (3) Specific Sender Search: SEARCH * in EPI-INFO WHERE SENDER IS FARFAN (This command will find all emails where the sender's name was farfan.) (4) Broad Sender Search: SEARCH * IN EPI-INFO WHERE SENDER CONTAINS "SMITH" (This command will search for all emails sent to the listserve where the sender's name was smith or contained smith - goldsmith, or any name with smith would be included in the output). (5)Date Search: SEARCH * IN EPI-INFO SINCE 96/12/31 (This command will search for all emails sent to the listserve since December 31, 1996.) Also, try searching for the last 25 emails that were sent to the listserve (may not be as recent as this week). SEARCH * IN EPI-INFO.LAST25- For more information, there is a manual available at ftp://ftp.lsoft.com/documents/listdb.memo which helps users with various functions and options of the listserve. ========================================================================= Date: Sat, 22 May 1999 19:03:31 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Prefix on Subject Line of Epi Info LIST Messages Comments: cc: EPI Info Helpdesk MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" After many struggles, the LISTSERVer now attaches the prefix "Epi-Info" to messages from the Epi Info Discussion group. This provides a means of identifying the origin of the messages in case you prefer to save them to a separate folder (manually or automatically) or just bunch them up for later reading. Most email software provides a means of ordering messages by subject so that messages beginning with "Epi-Info" can be kept together. In Outlook, for example, clicking on the Subject column accomplishes this task. Let us know if you find this feature convenient. ========================================================================= Date: Sun, 23 May 1999 12:36:01 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: making a fast computer go slower Comments: cc: "Arner, Tom G." MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We intend to put the new versions on the web page, but are waiting for testing of DOMEAS, which may have a similar problem. We would also = like to produce a complete version 6.04c rather than 6.04b plus the "b-to-c" upgrade, but we need time or more hands, as Tom Arner, who puts = together all our release versions, is stretched in too many directions now with the installation program for Epi 2000 and the programming of the new Epi = Map. We hope to get to it before too long. -----Original Message----- From: Robert-Jean FREUND [mailto:rjfreund@ENSP.FR] Sent: Monday, May 03, 1999 3:40 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: making a fast computer go slower Importance: High Modified versions of both Epinut and Epitable have been released for beta tasting to a few of us ; I don't know if the tests are completed but it seems they work nicely on pentium 300 and 350Mhz we have perhaps Andy could tell us about releasing these versions on the CDC server ? Robert A 03:01 28/04/1999 -0400, vous avez =E9crit : >Hi everyone, > >I am enclosing the document file of the program that makes a fast computer >go slower (in case epinut or whatever doesn't work). It seems to be a >general problem, so I am sorry to disappoint anyone who might need the >program; it does not seem to be freeware, so I cannot send it to anyone >without breaching copyright, but perhaps you can find a version. > >However, I have heard that in this case the program does not work and that >the bug in epi info will be fixed in the next version. > >If all else fails you can try disabling the cache; this will make the >computer go slower and many programs (not all!!) will no longer terminate >in error. > >When I looked at this file it did not seem to have any macros, so if you >think it has any, please disable them or throw the file away. I think my >computer is virus-free, but you epidemiologists know there is always a >latency period and I don't like to send or receive doc files in this period. > >Please let me know how it all turns out! > >Leona Bassein >Attachment Converted: "C:\MESSAGE\Attach\MOSLO20.doc" > \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Mon, 24 May 1999 11:36:04 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Atrie, Jag" Subject: Re: Prefix on Subject Line of Epi Info LIST Messages Thank you for this feature. Yes, it is helpful. ________________________________ J Atrie Communicable Disease Control Health Department of Western Australia Telephone: (08) 9388 4844 Facsimile: (08) 9388 4848 E-Mail: jag.atrie@health.wa.gov.au ________________________________ ---------- From: Dean, Andrew G. [SMTP:agd1@CDC.GOV] Sent: Sunday, 23 May 1999 7:04 To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] Prefix on Subject Line of Epi Info LIST Messages After many struggles, the LISTSERVer now attaches the prefix "Epi-Info" to messages from the Epi Info Discussion group. This provides a means of identifying the origin of the messages in case you prefer to save them to a separate folder (manually or automatically) or just bunch them up for later reading. Most email software provides a means of ordering messages by subject so that messages beginning with "Epi-Info" can be kept together. In Outlook, for example, clicking on the Subject column accomplishes this task. Let us know if you find this feature convenient. ========================================================================= Date: Mon, 24 May 1999 09:57:43 +0200 Reply-To: burkowitz@t-online.de Sender: Epi Info Discussion Group From: Joerg Burkowitz Subject: Re: Prefix on Subject Line of Epi Info LIST Messages In-Reply-To: MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT For me it's unnecessary, cause my e-mail program (Pegasus) filters the mails on the basis of the "sender" or "to" fields and puts them in different mail-boxes. I think the prefix prevents the users from grasping the subjects at first sight. But this is maybe only my opinion. > After many struggles, the LISTSERVer now attaches the prefix "Epi-Info" to > messages from the Epi Info Discussion group. This provides a means of > identifying the origin of the messages in case you prefer to save them to a > separate folder (manually or automatically) or just bunch them up for later > reading. > > Most email software provides a means of ordering messages by subject so that > messages beginning with "Epi-Info" can be kept together. In Outlook, for > example, clicking on the Subject column accomplishes this task. > > Let us know if you find this feature convenient. Joerg Burkowitz PO-Box 1203, D-27296 Langwedel e-mail: burkowitz@t-online.de ========================================================================= Date: Mon, 24 May 1999 07:25:27 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "C. Jon Hinkle" Subject: Re: Prefix on Subject Line of Epi Info LIST Messages Mime-Version: 1.0 Content-Type: text/plain I must disagree with Mr. Burkowitz I use Pegasus at home and like it very much. However, I get my listserv messages at work, and they come to me via our network mail program, Groupwise. Placing the {EPI-INFO] in the subject makes it quite easy to write a rule to place all my epi list messages in their own folder. Thank you for this improvement. >>> Joerg Burkowitz 05/24 2:57 AM >>> For me it's unnecessary, cause my e-mail program (Pegasus) filters the mails on the basis of the "sender" or "to" fields and puts them in different mail-boxes. I think the prefix prevents the users from grasping the subjects at first sight. But this is maybe only my opinion. > After many struggles, the LISTSERVer now attaches the prefix "Epi-Info" to > messages from the Epi Info Discussion group. This provides a means of > identifying the origin of the messages in case you prefer to save them to a > separate folder (manually or automatically) or just bunch them up for later > reading. > > Most email software provides a means of ordering messages by subject so that > messages beginning with "Epi-Info" can be kept together. In Outlook, for > example, clicking on the Subject column accomplishes this task. > > Let us know if you find this feature convenient. Joerg Burkowitz PO-Box 1203, D-27296 Langwedel e-mail: burkowitz@t-online.de ! ========================================================================= Date: Mon, 24 May 1999 09:58:45 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: Prefix on Subject Line of Epi Info LIST Messages In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I see there are different opinions. I personally read almost all the Epi info mail immediately (the amount is not overwhelming as instead SAS-L is), and it keeps me company and is a welcome break from pressing problems. Even though I usually can tell from the subject that the message is relevant to epi info, I personally like the innovation, so if I'm in a hurry I can just file it and read it later. Variety is the spice of life (especially for statisticians/epidemiologists!). Many listservs have options so perhaps with a "set" command one could ask for the prefix or ask that it not be used. Probably, even if only 20% likes the prefix, and few dislike it violently, perhaps the solution (if set should not be possible) would be to keep it, because the marginal quality of life of the 20% who really use the option would be greater than the marginal quality of life lost by those who see it as an annoyance. Hope this helps. Leona Bassein Hospital Statistician in Bologna,Italy ======================= At 07:25 24/05/99 -0500, you wrote: >I must disagree with Mr. Burkowitz >I use Pegasus at home and like it very much. However, I get my listserv messages at work, and they come to me via our network mail program, Groupwise. Placing the {EPI-INFO] in the subject makes it quite easy to write a rule to place all my epi list messages in their own folder. > >Thank you for this improvement. > >>>> Joerg Burkowitz 05/24 2:57 AM >>> >For me it's unnecessary, cause my e-mail program (Pegasus) >filters the mails on the basis of the "sender" or "to" fields and puts >them in different mail-boxes. I think the prefix prevents the users >from grasping the subjects at first sight. But this is maybe only my >opinion. > > >> After many struggles, the LISTSERVer now attaches the prefix "Epi-Info" to >> messages from the Epi Info Discussion group. This provides a means of >> identifying the origin of the messages in case you prefer to save them to a >> separate folder (manually or automatically) or just bunch them up for later >> reading. >> >> Most email software provides a means of ordering messages by subject so that >> messages beginning with "Epi-Info" can be kept together. In Outlook, for >> example, clicking on the Subject column accomplishes this task. >> >> Let us know if you find this feature convenient. > > > >Joerg Burkowitz >PO-Box 1203, D-27296 Langwedel >e-mail: burkowitz@t-online.de > ! > > ========================================================================= Date: Mon, 24 May 1999 16:58:55 +0200 Reply-To: burkowitz@t-online.de Sender: Epi Info Discussion Group From: Joerg Burkowitz Subject: Re: Prefix on Subject Line of Epi Info LIST Messages In-Reply-To: <3.0.5.16.19990524144912.2ccf7d32@pop> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Absolutely right! > Probably, even if only 20% likes the prefix, and few dislike it violently, > perhaps the solution (if set should not be possible) would be to keep it, > because the marginal quality of life of the 20% who really use the option > would be greater than the marginal quality of life lost by those who see it > as an annoyance. > > Hope this helps. > > Leona Bassein > Hospital Statistician in Bologna,Italy > > ======================= > > At 07:25 24/05/99 -0500, you wrote: > >I must disagree with Mr. Burkowitz > >I use Pegasus at home and like it very much. However, I get my listserv > messages at work, and they come to me via our network mail program, > Groupwise. Placing the {EPI-INFO] in the subject makes it quite easy to > write a rule to place all my epi list messages in their own folder. > > > >Thank you for this improvement. > > > >>>> Joerg Burkowitz 05/24 2:57 AM >>> > >For me it's unnecessary, cause my e-mail program (Pegasus) > >filters the mails on the basis of the "sender" or "to" fields and puts > >them in different mail-boxes. I think the prefix prevents the users > >from grasping the subjects at first sight. But this is maybe only my > >opinion. > > > > > >> After many struggles, the LISTSERVer now attaches the prefix "Epi-Info" to > >> messages from the Epi Info Discussion group. This provides a means of > >> identifying the origin of the messages in case you prefer to save them to a > >> separate folder (manually or automatically) or just bunch them up for later > >> reading. > >> > >> Most email software provides a means of ordering messages by subject so > that > >> messages beginning with "Epi-Info" can be kept together. In Outlook, for > >> example, clicking on the Subject column accomplishes this task. > >> > >> Let us know if you find this feature convenient. > > > > > > > >Joerg Burkowitz > >PO-Box 1203, D-27296 Langwedel > >e-mail: burkowitz@t-online.de > > > > > > > > > > > > > > > ! > > > > Joerg Burkowitz PO-Box 1203, D-27296 Langwedel e-mail: burkowitz@t-online.de ========================================================================= Date: Fri, 28 May 1999 15:08:42 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: EPI 2000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We hope to release it within the next few months. A beta version is available on request if you would like to see what it is like. But the beta is not ready for field use. To request it, send email to epiinfo@cdc.gov and ask to be a beta tester. -----Original Message----- From: Alison Anderson [mailto:anderson@MOS.COM.NP] Sent: Tuesday, May 18, 1999 11:13 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] EPI 2000 Dear Colleagues Can anyone tell me when and where I will be able to get EPI 2000, and the minimum system requirements that it will need? Thanks Alison M Anderson Biostatistician INF RELEASE Project - POKHARA NEPAL anderson@mos.com.np From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9905C" ========================================================================= Date: Mon, 17 May 1999 10:53:51 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: EPIMAP In-Reply-To: <3.0.5.32.19990513163420.00940100@pophost.aber.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Dear Claudia, Sorry I can't help you, but I am curious how or why you plan to use the date in EPIMAP. Perhaps date of contagion? I've seen it used and it is a beautiful program. Leona Bassein ======== At 16:34 13/05/99 +0100, Claudia Aparecida Lima wrote: >Hello, > >I would like to know if any one can help me to use EPIMAP. I did an >epidemiological research(case-control study)and now I need to use the date >in EPIMAP. >Can anyone help me. >Thanks a lot. >Claudia. > > ========================================================================= Date: Sun, 16 May 1999 16:27:41 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Claudia Aparecida Lima Subject: Re: EPIMAP In-Reply-To: <3.0.5.16.19990517154619.2c5fbd2e@pop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Dear Leona, I'm PhD student and I want use GIS to show that there is association between bracken fern ingestion and cancer. I don't know yet how I have to do. In this moment I'm looking for someone that know about it. By for now. Claudia. At 10:53 17/05/99 -0400, you wrote: >Dear Claudia, > >Sorry I can't help you, but I am curious how or why you plan to use the >date in EPIMAP. Perhaps date of contagion? > >I've seen it used and it is a beautiful program. > >Leona Bassein >======== > >At 16:34 13/05/99 +0100, Claudia Aparecida Lima wrote: >>Hello, >> >>I would like to know if any one can help me to use EPIMAP. I did an >>epidemiological research(case-control study)and now I need to use the date >>in EPIMAP. >>Can anyone help me. >>Thanks a lot. >>Claudia. >> >> > > ========================================================================= Date: Mon, 17 May 1999 09:07:12 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Bailey, Gloria" Subject: Re: EPIMAP MIME-Version: 1.0 Content-Type: text/plain For those interested in GIS, there is an email discussion group -- WAPHGIS that started in Western Washington but now includes people from all over. send an email to listproc@u.washington.edu and write "subscribe WAPHGIS" They really aren't discussing EPIMAP though, but would be more experienced with general GIS techniques. EPIMAP specific questions are probably best answered right here in the EPI INFO discussion group. Gloria A. Bailey, Ph.D. Epidemiologist King County Mental Health Division Department of Community and Human Services Key Tower, 700 fifth Avenue, Suite 3800 Seattle, WA 98104-5038 206-205-1359 gloria.bailey@metrokc.gov > ---------- > From: Claudia Aparecida Lima[SMTP:cal97@ABER.AC.UK] > Reply To: Epi Info Discussion Group > Sent: Sunday, May 16, 1999 8:27 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: [EPI-INFO] EPIMAP > > Dear Leona, > > I'm PhD student and I want use GIS to show that there is association > between bracken fern ingestion and cancer. I don't know yet how I have to > do. In this moment I'm looking for someone that know about it. > By for now. > Claudia. > > At 10:53 17/05/99 -0400, you wrote: > >Dear Claudia, > > > >Sorry I can't help you, but I am curious how or why you plan to use the > >date in EPIMAP. Perhaps date of contagion? > > > >I've seen it used and it is a beautiful program. > > > >Leona Bassein > >======== > > > >At 16:34 13/05/99 +0100, Claudia Aparecida Lima wrote: > >>Hello, > >> > >>I would like to know if any one can help me to use EPIMAP. I did an > >>epidemiological research(case-control study)and now I need to use the > date > >>in EPIMAP. > >>Can anyone help me. > >>Thanks a lot. > >>Claudia. > >> > >> > > > > > ========================================================================= Date: Mon, 17 May 1999 16:23:35 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jose A. Farfan" Subject: reading previous messages Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear members of the discussion group: I would like to know if it is possible to read the previous messages sent to the group. In the EpiInfo page, it is presented the option. However, I have been trying unsuccessfully to get into the old messages. Please let me know how to do it. Jose A. Farfan Universidad Autonoma de Yucatan Mexico Dr. Jose Arturo Farfan Ale Centro de Investigaciones Regionales "Dr. Hideyo Noguchi" Universidad Aut=F3noma de Yucat=E1n Av. Itz=E1es por 59, num. 490 M=E9rida, Yucat=E1n, M=E9xico 97000 Tel: (99) 23-22-74 (99) 24-57-55 Fax: (99) 23-61-20 ========================================================================= Date: Tue, 18 May 1999 11:09:22 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Discussion Group Subject: Re: reading previous messages MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable You may retrieve archived emails by keyword, subject, sender, or date. = Use the following email address: LISTSERV@LISTSERV.CDC.GOV (1) Keyword Search: SEARCH 'ANALYSIS' IN EPI-INFO SINCE 97/01/01 (This command will search for emails since January 1, 1997 to the = present containing the keyword "analysis". The Date must be in yy/mm/dd = format.) (2) Subject Search: SEARCH * IN EPI-INFO WHERE SUBJECT CONTAINS = 'EPITABLE' (This command will search for all emails where the subject or header contained the word EPITABLE. Note: The * sign designates all emails = as opposed to restricting the search to a particular date or subject.) (3) (A) Specific Sender Search: SEARCH * in EPI-INFO WHERE SENDER = IS FARFAN (This command will find all emails where the sender's name was farfan.) (B) Broad Sender Search: SEARCH * IN EPI-INFO WHERE SENDER CONTAINS "SMITH" (This command will search for all emails sent to the listserve where = the sender's name was smith or contained smith - goldsmith, or any name = with smith would be included in the output). (4) Date Search: SEARCH * IN EPI-INFO SINCE 96/12/31 (This command will search for all emails sent to the listserve since December 31, 1996.) Also, try searching for the last 25 emails that were sent to the = listserve (may not be as recent as this week). SEARCH * IN EPI-INFO.LAST25- Hope this helps, Epi Info Support -----Original Message----- From: Jose A. Farfan [mailto:fale@TUNKU.UADY.MX] Sent: Monday, May 17, 1999 5:24 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] reading previous messages Dear members of the discussion group: I would like to know if it is possible to read the previous messages = sent to the group. In the EpiInfo page, it is presented the option. However, = I have been trying unsuccessfully to get into the old messages. Please = let me know how to do it. Jose A. Farfan Universidad Autonoma de Yucatan Mexico Dr. Jose Arturo Farfan Ale Centro de Investigaciones Regionales "Dr. Hideyo Noguchi" Universidad Aut=F3noma de Yucat=E1n Av. Itz=E1es por 59, num. 490 M=E9rida, Yucat=E1n, M=E9xico 97000 Tel: (99) 23-22-74 (99) 24-57-55 Fax: (99) 23-61-20 ========================================================================= Date: Wed, 19 May 1999 08:42:32 +0530 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Alison Anderson Subject: EPI 2000 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear Colleagues Can anyone tell me when and where I will be able to get EPI 2000, and the minimum system requirements that it will need? Thanks Alison M Anderson Biostatistician INF RELEASE Project - POKHARA NEPAL anderson@mos.com.np ========================================================================= Date: Wed, 19 May 1999 07:55:26 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Helpdesk Subject: Re: EPI 2000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Epi Info 2000 BETA Version Available A BETA version of Epi Info 2000 is available to a limited number of interested persons. Instructions are given below for downloading it by FTP, with a password. The BETA version is primarily for testing. It has many more features than the ALPHA version of September 98, but still lacks a few of the functions that the RELEASE versions will have. Please see the "GUIDED TOUR" from the main menu for an introduction to the system. A list of features not yet implemented is provided below. The following are required to run the BETA: 1. Windows 95, 98, or NT 2. A reasonably fast computer, with at least 32 meg of RAM The Microsoft Internet Explorer IS NO LONGER REQUIRED, as Epi Info provides a small, off-line browser. The BETA should not be relied upon for serious epidemiologic work, and should not be distributed to others for that purpose. To see the features of the system under development, install the BETA as recommended, and run the main menu, EPI2000.EXE. Click on the GUIDED TOUR button and then print the document that appears. The TOUR outlines the features that currently work. Please do not post the BETA or password on WWW sites or through other public channels, although we are making the password available through this e-mail. Out intention is to limit distribution of the BETA to those seriously interested in a first look at the Epi 2000 technology, but who can tolerate partial features and the bugs associated with development. Bug reports should be sent to epiinfo@cdc.gov. Since this is a BETA test, we are asking for bug reports, and a questionnaire is provided for this purpose via the button called BETA RESULTS on the main menu. The Epi Info HelpLine will receive comments about the system or resolve specific problems about installation, but cannot provide help in developing applications with the new system until it is released. Comments of a general nature or suggestions can be sent to Dr. Andy Dean at agd1@cdc.gov Instructions for Downloading the BETA Version of Epi Info 2000 (Realizing that it is incomplete and not ready for serious work) To download the Epi2000 BETA files you can use a Web browser like the Microsoft Internet Explorer or Netscape, or an FTP software package like WS_FTP or Rapid Filer. To use the Netscape or Internet Explorer browsers, click on the following address, which includes the password: ftp://epidemo:meds1998@sftp.cdc.gov/ftp/epidemo/pub/epi2000/ If this does not bring up your web browser, you can copy the address (URL) to the address window in the browser and press enter. As always, with the Internet, if the first attempt does not work, try again. This transmits the userid, the password, the ftp site, and the correct directory all in one line, and should bring up a list of 13 SETUP files that can be downloaded by clicking on one at a time. Be sure that they arrive on your system with the same names they have in the ftp site. (The Internet Explorer sometimes appends "(1)" or "(2)" to SETUP. Change the filenames back to SETUP when you are asked to designate the filename.) Netscape does not like the files with a .w0? extension. It will take you to a text editor screen when you try to download a .w0? file. Just click on "SAVE AS" (under the "FILE" menu) and click OK and Netscape will continue with the download. If you are using FTP software other than a browser, the information needed is: NAME: sftp.cdc.gov USERID: epidemo PASSWORD: meds1998 After the thirteen files are in a temporary directory on your hard disk or on thirteen diskettes, install the BETA system as follows: Installing Epi Info 2000 These instructions assume that the program called SETUP and the necessary files are either on diskettes or on your hard disk. From the STARTUP menu in Windows 95 or Windows NT, choose RUN and enter the location of your setup file and its name, as in "C:\TEMP\SETUP.EXE", or use the browse button on the RUN dialog to find and select the same file and then click OK. The password for installation is DEMOONLY After experimenting with the BETA, you will be able to UNINSTALL it by running the UNINSTAL.EXE program found in the same directory with Epi Info 2000. Running Epi Info 2000 After installation, use the Epi Info 2000 icon on the DESKTOP, the PROGRAMS menu under START, or the Windows Explorer to run EPI2000.EXE. Getting Acquainted When you see the menu of Epi Info 2000, click on the button called GUIDED TOUR. The GUIDED.HTM file that appears gives specific instructions for the most efficient way to get acqainted with the programs. We strongly recommend that you print the GUIDED TOUR document, using the PRINT button at the top of the screen, and then use the printed document as your guide through the system. Features not yet implemented 1. The CFREQ, CTABLES, and CMEANS statistics for complex samples 2. The ability to change field or variable names or data types after a data table has been created and data have been entered. 3. Access to ODBC databases 4. Analytic features for nutritional databases 5. A program for entering data from the screen for statistical calculations (like STATCALC from Epi Info for DOS) 6. Several features of Epi Map 7. Printing of questionnaires 8. A report generator for Analysis 9. Changes in the way Views are linked to data tables We hope that you enjoy testing the BETA version of Epi Info 2000, and look forward to receiving you detailed findings, either by email or by sending the database BETATEST.MDB file containing comments entered from the BETA RESULTS button on the main screen. -----Original Message----- From: Alison Anderson [mailto:anderson@MOS.COM.NP] Sent: Tuesday, May 18, 1999 11:13 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: [EPI-INFO] EPI 2000 Dear Colleagues Can anyone tell me when and where I will be able to get EPI 2000, and the minimum system requirements that it will need? Thanks Alison M Anderson Biostatistician INF RELEASE Project - POKHARA NEPAL anderson@mos.com.np ========================================================================= Date: Wed, 19 May 1999 10:32:16 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: EPI 2000 In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi everyone, I receive the message that Epi Info 2000 BETA Version is now Available >A BETA version of Epi Info 2000 is available to a limited number of >interested persons. Instructions are given below for downloading it by FTP, >with a password. Some time ago I read a message from some unfortunate beta tester who installed the beta version and really messed up his/her computer, because of dll's etc. Further back in time there was some discussion as to whether everything (including shared files like dll's) should reside in the epi2000 directory. I personally think the user should be given a choice, especially because epi2000 will be used all over the world (and different languages can mean different types of installations, not only because of translating but also way of functioning), Linux with windows emulator is making progress (I don't know how much, but it is a phenomenon that cannot be ignored) and also some Mac's can run some windows programs. From 13 installation disks, what would be the added volume of putting everything in the same directory? What are the current opitons and what do others think? Thank you very much. Leona Bassein Hospital statistician in Bologna (Italy) ========================================================================= Date: Thu, 20 May 1999 08:53:57 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Atrie, Jag" Subject: Re: EPI 2000 Comments: To: Leona Bassein From what I understand, the problem lies not with the team developing EpiInfo2000 but with the way MS Windows95/98 or NT operates. The OS apparently does not allow some system files to exist in a directory different to what is specified for the OS. Hence the dilemma. I believe that there is no easy solution. Regards, ________________________________ Jag Atrie Communicable Disease Control Health Department of Western Australia Telephone: (08) 9388 4844 Facsimile: (08) 9388 4848 E-Mail: jag.atrie@health.wa.gov.au ________________________________ ---------- From: Leona Bassein [SMTP:bassein@ORSOLA-MALPIGHI.MED.UNIBO.IT] Sent: Wednesday, 19 May 1999 22:32 To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: [EPI-INFO] EPI 2000 Hi everyone, I receive the message that Epi Info 2000 BETA Version is now Available >A BETA version of Epi Info 2000 is available to a limited number of >interested persons. Instructions are given below for downloading it by FTP, >with a password. Some time ago I read a message from some unfortunate beta tester who installed the beta version and really messed up his/her computer, because of dll's etc. Further back in time there was some discussion as to whether everything (including shared files like dll's) should reside in the epi2000 directory. I personally think the user should be given a choice, especially because epi2000 will be used all over the world (and different languages can mean different types of installations, not only because of translating but also way of functioning), Linux with windows emulator is making progress (I don't know how much, but it is a phenomenon that cannot be ignored) and also some Mac's can run some windows programs. From 13 installation disks, what would be the added volume of putting everything in the same directory? What are the current opitons and what do others think? Thank you very much. Leona Bassein Hospital statistician in Bologna (Italy) From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9905B" ========================================================================= Date: Mon, 10 May 1999 07:06:57 +0200 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Cism Subject: EPI-INFO in the Microsoft hell... Re: Epi Info 2000 BETA Version Available MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit First impressions after downloading, installing, and testing epi2000beta and more... I liked very much Epi5 and Epi6 for their good and strong design in perfect adequation with epidemiological work. Sorry to have to write this but Epi2000 transforms our good EPI6 in typical Microsoft freak : myriads of windows, lists, buttons which make the overall functional design completely opaque. If only all this new stuff was exactly the same as there counterparts in MS-Office, because everyone as to learn this suite and understand its bizarreness (Ah ! MS-Graph objets especially under a MS-Access form...), but NO its look like MS-Office but it's not the same so we have to relearn both Epi6 and Ms-Office ! I guess it's not your fault and by using Win9x, MS-Access file format, and VB you have to deal with the universally known poorness and stupidity of Microsoft designs. But the only problem of EPI6 was the DOS quality of the results output : why not simply write a good interface between EPI6 and MS-Office apps ? (control of EPI6 with automatic recuperation and formatting of its outputs from any of the MS-Office apps) ... and the rest : during the intall of EPI-INFO 2000 I was afraid of the lot of things transferred to windows\system and was right ! First reboot and EPI2000 test was OK. On second reboot my system (Win95 osr2.5, Office-dev with SRs installed) stopped with an error in a vxd in IOSUBSYS. Can't resolved the pb so reinstall Window but new stop on a NTKERN driver with a msg talking about system.ini etc. Can't solved this one too so must deltree c:\windows and reinstall it and all my apps... something about 7h... OK that's MS routine for lambda user but ... something more positive : the LIKE operator for expression matching is a very good addition to analysis. ========================================================================= Date: Mon, 10 May 1999 07:46:06 +0200 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Leona Bassein Subject: Re: EPI-INFO in the Microsoft hell... Re: Epi Info 2000 BETA Version Available In-Reply-To: <000e01be9aa2$f35d25a0$97d5a7c2@rppc> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 07:06 10/05/99 +0200, Cism wrote: >... and the rest : during the intall of EPI-INFO 2000 I was afraid of the >lot of things transferred to windows\system and was right ! First reboot and >EPI2000 test was OK. On second reboot my system (Win95 osr2.5, Office-dev >with SRs installed) stopped with an error in a vxd in IOSUBSYS. Can't >resolved the pb so reinstall Window but new stop on a NTKERN driver with a >msg talking about system.ini etc. Can't solved this one too so must deltree >c:\windows and reinstall it and all my apps... something about 7h... OK >that's MS routine for lambda user but ... Wasn't there some discussion during trial of the alpha version to allow users who wanted to, to put all the libraries etc. in the epi2000 directory? Would this be sufficient to avoid problems? Certainly there is something terribly wrong with the Microsoft environment if such nasty things happen during the installation of a program that uses *their* ACCESS, *their* Video Basic, etc. Perhaps the problem is with different languages? But of course they should have foreseen this too! Best of luck! Leona Bassein PS I use Star Office at home, and find it stimulating to see how it is different from MS office that I use at work, so I think I would not be bothered by the different interface Cism mentions. Also I do not think everyone necessarily uses MS Office. >Sorry to have to write this but Epi2000 >transforms our good EPI6 in typical Microsoft freak : myriads of >windows, lists, buttons which make the overall functional design completely >opaque. If only all this new stuff was exactly the same as there >counterparts in MS-Office, because everyone as to learn this suite and >understand its bizarreness (Ah ! MS-Graph objets especially under a >MS-Access form...), but NO its look like MS-Office but it's not the same so >we have to relearn both Epi6 and Ms-Office ! > ========================================================================= Date: Tue, 11 May 1999 12:00:27 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Ninan, Anil" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" This is a test ========================================================================= Date: Tue, 11 May 1999 14:58:59 EDT Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: e c groh thanx to all who helped with my previous question about setting up my questionaire. To be more specific , I am needing to set up questionaire which allows me record diagnosis, treatments, and compare them to pre and post test scores on a 32 item survey I have also incorporated into this questionaire. The scoring of the survey is done automatically as items are entered in enterx so all scores are already part of the rec file. What is the best way to set this up? e.c groh Fulton County Health and Wellness Behavioral Health Atlanta, USA ========================================================================= Date: Tue, 11 May 1999 17:21:12 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Setareh Williams Subject: Re: missing data In-Reply-To: <19990511.150359.6431.0.ecgroh@juno.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Hello, I have been entering my data in Epi-info and leaving the missing values blank. After looking at my data in SAS, I believe that perhaps I should code missing values and not leave them blank.Please let me know if there are specific procedures for entering missing data (i.e., in SAS we use a period for missing data). Thanks, Setareh Setareh Aria Williams PhD Student Epidemiology and Public Health Yale University 60 College Street New Haven CT 06430 ========================================================================= Date: Wed, 12 May 1999 16:12:36 +1100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Tom Kiedrzynski Subject: Re: Epi Info 2000 BETA Version Available MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I've been trying and trying for the last couple of days to access the site in order to download the software but it doesn't work... The message I get is : ERROR The requested URL could not be retrieved The following URL could not be retrieved: Squid sent the following FTP command: CWD ftp and then received this reply /d:/ftp/epidemo/pub/ftp: No such file or directory. This might be caused by an FTP URL with an absolute path (which does not comply with RFC 1738). If this is the cause, then the file can be found at . .... (I've tried the second address as well) So could anybody give me some hints? Thanks! Tom > _____________________________ > Dr Tom Kiedrzynski > Notifiable Disease Specialist - SPC > Ph.: (687) 26 20 00 > Fax: (687) 26 38 18 > e-mail: tomk@spc.org.nc > > ATTACHMENTS - Any attachments in this message > will be compressed in standard ZIP format. Use WINZIP or PKUNZIP to > decompress. > -----Original Message----- From: Dean, Andrew G. [mailto:agd1@CDC.GOV] Sent: 05 May 1999 08:05 To: EPI-INFO@LISTSERV.CDC.GOV Subject: Epi Info 2000 BETA Version Available Epi Info 2000 BETA Version Available A BETA version of Epi Info 2000 is available to a limited number of interested persons. Instructions are given below for downloading it by FTP, with a password. The BETA version is primarily for testing. It has many more features than the ALPHA version of September 98, but still lacks a few of the functions that the RELEASE versions will have. Please see the "GUIDED TOUR" from the main menu for an introduction to the system. A list of features not yet implemented is provided below. The following are required to run the BETA: 1. Windows 95, 98, or NT 2. A reasonably fast computer, with at least 32 meg of RAM The Microsoft Internet Explorer IS NO LONGER REQUIRED, as Epi Info provides a small, off-line browser. The BETA should not be relied upon for serious epidemiologic work, and should not be distributed to others for that purpose. To see the features of the system under development, install the BETA as recommended, and run the main menu, EPI2000.EXE. Click on the GUIDED TOUR button and then print the document that appears. The TOUR outlines the features that currently work. Please do not post the BETA or password on WWW sites or through other public channels, although we are making the password available through this e-mail. Out intention is to limit distribution of the BETA to those seriously interested in a first look at the Epi 2000 technology, but who can tolerate partial features and the bugs associated with development. Bug reports should be sent to epiinfo@cdc.gov . Since this is a BETA test, we are asking for bug reports, and a questionnaire is provided for this purpose via the button called BETA RESULTS on the main menu. The Epi Info HelpLine will receive comments about the system or resolve specific problems about installation, but cannot provide help in developing applications with the new system until it is released. Comments of a general nature or suggestions can be sent to Dr. Andy Dean at agd1@cdc.gov Instructions for Downloading the BETA Version of Epi Info 2000 (Realizing that it is incomplete and not ready for serious work) To download the Epi2000 BETA files you can use a Web browser like the Microsoft Internet Explorer or Netscape, or an FTP software package like WS_FTP or Rapid Filer. To use the Netscape or Internet Explorer browsers, click on the following address, which includes the password: ftp://epidemo:meds1998@sftp.cdc.gov/ftp/epidemo/pub/epi2000/ If this does not bring up your web browser, you can copy the address (URL) to the address window in the browser and press enter. As always, with the Internet, if the first attempt does not work, try again. This transmits the userid, the password, the ftp site, and the correct directory all in one line, and should bring up a list of 13 SETUP files that can be downloaded by clicking on one at a time. Be sure that they arrive on your system with the same names they have in the ftp site. (The Internet Explorer sometimes appends "(1)" or "(2)" to SETUP. Change the filenames back to SETUP when you are asked to designate the filename.) Netscape does not like the files with a .w0? extension. It will take you to a text editor screen when you try to download a .w0? file. Just click on "SAVE AS" (under the "FILE" menu) and click OK and Netscape will continue with the download. If you are using FTP software other than a browser, the information needed is: NAME: sftp.cdc.gov USERID: epidemo PASSWORD: meds1998 After the thirteen files are in a temporary directory on your hard disk or on thirteen diskettes, install the BETA system as follows: Installing Epi Info 2000 These instructions assume that the program called SETUP and the necessary files are either on diskettes or on your hard disk. From the STARTUP menu in Windows 95 or Windows NT, choose RUN and enter the location of your setup file and its name, as in "C:\TEMP\SETUP.EXE", or use the browse button on the RUN dialog to find and select the same file and then click OK. The password for installation is DEMOONLY After experimenting with the BETA, you will be able to UNINSTALL it by running the UNINSTAL.EXE program found in the same directory with Epi Info 2000. Running Epi Info 2000 After installation, use the Epi Info 2000 icon on the DESKTOP, the PROGRAMS menu under START, or the Windows Explorer to run EPI2000.EXE. Getting Acquainted When you see the menu of Epi Info 2000, click on the button called GUIDED TOUR. The GUIDED.HTM file that appears gives specific instructions for the most efficient way to get acqainted with the programs. We strongly recommend that you print the GUIDED TOUR document, using the PRINT button at the top of the screen, and then use the printed document as your guide through the system. Features not yet implemented 1. The CFREQ, CTABLES, and CMEANS statistics for complex samples 2. The ability to change field or variable names or data types after a data table has been created and data have been entered. 3. Access to ODBC databases 4. Analytic features for nutritional databases 5. A program for entering data from the screen for statistical calculations (like STATCALC from Epi Info for DOS) 6. Several features of Epi Map 7. Printing of questionnaires 8. A report generator for Analysis 9. Changes in the way Views are linked to data tables We hope that you enjoy testing the BETA version of Epi Info 2000, and look forward to receiving you detailed findings, either by email or by sending the database BETATEST.MDB file containing comments entered from the BETA RESULTS button on the main screen. ========================================================================= Date: Wed, 12 May 1999 00:14:26 -0600 Reply-To: "Donna L. Alden" Sender: EPI-INFO From: "Donna L. Alden" Organization: Alden Health Services Subject: Re: Epi Info 2000 BETA Version Available MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I had the same problems and I just entered the following information and downloaded them that way. ftp://sftp.cdc.gov/ftp/epidemo/pub/epi2000/ However the site is often busy and that is why you keep getting the Server Busy or Page Cannot be displayed or found messages. I did finally get on after a while, but it takes time. Try some time late at night or very early in the morning. Regards, Donna Alden ********************************************************************** Donna L. Alden, RN, BScNurs(Distinction), BSc, DipEH, CPHI(C), MSc(S) Infection Control and Epidemiology Consultant Edmonton, Alberta, Canada Email: dalden@ualberta.ca My Web Pages: The Public Health and Infectious Diseases Network http://www.ualberta.ca/~dalden/ Master's Student (Infectious Disease Epidemiology) at the University of Alberta, Faculty of Medicine, Department of Public Health Sciences ListMaster of Pubhealthnet - a list for public health professionals to network and post/view jobs in the public health field. To join, go to my web pages listed above and follow the instructions. ****************************************************************** ----- Original Message ----- From: Tom Kiedrzynski To: Sent: Tuesday, May 11, 1999 11:12 PM Subject: Re: Epi Info 2000 BETA Version Available > I've been trying and trying for the last couple of days to access the site > in order to download the software but it doesn't work... > > The message I get is : > > ERROR > The requested URL could not be retrieved > > The following URL could not be retrieved: > > Squid sent the following FTP command: > CWD ftp > and then received this reply > /d:/ftp/epidemo/pub/ftp: No such file or directory. > This might be caused by an FTP URL with an absolute path (which does not > comply with RFC 1738). If this is the cause, then the file can be found at > . > .... > > (I've tried the second address as well) > > So could anybody give me some hints? > > Thanks! > > Tom > > _____________________________ > > Dr Tom Kiedrzynski > > Notifiable Disease Specialist - SPC > > Ph.: (687) 26 20 00 > > Fax: (687) 26 38 18 > > e-mail: tomk@spc.org.nc > > > > ATTACHMENTS - Any attachments in this message > > will be compressed in standard ZIP format. Use WINZIP or PKUNZIP to > > decompress. > > > > > > > > -----Original Message----- > From: Dean, Andrew G. [mailto:agd1@CDC.GOV] > Sent: 05 May 1999 08:05 > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Epi Info 2000 BETA Version Available > > > Epi Info 2000 BETA Version Available > A BETA version of Epi Info 2000 is available to a limited number of > interested persons. Instructions are given below for downloading it by FTP, > with a password. > The BETA version is primarily for testing. It has many more > features than the ALPHA version of September 98, but still lacks a few of > the functions that the RELEASE versions will have. Please see the "GUIDED > TOUR" from the main menu for an introduction to the system. A list of > features not yet implemented is provided below. > The following are required to run the BETA: > 1. Windows 95, 98, or NT > 2. A reasonably fast computer, with at least 32 meg of > RAM > > The Microsoft Internet Explorer IS NO LONGER REQUIRED, as > Epi Info provides a small, off-line browser. > > The BETA should not be relied upon for serious epidemiologic work, > and should not be distributed to others for that purpose. To see the > features of the system under development, install the BETA as recommended, > and run the main menu, EPI2000.EXE. Click on the GUIDED TOUR button and > then print the document that appears. The TOUR outlines the features that > currently work. > Please do not post the BETA or password on WWW sites or through > other public channels, although we are making the password available through > this e-mail. Out intention is to limit distribution of the BETA to those > seriously interested in a first look at the Epi 2000 technology, but who can > tolerate partial features and the bugs associated with development. > Bug reports should be sent to epiinfo@cdc.gov > . Since this is a BETA test, we are asking for bug > reports, and a questionnaire is provided for this purpose via the button > called BETA RESULTS on the main menu. The Epi Info HelpLine will receive > comments about the system or resolve specific problems about installation, > but cannot provide help in developing applications with the new system until > it is released. Comments of a general nature or suggestions can be sent to > Dr. Andy Dean at agd1@cdc.gov > > Instructions for Downloading the BETA Version of Epi Info 2000 > (Realizing that it is incomplete and not ready for serious work) > To download the Epi2000 BETA files you can use a Web browser like > the Microsoft Internet Explorer or Netscape, or an FTP software package like > WS_FTP or Rapid Filer. To use the Netscape or Internet Explorer browsers, > click on the following address, which includes the password: > > ftp://epidemo:meds1998@sftp.cdc.gov/ftp/epidemo/pub/epi2000/ > > > If this does not bring up your web browser, you can > copy the address (URL) to the address window in the browser and press enter. > As always, with the Internet, if the first attempt does not work, try again. > > > > This transmits the userid, the password, the ftp site, and the > correct directory all in one line, and should bring up a list of 13 SETUP > files that can be downloaded by clicking on one at a time. Be sure that > they arrive on your system with the same names they have in the ftp site. > (The Internet Explorer sometimes appends "(1)" or "(2)" to SETUP. Change > the filenames back to SETUP when you are asked to designate the filename.) > Netscape does not like the files with a .w0? extension. It will take you to > a text editor screen when you try to download a .w0? file. Just click on > "SAVE AS" (under the "FILE" menu) and click OK and Netscape will continue > with the download. > If you are using FTP software other than a browser, the information > needed is: > NAME: sftp.cdc.gov > USERID: epidemo > PASSWORD: meds1998 > > After the thirteen files are in a temporary directory on your hard > disk or on thirteen diskettes, install the BETA system as follows: > > Installing Epi Info 2000 > These instructions assume that the program called SETUP and the > necessary files are either on diskettes or on your hard disk. > > From the STARTUP menu in Windows 95 or Windows NT, choose RUN and > enter the location of your setup file and its name, as in > "C:\TEMP\SETUP.EXE", or use the browse button on the RUN dialog to find and > select the same file and then click OK. The password for installation is > > DEMOONLY > > After experimenting with the BETA, you will be able to UNINSTALL it > by running the UNINSTAL.EXE program found in the same directory with Epi > Info 2000. > > > Running Epi Info 2000 > > After installation, use the Epi Info 2000 icon on the DESKTOP, the > PROGRAMS menu under START, or the Windows Explorer to run EPI2000.EXE. > > > Getting Acquainted > When you see the menu of Epi Info 2000, click on the button called > GUIDED TOUR. The GUIDED.HTM file that appears gives specific instructions > for the most efficient way to get acqainted with the programs. We strongly > recommend that you print the GUIDED TOUR document, using the PRINT button at > the top of the screen, and then use the printed document as your guide > through the system. > > Features not yet implemented > > 1. The CFREQ, CTABLES, and CMEANS statistics for complex > samples > > 2. The ability to change field or variable names or data types > after a data table has been created and data have been entered. > > 3. Access to ODBC databases > > 4. Analytic features for nutritional databases > > 5. A program for entering data from the screen for statistical > calculations (like STATCALC from Epi Info for DOS) > > 6. Several features of Epi Map > > 7. Printing of questionnaires > > 8. A report generator for Analysis > > 9. Changes in the way Views are linked to data tables > > > We hope that you enjoy testing the BETA version of Epi Info 2000, > and look forward to receiving you detailed findings, either by email or by > sending the database BETATEST.MDB file containing comments entered from the > BETA RESULTS button on the main screen. ========================================================================= Date: Wed, 12 May 1999 08:13:41 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Leona Bassein Subject: Re: missing data In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I think it depends on how you transport your data to SAS. I use DBMSCOPY and have not had any problems (except that epi6 accepts 10 character variable names and SAS uses up to 8 character names, so renaming might be necessary). Anyway alphanumeric and numeric missing data are coded differently for SAS and I think the period only works for numeric data. Be careful about going through db3 to transport data: blank and zero are the same for numeric db3 variables, and this vital distinction might get lost. Leona Bassein Hospital statistician in Italy =============== At 17:21 11/05/99 -0400, Setareh Williams wrote: >Hello, > >I have been entering my data in Epi-info and leaving the missing values >blank. After looking at my data in SAS, I believe that perhaps I should >code missing values and not leave them blank.Please let me know if there >are specific procedures for entering missing data (i.e., in SAS we use a >period for missing data). > >Thanks, > >Setareh > >Setareh Aria Williams >PhD Student >Epidemiology and Public Health >Yale University >60 College Street >New Haven CT 06430 > > ========================================================================= Date: Wed, 12 May 1999 09:53:04 -0500 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Richard Lasater Subject: Re: missing data Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable For the last 10 years or so I have employed the following convention in = entering the demographic info into epidemiological databases. For race & = sex and what have you 9 =3D unknown for age, 99 =3D unknown, This has worked well. One objection to 99 for unknown for age is=20 the predictable "What about cases 99 years old"? Well, and alas in ten years we have had no cases 99 years old. (I would = like to volunteer to be the first:-):-):-) ) In general not knowing a value for a field and using a code to indicate = that is better than leaving a field blank. Those coming behind you tend = to ask questions about blank fields. regards Richard Lasater St. of Tennessee Dpt Health Communicable Disease Division Surveillance Section >>> Setareh Williams 05/11/99 04:21PM >>> Hello, I have been entering my data in Epi-info and leaving the missing values blank. After looking at my data in SAS, I believe that perhaps I should code missing values and not leave them blank.Please let me know if there are specific procedures for entering missing data (i.e., in SAS we use a period for missing data). Thanks, Setareh Setareh Aria Williams PhD Student Epidemiology and Public Health Yale University 60 College Street New Haven CT 06430 ========================================================================= Date: Wed, 12 May 1999 09:59:58 -0500 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Richard Lasater Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable did I pass? >>> "Ninan, Anil" 05/11/99 11:00AM >>> This is a test ========================================================================= Date: Wed, 12 May 1999 13:26:48 +0100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Paul Collery Subject: epi-2000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Hi Could someone please tell me how to download epi-2000 thanks Paul Collery Vet. Res. Lab., Abbotstown, Dublin Ireland Phone 353-1-6072688; Fax 353-1-8213010; 353-1-6072604 ========================================================================= Date: Wed, 12 May 1999 11:17:55 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: EPI Info Helpdesk Subject: Re: epi-2000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Epi Info 2000 BETA Version Available A BETA version of Epi Info 2000 is available to a limited number of interested persons. Instructions are given below for downloading it by FTP, with a password. The BETA version is primarily for testing. It has many more features than the ALPHA version of September 98, but still lacks a few of the functions that the RELEASE versions will have. Please see the "GUIDED TOUR" from the main menu for an introduction to the system. A list of features not yet implemented is provided below. The following are required to run the BETA: 1. Windows 95, 98, or NT 2. A reasonably fast computer, with at least 32 meg of RAM The Microsoft Internet Explorer IS NO LONGER REQUIRED, as Epi Info provides a small, off-line browser. The BETA should not be relied upon for serious epidemiologic work, and should not be distributed to others for that purpose. To see the features of the system under development, install the BETA as recommended, and run the main menu, EPI2000.EXE. Click on the GUIDED TOUR button and then print the document that appears. The TOUR outlines the features that currently work. Please do not post the BETA or password on WWW sites or through other public channels, although we are making the password available through this e-mail. Out intention is to limit distribution of the BETA to those seriously interested in a first look at the Epi 2000 technology, but who can tolerate partial features and the bugs associated with development. Bug reports should be sent to epiinfo@cdc.gov. Since this is a BETA test, we are asking for bug reports, and a questionnaire is provided for this purpose via the button called BETA RESULTS on the main menu. The Epi Info HelpLine will receive comments about the system or resolve specific problems about installation, but cannot provide help in developing applications with the new system until it is released. Comments of a general nature or suggestions can be sent to Dr. Andy Dean at agd1@cdc.gov Instructions for Downloading the BETA Version of Epi Info 2000 (Realizing that it is incomplete and not ready for serious work) To download the Epi2000 BETA files you can use a Web browser like the Microsoft Internet Explorer or Netscape, or an FTP software package like WS_FTP or Rapid Filer. To use the Netscape or Internet Explorer browsers, click on the following address, which includes the password: ftp://epidemo:meds1998@sftp.cdc.gov/ftp/epidemo/pub/epi2000/ If this does not bring up your web browser, you can copy the address (URL) to the address window in the browser and press enter. As always, with the Internet, if the first attempt does not work, try again. This transmits the userid, the password, the ftp site, and the correct directory all in one line, and should bring up a list of 13 SETUP files that can be downloaded by clicking on one at a time. Be sure that they arrive on your system with the same names they have in the ftp site. (The Internet Explorer sometimes appends "(1)" or "(2)" to SETUP. Change the filenames back to SETUP when you are asked to designate the filename.) Netscape does not like the files with a .w0? extension. It will take you to a text editor screen when you try to download a .w0? file. Just click on "SAVE AS" (under the "FILE" menu) and click OK and Netscape will continue with the download. If you are using FTP software other than a browser, the information needed is: NAME: sftp.cdc.gov USERID: epidemo PASSWORD: meds1998 After the thirteen files are in a temporary directory on your hard disk or on thirteen diskettes, install the BETA system as follows: Installing Epi Info 2000 These instructions assume that the program called SETUP and the necessary files are either on diskettes or on your hard disk. From the STARTUP menu in Windows 95 or Windows NT, choose RUN and enter the location of your setup file and its name, as in "C:\TEMP\SETUP.EXE", or use the browse button on the RUN dialog to find and select the same file and then click OK. The password for installation is DEMOONLY After experimenting with the BETA, you will be able to UNINSTALL it by running the UNINSTAL.EXE program found in the same directory with Epi Info 2000. Running Epi Info 2000 After installation, use the Epi Info 2000 icon on the DESKTOP, the PROGRAMS menu under START, or the Windows Explorer to run EPI2000.EXE. Getting Acquainted When you see the menu of Epi Info 2000, click on the button called GUIDED TOUR. The GUIDED.HTM file that appears gives specific instructions for the most efficient way to get acqainted with the programs. We strongly recommend that you print the GUIDED TOUR document, using the PRINT button at the top of the screen, and then use the printed document as your guide through the system. Features not yet implemented 1. The CFREQ, CTABLES, and CMEANS statistics for complex samples 2. The ability to change field or variable names or data types after a data table has been created and data have been entered. 3. Access to ODBC databases 4. Analytic features for nutritional databases 5. A program for entering data from the screen for statistical calculations (like STATCALC from Epi Info for DOS) 6. Several features of Epi Map 7. Printing of questionnaires 8. A report generator for Analysis 9. Changes in the way Views are linked to data tables We hope that you enjoy testing the BETA version of Epi Info 2000, and look forward to receiving you detailed findings, either by email or by sending the database BETATEST.MDB file containing comments entered from the BETA RESULTS button on the main screen. -----Original Message----- From: Paul Collery [mailto:pcollery@INDIGO.IE] Sent: Wednesday, May 12, 1999 8:27 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: epi-2000 Hi Could someone please tell me how to download epi-2000 thanks Paul Collery Vet. Res. Lab., Abbotstown, Dublin Ireland Phone 353-1-6072688; Fax 353-1-8213010; 353-1-6072604 ========================================================================= Date: Thu, 13 May 1999 11:26:52 +0800 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Atrie, Jag" Subject: Different drop-down menus for the same variable Comments: To: "epiinfo@CDC.GOV" , "d.coulombier@rnsp-sante.fr" , "mark@MYATT.DEMON.CO.UK" , "gdaurat@club-internet.fr" , "JML@DADLNET.DK" , "greniej@CITENET.NET" , "bassein@ORSOLA-MALPIGHI.MED.UNIBO.IT" , "cdckms@SPH.EMORY.EDU" Hello everyone, I am having a little difficulty with coding a field "EXTRA" to allow disease-specific additional information. Here is what I would like to achieve. In the database (not a relational model), the two fields in question are DISEASE (2 digit integer field containing disease codes) and EXTRA (8-character alphanumeric field for disease-specific extra information). When someone enters say 54 (which stands for Chlamydia - genital) then the EXTRA field should be deactivated and the cursor should go to the next appropriate field. I am able to do this by using the HIDE command. But if the person enters say 28 (which stands for malaria) in the DISEASE field then I would like 1. to activate the EXTRA field (I can achieve this by using the UNHIDE command), and 2. to provide disease-specific drop-down menus with appropriate values (say 1 falciparum, 2 vivax, 3 ovale, 4 malariae, 5 mixed and 9 unknown). If the disease is Salmonella then I would like the drop-down menu to display only species of Salmonella and not Plasmodium. In other words, what I would like to achieve is to be able to provide different drop-down menus for the same variable "EXTRA" for different diseases. It is at this point that I seem to have a problem. Any ideas or suggestions? I am difficulty posting to the group as a whole and therefore in addition to my nth attempt at posting to the group I am also attempting to e-mail to specific people on the group. Thank you in advance. Regards, ________________________________ Jag Atrie Communicable Disease Control Health Department of Western Australia Telephone: (08) 9388 4844 Facsimile: (08) 9388 4848 E-Mail: jag.atrie@health.wa.gov.au ________________________________ ========================================================================= Date: Thu, 13 May 1999 09:10:54 +0200 Reply-To: Henriette Jansen Sender: EPI-INFO From: Henriette Jansen Subject: KEY UNIQUE command in CHECK file MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Dear all, I am new to this list, so I apologize if this problem has been discussed before. I am using EPIINFO version 6.04b to c upgrade. For a survey of children attended at health facilities I wanted to have a variable (with variablename UCODE) that would contain a unique identification number. This identification number would ensure that no duplicate records would be entered and it would be used to relate (link) different files during data entry. I have tried to do this as follows: During dataentry the health facility id-number (variable F1FID, a code, unique for each facility) as well as a child id-number (variable F1CHID, containing numbers 1-6 given in order of arrival) would be used to automatically calculate the value for UCODE (formula: F1FID*100+F1CHID). Below I have copied sections of the data entry (QES) file and the check file to show how this was done. The problem now is that this works most of the times but not always: thus in some occasions in which the value for UCODE is calculated we are getting an warning message indicating that the code is not unique, while it is! What are we doing wrong! Thanks in advance you for any suggestion! Henriette Jansen --- section of data entry (QES) file: ---- Name of facility {f1fid} ## {f1fname} Type of facility {f1ftype} # ID No. child {f1chid} ## {ucode} #### (fid+chid) ---- section of check file: ---- F1FID REPEAT MUSTENTER AutoJump F1FTYPE CODEFIELD F1FNAME CODES INCLUDE FACILIT.TXT END *refers to a file FACILIT.TXT that contains the numbers and names of health facilities END F1FNAME NOENTER REPEAT CODEFIELD F1FID END F1FTYPE REPEAT COMMENT LEGAL 1 HOSPITAL 2 "CENTRO DE SALUD" 3 "PUESTO DE SALUD" 8 OTRO 9 DESCONOCIDO END END F1CHID MUSTENTER END UCODE HELP "\N CALCULATED AUTOMATICALLY \N UCODE MUST BE UNIQUE \N PRESS ENTER TWICE \N" 15 15 KEY UNIQUE 1 LET UCODE = F1FID*100+F1CHID ENTER END ========================================================================= Date: Thu, 13 May 1999 09:33:06 +0100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Mark Myatt Subject: Re: Different drop-down menus for the same variable In-Reply-To: <3FD1ACEAC907D111A8750060B0097EEF5152E0@nt001bdcgvh.health.wa.gov.au> MIME-Version: 1.0 Jag, You write: >But if the person enters say 28 (which stands for malaria) in the DISEASE >field then I would like > >1. to activate the EXTRA field (I can achieve this by using the UNHIDE >command), and >2. to provide disease-specific drop-down menus with appropriate values (say >1 falciparum, 2 vivax, 3 ovale, 4 malariae, 5 mixed and 9 unknown). If the >disease is Salmonella then I would like the drop-down menu to display only >species of Salmonella and not Plasmodium. In other words, what I would like >to achieve is to be able to provide different drop-down menus for the same >variable "EXTRA" for different diseases. It is at this point that I seem to >have a problem. Any ideas or suggestions? > >I am difficulty posting to the group as a whole and therefore in addition to >my nth attempt at posting to the group I am also attempting to e-mail to >specific people on the group. I have had discussion with Andy Dean on adding this functionality to Epi2000 as I find it tricky in EpiInfo v6.xx and heirarchical coding systems / trees are the basis of many coding schemes (e.g. ICD). I have resorted to a kludge ... here is a CHECK code snippet that I have used in a surveillance system: IF GENUS = "SALMONELLA" THEN HELP " 1 Enteritidis, 2 Paratyphi, 3 Typhi, 4 Typhimurium, 5 Virchow " 8 11 KEYS="12345" IF RESULT = 1 THEN LET SPECIES = "ENTERITIDIS" GOTO TYPE ELSE IF RESULT = 2 THEN LET SPECIES = "PARATYPHI" GOTO TYPE ELSE IF RESULT = 3 THEN LET SPECIES = "TYPHI" GOTO TYPE ELSE IF RESULT = 4 THEN LET SPECIES = "TYPHIMURIUM" GOTO TYPE ELSE IF RESULT = 5 THEN LET SPECIES = "VIRCHOW" GOTO TYPE ENDIF ENDIF ENDIF ENDIF ENDIF ENDIF If it's not in the list then the user presses and can enter SPECIES directly. You would add HIDE and UNHIDE to all that. It's not elegant but it does work. If you'd like it, I can send you the .REC and .CHK files for the whole thing as it teems with fixes like this one. This system uses a 32.8 KB .CHK file and loads an 11 KB TSR program and runs OK on a standard 640KB PC with ENTER but anything larger would probably require ENTERx to make batter use of memory. Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Thu, 13 May 1999 09:37:55 +0100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Mark Myatt Subject: Re: KEY UNIQUE command in CHECK file Comments: To: Henriette Jansen In-Reply-To: <009301be9d0f$e6f77580$cfd879c3@heja> MIME-Version: 1.0 >I have tried to do this as follows: During dataentry the health facility >id-number (variable F1FID, a code, unique for each facility) as well as a >child id-number (variable F1CHID, containing numbers 1-6 given in order of >arrival) would be used to automatically calculate the value for UCODE >(formula: F1FID*100+F1CHID). Below I have copied sections of the data entry >(QES) file and the check file to show how this was done. > >The problem now is that this works most of the times but not always: thus in >some occasions in which the value for UCODE is calculated we are getting an >warning message indicating that the code is not unique, while it is! >What are we doing wrong! I think the problem might be the location of the commands to calculate the ID ... Here is some of my own code that works: LACODE REPEAT MUSTENTER COMMENT LEGAL 6021 "THE CITY" 6022 BARKING 6023 BARNET 6024 BEXLEY 6025 BRENT 6026 BROMLEY END BEFORE ENTRY LET SENDFILEID = LACODE + "-" + IDENT END AFTER ENTRY LET SENDFILEID = LACODE + "-" + IDENT END END SENDFILEID NOENTER KEY UNIQUE 1 END IDENT is an field in this case but could be an entered field. Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Thu, 13 May 1999 09:09:39 +0100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Mark Myatt Subject: Re: missing data In-Reply-To: MIME-Version: 1.0 Setareh Williams writes: >I have been entering my data in Epi-info and leaving the missing values >blank. After looking at my data in SAS, I believe that perhaps I should >code missing values and not leave them blank.Please let me know if there >are specific procedures for entering missing data (i.e., in SAS we use a >period for missing data). It all depends on the transport file format that you use to transfer data between EpiInfo and SAS. I use DBMS/Copy and missing values are handled as expected. If you use dBase you might find problems as empty defaults to zero in numeric fields. Mark -- Mark Myatt ========================================================================= Date: Thu, 13 May 1999 07:58:00 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Jung, Betty C." Subject: Re: missing data MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable FROM:Jung, Betty C. TO:EpiInfo Listserv CC:Jung, Betty C. SUBJECT:Re: missing data DATE: 05-13-1999 07:55 PRIORITY: ATTACHMENT: =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF Why don't you try and run a frequency after you do a set = ignoremissing=3Doff? This way, you will be able to get a count of all the empty variables. I think it's better to leave missing values empty.=20 Betty C. Jung=20 -------------------------------- FORWARDED FROM: Jung, Betty C. From: Setareh Williams To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: missing data Date: 1999-05-11 17:21 Priority: 3 Message ID: 07551049DB07D3118CEA00805FFEE00C -------------------------------------------------- Hello, I have been entering my data in Epi-info and leaving the missing values blank. After looking at my data in SAS, I believe that perhaps I should code missing values and not leave them blank.Please let me know if = there are specific procedures for entering missing data (i.e., in SAS we use = a period for missing data). Thanks, Setareh Setareh Aria Williams PhD Student Epidemiology and Public Health Yale University 60 College Street New Haven CT 06430 ========================================================================= Date: Thu, 13 May 1999 08:31:49 -0500 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "C. Jon Hinkle" Subject: Re: Different drop-down menus for the same variable Comments: To: Jag.Atrie@HEALTH.WA.GOV.AU Mime-Version: 1.0 Content-Type: text/plain I would suggest using the Jump command in your Check file to get to where you want to go, rather than hiding and unhiding the EXTRA field. For the drop downs, you might be able to use a series of recfiles that contained the legal entries in the EXTRA field and then access a different recfile for each different disease with IF/THEN statements in the check file. Here is one from my NETSS file. I use it to list s Salmonella, Shigella, and Meningococcal serotypes. The scheme with the numbers greater than 500 was to allow using CDC's serotype numbers. That is to say, Salmonella serotype 3 is Newport while Shigella type 3 is Sonnei. the seroname.rec file must be indexed on serotype and you can't have 2 identical entries. Therefore, I added 540 (who knows why such an odd number...) to the Shigella serotypes in the recfile and then remove it when it gets inserted. The SERONAME.REC file only has 2 fields, Serotype and seroname. Hitting F9 in the serotype field displays an alphabetical list of serotype names and accepting on the appropriate name inserts the cooresponding serotype. SEROTYPE COMMENT LEGAL SERONAME.REC define SERO ### GLOBAL IF SEROTYPE >500 AND SEROTYPE <600 THEN SERO=(SEROTYPE-540) ENDIF IF SEROTYPE >600 AND SEROTYPE <700 THEN SERO=(SEROTYPE-600) ENDIF IF SEROTYPE >700 AND SEROTYPE <800 THEN SERO=(SEROTYPE-700) ENDIF if serotype > 500 then let serotype = sero endif END Hope this helps. >>> "Atrie, Jag" 05/12 10:26 PM >>> Hello everyone, I am having a little difficulty with coding a field "EXTRA" to allow disease-specific additional information. Here is what I would like to achieve. ! ! ========================================================================= Date: Fri, 14 May 1999 09:29:21 +0800 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Atrie, Jag" Subject: Re: Different drop-down menus for the same variable Comments: To: Mark Myatt Thanks Mark for your, as usual, prompt reply. Actually that is the sort of code I currently use. The only snag with this coding is there is a limit of the number options you can allow the user to choose from. By pressing and allowing user to enter has a greater potentiality for data-entry errors (even with a manual handy!). Regards, Jag ________________________________ J Atrie Communicable Disease Control Health Department of Western Australia Telephone: (08) 9388 4844 Facsimile: (08) 9388 4848 E-Mail: jag.atrie@health.wa.gov.au ________________________________ ---------- From: Mark Myatt [SMTP:mark@MYATT.DEMON.CO.UK] Sent: Thursday, 13 May 1999 16:33 To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: Different drop-down menus for the same variable Jag, You write: >But if the person enters say 28 (which stands for malaria) in the DISEASE >field then I would like > >1. to activate the EXTRA field (I can achieve this by using the UNHIDE >command), and >2. to provide disease-specific drop-down menus with appropriate values (say >1 falciparum, 2 vivax, 3 ovale, 4 malariae, 5 mixed and 9 unknown). If the >disease is Salmonella then I would like the drop-down menu to display only >species of Salmonella and not Plasmodium. In other words, what I would like >to achieve is to be able to provide different drop-down menus for the same >variable "EXTRA" for different diseases. It is at this point that I seem to >have a problem. Any ideas or suggestions? > >I am difficulty posting to the group as a whole and therefore in addition to >my nth attempt at posting to the group I am also attempting to e-mail to >specific people on the group. I have had discussion with Andy Dean on adding this functionality to Epi2000 as I find it tricky in EpiInfo v6.xx and heirarchical coding systems / trees are the basis of many coding schemes (e.g. ICD). I have resorted to a kludge ... here is a CHECK code snippet that I have used in a surveillance system: IF GENUS = "SALMONELLA" THEN HELP " 1 Enteritidis, 2 Paratyphi, 3 Typhi, 4 Typhimurium, 5 Virchow " 8 11 KEYS="12345" IF RESULT = 1 THEN LET SPECIES = "ENTERITIDIS" GOTO TYPE ELSE IF RESULT = 2 THEN LET SPECIES = "PARATYPHI" GOTO TYPE ELSE IF RESULT = 3 THEN LET SPECIES = "TYPHI" GOTO TYPE ELSE IF RESULT = 4 THEN LET SPECIES = "TYPHIMURIUM" GOTO TYPE ELSE IF RESULT = 5 THEN LET SPECIES = "VIRCHOW" GOTO TYPE ENDIF ENDIF ENDIF ENDIF ENDIF ENDIF If it's not in the list then the user presses and can enter SPECIES directly. You would add HIDE and UNHIDE to all that. It's not elegant but it does work. If you'd like it, I can send you the .REC and .CHK files for the whole thing as it teems with fixes like this one. This system uses a 32.8 KB .CHK file and loads an 11 KB TSR program and runs OK on a standard 640KB PC with ENTER but anything larger would probably require ENTERx to make batter use of memory. Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Fri, 14 May 1999 08:56:48 +0800 Reply-To: "Suriah Bt Abdul Rahman (Dr.)" Sender: EPI-INFO From: "Suriah Bt Abdul Rahman (Dr.)" Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0033_01BE9DE7.B398E2E0" This is a multi-part message in MIME format. ------=_NextPart_000_0033_01BE9DE7.B398E2E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Sir, How do I withdraw myself from the epi-info discussion group. Thanks ------=_NextPart_000_0033_01BE9DE7.B398E2E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear Sir,
How do I withdraw myself from the = epi-info=20 discussion group.
Thanks
------=_NextPart_000_0033_01BE9DE7.B398E2E0-- ========================================================================= Date: Fri, 14 May 1999 09:20:33 +0100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Mark Myatt Subject: Re: Different drop-down menus for the same variable Comments: To: "Atrie, Jag" In-Reply-To: <3FD1ACEAC907D111A8750060B0097EEF5152E1@nt001bdcgvh.health.wa.gov.au> MIME-Version: 1.0 Atrie, Jag writes: >Thanks Mark for your, as usual, prompt reply. > >Actually that is the sort of code I currently use. The only snag with this >coding is there is a limit of the number options you can allow the user to >choose from. By pressing and allowing user to enter has a greater >potentiality for data-entry errors (even with a manual handy!). Make the target field NOENTER. Here is a longer portion of the .CHK file in which I do this ... It is tedious and limited though ... [ Section: 1/1 File: D_not.chk UUencoded by: Turnpike Version 4.00 ] sum -r/size 32897/46402 section (from "begin" to "end") sum -r/size 50883/33659 entire input file -- Mark Myatt ========================================================================= Date: Fri, 14 May 1999 17:03:51 +0800 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Atrie, Jag" Subject: Re: Different drop-down menus for the same variable Comments: To: Mark Myatt Thanks a million Mark. Just a thought. Are the number of characters one uses per option line (in the CHK file) limited to 256 characters? Regards, Jag ________________________________ J Atrie Communicable Disease Control Health Department of Western Australia Telephone: (08) 9388 4844 Facsimile: (08) 9388 4848 E-Mail: jag.atrie@health.wa.gov.au ________________________________ ---------- From: Mark Myatt [SMTP:mark@MYATT.DEMON.CO.UK] Sent: Friday, 14 May 1999 16:21 To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: Different drop-down menus for the same variable Make the target field NOENTER. Here is a longer portion of the .CHK file in which I do this ... It is tedious and limited though ... [ Section: 1/1 File: D_not.chk UUencoded by: Turnpike Version 4.00 ] begin 644 D_not.chk M4U523D%-10T*("!+15D@,@T*14Y$#0H-"DE$14Y4#0H@($M%62`T#0I%3D0- M"@T*1D]214Y!344-"B`@2T59(#,-"B`@05543U-%05)#2`T*14Y$#0H-"DQ! M0T]$10T*("!215!%050-"B`@35535$5.5$52#0H@($-/34U%3E0@3$5'04P- M"B`@("`V,#(Q(")42$4@0TE462(-"B`@("`V,#(R($)!4DM)3D<-"B`@("`V . . . -- Mark Myatt ========================================================================= Date: Fri, 14 May 1999 11:06:35 -0700 Reply-To: gdaurat@club-internet.fr Sender: EPI-INFO From: Gérald DAURAT Subject: Re: Different drop-down menus for the same variable Comments: To: "Atrie, Jag" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Atrie, Jag wrote: > > Hello everyone, > > I am having a little difficulty with coding a field "EXTRA" to allow > disease-specific additional information. Here is what I would like to > achieve. > > In the database (not a relational model), the two fields in question are > DISEASE (2 digit integer field containing disease codes) and EXTRA > (8-character alphanumeric field for disease-specific extra information). > > When someone enters say 54 (which stands for Chlamydia - genital) then the > EXTRA field should be deactivated and the cursor should go to the next > appropriate field. I am able to do this by using the HIDE command. > > But if the person enters say 28 (which stands for malaria) in the DISEASE > field then I would like > > 1. to activate the EXTRA field (I can achieve this by using the UNHIDE > command), and > 2. to provide disease-specific drop-down menus with appropriate values (say > 1 falciparum, 2 vivax, 3 ovale, 4 malariae, 5 mixed and 9 unknown). If the > disease is Salmonella then I would like the drop-down menu to display only > species of Salmonella and not Plasmodium. In other words, what I would like > to achieve is to be able to provide different drop-down menus for the same > variable "EXTRA" for different diseases. It is at this point that I seem to > have a problem. Any ideas or suggestions? > > I am difficulty posting to the group as a whole and therefore in addition to > my nth attempt at posting to the group I am also attempting to e-mail to > specific people on the group. > > Thank you in advance. > > Regards, > ________________________________ > Jag Atrie > Communicable Disease Control > Health Department of Western Australia > Telephone: (08) 9388 4844 > Facsimile: (08) 9388 4848 > E-Mail: > jag.atrie@health.wa.gov.au > ________________________________ Hello I tried to find some simple solution to your problem, such as a short CHECK program using include or define statements It did not work Now I suppose, only a limited number of deseases are under surveillance (let's say less than 25) The only working solution I found is - In REC file to make intermediary variables named d28 for malaria d55 for salmonella and so on Keep the ultimate EXTRA variable This is an example of DESEASE.QES DESEASE ## d28 d55 EXTRA ENDrec (endrec is a sample variable to allow you to add further variables and d28 d55 are same lengh and type as EXTRA) I only managed to write a heavy CHECK program. My proposal is. *content of DESEASE.CHK BEFORE RECORD HIDE EXTRA HIDE D28 HIDE D55 *don't forget other intermediate variables END DESEASE COMMENT LEGAL 27 TETANOS 28 MALARIA 54 CHLAMYDIA 55 SALMONELLA *don't forget other codes END Jumps 27 ENDREC 54 ENDREC **don't forget other codes END IF desease = 28 THEN UNHIDE EXTRA UNHIDE D28 GOTO D28 ENDIF IF desease = 55 THEN UNHIDE EXTRA UNHIDE D55 GOTO D55 ENDIF *don't forget other if statements for relevant codes END D28 LEGAL FALCIPAR VIVAX OVALE MALARIAE MIXED UNKNOWN END AFTER ENTRY LET EXTRA = d28 GOTO ENDREC END END D55 LEGAL "TYPHY MU" "GOLD COA" ENTERITI END AFTER ENTRY LET EXTRA = d55 GOTO ENDREC END END *don't forget other dxx variables EXTRA NOENTER END This has been once imagined by R J Freund (member of this mailing list) I tried it and it actually works on this example Of course this is only an example and you should implement both Desease.qes and Desease.chk to apply to your surveillance system NB: Do use EnterX (instead of Enter) to make sure your machine does go out of memory. Hope that helps Gérald Daurat Montpellier France ========================================================================= Date: Fri, 14 May 1999 11:57:42 +0100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Mark Myatt Subject: Re: Different drop-down menus for the same variable Comments: To: gdaurat@club-internet.fr In-Reply-To: <373C662B.4AD4@club-internet.fr> MIME-Version: 1.0 Grald DAURAT writes: This is rather clever. What you could also do is go into the .REC file header and set the XY co-ordinates for the hidden fields so they overlap and use TYPE COMMENT to place a prompt in front of the field when you unhide it. Mark > >I tried to find some simple solution to your problem, >such as a short CHECK program using include or define statements >It did not work > >Now I suppose, only a limited number of deseases are under surveillance >(let's say less than 25) > >The only working solution I found is > >- In REC file >to make intermediary variables named >d28 for malaria >d55 for salmonella >and so on > > >Keep the ultimate EXTRA variable > >This is an example of DESEASE.QES > >DESEASE ## d28 d55 >EXTRA >ENDrec > >(endrec is a sample variable to allow you to add further variables and >d28 d55 >are same lengh and type as EXTRA) > > >I only managed to write a heavy CHECK program. > >My proposal is. > >*content of DESEASE.CHK > >BEFORE RECORD > HIDE EXTRA > HIDE D28 > HIDE D55 >*don't forget other intermediate variables >END > >DESEASE > COMMENT LEGAL > 27 TETANOS > 28 MALARIA > 54 CHLAMYDIA > 55 SALMONELLA >*don't forget other codes > END > Jumps > 27 ENDREC > 54 ENDREC >**don't forget other codes > END > IF desease = 28 > THEN > UNHIDE EXTRA > UNHIDE D28 > GOTO D28 > ENDIF > IF desease = 55 > THEN > UNHIDE EXTRA > UNHIDE D55 > GOTO D55 > ENDIF >*don't forget other if statements for relevant codes >END > >D28 > LEGAL > FALCIPAR > VIVAX > OVALE > MALARIAE > MIXED > UNKNOWN > END > AFTER ENTRY > LET EXTRA = d28 > GOTO ENDREC > END >END > >D55 > LEGAL > "TYPHY MU" > "GOLD COA" > ENTERITI > END > AFTER ENTRY > LET EXTRA = d55 > GOTO ENDREC > END >END > >*don't forget other dxx variables > >EXTRA > NOENTER >END -- Mark Myatt ========================================================================= Date: Fri, 14 May 1999 11:53:52 +0100 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Mark Myatt Subject: Re: Different drop-down menus for the same variable In-Reply-To: <3FD1ACEAC907D111A8750060B0097EEF5152E6@nt001bdcgvh.health.wa.gov.au> MIME-Version: 1.0 Atrie, Jag writes: >Thanks a million Mark. Just a thought. Are the number of characters one >uses per option line (in the CHK file) limited to 256 characters? No idea, I think so. Why not try it? I am pretty sure the .CHK file is limited to 64K though. Mark -- Mark Myatt ========================================================================= Date: Thu, 13 May 1999 16:34:20 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Claudia Aparecida Lima Subject: EPIMAP Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hello, I would like to know if any one can help me to use EPIMAP. I did an epidemiological research(case-control study)and now I need to use the date in EPIMAP. Can anyone help me. Thanks a lot. Claudia. ========================================================================= Date: Fri, 14 May 1999 12:13:20 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Richard Lasater Subject: Re: EPIMAP Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Waht would you like to know? >>> Claudia Aparecida Lima 05/13/99 10:34AM >>> Hello, I would like to know if any one can help me to use EPIMAP. I did an epidemiological research(case-control study)and now I need to use the date in EPIMAP. Can anyone help me. Thanks a lot. Claudia. From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9905A" ========================================================================= Date: Fri, 30 Apr 1999 23:26:10 CDT Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Robert H. Hutcheson" Subject: Re: email address i don't understand from now on use my safe [?] but ok e mail address which is Elvis@Nashville.com commit it to memory yes it is a vanity e mail address but it is real abd cute On Mon, 26 Apr 1999 14:58:00 -0400 "Lasater, Richard" writes: >RlJPTTpMYXNhdGVyLCBSaWNoYXJkDQpUTzplcGlpbmZvIGxpc3QNCkNDOg0KU1VCSkVDVDplbWFp >bCBhZGRyZXNzIA0KUFJJT1JJVFk6DQoNCq+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+v >r6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr68NCkhvdyBkbyBJIGNo >YW5nZSBteSBlbWFpbCBhZHJlc3Mgb24gdGhpcyBsaXN0Lg0K > ========================================================================= Date: Sat, 1 May 1999 14:29:33 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Russell Rule Rycheck, M.D." Subject: Re: email address MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Richard, Your message are not readable - RRR ========================================================================= Date: Sat, 1 May 1999 14:52:16 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Russell Rule Rycheck, M.D." Subject: Re: email address MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Please, just explain to me what this e-imail address change is all about, and what is relates to. Thanks. RRR ========================================================================= Date: Sun, 2 May 1999 21:52:02 CDT Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Robert H. Hutcheson" Subject: Re: email address ok what is your new e-mail address ? mine is elvis@nadhville.com On Mon, 26 Apr 1999 14:58:00 -0400 "Lasater, Richard" writes: >RlJPTTpMYXNhdGVyLCBSaWNoYXJkDQpUTzplcGlpbmZvIGxpc3QNCkNDOg0KU1VCSkVDVDplbWFp >bCBhZGRyZXNzIA0KUFJJT1JJVFk6DQoNCq+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+v >r6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr68NCkhvdyBkbyBJIGNo >YW5nZSBteSBlbWFpbCBhZHJlc3Mgb24gdGhpcyBsaXN0Lg0K > ========================================================================= Date: Mon, 3 May 1999 09:39:51 +0200 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Robert-Jean FREUND Subject: Re: making a fast computer go slower Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Modified versions of both Epinut and Epitable have been released for beta tasting to a few of us ; I don't know if the tests are completed but it seems they work nicely on pentium 300 and 350Mhz we have perhaps Andy could tell us about releasing these versions on the CDC server= ? Robert A 03:01 28/04/1999 -0400, vous avez =E9crit : >Hi everyone, > >I am enclosing the document file of the program that makes a fast computer >go slower (in case epinut or whatever doesn't work). It seems to be a >general problem, so I am sorry to disappoint anyone who might need the >program; it does not seem to be freeware, so I cannot send it to anyone >without breaching copyright, but perhaps you can find a version. > >However, I have heard that in this case the program does not work and that >the bug in epi info will be fixed in the next version. > >If all else fails you can try disabling the cache; this will make the >computer go slower and many programs (not all!!) will no longer terminate >in error. > >When I looked at this file it did not seem to have any macros, so if you >think it has any, please disable them or throw the file away. I think my >computer is virus-free, but you epidemiologists know there is always a >latency period and I don't like to send or receive doc files in this= period. > >Please let me know how it all turns out! > >Leona Bassein >Attachment Converted: "C:\MESSAGE\Attach\MOSLO20.doc" > \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Mon, 3 May 1999 13:29:56 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Kaufmann, Rachel" Subject: Re: making a fast computer go slower MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Is it only Epinut and Epitable that have problems with the fast = machines, or are some of the other modules also problematic? > -----Original Message----- > From: Robert-Jean FREUND [SMTP:rjfreund@ENSP.FR] > Sent: Monday, May 03, 1999 3:40 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: making a fast computer go slower > Importance: High >=20 > Modified versions of both Epinut and Epitable have been released for = beta > tasting to a few of us ; I don't know if the tests are completed but = it > seems they work nicely on pentium 300 and 350Mhz we have >=20 > perhaps Andy could tell us about releasing these versions on the CDC > server ? >=20 >=20 > Robert >=20 >=20 >=20 > A 03:01 28/04/1999 -0400, vous avez =E9crit : > >Hi everyone, > > > >I am enclosing the document file of the program that makes a fast > computer > >go slower (in case epinut or whatever doesn't work). It seems to be = a > >general problem, so I am sorry to disappoint anyone who might need = the > >program; it does not seem to be freeware, so I cannot send it to = anyone > >without breaching copyright, but perhaps you can find a version. > > > >However, I have heard that in this case the program does not work = and > that > >the bug in epi info will be fixed in the next version. > > > >If all else fails you can try disabling the cache; this will make = the > >computer go slower and many programs (not all!!) will no longer = terminate > >in error. > > > >When I looked at this file it did not seem to have any macros, so if = you > >think it has any, please disable them or throw the file away. I = think my > >computer is virus-free, but you epidemiologists know there is always = a > >latency period and I don't like to send or receive doc files in this > period. > > > >Please let me know how it all turns out! > > > >Leona Bassein > >Attachment Converted: "C:\MESSAGE\Attach\MOSLO20.doc" > > > \\|// > (o o) > |-----------------o00o-(_)-o00o--------------------| > | Robert J.FREUND Epidemiologiste, Professeur | > | Ecole Nationale de la Sante Publique | > | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | > | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 > | rjfreund@ensp.fr http://www.ensp.fr | > |--------------------------------------------------| ========================================================================= Date: Tue, 4 May 1999 07:56:19 +0930 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: David Moore Subject: Re: making a fast computer go slower Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Robert, Does the modified version of epinut work when anthropometric calculations are called for within a rec file - on pentium 350mhz? David=20 At 09:39 AM 3/05/99 +0200, you wrote: >Modified versions of both Epinut and Epitable have been released for beta >tasting to a few of us ; I don't know if the tests are completed but it >seems they work nicely on pentium 300 and 350Mhz we have > >perhaps Andy could tell us about releasing these versions on the CDC server= ? > > >Robert > > > >A 03:01 28/04/1999 -0400, vous avez =E9crit : >>Hi everyone, >> >>I am enclosing the document file of the program that makes a fast computer >>go slower (in case epinut or whatever doesn't work). It seems to be a >>general problem, so I am sorry to disappoint anyone who might need the >>program; it does not seem to be freeware, so I cannot send it to anyone >>without breaching copyright, but perhaps you can find a version. >> >>However, I have heard that in this case the program does not work and that >>the bug in epi info will be fixed in the next version. >> >>If all else fails you can try disabling the cache; this will make the >>computer go slower and many programs (not all!!) will no longer terminate >>in error. >> >>When I looked at this file it did not seem to have any macros, so if you >>think it has any, please disable them or throw the file away. I think my >>computer is virus-free, but you epidemiologists know there is always a >>latency period and I don't like to send or receive doc files in this= period. >> >>Please let me know how it all turns out! >> >>Leona Bassein >>Attachment Converted: "C:\MESSAGE\Attach\MOSLO20.doc" >> > \\|// > (o o) >|-----------------o00o-(_)-o00o--------------------| >| Robert J.FREUND Epidemiologiste, Professeur | >| Ecole Nationale de la Sante Publique | >| Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | >| tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 >| rjfreund@ensp.fr http://www.ensp.fr | >|--------------------------------------------------| > > ========================================================================= Date: Tue, 4 May 1999 10:51:09 -0700 Reply-To: gdaurat@club-internet.fr Sender: EPI-INFO From: Gérald DAURAT Subject: Re: making a fast computer go slower MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kaufmann, Rachel wrote: > > Is it only Epinut and Epitable that have problems with the fast machines, or > are some of the other modules also problematic? > I didn't have any other problem with fast computers even when working on very large data files with millions of records. Import, merge enterx analysis check work very well. G Daurat Montpellier France ========================================================================= Date: Tue, 4 May 1999 08:43:00 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: EPI Info Discussion Group Subject: Re: making a fast computer go slower MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Only Epinut and epitable. -----Original Message----- From: Kaufmann, Rachel [mailto:rbk8@CDC.GOV] Sent: Monday, May 03, 1999 1:30 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: making a fast computer go slower Is it only Epinut and Epitable that have problems with the fast = machines, or are some of the other modules also problematic? > -----Original Message----- > From: Robert-Jean FREUND [SMTP:rjfreund@ENSP.FR] > Sent: Monday, May 03, 1999 3:40 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: making a fast computer go slower > Importance: High >=20 > Modified versions of both Epinut and Epitable have been released for = beta > tasting to a few of us ; I don't know if the tests are completed but = it > seems they work nicely on pentium 300 and 350Mhz we have >=20 > perhaps Andy could tell us about releasing these versions on the CDC > server ? >=20 >=20 > Robert >=20 >=20 >=20 > A 03:01 28/04/1999 -0400, vous avez =E9crit : > >Hi everyone, > > > >I am enclosing the document file of the program that makes a fast > computer > >go slower (in case epinut or whatever doesn't work). It seems to be = a > >general problem, so I am sorry to disappoint anyone who might need = the > >program; it does not seem to be freeware, so I cannot send it to = anyone > >without breaching copyright, but perhaps you can find a version. > > > >However, I have heard that in this case the program does not work = and > that > >the bug in epi info will be fixed in the next version. > > > >If all else fails you can try disabling the cache; this will make = the > >computer go slower and many programs (not all!!) will no longer = terminate > >in error. > > > >When I looked at this file it did not seem to have any macros, so if = you > >think it has any, please disable them or throw the file away. I = think my > >computer is virus-free, but you epidemiologists know there is always = a > >latency period and I don't like to send or receive doc files in this > period. > > > >Please let me know how it all turns out! > > > >Leona Bassein > >Attachment Converted: "C:\MESSAGE\Attach\MOSLO20.doc" > > > \\|// > (o o) > |-----------------o00o-(_)-o00o--------------------| > | Robert J.FREUND Epidemiologiste, Professeur | > | Ecole Nationale de la Sante Publique | > | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | > | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 > | rjfreund@ensp.fr http://www.ensp.fr | > |--------------------------------------------------| ========================================================================= Date: Tue, 4 May 1999 10:12:32 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Kaufmann, Rachel" Subject: Re: making a fast computer go slower MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Great. How can I get a copy of the modified .EXE files for fast = computers? > -----Original Message----- > From: EPI Info Discussion Group [SMTP:epiwww@CDC.GOV] > Sent: Tuesday, May 04, 1999 8:43 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: making a fast computer go slower >=20 > Only Epinut and epitable. >=20 > -----Original Message----- > From: Kaufmann, Rachel [mailto:rbk8@CDC.GOV] > Sent: Monday, May 03, 1999 1:30 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: making a fast computer go slower >=20 >=20 > Is it only Epinut and Epitable that have problems with the fast = machines, > or > are some of the other modules also problematic? >=20 > > -----Original Message----- > > From: Robert-Jean FREUND [SMTP:rjfreund@ENSP.FR] > > Sent: Monday, May 03, 1999 3:40 AM > > To: EPI-INFO@LISTSERV.CDC.GOV > > Subject: Re: making a fast computer go slower > > Importance: High > >=20 > > Modified versions of both Epinut and Epitable have been released = for > beta > > tasting to a few of us ; I don't know if the tests are completed = but it > > seems they work nicely on pentium 300 and 350Mhz we have > >=20 > > perhaps Andy could tell us about releasing these versions on the = CDC > > server ? > >=20 > >=20 > > Robert > >=20 > >=20 > >=20 > > A 03:01 28/04/1999 -0400, vous avez =E9crit : > > >Hi everyone, > > > > > >I am enclosing the document file of the program that makes a fast > > computer > > >go slower (in case epinut or whatever doesn't work). It seems to = be a > > >general problem, so I am sorry to disappoint anyone who might need = the > > >program; it does not seem to be freeware, so I cannot send it to = anyone > > >without breaching copyright, but perhaps you can find a version. > > > > > >However, I have heard that in this case the program does not work = and > > that > > >the bug in epi info will be fixed in the next version. > > > > > >If all else fails you can try disabling the cache; this will make = the > > >computer go slower and many programs (not all!!) will no longer > terminate > > >in error. > > > > > >When I looked at this file it did not seem to have any macros, so = if > you > > >think it has any, please disable them or throw the file away. I = think > my > > >computer is virus-free, but you epidemiologists know there is = always a > > >latency period and I don't like to send or receive doc files in = this > > period. > > > > > >Please let me know how it all turns out! > > > > > >Leona Bassein > > >Attachment Converted: "C:\MESSAGE\Attach\MOSLO20.doc" > > > > > \\|// > > (o o) > > |-----------------o00o-(_)-o00o--------------------| > > | Robert J.FREUND Epidemiologiste, Professeur | > > | Ecole Nationale de la Sante Publique | > > | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | > > | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 > > | rjfreund@ensp.fr http://www.ensp.fr | > > |--------------------------------------------------| ========================================================================= Date: Tue, 4 May 1999 10:17:20 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: EPI Info Helpdesk Subject: Re: making a fast computer go slower MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I will forward the .EXEfiles to you. Thanks Epi Info Technical Support -----Original Message----- From: Kaufmann, Rachel [mailto:rbk8@CDC.GOV] Sent: Tuesday, May 04, 1999 10:13 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: making a fast computer go slower Great. How can I get a copy of the modified .EXE files for fast = computers? > -----Original Message----- > From: EPI Info Discussion Group [SMTP:epiwww@CDC.GOV] > Sent: Tuesday, May 04, 1999 8:43 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: making a fast computer go slower >=20 > Only Epinut and epitable. >=20 > -----Original Message----- > From: Kaufmann, Rachel [mailto:rbk8@CDC.GOV] > Sent: Monday, May 03, 1999 1:30 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: making a fast computer go slower >=20 >=20 > Is it only Epinut and Epitable that have problems with the fast = machines, > or > are some of the other modules also problematic? >=20 > > -----Original Message----- > > From: Robert-Jean FREUND [SMTP:rjfreund@ENSP.FR] > > Sent: Monday, May 03, 1999 3:40 AM > > To: EPI-INFO@LISTSERV.CDC.GOV > > Subject: Re: making a fast computer go slower > > Importance: High > >=20 > > Modified versions of both Epinut and Epitable have been released = for > beta > > tasting to a few of us ; I don't know if the tests are completed = but it > > seems they work nicely on pentium 300 and 350Mhz we have > >=20 > > perhaps Andy could tell us about releasing these versions on the = CDC > > server ? > >=20 > >=20 > > Robert > >=20 > >=20 > >=20 > > A 03:01 28/04/1999 -0400, vous avez =E9crit : > > >Hi everyone, > > > > > >I am enclosing the document file of the program that makes a fast > > computer > > >go slower (in case epinut or whatever doesn't work). It seems to = be a > > >general problem, so I am sorry to disappoint anyone who might need = the > > >program; it does not seem to be freeware, so I cannot send it to = anyone > > >without breaching copyright, but perhaps you can find a version. > > > > > >However, I have heard that in this case the program does not work = and > > that > > >the bug in epi info will be fixed in the next version. > > > > > >If all else fails you can try disabling the cache; this will make = the > > >computer go slower and many programs (not all!!) will no longer > terminate > > >in error. > > > > > >When I looked at this file it did not seem to have any macros, so = if > you > > >think it has any, please disable them or throw the file away. I = think > my > > >computer is virus-free, but you epidemiologists know there is = always a > > >latency period and I don't like to send or receive doc files in = this > > period. > > > > > >Please let me know how it all turns out! > > > > > >Leona Bassein > > >Attachment Converted: "C:\MESSAGE\Attach\MOSLO20.doc" > > > > > \\|// > > (o o) > > |-----------------o00o-(_)-o00o--------------------| > > | Robert J.FREUND Epidemiologiste, Professeur | > > | Ecole Nationale de la Sante Publique | > > | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | > > | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 > > | rjfreund@ensp.fr http://www.ensp.fr | > > |--------------------------------------------------| ========================================================================= Date: Tue, 4 May 1999 17:52:54 +0200 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Vegard Hogli Subject: Problem with fast computer in Epi Map too In-Reply-To: <3.0.1.32.19990503093951.006b8dd0@newnetra.ensp.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I have noted the discussion on incompatibilities with fast computers and EpiNut. I have an application that writes maps from Epi Map to .PCX files. This won't work on my 300Mhz PII. - gets Runtime Error. My solution has been to do this particular job on an older and slower machine, but I am interested to know if any other has another solution? Vegard Hoegli ========================================================================= Date: Tue, 4 May 1999 17:05:04 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Dean, Andrew G." Subject: Epi Info 2000 BETA Version Available Comments: cc: EPI Info Helpdesk MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Epi Info 2000 BETA Version Available A BETA version of Epi Info 2000 is available to a limited number of interested persons. Instructions are given below for downloading it by FTP, with a password. The BETA version is primarily for testing. It has many more features than the ALPHA version of September 98, but still lacks a few of the functions that the RELEASE versions will have. Please see the "GUIDED TOUR" from the main menu for an introduction to the system. A list of features not yet implemented is provided below. The following are required to run the BETA: 1. Windows 95, 98, or NT 2. A reasonably fast computer, with at least 32 meg of RAM The Microsoft Internet Explorer IS NO LONGER REQUIRED, as Epi Info provides a small, off-line browser. The BETA should not be relied upon for serious epidemiologic work, and should not be distributed to others for that purpose. To see the features of the system under development, install the BETA as recommended, and run the main menu, EPI2000.EXE. Click on the GUIDED TOUR button and then print the document that appears. The TOUR outlines the features that currently work. Please do not post the BETA or password on WWW sites or through other public channels, although we are making the password available through this e-mail. Out intention is to limit distribution of the BETA to those seriously interested in a first look at the Epi 2000 technology, but who can tolerate partial features and the bugs associated with development. Bug reports should be sent to epiinfo@cdc.gov . Since this is a BETA test, we are asking for bug reports, and a questionnaire is provided for this purpose via the button called BETA RESULTS on the main menu. The Epi Info HelpLine will receive comments about the system or resolve specific problems about installation, but cannot provide help in developing applications with the new system until it is released. Comments of a general nature or suggestions can be sent to Dr. Andy Dean at agd1@cdc.gov Instructions for Downloading the BETA Version of Epi Info 2000 (Realizing that it is incomplete and not ready for serious work) To download the Epi2000 BETA files you can use a Web browser like the Microsoft Internet Explorer or Netscape, or an FTP software package like WS_FTP or Rapid Filer. To use the Netscape or Internet Explorer browsers, click on the following address, which includes the password: ftp://epidemo:meds1998@sftp.cdc.gov/ftp/epidemo/pub/epi2000/ If this does not bring up your web browser, you can copy the address (URL) to the address window in the browser and press enter. As always, with the Internet, if the first attempt does not work, try again. This transmits the userid, the password, the ftp site, and the correct directory all in one line, and should bring up a list of 13 SETUP files that can be downloaded by clicking on one at a time. Be sure that they arrive on your system with the same names they have in the ftp site. (The Internet Explorer sometimes appends "(1)" or "(2)" to SETUP. Change the filenames back to SETUP when you are asked to designate the filename.) Netscape does not like the files with a .w0? extension. It will take you to a text editor screen when you try to download a .w0? file. Just click on "SAVE AS" (under the "FILE" menu) and click OK and Netscape will continue with the download. If you are using FTP software other than a browser, the information needed is: NAME: sftp.cdc.gov USERID: epidemo PASSWORD: meds1998 After the thirteen files are in a temporary directory on your hard disk or on thirteen diskettes, install the BETA system as follows: Installing Epi Info 2000 These instructions assume that the program called SETUP and the necessary files are either on diskettes or on your hard disk. From the STARTUP menu in Windows 95 or Windows NT, choose RUN and enter the location of your setup file and its name, as in "C:\TEMP\SETUP.EXE", or use the browse button on the RUN dialog to find and select the same file and then click OK. The password for installation is DEMOONLY After experimenting with the BETA, you will be able to UNINSTALL it by running the UNINSTAL.EXE program found in the same directory with Epi Info 2000. Running Epi Info 2000 After installation, use the Epi Info 2000 icon on the DESKTOP, the PROGRAMS menu under START, or the Windows Explorer to run EPI2000.EXE. Getting Acquainted When you see the menu of Epi Info 2000, click on the button called GUIDED TOUR. The GUIDED.HTM file that appears gives specific instructions for the most efficient way to get acqainted with the programs. We strongly recommend that you print the GUIDED TOUR document, using the PRINT button at the top of the screen, and then use the printed document as your guide through the system. Features not yet implemented 1. The CFREQ, CTABLES, and CMEANS statistics for complex samples 2. The ability to change field or variable names or data types after a data table has been created and data have been entered. 3. Access to ODBC databases 4. Analytic features for nutritional databases 5. A program for entering data from the screen for statistical calculations (like STATCALC from Epi Info for DOS) 6. Several features of Epi Map 7. Printing of questionnaires 8. A report generator for Analysis 9. Changes in the way Views are linked to data tables We hope that you enjoy testing the BETA version of Epi Info 2000, and look forward to receiving you detailed findings, either by email or by sending the database BETATEST.MDB file containing comments entered from the BETA RESULTS button on the main screen. ========================================================================= Date: Wed, 5 May 1999 09:42:30 EDT Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: e c groh In my questionnaire, what is the best way to set up a section on "treatments". A patient may be provided multiple treatments concurrently and I want to be able to generate reports of these combinations of treatments. e.c groh Fulton County Health and Wellness Behavioral Health Atlanta, USA ========================================================================= Date: Wed, 5 May 1999 16:51:15 +0200 Reply-To: Moharram@Canada.com Sender: EPI-INFO From: Moharram Khalifa MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit you may put the possible answers as different variables with the answer is yes/no or better 1=yes 2=no for example treatment: {drug A}: # 1= yes, 2= no {drug B}: # 1= yes, 2= no {drug c}: # 1= yes, 2= no and so Moharram Khalifa Director of Training FETP, Egypt e c groh wrote: > In my questionnaire, what is the best way to set up a section on > "treatments". A patient may be provided multiple treatments concurrently > and I want to be able to generate reports of these combinations of > treatments. > > e.c groh > Fulton County Health and Wellness > Behavioral Health > Atlanta, USA ========================================================================= Date: Wed, 5 May 1999 10:15:39 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Leona Bassein In-Reply-To: <19990505.094713.9879.0.ecgroh@juno.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" It depends on how many kinds of treatments are available, and if you think a patient will get at least one. They must be codified and one to each variable or you will get misspelling. If many types are available, you might have to set up a relational data base with patient id, perhaps dates or similar and treatment code. A rec file would include treatments and codes. Another could contain patient demographics. Each treatment (with patient id, dates etc.) is a record in the treatment rec file. If few types are available you might simplify and name a variable for each treatment and do a logical (yes/no) format. This will waste space but if you want to analyze simultaneous occurrence you will probably save time. Hope this helps, Leona Bassein S.Orsola-Malpighi Community Teaching Hospital Bologna, Italy At 09:42 05/05/99 EDT, you wrote: >In my questionnaire, what is the best way to set up a section on >"treatments". A patient may be provided multiple treatments concurrently >and I want to be able to generate reports of these combinations of >treatments. > >e.c groh >Fulton County Health and Wellness >Behavioral Health >Atlanta, USA > > ========================================================================= Date: Fri, 7 May 1999 11:38:26 -0700 Reply-To: gdaurat@club-internet.fr Sender: EPI-INFO From: Gérald DAURAT MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit e c groh wrote: > > In my questionnaire, what is the best way to set up a section on > "treatments". A patient may be provided multiple treatments concurrently > and I want to be able to generate reports of these combinations of > treatments. > > e.c groh > Fulton County Health and Wellness > Behavioral Health > Atlanta, USA In fact you shouldn't mix two different statistical units in the same file, except on some very simple situations. The best way is probably to make a related file called treatmen.rec (for example) and to analyse this data file using the analysis RELATE command. See manual in chapter 25 for further details. This allows you to enter as many treatments as needed and to analyse the data file very easily. Hope that helps. Gérald DAURAT Montpellier France From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9904E" ========================================================================= Date: Wed, 28 Apr 1999 23:50:44 CDT Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Robert H. Hutcheson" Subject: Re: email address i don't understand plz repeat your msg which follows On Mon, 26 Apr 1999 14:58:00 -0400 "Lasater, Richard" writes: >RlJPTTpMYXNhdGVyLCBSaWNoYXJkDQpUTzplcGlpbmZvIGxpc3QNCkNDOg0KU1VCSkVDVDplbWFp >bCBhZGRyZXNzIA0KUFJJT1JJVFk6DQoNCq+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+v >r6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr68NCkhvdyBkbyBJIGNo >YW5nZSBteSBlbWFpbCBhZHJlc3Mgb24gdGhpcyBsaXN0Lg0K > ========================================================================= Date: Thu, 29 Apr 1999 13:19:03 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Dean, Andrew G." Subject: Re: email address MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" It doesn't make much sense to me. Andy -----Original Message----- From: Robert H. Hutcheson [mailto:rhhutchesonjr@JUNO.COM] Sent: Thursday, April 29, 1999 12:51 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: email address i don't understand plz repeat your msg which follows On Mon, 26 Apr 1999 14:58:00 -0400 "Lasater, Richard" writes: >RlJPTTpMYXNhdGVyLCBSaWNoYXJkDQpUTzplcGlpbmZvIGxpc3QNCkNDOg0KU1VCSkVDVDplbWF p >bCBhZGRyZXNzIA0KUFJJT1JJVFk6DQoNCq+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+ v >r6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr68NCkhvdyBkbyBJIGN o >YW5nZSBteSBlbWFpbCBhZHJlc3Mgb24gdGhpcyBsaXN0Lg0K > From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9904D" ========================================================================= Date: Thu, 22 Apr 1999 22:18:02 +0930 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: David Moore Subject: epinut and pentium 350hz Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Has any one had difficulty with Epinut working within a .rec file entered using the advised batch file to enter the .rec file for "automatic" anthropometric calculations WAP, WAZ, HAP, HAZ etc etc, when trying to use this on a pentium 350hz or greater? The auto fill anthropometric calculations are not made having entered height, weight and age in months. Apparantly there is a problem which occurs in pentiums with cpu speed greater than 200hz. Help desk sent me an updated epinut.exe which at least enables me to enter epinut from the main menu (thanks) but I still cannot "auto calculate" anthropometrics when entering various .rec files via the batch file as recommended. Has any one been able to sort out and remedy this problem? My only solution has been to work with a 486 IBM compatible PC, where the auto calculation works a treat. Regards David Moore Women's and Children's Hospital Adelaide South Australia ========================================================================= Date: Thu, 22 Apr 1999 09:29:12 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Leona Bassein Subject: Re: epinut and pentium 350hz Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" (I sent the files directly to the person I was answering. If people in the list wish and if it is legally possible to distribute them, I can send them to the list.) A friend of mine sent me these files, which slow down a fast computer to a speed you can choose. I am sending you them instead of to the list because I have not yet used them and have not checked: if they work if they are virus free if they are freeware, shareware or other. He said they worked better than my original method of disabling the cache, which makes everything very slow. If the programs work and are distributable and not too big, you might consider posting them to the list (I understand that many people do not wish to receive files; both com and doc could also contain viruses, although I hope they do not) or have the Help Desk put a link to them for download. Please let me know what you think. I have a pentium II at home and will eventually install them. Best of luck, Leona =========== At 22:18 22/04/99 +0930, you wrote: >Has any one had difficulty with Epinut working within a .rec file entered >using the advised batch file to enter the .rec file for "automatic" >anthropometric calculations WAP, WAZ, HAP, HAZ etc etc, when trying to use >this on a pentium 350hz or greater? > >The auto fill anthropometric calculations are not made having entered >height, weight and age in months. Apparantly there is a problem which >occurs in pentiums with cpu speed greater than 200hz. > >Help desk sent me an updated epinut.exe which at least enables me to enter >epinut from the main menu (thanks) but I still cannot "auto calculate" >anthropometrics when entering various .rec files via the batch file as >recommended. > >Has any one been able to sort out and remedy this problem? > >My only solution has been to work with a 486 IBM compatible PC, where the >auto calculation works a treat. > >Regards > >David Moore >Women's and Children's Hospital >Adelaide >South Australia > > ========================================================================= Date: Mon, 26 Apr 1999 14:58:00 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Lasater, Richard" Subject: email address MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 RlJPTTpMYXNhdGVyLCBSaWNoYXJkDQpUTzplcGlpbmZvIGxpc3QNCkNDOg0KU1VCSkVDVDplbWFp bCBhZGRyZXNzIA0KUFJJT1JJVFk6DQoNCq+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+v r6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr68NCkhvdyBkbyBJIGNo YW5nZSBteSBlbWFpbCBhZHJlc3Mgb24gdGhpcyBsaXN0Lg0K ========================================================================= Date: Mon, 26 Apr 1999 15:09:00 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Dean, Andrew G." Subject: Re: email address MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Unsubscribe from the old address. Subscribe from the new address. Otherwise, you may have to correspond with Natalie and Uliecia, who maintain the list, so that they can make a manual change in the List. = They are at Epiinfo@cdc.gov =20 Andy Dean -----Original Message----- From: Lasater, Richard [mailto:LASA100W@CDC.GOV] Sent: Monday, April 26, 1999 11:58 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: email address FROM:Lasater, Richard TO:epiinfo list CC: SUBJECT:email address=20 PRIORITY: =09 =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF How do I change my email adress on this list. ========================================================================= Date: Wed, 28 Apr 1999 03:01:38 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Leona Bassein Subject: making a fast computer go slower Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_925311420==_" --=====================_925311420==_ Content-Type: text/plain; charset="us-ascii" Hi everyone, I am enclosing the document file of the program that makes a fast computer go slower (in case epinut or whatever doesn't work). It seems to be a general problem, so I am sorry to disappoint anyone who might need the program; it does not seem to be freeware, so I cannot send it to anyone without breaching copyright, but perhaps you can find a version. However, I have heard that in this case the program does not work and that the bug in epi info will be fixed in the next version. If all else fails you can try disabling the cache; this will make the computer go slower and many programs (not all!!) will no longer terminate in error. When I looked at this file it did not seem to have any macros, so if you think it has any, please disable them or throw the file away. I think my computer is virus-free, but you epidemiologists know there is always a latency period and I don't like to send or receive doc files in this period. Please let me know how it all turns out! Leona Bassein --=====================_925311420==_ Content-Type: application/msword; charset="us-ascii" Content-Disposition: attachment; filename="MOSLO20.DOC" Mo'Slo Deluxe v2.0 from Dr.David's Super Crispy Software Copyright (c) David Perrell 1990,1993,1996 PLEASE READ THIS SOFTWARE LICENSE BEFORE INSTALLING MO'SLO DELUXE. ======================== SOFTWARE LICENSE =========================== The Mo'Slo Deluxe software program (subsequently referred to as the Software) is owned by David Perrell and is protected by United States copyright laws and related international treaty provisions. License to use the software is granted under the following terms and conditions: 1. License is granted to use one copy of the Software on a single terminal or workstation of a single computer so long as all of the terms and conditions of this agreement are complied with. 2. You may either (a) make one backup copy of the Software for archival purposes or (b) transfer the Software onto one hard disk, keeping the original disk for archival purposes. You may not otherwise copy or distribute the Software or the accompanying documentation in any way. 3. You may not make, or have made by another, any modification to the Software or its accompanying documentation. You may not adapt, translate, reverse engineer, disassemble, or create derivative works based on the Software. 4. You may transfer the Software to another party PROVIDED (a) you retain no copies of the Software or its documentation, (b) the Software and documentation are transferred solely as the unaltered diskette upon which they were purchased, and (c) the recipient agrees to the terms of this License Agreement. Use of the Software implies agreement. If you do not agree to comply with these terms and conditions, return the Software to the place of purchase for a full refund and delete any copies you may have made. ===================== DISCLAIMER OF WARRANTY ======================== Mo'Slo Deluxe is provided without warranty of any kind, express or implied, and the user assumes the entire risk of using it. The author will not be liable for any incidental, consequential, indirect or similar damages resulting from the use of this software. In no event will the author's liability ever exceed the price paid for the license to use the software, regardless of the nature of the claim. ======================= TECHNICAL SUPPORT =========================== VOICE OR FAX: 1-818-884-7157 EMAIL: davidp@earthlink.net IBM PC, XT are trademarks of International Business Machines MS DOS is a trademark of Microsoft Corporation MO'SLO DELUXE PAGE 2 of 3 ============== INSTALLING AND USING MO'SLO DELUXE =================== To install, simply copy MOSLO.COM and MOSLO.DOC to a drive and directory listed in your system's environment PATH statement. To see which directories are in your PATH statement, simply enter "PATH" (without the quotes) on the DOS command line. Mo'Slo Deluxe lets you to slow the speed of your computer from 0.1-99.9% of normal in 0.1% increments. To use it, you supply the name of the program or batch file you want to run slow as a commandline argument. Slowness is adjusted with a command line switch. If a % switch is not supplied, Mo'Slo Deluxe slows your computer to approximate a 4.77MHz PC/XT. If you do not provide the filename extension (COM, EXE, or BAT), Mo'Slo Deluxe first looks for a matching COM file, then an EXE file, then a BAT file in that order. Since many games use other files to keep high scores, background bitmaps, etc., it's best to switch to the directory in which the game resides before running it. You can include commandline arguments to the program being called. To run pcgame.exe at IBM PC/XT speed, enter: moslo pcgame.exe To run at 8% normal speed, enter: moslo /8 pcgame.exe When you exit pcgame, you'll exit Mo'Slo, and normal speed will be restored. Mo'Slo doesn't stay resident in memory and it doesn't alter the system clock. Running Mo'Slo Deluxe without any argument displays instructions. Mo'Slo Deluxe runs under PC/MS-DOS versions 2.0 and higher. MO'SLO DELUXE PAGE 3 of 3 Other utilities from Dr.David's Super Crispy Software: Dr.David's DOS Utilities package -- includes nine programs: REND2 -- Rename and/or move files and directories anywhere, combine multi-level paths into one directory, move large directory structures onto multiple floppy disks, move by date (before and after), archive (on or off), file by file prompt, plus additional options. DCOPY -- Like REND2 but copies instead of moves. Faster, more compact and with more options than XCOPY. DED -- Delete files or entire directories with one command. Delete matching files throughout a subdirectory path. Date & attribute filters, confirmation & zero-overwrite options, and more. CATT -- Change file attributes or find files based on current attributes and/or date range in one directory or complete paths. Hide directories. Show file names, attributes, number of matching files and combined size. GO -- Give often-used pathnames descriptive names of up to 63 characters. Transfer to named subdirectories quickly, without changing default drive manually. For names not in its list, GO works like DOS's Change Directory command. Waitfor -- Multi-purpose batch file utility. Read keystrokes, set alarms, run programs or reboot at specified intervals, build batch file menu systems and more. KBSET -- Use in your AUTOEXEC or other batch file to set keyboard typematic rates and turn the NumLock switch on/off. MPATH -- Changes the default path (including drive). If the specified subdirectory path doesn't exist, MPATH creates it. AutoPark -- Auto-park read-write heads on up to 8 hard drives at user-defined intervals. Less than 500 bytes TSR. For older MFM and RLL drives that do not self-park. PostScript utilities for desktop publishers and service bureaus: PSqueezer(tm) -- reduces size of PostScript files containing downloaded fonts 90% and more. PSqueezed files can print more than 67% faster. PS*x(tm) Professional -- extracts any combination of pages and/or spot color overlays from multi-page and/or multi-color PostScript files. Dr.David's DOS Utilities are available from the reseller from whom you purchased Mo'Slo. PostScript utilities are available directly from Dr.David's Software, prepaid w/chk or MO (both for $99 +$5 shipping/handling. +sales tax in CA). --=====================_925311420==_-- ========================================================================= Date: Wed, 28 Apr 1999 11:58:11 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Russell Rule Rycheck, M.D." Subject: Re: email address MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII I cannot read your message. RRR From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9904B" ========================================================================= Date: Thu, 8 Apr 1999 08:45:58 -0500 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "C. Jon Hinkle" Subject: Re: Recoding a variable Mime-Version: 1.0 Content-Type: text/plain I originally replied to Franck Golliot with a copy to the listserv from an account I maintain as a spam trap. Since it was not the account I used to subscribe my reply was rejected. Here it is for anyone else who cares: Note that since that time Mr. Golliot has told me of a much simpler solution submitted to him that involves splitting the replace test in to segments and then replacing them directly instead of writing them to variables first. Given that simpler is usually better, that gets my vote. >>>from C. Jon Hinkle 4/7/99 9:04 AM<<< >>> Franck Golliot 04/07 8:15 AM >>> >Hi everyone, >I have a problem in recoding a numeric variable to a 80 characters >snip< I had a similar problem using IF/THEN statements to replace string variables. The replacement strings were truncated at 25 characters. The solution I used was to pull the entire .RECfile into dBASE and use dBASE's replace function. This is not a very elegant solution. It occurs to me as I write this that you might be able to define 4 new variables (V1, V2, V3, V4) and put 1/4th of the final string into each variable. Then you could re-combine the strings. ****let v1 = "ecouvillonnage des c"**** ****let v2 = "anaux avec un deterg"**** ****let v3 = "ent ou un detergent/"**** ****let v4 = "desinfectant"**** **** If etp1=5 then let etpA1=V1+V2+V3+V4**** I tried this and it seems to work. Note that you should define the variables to be exactly as long as the strings you are putting in them to eliminate extraneous spaces. (Or I think you could use the TRIM function to do this) Be sure to include the spaces you want to be there. ****Let etpA1= trim(v1)+trim(v2) etc.*** I didn't try this, but it should work. ! ! From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9904A" ========================================================================= Date: Mon, 5 Apr 1999 09:15:10 +0200 Reply-To: =?iso-8859-1?Q?F=E9lix_NJEUMI?= Sender: EPI-INFO From: =?iso-8859-1?Q?F=E9lix_NJEUMI?= Subject: R: Information MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Dear all, Does anyone know some books o publication about: "Multistage sampling" ? Thanks you. Dr. NJEUMI FELIX PhD student in Epidemiology and Zoonose control Bologne Facolty of Veterinary ITALY Tel/fax: 0039.0521.289102 E-mail: fnjeumi@ntt.it ========================================================================= Date: Mon, 5 Apr 1999 12:31:16 -0300 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Enrique Finetti Subject: I still here Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I not received any mensages in last two weeks i still are in this list? Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Mon, 5 Apr 1999 12:38:04 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "Maldonado, Mr. Omar" Subject: Re: I still here MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Enrique, que bueno saber que no soy el =FAnico que dudaba de esto. Omar Maldonado A. Consultor Sistemas de Informaci=F3n OPS - OMS Chile -----Mensaje original----- De: Enrique Finetti [mailto:sapsalta@UNSA.EDU.AR] Enviado el: Lunes 5 de Abril de 1999 11:31 AM Para: EPI-INFO@LISTSERV.CDC.GOV Asunto: I still here I not received any mensages in last two weeks i still are in this list? Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Mon, 5 Apr 1999 14:21:46 -0400 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: "B. Gerstman" Subject: R: Information Comments: To: =?iso-8859-1?Q?F=E9lix_NJEUMI?= MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Sir: Books containing instruction on complex random sampling methods, such as two-stage sampling, include: Cochran, W. G. (1977). Sampling Techniques (3rd ed.). New York: John Wile= y & Sons. = Snedcor & Cochran. (1967). Statistical Methods (6th ed.). Ames, Iowa: Iow= a State University Press. Chapter 17. B. Gerstman San Jose, CA, USA > Message text written by Dr. NJEUMI FELIX > Dear all, Does anyone know some books o publication about: "Multista= ge sampling" ? Thanks you. ========================================================================= Date: Mon, 5 Apr 1999 14:29:42 -0500 Reply-To: Epi Info Discussion Group Sender: EPI-INFO From: Diana Echenique Subject: Re: I still here Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Isn't it wonderful, just the meat...don't worry, you are still part of the = list. ========================================================================= Date: Wed, 7 Apr 1999 15:15:09 +0200 Reply-To: golliot@ext.jussieu.fr Sender: EPI-INFO From: Franck Golliot Organization: CCLIN Paris-Nord Subject: recoding a variable MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi everyone, I have a problem in recoding a numeric variable to a 80 characters variable. My problem is that the program cut the string at 25 characters. This may sound trivial, but can some one tell me what the problem is ? ****If etp1=5 then etpA1= "ecouvillonnage des canaux avec un detergent ou un detergent/desinfectant"****** -- Franck GOLLIOT ========================================================================= Date: Wed, 7 Apr 1999 17:17:31 +0200 Reply-To: "d.coulombier@rnsp-sante.fr" Sender: EPI-INFO From: COULOMBIER Denis Organization: RNSP Subject: Re: recoding a variable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable A defined variable in ANALYSIS cannot exceed 25 characters. However, to = recode=20 your variable, you would gratly benefit from using a related table in = which you=20 would not have the 25 character limitation. Make a new ETP1.QES file, including a field for your code ETP1 (same = name and=20 field type as in your original file), and a string field called LABEL, = which=20 can be up to 80 characters in length. Enter each occurence of the code and the corresponding label in the = ETP1.REC=20 file In analysis (of your original file), use RELATE ETP1 ETP1 to get the = codes And use a FREQ EPT1.LABEL command to see the output. This will run much faster than recoding through IF, wil remove the = limitation=20 of 80 character, and is a good principle of normalization of databases. Denis Coulombier d.coulombier@rnsp-sante.fr tel : 33 1 41 79 67 81 -----Message d'origine----- De: Franck Golliot [SMTP:golliot@EXT.JUSSIEU.FR] Date: mercredi 7 avril 1999 15:15 =C0: EPI-INFO@LISTSERV.CDC.GOV Objet: recoding a variable Hi everyone, I have a problem in recoding a numeric variable to a 80 characters variable. My problem is that the program cut the string at 25 characters. This may sound trivial, but can some one tell me what the problem is ? ****If etp1=3D5 then etpA1=3D "ecouvillonnage des canaux avec un = detergent ou un detergent/desinfectant"****** -- Franck GOLLIOT From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9903D" ========================================================================= Date: Tue, 23 Mar 1999 09:52:10 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Bailey, Gloria" Subject: Questionnaire verification MIME-Version: 1.0 Content-Type: text/plain We are using Epi Info for data entry and (double entry) verification. This involved entering all the questionnaires once. Now the verification process is underway, and a data entry person is using the procedure in the Manual to do "validation" by choosing "4" at the data entry screen which is "Verify data previously entered". This process has worked for us in the past for two other surveys we have done. However, for this survey, it is not working. I have asked one of the data entry people to write up the problem and this is what he wrote: I've written below the message received when changes are made tot he data. Here is what I did to cause the message to occur. I changed the field that asks the agency ID (Question #9). I did change it to an incorrect value (028 instead of 027) but I would think that would be a valid one as well. Anyway, here is the message I received when entering this data. You get this message at the end, when it asks Write Data to Disk? Y N. This screen pops up. Review the non-matching field(s). Press (Esc) when done. If permitted, you can edit the field value. (Non-matching fields where editing is not permitted require you to abandon this record by answering "No" to the "Write Data to Disk" prompt. When you hit ESC, it takes you to the top of the record. It is difficult to determine what to do at this point. At least, the system should tell you what the bad fields are. Let me know what is going on with this. The questionnaire does have some range checks in it, but the variables being revised are not out of the valid range. In fact, it seems to give this error no matter what variable is revised. Does anyone know what is happening? It does not allow us to save the corrected survey. Instead, I have had to go in through Analysis Update to fix the variable after the data entry person finds an error. This is making the entire process take much too long. Thanks for your help. Gloria A. Bailey, Ph.D. Epidemiologist Mental Health Division Department of Community and Human Services Key Tower 700 Fifth Avenue, Suite 3800 Seattle, WA 98104-5038 206-205-1359 gloria.bailey@metrokc.gov ========================================================================= Date: Tue, 23 Mar 1999 23:20:34 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jens M. Lauritsen" Subject: Re: Questionnaire verification In-Reply-To: <2E7728EB3EC0D211BEC800805FA7E012013D4264@kcmail2.metrokc.g ov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 09:52 23-03-99 -0800, you wrote: >We are u...... At one time we had similar problems. As I remember it they disappered by two actions: 1. Updating to the latest enter+ enterx and using enterx 2. REmowing all unnecessesary (spelling ?) lines. I had the impression that it had to do with some "on the boundary" limits of the whole chk, qes, recfilelength combination. Kindly Jens M. Lauritsen, Senior Registrar, PhD. Fyns Amt (County of Fyn), Health Service Division Initiative for Accident Prevention Oerbaekvej 100, DK5220 Odense Soe, Denmark Phone: +45 65561241 Fax: +45 6556 1205 e-mail: JML@dadlnet.dk (or: jel@sus.fyns-amt.dk) ========================================================================= Date: Tue, 23 Mar 1999 17:38:22 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Setareh Williams Subject: Re: creating a questionnaire In-Reply-To: <3.0.5.32.19990323232034.00832810@dadlnet.uni2.dk> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Hello, I'm using Epi Info for the very first time. I have two questions: (1) Is there a way to override the 500 line limit of the questionnaire created? or do I have to resort to dividing my questionnaire into separate sections? (2) My questionnaire will include descriptive (additional )information that does not necessarily have to translate into a variable name (for subsequent data management and analysis), can this information be collected and managed some other way (as included in the questionnaire)without being given a variable name for future access? Thanks in advance for you help. ========================================================================= Date: Tue, 23 Mar 1999 15:02:03 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Bailey, Gloria" Subject: Re: Questionnaire verification MIME-Version: 1.0 Content-Type: text/plain Thank you. I'll pass that along to my programmer. When we figure this out, I'll let the group know what worked. Gloria > ---------- > From: Jens M. Lauritsen[SMTP:JML@DADLNET.DK] > Reply To: Epi Info Discussion Group > Sent: Tuesday, March 23, 1999 2:20 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: Questionnaire verification > > At 09:52 23-03-99 -0800, you wrote: > >We are u...... > > At one time we had similar problems. > > As I remember it they disappered by two actions: > 1. Updating to the latest enter+ enterx and using enterx > 2. REmowing all unnecessesary (spelling ?) lines. > > I had the impression that it had to do with some "on the boundary" limits > of the whole chk, qes, recfilelength combination. > > > > Kindly > > Jens M. Lauritsen, Senior Registrar, PhD. > Fyns Amt (County of Fyn), Health Service Division > Initiative for Accident Prevention > Oerbaekvej 100, DK5220 Odense Soe, Denmark > Phone: +45 65561241 Fax: +45 6556 1205 > e-mail: JML@dadlnet.dk (or: jel@sus.fyns-amt.dk) > ========================================================================= Date: Wed, 24 Mar 1999 17:00:13 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: problems in LAN Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" We have in our hospital (childrens hosptital) a patient register system based in epi-info (v 6.04 spanish + 4bupdate). It have some features like related files in enter, large external codes, nutricional anthropometry et. and work in LAN (with 25 users). For more speed, i put the executable files and codes files in every users terminal, and system realy work more speed. But an error when one user try to execute domeas and other user too ocur. If only one user in LAN executed domeasx, the error not happen. the error is "runtime error 162 at 0004:2884" Any can help me? Thank in advance. Sorry for my bad english, (my language is spanish) Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Thu, 25 Mar 1999 10:34:13 +0100 Reply-To: elivsj@post7.tele.dk Sender: Epi Info Discussion Group From: =?ISO-8859-1?Q?S=F8ren_Gustavsen?= Subject: Mailing list MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Could I please be deleted from the mailing list. Hans Trier elivsj@post7.tele.dk From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9903C" ========================================================================= Date: Mon, 15 Mar 1999 14:45:44 +0100 Reply-To: golliot@ext.jussieu.fr Sender: Epi Info Discussion Group From: Franck Golliot Organization: CCLIN Paris-Nord Subject: Numeric string MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Does anyone know how to select a numeric string ? It's easy to select a character string ([position , number of characters]), but it doesn't work with a numeric variable. Thanks for your help. -- Franck GOLLIOT Centre Interregional de Coordination de la Lutte contre les Infections Nosocomiales, Paris ========================================================================= Date: Mon, 15 Mar 1999 14:04:51 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Numeric string Comments: To: golliot@ext.jussieu.fr In-Reply-To: <36ED0F08.A23A72E4@idf.ext.jussieu.fr> MIME-Version: 1.0 Franck Golliot writes: >Hi, > >Does anyone know how to select a numeric string ? It's easy to select a >character string ([position , number of characters]), but it doesn't >work with a numeric variable. > The trick is to convert the number to a string and then select the substring. If your variable is called NUMBER and defined as #### then something like this should work: define temp temp = number newnumber = temp[2,2] hope that helps, Mark -- Mark Myatt ========================================================================= Date: Mon, 15 Mar 1999 09:01:34 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA - dll problems Comments: cc: "Arner, Tom G." MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We will do this to the maximum extent possible, putting all our own DLL's in the Epi2000 directory, but Win32 systems do not allow more than one registered copy of certain DLL's that are used by other Microsoft programs, such as DAO35.DLL, which not only can't be registered twice, but must be in a specified ...\SHARED directory designated by Microsoft. Others must be in the SYSTEM (or SYSTEM32) directory. It is a continual fight to get this right, but we are winning so far as we gain more experience with student laboratory settings and a wider range of computers. We are moving rapidly to remove the dependence on the Microsoft Internet Explorer (IE4.0), which has been a considerable barrier for those not wanting ANY on-line browser or preferring Netscape. Andy Dean -----Original Message----- From: Jens M. Lauritsen [mailto:JML@DADLNET.DK] Sent: Monday, March 01, 1999 11:19 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA - dll problems At 11:44 01-03-99 -0500, you wrote: One very simple (? - is anything at all simple with the windows environment) solution is to make sure that epi-info is SELFCONTAINED That is, forget about sharing dll files with the numerous versions around the world of all the dll users. A lot of problems have shown up in various programs due to the "nationalisations" of dll files in my experience. Therefore I suggest - even at this late time - that you make the user specify ONE and only one install directory for epi2000. Based on that one all needed dll etc could go into that same directory. Otherwise problemsolving, updating etc. will be quite bothersome both in relation to epi-info and other types of software. (By sharing dll's the user can risk lack of function in epi-info as well as other types of software). You might disagree, but this type of install system has been chosen by other software companies to ensure stability, which is what we need most. E.g. the program STATA, which has all the analysis needs for biostatistics, and it comes in 3 disks of 1.44 Mb. , which should be ude>The discussion below is based on the ALPHA version of Epi 2000 from >September, not the BETA, which we hope to make available very soon. Windows >programs in general have a very complicated installation dance that involves >determining which DLL's are already installed, how many programs use them, >and which ones are older. "Older" comes in two flavors, version number and >date, and sometimes both can be relevant. We have learned quite a few >things from Mark's experience that he outlines below and are grateful that >he was willing to help with the testing. Similarly we are still learning >from installations on various systems, and expect that installation problems >may occur on some machines even with the beta version. This is part of the >testing process and should not be taken as a problem with the final product >unless it persists all the way to the released version. It is fairly well >known that Visual Basic 4 and 5 do not coexist well on the same computer, >and I spent considerable time removing Visual Basic 6 from my laptop because >going backward to Version 5 was not a felicitous thing. > >Welcome to DLL H___. We are not alone, but things would not be better in >Delphi or C++. > >We hope to be able to let you have the BETA version within the next week or >two. We are teaching a class of 30 with it next week here in Atlanta, and >another 30 instructors of Epi and computing are coming in May. I think >Rachael can count on having a released version by summer, and we also plan >to use it in teaching EIS officers in July. > > -----Original Message----- > From: Mark Myatt [mailto:mark@MYATT.DEMON.CO.UK] > Sent: Monday, March 01, 1999 1:40 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: FW: Diff b/w Epi2000 & Epi6.04? > > Kaufmann, Rachel writes: > >Dear Mark, > > Regarding "likely to lose your data and give >unreliable results", is > >this based on your experience with EpiInfo 2000 or just a >general caveat > >relating to beta versions? I need to know because I will >be teaching a > >class of 25 how to use EpiInfo in July. I was expecting to >teach EpiInfo > >2000, but if it's that bad I'll stick with the old version. > > Thanks very much! > > I found the beta-test version very unstable. I think this is >because I > had some of the shared components (.DLL and .OCX files) >already > installed on my machine in a variety of versions. Not only >did Epi2000 > not work very well, it also destroyed the installation of >other > applications (notably versions of Visual Basic). I found the >uninstall > routine of dubious reliability. > > Epi2000 is written in Visual Basic which, in my experience, >is prone to > this "broken installation" problem due to multiple >incompatible versions > of various support files. > > The problems I experienced may have been due to a very >specific set of > circumstances on my test machine (i.e. several development >systems such > as Visual Basic 3/4/5, Visual C++, and Delphi 1/2 >installed). Try it and > see BUT I cannot recommend the current version (it is a test >version!) > for any serious work. > > I have no idea when Epi2000 will be released. Perhaps one of >the team > that monitor this list will be able to give us a firm date. > > Mark > > -- > Mark Myatt > > Kindly Jens M. Lauritsen, Senior Registrar, PhD. Fyns Amt (County of Fyn), Health Service Division Initiative for Accident Prevention Oerbaekvej 100, DK5220 Odense Soe, Denmark Phone: +45 65561241 Fax: +45 6556 1205 e-mail: JML@dadlnet.dk (or: jel@sus.fyns-amt.dk) ========================================================================= Date: Mon, 15 Mar 1999 13:21:43 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jose A. Farfan" Subject: Communicating with the screen Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear members of the group, I am trying to include in a program I use to list some of my data, a questionto select those case I want to list. I am following an example from the manual, but I do not get the expected result. My data file is called den98.rec. I have in my file a field called donset. I want to be able to select the starting date and ending date of the cases I want to list. In this example I am only presenting the question for the starting date (DAT1). When I run the program, I get the question asked to provide the starting date (DAT1), I give a date, but I get a list (DONSET PATID ELISA1 ELISA2) of all the cases in my datafile.=20 The other problem I have found is that in the label of the report, (line 4 in my example) I do not get the value for DAT1, as seen in the example in the manual. 1. READ DEN98 2. DAT1 =3D "?GIVE ME DATE 1: ?" 3. select donset >=3DDAT1=20 4. TYPE "\CREPORT STARTING ON DATE 1: @DAT1" 5. list DONSET PATID ELISA1 ELISA2 I will appreciatte your help. Respectfully Jose A. Farfan Dr. Jose Arturo Farfan Ale Centro de Investigaciones Regionales "Dr. Hideyo Noguchi" Universidad Aut=F3noma de Yucat=E1n Av. Itz=E1es por 59, num. 490 M=E9rida, Yucat=E1n, M=E9xico 97000 Tel: (99) 23-22-74 (99) 24-57-55 Fax: (99) 23-61-20 ========================================================================= Date: Mon, 15 Mar 1999 22:34:29 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Pedro Arias Bohigas Subject: Re: Communicating with the screen MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Estimado amigo. Mi nombre es Pedro Arias y trabajo en Madrid Espańa. Para permitir que el programa se comunique con el usuario, como es tu deseo, debes definir las variables en las que vas a guardar los valores introducidos desde el teclado como GLOBALES. En tu caso, la variable DAT1 almacenará la fecha que escriba el usuario desde el teclado, para ello debes incluir una orden como: DEFINE DAT1 __________ GLOB esto define la variable DAT1 como de tipo caracter con diez caracteres (8 si solo usas dos dígitos para el ańo) y de tipo global. La línea 2 de tu programa debes corregirla incluyendo delante la orden IMMEDIATE, esto le pedirá al usuario una fecha, que el debe escribir incluyendo las barras (por ejemplo :13/04/1959). El programa debería quedar así: READ DEN98 DEFINE DAT1 __________ GLOB immediate DAT1 = "?GIVE ME DATE 1 (Incuyendo las barras): ?" select donset >=DAT1 TYPE "\CREPORT STARTING ON DATE 1: @DAT1" list DONSET PATID ELISA1 ELISA2 Espero que funcione. Puedes ver un buen ejemplo en el programa que genera muestras aleatorias (RSAMPLE.PGM) y en algunos PGM del módulo NETSS. Saludos desde Espańa ========================================================================= Date: Mon, 15 Mar 1999 17:09:53 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: EpiMap Printing MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" No new drivers, but the easy way out is to run it in a DOS window in Windows, do ALT-PRINTSCREEN to copy the Window to the clipboard, and then PASTE the image into Microsoft Word or WordPerfect. You can also send the image to a variety of file formats and import one of these into a Windows program for printing with newer drivers. -----Original Message----- From: Pfister, John [mailto:jp@MAIL.SLH.WISC.EDU] Sent: Friday, March 05, 1999 8:40 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: EpiMap Printing A colleague is having trouble printing from EpiMap to a HP Deskjet 820 Cse. Are there new printer drivers available? Thanks, John R. Pfister, MS, RM(AAM) Assistant Scientist; Microbiologist/Epidemiologist Wisconsin State Laboratory of Hygiene University of Wisconsin-Madison 465 Henry Mall Madison, WI 53706 608-262-7404 608-262-3257 FAX ========================================================================= Date: Mon, 15 Mar 1999 17:20:36 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Communicating with the screen MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'd suggest the word IMMEDIATE in front of the " DAT1=3D ?........" = line, and also that you=20 DEFINE DAT1 __________ GLOBAL, since you want it to retain its value as = each record is read and not be reset to missing. -----Original Message----- From: Jose A. Farfan [mailto:fale@TUNKU.UADY.MX] Sent: Monday, March 15, 1999 11:22 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Communicating with the screen Dear members of the group, I am trying to include in a program I use to list some of my data, a questionto select those case I want to list. I am following an example from the manual, but I do not get the expected result. My data file is called den98.rec. I have in my file a field called donset. I want to be able to select the starting date and ending date of the cases I want to list. In this example I am only presenting the question for the starting date (DAT1). When I run the program, I get the question asked to provide the starting date (DAT1), I give a date, but I get a list (DONSET PATID ELISA1 ELISA2) of all the cases in my datafile.=20 The other problem I have found is that in the label of the report, (line 4 in my example) I do not get the value for DAT1, as seen in the example in the manual. 1. READ DEN98 2. DAT1 =3D "?GIVE ME DATE 1: ?" 3. select donset >=3DDAT1=20 4. TYPE "\CREPORT STARTING ON DATE 1: @DAT1" 5. list DONSET PATID ELISA1 ELISA2 I will appreciatte your help. Respectfully Jose A. Farfan Dr. Jose Arturo Farfan Ale Centro de Investigaciones Regionales "Dr. Hideyo Noguchi" Universidad Aut=F3noma de Yucat=E1n Av. Itz=E1es por 59, num. 490 M=E9rida, Yucat=E1n, M=E9xico 97000 Tel: (99) 23-22-74 (99) 24-57-55 Fax: (99) 23-61-20 ========================================================================= Date: Tue, 16 Mar 1999 10:03:25 +0100 Reply-To: golliot@ext.jussieu.fr Sender: Epi Info Discussion Group From: Franck Golliot Organization: CCLIN Paris-Nord Subject: Numeric substring MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I would like to thank all of those who answered to my question about numeric substring selection. The trick is to convert the number to a string and then select the substring (VARTEXT[x,y]). However, I would like to do this without generating a new variable... Thank you again -- Franck GOLLIOT Centre Interregional de Coordination de la Lutte contre les Infections Nosocomiales, Paris ========================================================================= Date: Tue, 16 Mar 1999 09:02:32 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Communicating with the screen In-Reply-To: <199903151921.NAA22413@tunku.uady.mx> MIME-Version: 1.0 Jose A. Farfan writes: >Dear members of the group, I am trying to include in a program I use to >list some of my data, a questionto select those case I want to list. >I am following an example from the manual, but I do not get the expected >result. > >1. READ DEN98 >2. DAT1 = "?GIVE ME DATE 1: ?" >3. select donset >=DAT1 >4. TYPE "\CREPORT STARTING ON DATE 1: @DAT1" >5. list DONSET PATID ELISA1 ELISA2 > Suggest you define DAT1 as GLOBAL. -- Mark Myatt ========================================================================= Date: Tue, 16 Mar 1999 10:19:47 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Numeric substring Comments: To: golliot@ext.jussieu.fr In-Reply-To: <36EE1E5D.FB7CD648@idf.ext.jussieu.fr> MIME-Version: 1.0 Franck Golliot writes: >I would like to thank all of those who answered to my question about >numeric substring selection. The trick is to convert the number to a >string and then select the substring (VARTEXT[x,y]). However, I would >like to do this without generating a new variable... I don't think that is possible but you do not need to save the new variable as all variables in ANALYSIS are temporary until you do a WRITE RECFILE. Mark -- Mark Myatt ========================================================================= Date: Tue, 16 Mar 1999 13:22:05 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Bredin Organization: Calgary Regional Health Authority Subject: Inconsistent results in Y2K testing MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Greetings, We have been doing some Y2K testing of Epi Info version 6.04b to c upgrade with the 4BUPDATE Y2K update applied. We have found inconsistent year results when a user only enters in two years for the date (i.e. 99 for 1999, 00 for 2000 and 01 for 2001). The results are as follows: Set Windows to year 1999, then enter a 4 digit year - 04/04/1999 Result: Epi Info responds appropriately and age calculations are correct. Set Windows to year 1999, then enter a 2 digit year - 04/04/99 (i.e. April 4th 1999) Result: Epi Info inserts century 19 appropriately, year reads 1999 and age calculations are correct. Set Windows to year 1999, then enter a 2 digit year - 04/04/00 (i.e. April 4th, 2000) Result: Epi Info does not insert century, year reads as 00 and age calculations are based on 1900. Set Windows to year 1999, then enter a 2 digit year - 04/04/01 (i.e. April 4th 2001) Result: Epi Info inserts century 19, year reads 1901 and age calculations based on 1901. Set Windows to year 2000, then enter a 4 digit year - 04/04/2000 (i.e. April 4th 2000) Result: Epi Info responds appropriately and age calculations are correct. Set Windows to year 2000, then enter a 2 digit year - 04/04/99 (i.e. April 4th 1999) Result: Epi Info inserts century 20, year reads 2099 and age calculations based on 2099. Set Windows to year 2000, then enter a 2 digit year - 04/04/00 (i.e. April 4th 2000) Result: Epi Info does not insert century, year reads as 00 and age calculations are based on 1900. Set Windows to year 2000, then enter a 2 digit year - 04/04/01 (i.e. April 4th 2001) Result: Epi Info inserts century 20, year reads as 2001 and age calculations are based on 2001. From the above results we will strongly recommend that all our users (approx. 100) start entering four digit dates. Unfortunately we are sure that old habits will prevail. We would feel more comfortable if we could devise a chk file that would disallow two digit year entries. We have been unable to do so. Do any of you have suggestions? Regards, Mark Bredin ========================================================================= Date: Wed, 17 Mar 1999 00:34:15 +0100 Reply-To: "d.coulombier@rnsp-sante.fr" Sender: Epi Info Discussion Group From: COULOMBIER Denis Organization: RNSP Subject: Inconsistent results in Y2K testing MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Y2K handling in enter is consistent. If a date is entered with only 2 = digits=20 for the year, it adds the current system date century to the date. This=20 behaviour could be questionned, but it should not pose too much trouble = next=20 century. A simple check is the date entered is posterior to the system = date=20 could allow to discriminate data entry errors. However there will be = room for=20 confusion for birth date in the early 1900 at the start of next century. A bigger problem is the fact that enter in the american version allows 3 = digit=20 years ! After discussion with the French translation team (Robert Freund = and=20 Gilles Desv=E9), we decided to refuse 3 digit years and return an error = message.=20 The French version of 6.04C should be available soon. You will be = informed=20 through this list. Denis Coulombier d.coulombier@rnsp-sante.fr tel : 33 1 41 79 67 81 ========================================================================= Date: Wed, 17 Mar 1999 00:37:48 +0100 Reply-To: "d.coulombier@rnsp-sante.fr" Sender: Epi Info Discussion Group From: COULOMBIER Denis Organization: RNSP Subject: Numeric strings MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mark solution of going through a defined string variable is certainly the simplest. However, it is possible select directly on a numeric variable substring : For instance if you want to select records based on the first 2 digits of a 5 digit number, you can use the following statement : SELECT (VARNUM DIV 1000) = XX DIV 1000 will remove the last 3 digits. XX would be the first 2 digits to select on. Denis Coulombier d.coulombier@rnsp-sante.fr tel : 33 1 41 79 67 81 ========================================================================= Date: Wed, 17 Mar 1999 16:04:29 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Bredin Organization: Calgary Regional Health Authority Subject: Re: Y2K Problems in EpiInfo Comments: To: Pat Turri MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks for your response Pat. I forwarded your suggestion to one of our programers and he responded that the "c" version of Epi Info does not seem to convert properly from substring year field to a numeric in our testing. Are you currently using v6.04b or earlier? It would seem that version 6.04b to c inserts the current century (either 19 or 20 depending on the BIOS date) immediatly into a two digit year entry. This always gives a four digit number that equals or exceeds 1900 before any testing can be done. Regards, Mark Bredin. Pat Turri wrote: > Mark: > > Glad to see the results of your testing. Very enlightening. You mentioned that you are having trouble testing for a date containing missing century. I have done this by parsing the date into parts with a substring function. If your date were 01/01/99 and it should be 01/01/1999 then I would compare the last for characters of the date to the value 1900. I believe if you add the following into your check file you will get satisfactory results: > > BEFORE RECORD > DEFINE TESTDATE #### > END > > DATE > TESTDATE= DATE[7,4] > IF TESTDATE < 1900 THEN > CLEAR DATE > GOTO DATE > END > > Let me know if you can't get this to work. I have chosen to not use the Y2K update since many things I was using became disabled when I upgraded to "c". Good Luck. > > |_|_ Patrick A. Turri > |_|_ Tennessee Department of Health > Policy Planning and Assurance > 425 5th Avenue North > Nashville, TN 37247-5261 _|_| > pturri@mail.state.tn.us _|_| -- Mark Bredin Project Manager Epi info Y2K Remediation Project Mark.Bredin@CRHA-Health.Ab.Ca Voice: (403) 258-4031 Fax: (403) 640-8925 ========================================================================= Date: Wed, 17 Mar 1999 16:13:37 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Bredin Organization: Calgary Regional Health Authority Subject: Re: Inconsistent results in Y2K testing Comments: To: Louk Meertens MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks for your response Louk. We have tested your suggestion and it works for "00" but not for any numbers between 01 - 99. It would seem that version 6.04b to c inserts the current century (either 19 or 20 depending on the BIOS date) immediately into a two digit year entry. This always gives a four digit number that equals or exceeds 1900 before any testing can be done. Optimally we would like to be able to test for the existence of two digits but "00" seems to be the only situation where Epi Info does not insert the current century. Regards, Mark Bredin. Louk Meertens wrote: > Hemskerk 16/03/1999 > > dear Mark Bredin, > > The following CHK- file entering might help you a bit: > > ENTRYDATE (a variable in european dateformat) > MUSTENTER > AFTER ENTRY > IF ENTRYDATE[9,2]="" THEN > HELP "YOU SHOULD ENTER A PROPER DATE !!!" 10 10 > ENDIF > END > END > > I tried it with the systemdate set to year 2000 and the help popped > up nicely. > I also discovered that a date entred as 23/12/00 was copied to a > defined variable as 23/12/1900. > Greetings, Louk Meertens > > You wrote: > > > Greetings, > > > > We have been doing some Y2K testing of Epi Info version 6.04b to c > > upgrade with the 4BUPDATE Y2K update applied. We have found > > inconsistent year results when a user only enters in two years for the > > date (i.e. 99 for 1999, 00 for 2000 and 01 for 2001). The results are > > as follows: > > > > Set Windows to year 1999, then enter a 4 digit year - 04/04/1999 > > Result: Epi Info responds appropriately and age calculations are > > correct. > > > > Set Windows to year 1999, then enter a 2 digit year - 04/04/99 (i.e. > > April 4th 1999) > > Result: Epi Info inserts century 19 appropriately, year reads 1999 and > > age calculations are correct. > > > > Set Windows to year 1999, then enter a 2 digit year - 04/04/00 (i.e. > > April 4th, 2000) > > Result: Epi Info does not insert century, year reads as 00 and age > > calculations are based on 1900. > > > > Set Windows to year 1999, then enter a 2 digit year - 04/04/01 (i.e. > > April 4th 2001) > > Result: Epi Info inserts century 19, year reads 1901 and age > > calculations based on 1901. > > > > Set Windows to year 2000, then enter a 4 digit year - 04/04/2000 (i.e. > > April 4th 2000) > > Result: Epi Info responds appropriately and age calculations are > > correct. > > > > Set Windows to year 2000, then enter a 2 digit year - 04/04/99 (i.e. > > April 4th 1999) > > Result: Epi Info inserts century 20, year reads 2099 and age > > calculations based on 2099. > > > > Set Windows to year 2000, then enter a 2 digit year - 04/04/00 (i.e. > > April 4th 2000) > > Result: Epi Info does not insert century, year reads as 00 and age > > calculations are based on 1900. > > > > Set Windows to year 2000, then enter a 2 digit year - 04/04/01 (i.e. > > April 4th 2001) > > Result: Epi Info inserts century 20, year reads as 2001 and age > > calculations are based on 2001. > > > > >From the above results we will strongly recommend that all our users > > (approx. 100) start entering four digit dates. Unfortunately we are > > sure that old habits will prevail. We would feel more comfortable if we > > could devise a chk file that would disallow two digit year entries. We > > have been unable to do so. > > > > Do any of you have suggestions? > > > > Regards, > > > > Mark Bredin > > > > > REDFLAMINGO -- Mark Bredin Project Manager Epi info Y2K Remediation Project Mark.Bredin@CRHA-Health.Ab.Ca Voice: (403) 258-4031 Fax: (403) 640-8925 ========================================================================= Date: Wed, 17 Mar 1999 16:25:38 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Bredin Organization: Calgary Regional Health Authority Subject: Re: Inconsistent results in Y2K testing Comments: To: "Crane, Giles L." MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Thanks for your suggestions. 0) Unfortunately, training over 100 users in over 20 locations using 12 different applications of Epi Info is not covered in my Y2K budget. 1) It would seem that version 6.04b to c inserts the current century (either 19 or 20 depending on the BIOS date) immediately into a two digit year entry. This always gives a four digit number that equals or exceeds 1900 before any testing can be done. 2) Unfortunately, rewriting over 100 users in over 20 locations using 12 different applications of Epi Info is not covered in my Y2K budget. 3) Absolutely! Warmest regards, Mark Bredin. Crane, Giles L. wrote: > FROM:Crane, Giles L. > TO:Bredin, Mark > CC: > SUBJECT:Inconsistent results in Y2K testing > DATE: 03-17-1999 10:52 > PRIORITY: > ATTACHMENT: > > ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ > Suggestions: > (0) Find reliable person to input data and give training > which includes dates. > (1) Use check file to screen answers (RANGE, if statements) > and remind operator if 1901 detected. > (2) Use ANALYSIS.EXE to run a .pgm file which checks this > and other possible inconsistencies. > (3) Program own date entry using string variables and > instructions in .CHK file to fill date variables > in a desired way. > (4) Have a happy St. Patrick's Day. > Cordially, > Giles Crane, M.P.H. > NJ Dept. of Health > > -------------------------------- > REPLY FROM: Crane, Giles L. > From: Mark Bredin > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Inconsistent results in Y2K testing > Date: 1999-03-16 15:22 > Priority: 3 > Message ID: 0D664BFED2DBD21198140000F840E81B > > -------------------------------------------------- > > Greetings, > > We have been doing some Y2K testing of Epi Info version 6.04b to c > upgrade with the 4BUPDATE Y2K update applied. We have found > inconsistent year results when a user only enters in two years for the > date (i.e. 99 for 1999, 00 for 2000 and 01 for 2001). The results are > as follows: > > Set Windows to year 1999, then enter a 4 digit year - 04/04/1999 > Result: Epi Info responds appropriately and age calculations are > correct. > > Set Windows to year 1999, then enter a 2 digit year - 04/04/99 (i.e. > April 4th 1999) > Result: Epi Info inserts century 19 appropriately, year reads 1999 and > age calculations are correct. > > Set Windows to year 1999, then enter a 2 digit year - 04/04/00 (i.e. > April 4th, 2000) > Result: Epi Info does not insert century, year reads as 00 and age > calculations are based on 1900. > > Set Windows to year 1999, then enter a 2 digit year - 04/04/01 (i.e. > April 4th 2001) > Result: Epi Info inserts century 19, year reads 1901 and age > calculations based on 1901. > > Set Windows to year 2000, then enter a 4 digit year - 04/04/2000 (i.e. > April 4th 2000) > Result: Epi Info responds appropriately and age calculations are > correct. > > Set Windows to year 2000, then enter a 2 digit year - 04/04/99 (i.e. > April 4th 1999) > Result: Epi Info inserts century 20, year reads 2099 and age > calculations based on 2099. > > Set Windows to year 2000, then enter a 2 digit year - 04/04/00 (i.e. > April 4th 2000) > Result: Epi Info does not insert century, year reads as 00 and age > calculations are based on 1900. > > Set Windows to year 2000, then enter a 2 digit year - 04/04/01 (i.e. > April 4th 2001) > Result: Epi Info inserts century 20, year reads as 2001 and age > calculations are based on 2001. > > From the above results we will strongly recommend that all our users > (approx. 100) start entering four digit dates. Unfortunately we are > sure that old habits will prevail. We would feel more comfortable if we > could devise a chk file that would disallow two digit year entries. We > have been unable to do so. > > Do any of you have suggestions? > > Regards, > > Mark Bredin -- Mark Bredin Project Manager Epi info Y2K Remediation Project Mark.Bredin@CRHA-Health.Ab.Ca Voice: (403) 258-4031 Fax: (403) 640-8925 ========================================================================= Date: Wed, 17 Mar 1999 16:45:22 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Bredin Organization: Calgary Regional Health Authority Subject: Y2K testing of v6.04b to c Comments: To: d.coulombier@RNSP-SANTE.FR MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks for your response Denis, Your observations are what we have found. It would seem that version 6.04b to c inserts the current century (either 19 or 20 depending on the BIOS date) immediately into a two digit year entry (except "00"). This always gives a four digit number that equals or exceeds 1900 before any testing can be done. Entering "00" results in 1900 being used in any date calculations but only the two digits "00" being saved in the field. This makes date testing/confirmation across two centuries very difficult to achieve with a reasonably sized check file. Regards, Mark Bredin. ------------------------------ Date: Wed, 17 Mar 1999 00:34:15 +0100 From: COULOMBIER Denis Subject: Inconsistent results in Y2K testing Y2K handling in enter is consistent. If a date is entered with only 2 = digits=20 for the year, it adds the current system date century to the date. This=20 behaviour could be questionned, but it should not pose too much trouble = next=20 century. A simple check is the date entered is posterior to the system = date=20 could allow to discriminate data entry errors. However there will be = room for=20 confusion for birth date in the early 1900 at the start of next century. A bigger problem is the fact that enter in the american version allows 3 = digit=20 years ! After discussion with the French translation team (Robert Freund = and=20 Gilles Desv=E9), we decided to refuse 3 digit years and return an error = message.=20 The French version of 6.04C should be available soon. You will be = informed=20 through this list. Denis Coulombier d.coulombier@rnsp-sante.fr tel : 33 1 41 79 67 81 ------------------------------ Date: Wed, 17 Mar 1999 00:37:48 +0100 From: COULOMBIER Denis Subject: Numeric strings Mark solution of going through a defined string variable is certainly the simplest. However, it is possible select directly on a numeric variable substring : For instance if you want to select records based on the first 2 digits of a 5 digit number, you can use the following statement : SELECT (VARNUM DIV 1000) = XX DIV 1000 will remove the last 3 digits. XX would be the first 2 digits to select on. Denis Coulombier d.coulombier@rnsp-sante.fr tel : 33 1 41 79 67 81 ========================================================================= Date: Wed, 17 Mar 1999 14:41:47 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Claudia Aparecida Lima Subject: questionnaire Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hello, I m starting to work with EPI-Info and I have got difficuties. I`would like to know if somebody can help me. I created a questionnaire and fill in it with a example. Now I want to print and I don`t get. When I press F5 I find this message: Record number# Last# Single Sheet(Y/N)? After that I complete these questions appear: Insert next sheet, press a key. I don`t know what is the key. Thanks a lot. Claudia cal97@aber.ac.uk ========================================================================= Date: Sat, 20 Mar 1999 19:12:14 +1100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Andrew James Baillie Subject: SF36/12 scorer MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi everyone, Sometime ago a very kind soul on this mailing list sent me a copy of a .chk file to score the sf36. Seeing how someone else had done this helped me to master calcuations in .chk files and made my life much easier - however I stupidly deleted the email. I have a spss scorer but I'd rather not spend the time doing the translation to a ..chk file if possible. I wouldn't mind a sf12 scorer if any one has one of them (I have sas and spss here already but again I'm lazy ;-)) thanks for all the excellent support for epi info Andrew PS You guys can keep Baywatch! -- __________________________________________________________________________ Andrew Baillie phone +61 2 9850 9439 Psychology Department fax +61 2 9850 8062 Macquarie University NSW 2109 AUSTRALIA Andrew.Baillie@mq.edu.au http://www.ocs.mq.edu.au/~abaillie __________________________________________________________________________ From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9903B" ========================================================================= Date: Mon, 8 Mar 1999 08:36:48 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Discussion Group Subject: Re: TEST MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Users, Please stop responding to the email below. It was not generated by Epi = Info Support. -----Original Message----- From: Ingrid Eckerman [mailto:eckerman@ALGONET.SE] Sent: Friday, March 05, 1999 7:07 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: SV: TEST How many replies do you want?=20 -----Ursprungligt meddelande----- Fr=E5n: Tsuyoshi Matsuo Till: EPI-INFO@LISTSERV.CDC.GOV Datum: den 5 mars 1999 00:03 =C4mne: TEST >TEST - PLEASE REPLY > ========================================================================= Date: Fri, 5 Mar 1999 14:48:13 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: Re: TEST In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 16:13 5/03/99 +0000, you wrote: >Replying as requested. > >On Fri, 5 Mar 1999, RICHARD, CHRIS wrote: > >> ---------- >>From: Epi Info Discussion Group >>To: EPI-INFO >>Subject: TEST >>Date: Thursday, March 04, 1999 2:45PM >> >>TEST - PLEASE REPLY >> > >-- >(Mr.) Christopher R. West, MA (Lecturer in Public Health Computing) >Department of Public Health, Whelan Building, Quadrangle, >University of Liverpool, Liverpool, L69 3GB, UK > >Tel: +44 (0)151 794 5587 Fax: +44 (0)151 794 5588 >e-mail: c.r.west@liverpool.ac.uk >WWW (Dept.): http://www.liv.ac.uk/PublicHealth/home.html > > Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Mon, 8 Mar 1999 11:37:12 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jaime Bonilla Subject: Read: TEST MIME-Version: 1.0 Content-Type: text/plain Your message To: 'Epi Info Discussion Group' Cc: Subject: RES: TEST Sent: Thu, 4 Mar 1999 18:59:09 -0500 was read on Mon, 8 Mar 1999 11:44:38 -0500 ========================================================================= Date: Mon, 8 Mar 1999 16:30:00 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Lasater, Richard" Subject: soundex MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable FROM:Lasater, Richard TO:epiinfo list CC: SUBJECT:soundex PRIORITY: =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF I am trying to use soundex in a rec/chk system but can only get the = soundex result to flicker fleetingly on the screen, can't figure out why the = result screen won't pop up and stay. Any sugestions? txs rl ========================================================================= Date: Mon, 8 Mar 1999 18:07:11 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Fagan, Robert F." Subject: Re: soundex MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable would you include the .chk code with your question please. The index = must be a soundex index for it to work. rff -----Original Message----- From: Lasater, Richard [mailto:LASA100W@CDC.GOV] Sent: Monday, March 08, 1999 4:30 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: soundex FROM:Lasater, Richard TO:epiinfo list CC: SUBJECT:soundex PRIORITY: =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF I am trying to use soundex in a rec/chk system but can only get the = soundex result to flicker fleetingly on the screen, can't figure out why the = result screen won't pop up and stay. Any sugestions? txs rl ========================================================================= Date: Tue, 9 Mar 1999 08:28:03 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Atrie, Jag" Subject: Re: soundex Comments: To: "Lasater, Richard" I believe you will get a listing of records that "stays" on the screen only when the soundex module detects a possible duplicate. Hence "no news is good news" in this instance. ________________________________ Jag Atrie Communicable Disease Control Health Department of Western Australia Telephone: (08) 9388 4844 Facsimile: (08) 9388 4848 E-Mail: jag.atrie@health.wa.gov.au ________________________________ ---------- From: Lasater, Richard [SMTP:LASA100W@CDC.GOV] Sent: Tuesday, 9 March 1999 5:30 To: EPI-INFO@LISTSERV.CDC.GOV Subject: soundex FROM:Lasater, Richard TO:epiinfo list CC: SUBJECT:soundex PRIORITY: ???????????????????????????????????????????????????????????????????????????? I am trying to use soundex in a rec/chk system but can only get the soundex result to flicker fleetingly on the screen, can't figure out why the result screen won't pop up and stay. Any sugestions? txs rl ========================================================================= Date: Tue, 9 Mar 1999 21:00:41 +1100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Neil Duggan Subject: Re: TEST MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply as requested. Tsuyoshi Matsuo wrote: > TEST - PLEASE REPLY From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9903A" ========================================================================= Date: Mon, 1 Mar 1999 09:39:43 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: FW: Diff b/w Epi2000 & Epi6.04? Comments: To: "Kaufmann, Rachel" , EpiInfo List ADMINISTRATOR In-Reply-To: MIME-Version: 1.0 Kaufmann, Rachel writes: >Dear Mark, > Regarding "likely to lose your data and give unreliable results", is >this based on your experience with EpiInfo 2000 or just a general caveat >relating to beta versions? I need to know because I will be teaching a >class of 25 how to use EpiInfo in July. I was expecting to teach EpiInfo >2000, but if it's that bad I'll stick with the old version. > Thanks very much! I found the beta-test version very unstable. I think this is because I had some of the shared components (.DLL and .OCX files) already installed on my machine in a variety of versions. Not only did Epi2000 not work very well, it also destroyed the installation of other applications (notably versions of Visual Basic). I found the uninstall routine of dubious reliability. Epi2000 is written in Visual Basic which, in my experience, is prone to this "broken installation" problem due to multiple incompatible versions of various support files. The problems I experienced may have been due to a very specific set of circumstances on my test machine (i.e. several development systems such as Visual Basic 3/4/5, Visual C++, and Delphi 1/2 installed). Try it and see BUT I cannot recommend the current version (it is a test version!) for any serious work. I have no idea when Epi2000 will be released. Perhaps one of the team that monitor this list will be able to give us a firm date. Mark -- Mark Myatt ========================================================================= Date: Mon, 1 Mar 1999 08:26:11 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Discussion Group Subject: Re: Change of email MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Jacks, Please include your old (former) email address in order for us to = change your email address on the EPI-INFO list serve. -----Original Message----- From: =C1rea de Patologia - FOP/UNICAMP = [mailto:ruibrito@FOP.UNICAMP.BR] Sent: Sunday, February 28, 1999 2:49 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Change of email Dear Sr mail list administrator, I'd like to change the email to receive the EPI-INFO mail list. My new email is jacks@fop.unicamp.br This email i've been getting my discussion list is located in another computer of my office. Thank you very much, Jacks Jorge Piracicaba's School of Dentistry, UNICAMP. ========================================================================= Date: Mon, 1 Mar 1999 08:52:27 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Discussion Group MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Omar, The archive of emails is not available to the discussion group. The emails are grouped by postings. They have to be individually retrieved from the server. Sorry about that. EPI INFO SUPPORT -----Original Message----- From: Omar Jorge Medina [mailto:omedina@INFOVIA.COM.AR] Sent: Friday, February 26, 1999 6:49 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: help INDEX EPI-INFO ========================================================================= Date: Mon, 1 Mar 1999 11:44:04 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Epi 2000 ALPHA vs. Epi 2000 BETA Comments: cc: "Arner, Tom G." MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" The discussion below is based on the ALPHA version of Epi 2000 from September, not the BETA, which we hope to make available very soon. Windows programs in general have a very complicated installation dance that involves determining which DLL's are already installed, how many programs use them, and which ones are older. "Older" comes in two flavors, version number and date, and sometimes both can be relevant. We have learned quite a few things from Mark's experience that he outlines below and are grateful that he was willing to help with the testing. Similarly we are still learning from installations on various systems, and expect that installation problems may occur on some machines even with the beta version. This is part of the testing process and should not be taken as a problem with the final product unless it persists all the way to the released version. It is fairly well known that Visual Basic 4 and 5 do not coexist well on the same computer, and I spent considerable time removing Visual Basic 6 from my laptop because going backward to Version 5 was not a felicitous thing. Welcome to DLL H___. We are not alone, but things would not be better in Delphi or C++. We hope to be able to let you have the BETA version within the next week or two. We are teaching a class of 30 with it next week here in Atlanta, and another 30 instructors of Epi and computing are coming in May. I think Rachael can count on having a released version by summer, and we also plan to use it in teaching EIS officers in July. -----Original Message----- From: Mark Myatt [mailto:mark@MYATT.DEMON.CO.UK] Sent: Monday, March 01, 1999 1:40 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: FW: Diff b/w Epi2000 & Epi6.04? Kaufmann, Rachel writes: >Dear Mark, > Regarding "likely to lose your data and give unreliable results", is >this based on your experience with EpiInfo 2000 or just a general caveat >relating to beta versions? I need to know because I will be teaching a >class of 25 how to use EpiInfo in July. I was expecting to teach EpiInfo >2000, but if it's that bad I'll stick with the old version. > Thanks very much! I found the beta-test version very unstable. I think this is because I had some of the shared components (.DLL and .OCX files) already installed on my machine in a variety of versions. Not only did Epi2000 not work very well, it also destroyed the installation of other applications (notably versions of Visual Basic). I found the uninstall routine of dubious reliability. Epi2000 is written in Visual Basic which, in my experience, is prone to this "broken installation" problem due to multiple incompatible versions of various support files. The problems I experienced may have been due to a very specific set of circumstances on my test machine (i.e. several development systems such as Visual Basic 3/4/5, Visual C++, and Delphi 1/2 installed). Try it and see BUT I cannot recommend the current version (it is a test version!) for any serious work. I have no idea when Epi2000 will be released. Perhaps one of the team that monitor this list will be able to give us a firm date. Mark -- Mark Myatt ========================================================================= Date: Mon, 1 Mar 1999 20:18:46 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jens M. Lauritsen" Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA - dll problems In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:44 01-03-99 -0500, you wrote: One very simple (? - is anything at all simple with the windows environment) solution is to make sure that epi-info is SELFCONTAINED That is, forget about sharing dll files with the numerous versions around the world of all the dll users. A lot of problems have shown up in various programs due to the "nationalisations" of dll files in my experience. Therefore I suggest - even at this late time - that you make the user specify ONE and only one install directory for epi2000. Based on that one all needed dll etc could go into that same directory. Otherwise problemsolving, updating etc. will be quite bothersome both in relation to epi-info and other types of software. (By sharing dll's the user can risk lack of function in epi-info as well as other types of software). You might disagree, but this type of install system has been chosen by other software companies to ensure stability, which is what we need most. E.g. the program STATA, which has all the analysis needs for biostatistics, and it comes in 3 disks of 1.44 Mb. , which should be ude>The discussion below is based on the ALPHA version of Epi 2000 from >September, not the BETA, which we hope to make available very soon. Windows >programs in general have a very complicated installation dance that involves >determining which DLL's are already installed, how many programs use them, >and which ones are older. "Older" comes in two flavors, version number and >date, and sometimes both can be relevant. We have learned quite a few >things from Mark's experience that he outlines below and are grateful that >he was willing to help with the testing. Similarly we are still learning >from installations on various systems, and expect that installation problems >may occur on some machines even with the beta version. This is part of the >testing process and should not be taken as a problem with the final product >unless it persists all the way to the released version. It is fairly well >known that Visual Basic 4 and 5 do not coexist well on the same computer, >and I spent considerable time removing Visual Basic 6 from my laptop because >going backward to Version 5 was not a felicitous thing. > >Welcome to DLL H___. We are not alone, but things would not be better in >Delphi or C++. > >We hope to be able to let you have the BETA version within the next week or >two. We are teaching a class of 30 with it next week here in Atlanta, and >another 30 instructors of Epi and computing are coming in May. I think >Rachael can count on having a released version by summer, and we also plan >to use it in teaching EIS officers in July. > > -----Original Message----- > From: Mark Myatt [mailto:mark@MYATT.DEMON.CO.UK] > Sent: Monday, March 01, 1999 1:40 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: FW: Diff b/w Epi2000 & Epi6.04? > > Kaufmann, Rachel writes: > >Dear Mark, > > Regarding "likely to lose your data and give >unreliable results", is > >this based on your experience with EpiInfo 2000 or just a >general caveat > >relating to beta versions? I need to know because I will >be teaching a > >class of 25 how to use EpiInfo in July. I was expecting to >teach EpiInfo > >2000, but if it's that bad I'll stick with the old version. > > Thanks very much! > > I found the beta-test version very unstable. I think this is >because I > had some of the shared components (.DLL and .OCX files) >already > installed on my machine in a variety of versions. Not only >did Epi2000 > not work very well, it also destroyed the installation of >other > applications (notably versions of Visual Basic). I found the >uninstall > routine of dubious reliability. > > Epi2000 is written in Visual Basic which, in my experience, >is prone to > this "broken installation" problem due to multiple >incompatible versions > of various support files. > > The problems I experienced may have been due to a very >specific set of > circumstances on my test machine (i.e. several development >systems such > as Visual Basic 3/4/5, Visual C++, and Delphi 1/2 >installed). Try it and > see BUT I cannot recommend the current version (it is a test >version!) > for any serious work. > > I have no idea when Epi2000 will be released. Perhaps one of >the team > that monitor this list will be able to give us a firm date. > > Mark > > -- > Mark Myatt > > Kindly Jens M. Lauritsen, Senior Registrar, PhD. Fyns Amt (County of Fyn), Health Service Division Initiative for Accident Prevention Oerbaekvej 100, DK5220 Odense Soe, Denmark Phone: +45 65561241 Fax: +45 6556 1205 e-mail: JML@dadlnet.dk (or: jel@sus.fyns-amt.dk) ========================================================================= Date: Mon, 1 Mar 1999 20:29:44 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jens M. Lauritsen" Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA - dll problems In-Reply-To: <3.0.5.32.19990301201846.007fe420@dadlnet.uni2.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ps Excuses for not deleting the old message after my comments ! Kindly Jens M.Lauritsen _____________________________________________________________ venlig hilsen Jens M. Lauritsen, Ph.d. Afdelingslaege Fyns amt. Sundhedssekretariatet, Initiativ for Ulykkesforebyggelse Oerbaekvej 100, DK5220 Odense Soe Tlf: +45 65561241 Fax: +45 6556 1205 Internet: Jel@sus.fyns-amt.dk, JML@dadlnet.dk ========================================================================= Date: Mon, 1 Mar 1999 13:48:10 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Tsuyoshi Matsuo Subject: Re: RE ODDS RATIO INTERPRETATION My interpretation of odds ratio is the ratio of the odds of exposure for cases to the odds of exposure for controls. (Exposure odds ratio) And in this example, if we consider "family type-not natural" to be the exposure, we get the odds ratio of (92/8)/(81/19)=2.70. In plain English, we can interpret it as, "Juvinile sex offenders are about three times as likely as non-juvinile sex offenders to be raised in a family with one or both parents not being natural parents." 0.37 is the odds ratio we get if we consider "family type-natural" to be the exposure. (Note 2.70 and 0.37 are the inverse of each other.) Another interpretation of odds ratio is the ratio of the odds of disease for exposed to the odds of disease for unexposed. (Disease odds ratio) By this interpretation, we get the odds ratio of (92/81)/(8/19)=2.70. And in plain English, we can interpret it as, "Those from intact families are about three times less likely as those from non-intact families to be juvenile sex offenders." Tsuyoshi Matuo -----Original Message----- From: Mark Myatt To: EPI-INFO@LISTSERV.CDC.GOV Date: Wednesday, February 24, 1999 7:53 AM Subject: Re: RE ODDS RATIO INTERPRETATION >RHassad writes: >> JSO >>Non-JSO >>Total >> >> Intact 8 >>19 >> 27 >> >> Non-intact 92 >>81 >> 173 >> >> Totals 100 >>100 >> 200 >> >> >> JSO- JUVENILE SEX OFFENDERS >> NON JSO- NON JUVENILE SEX OFFENDERS >> >> INTACT (FAMILY TYPE- BOTH NATURAL PARENTS) >> NON INTACT (FAMILY TYPE -NOT NATURAL) >> >>ODDS RATIO:0.37 >>95% Conidence Interval = 0.13 - 0.95 >> >>How should this less than unity (but significant OR) be interpreted) > >Those from intact families are less likely (i.e. about one third less >likely) to be JSO than those from non-intact families. > >Mark > >-- >Mark Myatt ========================================================================= Date: Mon, 1 Mar 1999 17:16:38 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA In-Reply-To: MIME-Version: 1.0 Dean, Andrew G. writes: >The discussion below is based on the ALPHA version of Epi 2000 from >September, not the BETA, which we hope to make available very soon. Yes, very sorry for the mistake ... I was not complaining as it was exactly what I expected with test software. >Welcome to DLL H___. We are not alone, but things would not be better in >Delphi or C++. My experience is that all Windows programming tasks can become DLL HELL but I have more problems with VB than with Delphi or Visual C++ because we have two DLL types (.DLL and .OCX) and more support files overall. The problem is not just older .DLLs ... most of my problems have come from newer versions of standard DLLs that have changed their way of working. I am not suggesting that that Epi2000 be moved to Delphi (we are much too far in for that) but that serious attention be paid to protecting Epi2000 .DLL and .OCX files from the snake pit of the WINDOWS\SYSTEM directory. Mark -- Mark Myatt ========================================================================= Date: Tue, 2 Mar 1999 11:45:58 -0800 Reply-To: gdaurat@club-internet.fr Sender: Epi Info Discussion Group From: Gérald DAURAT Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Myatt wrote: > > Dean, Andrew G. writes: > > >The discussion below is based on the ALPHA version of Epi 2000 from > >September, not the BETA, which we hope to make available very soon. > > Yes, very sorry for the mistake ... I was not complaining as it was > exactly what I expected with test software. > > >Welcome to DLL H___. We are not alone, but things would not be better in > >Delphi or C++. > > My experience is that all Windows programming tasks can become DLL HELL > but I have more problems with VB than with Delphi or Visual C++ because > we have two DLL types (.DLL and .OCX) and more support files overall. > The problem is not just older .DLLs ... most of my problems have come > from newer versions of standard DLLs that have changed their way of > working. I am not suggesting that that Epi2000 be moved to Delphi (we > are much too far in for that) but that serious attention be paid to > protecting Epi2000 .DLL and .OCX files from the snake pit of the > WINDOWS\SYSTEM directory. > > Mark > > -- > Mark Myatt Hi I'm also fed up with win95 win98 and all that MS rubish. I hope we'll soon get rid of it and have operating systems that work such as mac OS or LINUX. Sorry, that won't help but I feel better now. G Daurat Montpellier France ========================================================================= Date: Tue, 2 Mar 1999 13:04:47 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA Comments: To: gdaurat@club-internet.fr In-Reply-To: <36DC3FF6.2357@club-internet.fr> MIME-Version: 1.0 Grald DAURAT writes: >I'm also fed up with win95 win98 and all that MS rubish. And things looks set to get a whole lot more rocky as we will have Windows 2000 (which is NT 5.0 by another name) thrust down our throats. In my experience, the stability of NT is a bit of a myth. So we'll get a much more complicated OS with little gain. What we'll get is three different and incompatible 16-bit windows (3.1, 3.11, WfWg 3.11) and several different 32-bit versions (95, 95 with kernel patch, 95OSR2, any version of 95 with IE 4.xx installed, 98, CE 1.xx, 2.xx, NT 3.51, NT 4.00, NT 4.00 SP1,2,3,4, Windows 2000 plus the inevitable service packs, any 32-bit versions with IE 5.xx installed. Oh, mustn't forget that there will be workstation, server, professional, &c. Versions with and without BackOffice and InterNet services of NT/Win 2000) plus all the variations added by applications that piss all over the standard system .DLLs (some of them written by MS). All with different versions of the same .DLLs with functions requiring and returning different numbers and types of parameters. Its the Tower of Babel all over again! >I hope we'll soon get rid of it and have operating systems that work >such as mac OS or LINUX. I have dabbled in LINUX and it is very stable but, as yet, it does not appear ready for the big time in terms of the user interface, installation routines, and user-interface (X.11 based GUIs are powerful but not standardised and drag-and-drop requires a hole lot of work. It shares a lack of applications with the MAC. I think, however, that it will mature in those areas very fast now it has grabbed some level of awareness and support by IBM and Corel. BeOS looks great too but has no applications. >Sorry, that won't help but I feel better now. It is good to get these things off our chest before getting down to tracking down yet another elusive .DLL conflict ... I have a real thorny one at the moment to do with 16-bit OLE2 support that works on my Win 3.1 test installation but not on any of my clients machines. Arrrrrggggghhhhh. I must go out and strangle some chickens. I used to enjoy software development as adding variety to the other work that I do but I am think that, apart from support of existing clients, I will not be developing any further commercial software. Mark -- Mark Myatt ========================================================================= Date: Tue, 2 Mar 1999 15:43:39 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: error 10140 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" We are use a patient register system based in epi-info (v 6.04 spanish). It have some features like related files in enter, large external codes et. and work in LAN (with 25 users). Sometimes while a user are in enter, suddenly the system no works and appear a legend "error 10140". This happen when a user began to use a system. What does this mean? how i can resolve it? Thanks in advance (sorry for my bad english again) Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Tue, 2 Mar 1999 15:53:27 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Printing from Epi/Info Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Without exception, every Epi/Info program that I've used, I have had = problems printing. Here's what happens... If the text is longer than one page, it will print the first page = normally, the second page will be blank except for a line or two at the = bottom. The printing will continue on in this fashion. It's like the = number of lines for each page is off. I've dealt with the problem by = entering NEWPAGE after each frequency distribution or crosstabulation, = etc...This works fine unless there is an individual distribution or table = that is longer than one page and a blank page will be ejected after each = printed one. Is there a way to change the page formatting for printing or = resolve this problem otherwise? thanks msnell ========================================================================= Date: Wed, 3 Mar 1999 14:36:56 +0000 Reply-To: evan.sergeant@agric.nsw.gov.au Sender: Epi Info Discussion Group Comments: Authenticated sender is From: Evan Sergeant Subject: (John Snow's map Dear all, Can anyone out there provide me with a digital version of John Snow's map of the London Cholera outbreak, or let me know where I might find one please? I am sure I have seen one on the web somewhere, but can no longer find it. Thanks Evan Evan Sergeant Technical Specialist, Disease Surveillance & Risk Management NSW Agriculture, Locked Bag 21 Orange NSW 2800 Phone: 02 6391 3687 Fax: 02 6361 9976 For summary information on Australia's animal health status, check out the NAHIS web site: http://www.brs.gov.au/aphb/aha ========================================================================= Date: Wed, 3 Mar 1999 10:21:37 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert-Jean FREUND Subject: Re: Printing from Epi/Info In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Here is a copy of the message I send to the list a few weekw ago : I personnally no longer use direct DOS printing since this might be complex sometimes (lack of DOS compatibility for new HP printers, lack of appropriate driver, network problems, etc..) I create either from Epi6 or EpiMap CGM, PCX or BMP files for graphics and maps CGM reveals to be excellent since it is a vectorial format and it does not modify significantly colors in EpiMap Then I insert in Word or PowerPoint without any problem then print using standard Windows facilities available on any machine whatever is the configuration. Moreover, if you insert with a link in Word or PowerPoint, your DOC or PPT document will be updated any time you update the original graphics or map files For text printing you just ROUTE your results in a file (eg FILE.TXT ) This file is a MSDOS text format in Word (6 or 97) In Word 6 you need to choose COURIER font to get the exact fac simile of EpiInfo text It's automatic in Word 97 Hope that helps A 15:53 02/03/1999 -0700, vous avez =E9crit : >Without exception, every Epi/Info program that I've used, I have had problems printing. Here's what happens... > >If the text is longer than one page, it will print the first page normally, the second page will be blank except for a line or two at the bottom. The printing will continue on in this fashion. It's like the number of lines for each page is off. I've dealt with the problem by entering NEWPAGE after each frequency distribution or crosstabulation, etc...This works fine unless there is an individual distribution or table that is longer than one page and a blank page will be ejected after each printed one. Is there a way to change the page formatting for printing or resolve this problem otherwise? > >thanks >msnell > \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Wed, 3 Mar 1999 05:47:20 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: y2k and italian version? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi, Does anyone use the Italian version of epi info (I think 6.04b)? Does it upgrade to y2k compatibility? More generally, is it only 6.04c that can be upgraded? What happens to European dates (I notice that among 6.04a b and c European dates are not always treated the same way, so some pgm files have to be rewritten)? What about letters with accents? Thank you very much. Leona ========================================================================= Date: Wed, 3 Mar 1999 05:47:21 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: Printing from Epi/Info In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I had this problem too (using freq and a HP LaserJet 6P). I thought it was just a question of setting the page size wrong, but perhaps it is more complicated? Perhaps the printer also needs a setting of some kind (I think it has margin constraints which make the printable part of the paper smaller than the whole page). Perhaps there is a way to tell epi info that printing can be continuous, even if a table is split? Leona Bassein ======== At 15:53 02/03/99 -0700, Matt Snell wrote: >Without exception, every Epi/Info program that I've used, I have had problems printing. Here's what happens... > >If the text is longer than one page, it will print the first page normally, the second page will be blank except for a line or two at the bottom. The printing will continue on in this fashion. It's like the number of lines for each page is off. I've dealt with the problem by entering NEWPAGE after each frequency distribution or crosstabulation, etc...This works fine unless there is an individual distribution or table that is longer than one page and a blank page will be ejected after each printed one. Is there a way to change the page formatting for printing or resolve this problem otherwise? > >thanks >msnell > > ========================================================================= Date: Wed, 3 Mar 1999 05:47:21 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: Epi 2000 ALPHA vs. Epi 2000 BETA - dll problems In-Reply-To: <3.0.5.32.19990301201846.007fe420@dadlnet.uni2.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi, let me say I agree, one and only one install directory for epi2000. Hard disks are ever bigger, and wasted space is less expensive than resolving conflicts! Then think that epi info is used all over the world with os's (and dll's) in many languages. Sharing is good for suites put out by a single firm. Leona Bassein ============ At 20:18 01/03/99 +0100, Jens M. Lauritsen wrote: >At 11:44 01-03-99 -0500, you wrote: >One very simple (? - is anything at all simple with the windows >environment) solution is to make sure that epi-info is SELFCONTAINED > >That is, forget about sharing dll files with the numerous versions around >the world of all the dll users. A lot of problems have shown up in various >programs due to the "nationalisations" of dll files in my experience. > >Therefore I suggest - even at this late time - that you make the user >specify ONE and only one install directory for epi2000. > >Based on that one all needed dll etc could go into that same directory. >Otherwise problemsolving, updating etc. will be quite bothersome both in >relation to epi-info and other types of software. (By sharing dll's the >user can risk lack of function in epi-info as well as other types of >software). > >You might disagree, but this type of install system has been chosen by >other software companies to ensure stability, which is what we need most. ========================================================================= Date: Wed, 3 Mar 1999 11:11:13 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Printing from Epi/Info In-Reply-To: MIME-Version: 1.0 Matt Snell writes: >Without exception, every Epi/Info program that I've used, I have had problems >printing. Here's what happens... > >If the text is longer than one page, it will print the first page normally, the >second page will be blank except for a line or two at the bottom. The printing >will continue on in this fashion. It's like the number of lines for each page >is off. I've dealt with the problem by entering NEWPAGE after each frequency >distribution or crosstabulation, etc...This works fine unless there is an >individual distribution or table that is longer than one page and a blank page >will be ejected after each printed one. Is there a way to change the page >formatting for printing or resolve this problem otherwise? You need to play with the settings for: SET PLINES = and SET PAGE = To get the page length and width settings correct. With page printers (laser and inkjet) you need to add a NEWPAGE for the final page only. When analysing data I usually send output to a file and view this in an editor or wordprocessor. I edit out what I don't want and print only what I need. In systems such as surveillance systems or vaccine recall lists that are run periodically I usually set up a menu system and use the type command to add form-feed characters into the file which I view with the VIEW command in the .MNU file. Mark -- Mark Myatt ========================================================================= Date: Wed, 3 Mar 1999 11:13:39 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: error 10140 In-Reply-To: <3.0.6.32.19990302154339.0079d880@ciunsa.unsa.edu.ar> MIME-Version: 1.0 Enrique Finetti writes: >We are use a patient register system based in epi-info (v 6.04 spanish). It >have some features like related files in enter, large external codes et. >and work in LAN (with 25 users). >Sometimes while a user are in enter, suddenly the system no works and >appear a legend "error 10140". This happen when a user began to use a >system. What does this mean? how i can resolve it? I need to know if it is the operating system or EpiInfo. If EpiInfo, which module of EpiInfo? Mark -- Mark Myatt ========================================================================= Date: Wed, 3 Mar 1999 11:36:01 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "B. Gerstman" Subject: (John Snow's map Comments: To: "INTERNET:evan.sergeant@agric.nsw.gov.au" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Message text written by INTERNET:evan.sergeant@agric.nsw.gov.au >Dear all, Can anyone out there provide me with a digital version of John Snow's map of the London Cholera outbreak, or let me know where I might find one please? I am sure I have seen one on the web somewhere, but can no longer find it. < Because of its large size and high level of detail, John Snow's full map does not reproduce well digitally. (A half-decent reproduction takes several hundred megabytes -- clearly impractical by current standards). O= ne solution is to take a small section of the map and have an artist rewrite= the text labels (in a similar font) in order to shrink the file and increase legibility. We have done this to produce the figure on page 9 of= "Epidemiology Kept Simple" (John Wiley & Sons, 1998). If you want a digit= al copy of the file, please contact the publisher to obtain permission and then get back to me with a copy of the response. I will then post the fil= e on my web site (www.sjsu.edu/faculty/gerstman/) and notify the member of the LISTERSERVE of its availability. = Bud Gerstman San Jose, CA, USA P.S. Epi 2000 shows a detail of the map in three dimensions on its sign-o= n screen -- not exactly my cup of tea (the aesthetics and detail are lacking), but a view of the map, nonetheless. = ========================================================================= Date: Wed, 3 Mar 1999 17:02:37 -0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Richard Hall Subject: Re: (John Snow's map Comments: To: evan.sergeant@agric.nsw.gov.au In-Reply-To: <199903030336.OAA09272@vogon.agric.nsw.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit John snow's map http://www.nationalgeographic.com/resources/ngo/education/ideas912/912choler aho3.html Regards Richard W Hall Richard W Hall Sowerby Centre for Health Informatics in Newcastle (SCHIN) University of Newcastle upon Tyne -->-----Original Message----- -->From: Epi Info Discussion Group [mailto:EPI-INFO@LISTSERV.CDC.GOV]On -->Behalf Of Evan Sergeant -->Sent: Wednesday, March 03, 1999 2:37 PM -->To: EPI-INFO@LISTSERV.CDC.GOV -->Subject: (John Snow's map --> --> -->Dear all, --> -->Can anyone out there provide me with a digital version of John Snow's -->map of the London Cholera outbreak, or let me know where I might find -->one please? --> -->I am sure I have seen one on the web somewhere, but can no longer -->find it. --> -->Thanks --> -->Evan -->Evan Sergeant -->Technical Specialist, -->Disease Surveillance & Risk Management -->NSW Agriculture, -->Locked Bag 21 -->Orange NSW 2800 --> -->Phone: 02 6391 3687 -->Fax: 02 6361 9976 --> -->For summary information on Australia's animal health status, -->check out -->the NAHIS web site: --> -->http://www.brs.gov.au/aphb/aha --> ========================================================================= Date: Thu, 4 Mar 1999 08:54:08 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Vegard Hogli Subject: Re: John Snow's map In-Reply-To: <199903031136_MC2-6C8F-5BEF@compuserve.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:36 03.03.99 -0500, you wrote: >Message text written by INTERNET:evan.sergeant@agric.nsw.gov.au >>Dear all, > >Can anyone out there provide me with a digital version of John Snow's >map of the London Cholera outbreak, or let me know where I might find >one please? > >I am sure I have seen one on the web somewhere, but can no longer >find it. Freware search engine WebFerret (http://www.ferretsoft.com/netferret/index.html) came up with 386 hits on "John Snow" and map. Here are a few (semi-ranked list): http://www.ncgia.ucsb.edu/pubs/snow/snow.html http://www.nationalgeographic.com/resources/ngo/education/ideas912/912choler aho1.html http://www.utexas.edu/depts/grg/gcraft/warmup/cholera/cholera.html http://www.gfz-potsdam.de/~marco/bsp/cholera.html http://www.volume5.com/book/visual/intro.html http://www.epcc.ed.ac.uk/epcc-tec/documents/SciVis-course/SciVis.book_5.html #HEADING4 Vegard Hoegli ========================================================================= Date: Thu, 4 Mar 1999 10:07:09 -0500 Reply-To: melthorn@welchlink.welch.jhu.edu Sender: Epi Info Discussion Group From: "Melvyn C. Thorne" Organization: Johns Hopkins University Subject: Re: (John Snow's map MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks, Richard Hall. Here's the URL again, hopefully clickable: http://www.nationalgeographic.com/resources/ngo/education/ideas912/912choleraho3.html Richard Hall wrote: > > John snow's map > > http://www.nationalgeographic.com/resources/ngo/education/ideas912/912choler > aho3.html > > Regards > Richard W Hall > > Richard W Hall > Sowerby Centre for Health Informatics in Newcastle (SCHIN) > University of Newcastle upon Tyne > > -->-----Original Message----- > -->From: Epi Info Discussion Group [mailto:EPI-INFO@LISTSERV.CDC.GOV]On > -->Behalf Of Evan Sergeant > -->Sent: Wednesday, March 03, 1999 2:37 PM > -->To: EPI-INFO@LISTSERV.CDC.GOV > -->Subject: (John Snow's map > --> > --> > -->Dear all, > --> > -->Can anyone out there provide me with a digital version of John Snow's > -->map of the London Cholera outbreak, or let me know where I might find > -->one please? > --> > -->I am sure I have seen one on the web somewhere, but can no longer > -->find it. > --> > -->Thanks > --> > -->Evan > -->Evan Sergeant > -->Technical Specialist, > -->Disease Surveillance & Risk Management > -->NSW Agriculture, > -->Locked Bag 21 > -->Orange NSW 2800 > --> > -->Phone: 02 6391 3687 > -->Fax: 02 6361 9976 > --> > -->For summary information on Australia's animal health status, > -->check out > -->the NAHIS web site: > --> > -->http://www.brs.gov.au/aphb/aha > --> -- Melvyn C. Thorne, MD, MPH Division of Health Systems Department of International Health Johns Hopkins U. School of Hygiene & PH http://www.jhsph.edu/do/software Delta Omega Alpha--> free Public Health Software ========================================================================= Date: Thu, 4 Mar 1999 14:45:04 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Tsuyoshi Matsuo Subject: TEST TEST - PLEASE REPLY ========================================================================= Date: Thu, 4 Mar 1999 20:59:09 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jacks Jorge Junior Subject: RES: TEST MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="---- =_NextPart_000_01BE6681.DBE6C160" ------ =_NextPart_000_01BE6681.DBE6C160 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Test O.K.! -----Mensagem original----- De: Tsuyoshi Matsuo [SMTP:matstsu@EMAIL.MSN.COM] Enviada em: Quinta-feira, 4 de Mar=E7o de 1999 19:45 Para: EPI-INFO@LISTSERV.CDC.GOV Assunto: TEST TEST - PLEASE REPLY ------ =_NextPart_000_01BE6681.DBE6C160 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+Ig4XAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEkAYA0AEAAAEAAAAQAAAAAwAAMAIAAAAL AA8OAAAAAAIB/w8BAAAAUQAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAAAEVwaSBJbmZvIERpc2N1 c3Npb24gR3JvdXAAU01UUABFUEktSU5GT0BMSVNUU0VSVi5DREMuR09WAAAAAB4AAjABAAAABQAA AFNNVFAAAAAAHgADMAEAAAAaAAAARVBJLUlORk9ATElTVFNFUlYuQ0RDLkdPVgAAAAMAFQwBAAAA AwD+DwYAAAAeAAEwAQAAABwAAAAnRXBpIEluZm8gRGlzY3Vzc2lvbiBHcm91cCcAAgELMAEAAAAf AAAAU01UUDpFUEktSU5GT0BMSVNUU0VSVi5DREMuR09WAAADAAA5AAAAAAsAQDoBAAAAHgD2XwEA AAAaAAAARXBpIEluZm8gRGlzY3Vzc2lvbiBHcm91cAAAAAIB918BAAAAUQAAAAAAAACBKx+kvqMQ GZ1uAN0BD1QCAAAAAEVwaSBJbmZvIERpc2N1c3Npb24gR3JvdXAAU01UUABFUEktSU5GT0BMSVNU U0VSVi5DREMuR09WAAAAAAMA/V8BAAAAAwD/XwAAAAACAfYPAQAAAAQAAAAAAAACiV0BBIABAAoA AABSRVM6IFRFU1QAhAIBBYADAA4AAADPBwMABAAUADsACQAEADkBASCAAwAOAAAAzwcDAAQAFAA6 ADgABABnAQEJgAEAIQAAADVFOEM2M0JFNzREMkQyMTE5QUQyMDBDMERGNTA1RERBAE4HAQOQBgB8 BQAAIgAAAAsAAgABAAAACwAjAAAAAAADACYAAAAAAAsAKQABAAAAAwAuAAAAAAACATEAAQAAALwA AABQQ0RGRUIwOQABAAIATQAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABNU1BTVC5ETEwAAAAAAE5J VEH5v7gBAKoAN9luAAAAQzpcRXhjaGFuZ2VcbWFpbGJveC5wc3QAGAAAAAAAAAA/vz0lVObREZrR AMDfUF3aooAAAAAAAAAYAAAAAAAAAD+/PSVU5tERmtEAwN9QXdrCgAAAEAAAAF6MY7500tIRmtIA wN9QXdoKAAAAUkVTOiBURVNUAAMANgAAAAAAQAA5AACHrv6aZr4BHgBwAAEAAAAKAAAAUkVTOiBU RVNUAAAAAgFxAAEAAAAWAAAAAb5mmv6dvmOMX9J0EdKa0gDA31Bd2gAAHgAeDAEAAAADAAAATVMA AB4AHwwBAAAAFQAAAFdpbmRvd3MvTUFTVEVSL0phY2tzAAAAAAMABhAqSqSlAwAHEKsAAAAeAAgQ AQAAAGUAAABURVNUT0stLS0tLU1FTlNBR0VNT1JJR0lOQUwtLS0tLURFOlRTVVlPU0hJTUFUU1VP U01UUDpNQVRTVFNVQEVNQUlMTVNOQ09NRU5WSUFEQUVNOlFVSU5UQS1GRUlSQSw0REVNAAAAAAIB CRABAAAApgEAAKIBAACDAgAATFpGdZJcL7gDAAoAcmNwZzEyNRYyAPgLYG4OEDA0Np0B9yACpAPj AgBjaArA4HNldDAgBxMCgwBQ4RB2cHJxMhF5DlASSpkQ3319CoAIyCA7CW/NDjA1AoAKgXVjAFAL A2ZjEhILxCBUB5AFQE/wLksuIQqiCoQKhAsw8GxpMzYBQBjAAUASwBRvdAWQdBIEMTYgCi0c4k0J 8HNhZ2XkbSAFsGlnC4AHQBzjHxomG/QbwQsTG/ZpLTGMNDQBQBtAMTgwAUCDDNAgk2IgRGU6DIQF DKFiGWFzdXlvcyRoaQXQYXQi4G8gwFtTTVRQOgDAI4ABI4FARU1BSUwugQXgTi5DT01dGiURIcBF bnYHMGRhIMcdkCIKE5EgUXULgAGQAC1mZWlyYSwgDDQgAQAjUXJcJ2VmNyOwKMExOSnAKaE6VDQ1 JZdQCsBhIgtFAFBJLUlORk9AAExJU1RTRVJWgSVAREMuR09WJZeqQQQQdQIwbyIMRSyg/x6fH6ob RAu2GjMvUhzQKtA4TEVBLMAH8CvwTFkXGi4KgBWxADUgAAADABAQAAAAAAMAERAAAAAAAwCAEP// //9AAAcwoHq59ppmvgFAAAgwoHq59ppmvgELAACACCAGAAAAAADAAAAAAAAARgAAAAADhQAAAAAA AAMAAoAIIAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwAFgAggBgAAAAAAwAAAAAAAAEYAAAAA UoUAALcNAAAeACWACCAGAAAAAADAAAAAAAAARgAAAABUhQAAAQAAAAQAAAA4LjAAAwAmgAggBgAA AAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALAC+ACCAGAAAAAADAAAAAAAAARgAAAAAOhQAAAAAAAAMA MIAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAygAggBgAAAAAAwAAAAAAAAEYAAAAAGIUA AAAAAAAeAEGACCAGAAAAAADAAAAAAAAARgAAAAA2hQAAAQAAAAEAAAAAAAAAHgBCgAggBgAAAAAA wAAAAAAAAEYAAAAAN4UAAAEAAAABAAAAAAAAAB4AQ4AIIAYAAAAAAMAAAAAAAABGAAAAADiFAAAB AAAAAQAAAAAAAAAeAD0AAQAAAAYAAABSRVM6IAAAAAMADTT9NwAAcSM= ------ =_NextPart_000_01BE6681.DBE6C160-- ========================================================================= Date: Fri, 5 Mar 1999 01:58:17 +0000 Reply-To: c.r.west@liverpool.ac.uk Sender: Epi Info Discussion Group From: Chris West Subject: Re: TEST In-Reply-To: <001401be6690$aae7e300$2495fbd0@tsuyoshi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Replying as requested. Chris West -- On Thu, 4 Mar 1999 14:45:04 -0800 Tsuyoshi Matsuo wrote: > TEST - PLEASE REPLY ---------------------- (Mr) Christopher R West, MA (Lecturer in Public Health Computing) Department of Public Health The University of Liverpool Whelan Building, Quadrangle Liverpool, UK L69 3GB Tel: +44 (0)151 794 5587 Fax: +44 (0)151 794 5588 e-mail: c.r.west@liv.ac.uk ========================================================================= Date: Thu, 4 Mar 1999 21:28:09 -0500 Reply-To: melthorn@welchlink.welch.jhu.edu Sender: Epi Info Discussion Group From: "Melvyn C. Thorne" Organization: Johns Hopkins University Subject: Re: TEST MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here's a reply. Tsuyoshi Matsuo wrote: > > TEST - PLEASE REPLY -- Melvyn C. Thorne, MD, MPH Division of Health Systems Department of International Health Johns Hopkins U. School of Hygiene & PH http://www.jhsph.edu/do/software Delta Omega Alpha--> free Public Health Software ========================================================================= Date: Thu, 4 Mar 1999 09:14:17 -0400 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Ricardo Granero Subject: Re: TEST MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit A reply from Barquisimeto, Venezuela Saludos (Regards) -----Original Message----- From: Tsuyoshi Matsuo To: EPI-INFO@LISTSERV.CDC.GOV Date: Jueves 4 de Marzo de 1999 07:40 PM Subject: TEST >TEST - PLEASE REPLY > ========================================================================= Date: Fri, 5 Mar 1999 09:55:50 -0800 Reply-To: ZAMBART Project Sender: Epi Info Discussion Group From: ZAMBART Project Subject: Re: TEST MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Its working -----Original Message----- From: Tsuyoshi Matsuo To: EPI-INFO@LISTSERV.CDC.GOV Date: 04 March, 1999 4:56 PM Subject: TEST >TEST - PLEASE REPLY > ========================================================================= Date: Tue, 23 Feb 1999 09:16:17 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Abrantes =?iso-8859-1?Q?Ara=FAjo?= Silva Filho Subject: Re: TEST In-Reply-To: <001401be6690$aae7e300$2495fbd0@tsuyoshi> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Replying as requested. Abrantes Ara=FAjo Silva Filho Medicina, UFES. abrantes@tropical.com.br At 14:45 04/03/99 -0800, you wrote: >TEST - PLEASE REPLY >=20 ========================================================================= Date: Fri, 5 Mar 1999 08:56:11 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Carl deMarco Subject: Read: TEST MIME-Version: 1.0 Content-Type: text/plain Your message To: 'Epi Info Discussion Group' Cc: Subject: RES: TEST Sent: Thu, 4 Mar 1999 18:59:09 -0500 was read on Fri, 5 Mar 1999 09:15:24 -0500 ========================================================================= Date: Fri, 5 Mar 1999 09:05:16 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Richard Laing Subject: Re: TEST In-Reply-To: <001401be6690$aae7e300$2495fbd0@tsuyoshi> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" As requested At 02:45 PM 3/4/99 -0800, you wrote: >TEST - PLEASE REPLY > > Richard Laing Tel 617 414-1444 Associate Professor Fax 617 638-4476 Department of International Health E-mail richardl@bu.edu Boston University School of Public Health 715 Albany St Boston MA 02118-2526 ========================================================================= Date: Fri, 5 Mar 1999 10:22:00 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "RICHARD, CHRIS" Subject: Re: TEST ---------- From: Epi Info Discussion Group To: EPI-INFO Subject: TEST Date: Thursday, March 04, 1999 2:45PM TEST - PLEASE REPLY ========================================================================= Date: Fri, 5 Mar 1999 16:13:11 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Mr. C.R. West" Subject: Re: TEST In-Reply-To: <199903051529.KAA09079@nca-fw1.bcbsnca.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Replying as requested. On Fri, 5 Mar 1999, RICHARD, CHRIS wrote: > ---------- >From: Epi Info Discussion Group >To: EPI-INFO >Subject: TEST >Date: Thursday, March 04, 1999 2:45PM > >TEST - PLEASE REPLY > -- (Mr.) Christopher R. West, MA (Lecturer in Public Health Computing) Department of Public Health, Whelan Building, Quadrangle, University of Liverpool, Liverpool, L69 3GB, UK Tel: +44 (0)151 794 5587 Fax: +44 (0)151 794 5588 e-mail: c.r.west@liverpool.ac.uk WWW (Dept.): http://www.liv.ac.uk/PublicHealth/home.html ========================================================================= Date: Fri, 5 Mar 1999 10:40:10 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Pfister, John" Subject: EpiMap Printing MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" A colleague is having trouble printing from EpiMap to a HP Deskjet 820 Cse. Are there new printer drivers available? Thanks, John R. Pfister, MS, RM(AAM) Assistant Scientist; Microbiologist/Epidemiologist Wisconsin State Laboratory of Hygiene University of Wisconsin-Madison 465 Henry Mall Madison, WI 53706 608-262-7404 608-262-3257 FAX ========================================================================= Date: Fri, 5 Mar 1999 17:05:05 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Holmfridur Gunnarsdottir Subject: Re: TEST In-Reply-To: <199903051529.KAA09079@nca-fw1.bcbsnca.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Reply as requested At 10:22 5.3.1999 -0500, you wrote: > ---------- >From: Epi Info Discussion Group >To: EPI-INFO >Subject: TEST >Date: Thursday, March 04, 1999 2:45PM > >TEST - PLEASE REPLY > ========================================================================= Date: Fri, 5 Mar 1999 15:58:35 -0800 Reply-To: umcosway@cc.UManitoba.CA Sender: Epi Info Discussion Group From: Sylvia Cosway Organization: University of Manitoba Subject: Re: TEST MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit replying as requested RICHARD, CHRIS wrote: > > ---------- > From: Epi Info Discussion Group > To: EPI-INFO > Subject: TEST > Date: Thursday, March 04, 1999 2:45PM > > TEST - PLEASE REPLY ========================================================================= Date: Sat, 6 Mar 1999 01:07:00 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Ingrid Eckerman Subject: SV: TEST MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable How many replies do you want?=20 -----Ursprungligt meddelande----- Fr=E5n: Tsuyoshi Matsuo Till: EPI-INFO@LISTSERV.CDC.GOV Datum: den 5 mars 1999 00:03 =C4mne: TEST >TEST - PLEASE REPLY > From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9902D" ========================================================================= Date: Mon, 22 Feb 1999 11:42:53 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Searching In-Reply-To: MIME-Version: 1.0 Eiko Cusick writes: >Hello, >I am trying to figure out a way to search within a selection for only a few >letters. For example, I want to find any ethnicity that has "hawaiian" in >it and I am looking through selections that may read >"hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how >to do this kind of a search so I can find all people that have hawaiian in >their background. > >Thank you for your help on this. Try (e.g.) if ethnic = "*HA" then hawaiian = 1 -- Mark Myatt ========================================================================= Date: Mon, 22 Feb 1999 12:02:29 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Searching Comments: To: rhassad@lha.gsbc.com In-Reply-To: MIME-Version: 1.0 RHassad writes: >You guys are doing a great job. > >I need help with the following: > >1. While in the analysis mode, how do I save a recoded variable? Use ROUTE to specify a filename and WRITE RECFILE to save the file. This saves to NEWFILE.REC: route newfile.rec write recfile Note that if NEWFILE.REC already exists than data will be appended ... so best to ERASE the file first: erase newfile.rec route newfile.rec write recfile To prevent data spooling to the screen as the file is saved use the /NOECHO switch: erase newfile.rec route newfile.rec write recfile /noecho >2. How do I suppress the summary statistics when printing all frequencies >(freq *)? Set statistics = off Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Mon, 22 Feb 1999 08:34:56 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Pfister, John" Subject: Duplicate records in Epi-Info MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I'm looking for information on how to remove duplicate records from .REC files in EpiInfo. In the past I have exported files to SAS or SPSS to do this, but I'd like to be able to eliminate those extra data manipualion steps. There are three situations for which I'm looking for solutions: 1.) Multiple occurences of completely identical records. I'd like to keep only a single occurence in the data file. 2.) Multiple occurrences of records which have a variable that should be unique (e.g. "patient number"), but which may have other variables with different data (e.g. "date entered"). Under this situation, I'd like to delete all but a single occurence, and it wouldn't matter which record I would keep. 3.) The same situation as in #2, but I'd like to keep the first occurrence (i.e. earliest "date entered"), or the last occurrence (i.e. most recent "date entered"), and delete the others. Thanks for your assistance, John Pfister, MS, RM(AAM) Public Health Laboratory Microbiologist and Epidemiologist Wisconsin State Laboratory of Hygiene Madison, WI 53706 608-262-7404 608-262-3257 FAX ========================================================================= Date: Mon, 22 Feb 1999 14:48:47 -0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: JAMES WOOD Subject: Re: Duplicate records in Epi-Info MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Dear John You can do this through the use of sorting, global variables (that can be used to carry information from one line to the next), a comparison of the content in the global variable and the current line's variable, combined with conditional statements before saving a revised file. James Wood Epidemiology Unit Animal Health Trust Newmarket UK -----Original Message----- From: Pfister, John [SMTP:jp@MAIL.SLH.WISC.EDU] Sent: Monday, February 22, 1999 2:35 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Duplicate records in Epi-Info I'm looking for information on how to remove duplicate records from .REC files in EpiInfo. In the past I have exported files to SAS or SPSS to do this, but I'd like to be able to eliminate those extra data manipualion steps. There are three situations for which I'm looking for solutions: 1.) Multiple occurences of completely identical records. I'd like to keep only a single occurence in the data file. 2.) Multiple occurrences of records which have a variable that should be unique (e.g. "patient number"), but which may have other variables with different data (e.g. "date entered"). Under this situation, I'd like to delete all but a single occurence, and it wouldn't matter which record I would keep. 3.) The same situation as in #2, but I'd like to keep the first occurrence (i.e. earliest "date entered"), or the last occurrence (i.e. most recent "date entered"), and delete the others. Thanks for your assistance, John Pfister, MS, RM(AAM) Public Health Laboratory Microbiologist and Epidemiologist Wisconsin State Laboratory of Hygiene Madison, WI 53706 608-262-7404 608-262-3257 FAX ========================================================================= Date: Mon, 22 Feb 1999 15:50:37 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Vegard Hogli Subject: Re: Duplicate records in Epi-Info In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Epi Info has a companion utility: DUPS.EXE that builds an index taking into consideration misspelled names etc. Read the dups.rtf in the Epi6 directory (I'm not sure from what version it was added, I have Epi Info v 6.04b). There is a DUPS.PGM example that demonstrate the use of the utility as well. Heres the syntax: DUPS.EXE is an Epi Info utility that adds a variable holding an identification code built from various variables contained in an Epi Info data file.=20 Syntax DUPS {[

My Web Pages:
The International Infectious Diseases Web Site
Http://www.ualberta.ca/~dalden/cid.html

The Public Health Inspector/Environmental Health Officer Home Page
http://www.ualberta.ca/~dalden/Index.html

Master's Student (Epidemiology) at the University of Alberta
Faculty of Medicine, Department of Public Health Sciences

ListMaster of Pubhealthnet - a list for public health professionals
to network and post/view jobs in the public health field. To join,
go to my web pages listed above and follow the instructions.

******************************************************************
  ========================================================================= Date: Thu, 25 Feb 1999 09:36:37 -0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: JAMES WOOD Subject: Re: RE ODDS RATIO INTERPRETATION MIME-Version: 1.0 Content-Type: text/plain Or alternatively, biased control selection , or that those from non-intact families are less likely to get caught Those from intact families are less likely (i.e. about one third less likely) to be JSO than those from non-intact families. Mark -- Mark Myatt ========================================================================= Date: Thu, 25 Feb 1999 09:16:51 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Diff b/w Epi2000 & Epi6.04? Comments: To: imanurse@canada.com In-Reply-To: <36D487EB.D30AADD2@ualberta.ca> MIME-Version: 1.0 Donna L. Alden writes: > Hello, > > I read messages from people talking about Epi 6.04, but isn't there > an Epi2000 out? I have a copy of Epi2000 and I'm wondering what the > differences are between the two programs? Thanks > The current version of EpiInfo is v6.04c and runs under MSDOS. EpiInfo 2000 is a test version (technology preview) of the next version of EpiInfo which will run under Windows. The two work in very different ways. EpiInfo 2000 is test software and is likely to lose your data and give unreliable results. It should not be used for real work. Mark -- Mark Myatt ========================================================================= Date: Thu, 25 Feb 1999 01:52:13 PST Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: group chemistry Subject: Stalist Question Mime-Version: 1.0 Content-type: text/plain I want to have sex with you all!!!!!!!!!!!!! Now!!!!!!!!!! ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com ========================================================================= Date: Thu, 25 Feb 1999 11:02:46 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Stalist Question Comments: To: titrationkings@HOTMAIL.COM In-Reply-To: <19990225095213.26005.qmail@hotmail.com> MIME-Version: 1.0 group chemistry writes: >I want to have sex with you all!!!!!!!!!!!!! Now!!!!!!!!!! I think that would be a bit difficult but you might try us a few at a time. Are you willing to travel? Mark -- Mark Myatt ========================================================================= Date: Thu, 25 Feb 1999 09:29:02 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Deborah Pauli Subject: epi-info archive Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 2/26/99 Does this LISTSERV have an archive somewhere? How do we access it? =20 I hope it does so new members can have access to old discussions and so = old members can delete old email on individual PCs. Thanks Deborah Pauli Tennessee Department of Health, PPA-HSI Birth Defects Registry Cordell Hull Building, 4th Floor 425 Fifth Avenue North Nashville, TN 37247-5262 FAX: 615-532-7904 Phone: 615-532-7865 EMAIL: dpauli@mail.state.tn.us=20 ========================================================================= Date: Thu, 25 Feb 1999 15:47:15 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: epi-info archive In-Reply-To: MIME-Version: 1.0 Deborah Pauli writes: >2/26/99 > >Does this LISTSERV have an archive somewhere? How do we access it? > >I hope it does so new members can have access to old discussions and so old >members can delete old email on individual PCs. It's on the CDC WWW site. -- Mark Myatt ========================================================================= Date: Thu, 25 Feb 1999 18:42:54 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Greg Fegan Subject: Re: epi-info archive MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Mark et al, It looks as if the news server that the list was copied to at CDC is no longer there. It used to be called cnews.cdc.gov and I for one can no longer see it by clicking on the web link from the page I originally created at CDC. Andy D., Perhaps you could have someone at IRMO look into this. Also BTW is there someone designated at CDC to be the webmaster for the EPI Info pages. They are starting to look very old fashioned IMHO. Best wishes Greg -----Original Message----- From: Mark Myatt To: EPI-INFO@LISTSERV.CDC.GOV Date: Thursday, February 25, 1999 9:58 AM Subject: Re: epi-info archive >Deborah Pauli writes: >>2/26/99 >> >>Does this LISTSERV have an archive somewhere? How do we access it? >> >>I hope it does so new members can have access to old discussions and so old >>members can delete old email on individual PCs. > >It's on the CDC WWW site. > > > >-- >Mark Myatt > ========================================================================= Date: Fri, 26 Feb 1999 08:08:05 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Brad Otto Subject: subscribe Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" subscribe 0000,0000,8080 ------------------------------------------------------------ Brad Otto Macfarlane Burnet Centre for Medical Research blotto@denpasar.wasantara.net.id blotto@burnet.edu.au blotto@blotto.org phone: +62-361-732 205 fax: +62-361-732 198 mobile + 62-81-139 4152 (incl voicemail) ========================================================================= Date: Wed, 24 Feb 1999 23:26:42 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Bredin Subject: Y2K Upgrading MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------ADA969062D4508E55B1717E5" --------------ADA969062D4508E55B1717E5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Next month we will begin upgrading over seven dozen Epi Info PCs (some with versions as old as version 2) to version 6.04b and then apply the Y2K patch. We have completed some Epi Info test upgrades, a database upgrade (using the yytoyyyy.exe utility) and created an updated questionnaire file with the rec2qes.exe utility. We have experienced no problems during testing but anticipate that our luck will not hold over seven dozen upgrades. Any warnings, experiences, hints or suggestions from those of you that have already upgraded would be greatly appreciated. Regards, Mark Bredin. --------------ADA969062D4508E55B1717E5 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Next month we will begin upgrading over seven dozen Epi Info PCs (some with versions as old as version 2) to version 6.04b and then apply the Y2K patch.  We have completed some Epi Info test upgrades, a database upgrade (using the yytoyyyy.exe utility) and created an updated questionnaire file with the rec2qes.exe utility.  We have experienced no problems during testing but anticipate that our luck will not hold over seven dozen upgrades.

Any warnings, experiences, hints or suggestions from those of you that have already upgraded would be greatly appreciated.

Regards,

Mark Bredin. --------------ADA969062D4508E55B1717E5-- ========================================================================= Date: Fri, 26 Feb 1999 14:34:42 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Brad Otto Subject: Re: Y2K Upgrading In-Reply-To: <36D4ED22.3E7DDA43@shaw.wave.ca> Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Some epiglue systems I've found that were developed using version 6.04b passed both .pgm and .rec files to an analysis routine from the command line, eg: analysis program.pgm /data.rec Epi 6.04c no longer supports this. Any epiglue systems using this in their menuing will not run properly. The analysis command line only takes the first parameter....either the .rec file name to read, or the .pgm file to execute, but no longer both. B Otto At 23:26 24/2/99 -0700, you wrote: >>>> Next month we will begin upgrading over seven dozen Epi Info PCs (some with versions as old as version 2) to version 6.04b and then apply the Y2K patch. We have completed some Epi Info test upgrades, a database upgrade (using the yytoyyyy.exe utility) and created an updated questionnaire file with the rec2qes.exe utility. We have experienced no problems during testing but anticipate that our luck will not hold over seven dozen upgrades. Any warnings, experiences, hints or suggestions from those of you that have already upgraded would be greatly appreciated. Regards, Mark Bredin. <<<<<<<< ========================================================================= Date: Fri, 26 Feb 1999 07:44:44 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: =?ISO-8859-1?Q?Juan_Carlos_Fern=E1ndez_Merino?= Subject: Re: Y2K Upgrading In-Reply-To: <36D4ED22.3E7DDA43@shaw.wave.ca> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Hi! From: Mark Bredin > upgrade (using the yytoyyyy.exe utility) and created an updated > Any warnings, experiences, hints or suggestions from those of you that > have already upgraded would be greatly appreciated. > We have a Public Health Alert System on a complex system based on NETSS. There are a central point (us) with 10 PC and 8 remotes points at provinci= al level. There are transference of data between both places (import and merge) We have updated once month ago and all was OK. We start with central site = and a week after the remote places. The system was able to manage information from si= tes updated and not updated yet. There have not been any problems. (from now) Juan Carlos Fern=E1ndez Merino Servicio de Vigilancia Epidemiol=F3gica S.G. de Salud P=FAblica y Participaci=F3n Consejer=EDa de salud - Junta de Andaluc=EDa tlf. +34-954465100 fax. +34-954465145 ========================================================================= Date: Fri, 26 Feb 1999 10:45:43 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Diana Echenique Subject: Re: epi-info archive Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Greg, Did you ment to send this e-mail to me? Diana ========================================================================= Date: Fri, 26 Feb 1999 10:49:39 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Diana Echenique Subject: Re: Y2K Upgrading Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Juan Carlos, Good lock! I will say to wait a bit longer...try running some reports = with 00-dates, see if it really works? Diana ========================================================================= Date: Fri, 26 Feb 1999 11:02:32 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Diana Echenique Subject: Re: Stalist Question Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable What is going on here? Diana ========================================================================= Date: Fri, 26 Feb 1999 12:12:00 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Carl DeMarco Subject: Re: Stalist Question MIME-Version: 1.0 Content-Type: text/plain somebody saw a giant pie rolling down a hill. when they tasted it, it was cherry. but a chicken had run away with the ice cream so they couldn't have it alamode. but since charlie forgot the ice cream scoop it was of no concequence. i hear it was the new eggplant-onion flavor from hen and berries which wouldn't have been any good with cherry pie anyways. it was the actual size fo the pie that caused all the commotion. all make sense now? > -----Original Message----- > From: Epi Info Discussion Group [mailto:EPI-INFO@LISTSERV.CDC.GOV]On > Behalf Of Diana Echenique > Sent: Friday, February 26, 1999 12:03 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: Stalist Question > > > What is going on here? > > Diana > ========================================================================= Date: Fri, 26 Feb 1999 20:49:16 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Omar Jorge Medina MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01BE61C9.7922D800" This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BE61C9.7922D800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable help INDEX EPI-INFO ------=_NextPart_000_0008_01BE61C9.7922D800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

help
INDEX  EPI-INFO
 
------=_NextPart_000_0008_01BE61C9.7922D800-- ========================================================================= Date: Sun, 28 Feb 1999 01:52:23 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Tsuyoshi Matsuo Subject: Re: RE ODDS RATIO INTERPRETATION My interpretation of odds ratio is the ratio of the odds of exposure for cases to the odds of exposure for controls. (Exposure odds ratio) And in this example, if we consider "family type-not natural" to be the exposure, we get the odds ratio of (92/8)/(81/19)=2.70. In plain English, we can interpret it as, "Juvinile sex offenders are about three times as likely as non-juvinile sex offenders to be raised in a family with one or both parents not being natural parents." 0.37 is the odds ratio we get if we consider "family type-natural" to be the exposure. (Note 2.70 and 0.37 are inverse of each other.) Another interpretation of odds ratio is the ratio of the odds of disease for exposed to the odds of disease for unexposed. (Disease odds ratio) By this interpretation, we get the odds ratio of (92/81)/(8/19)=2.70. And in plain English, we can interpret it as, "Those from intact families are about three times less likely as those from non-intact families to be juvenile sex offenders. Tsuyoshi Matuo -----Original Message----- From: Mark Myatt To: EPI-INFO@LISTSERV.CDC.GOV Date: Wednesday, February 24, 1999 7:53 AM Subject: Re: RE ODDS RATIO INTERPRETATION >RHassad writes: >> JSO >>Non-JSO >>Total >> >> Intact 8 >>19 >> 27 >> >> Non-intact 92 >>81 >> 173 >> >> Totals 100 >>100 >> 200 >> >> >> JSO- JUVENILE SEX OFFENDERS >> NON JSO- NON JUVENILE SEX OFFENDERS >> >> INTACT (FAMILY TYPE- BOTH NATURAL PARENTS) >> NON INTACT (FAMILY TYPE -NOT NATURAL) >> >>ODDS RATIO:0.37 >>95% Conidence Interval = 0.13 - 0.95 >> >>How should this less than unity (but significant OR) be interpreted) > >Those from intact families are less likely (i.e. about one third less >likely) to be JSO than those from non-intact families. > >Mark > >-- >Mark Myatt ========================================================================= Date: Sun, 28 Feb 1999 16:48:36 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: =?iso-8859-1?Q?=C1rea_de_Patologia_=2D_FOP=2FUNICAMP?= Subject: Change of email MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear Sr mail list administrator, I'd like to change the email to receive the EPI-INFO mail list. My new email is jacks@fop.unicamp.br This email i've been getting my discussion list is located in another computer of my office. Thank you very much, Jacks Jorge Piracicaba's School of Dentistry, UNICAMP. From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9902C" ========================================================================= Date: Tue, 16 Feb 1999 09:56:00 -0600 Reply-To: jledesma@spin.com.mx Sender: Epi Info Discussion Group From: "Nut. Angel Ledesma" Organization: NutriPac Subject: epi nut crash! MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT hi, i have epinut form epi info, and i have many data, when process antro run ok, and when runn graphs, run ok, but when export in ascii format epinut crash!: runtime eror 200! help me please! thanks Estamos en contacto... Regards, Nut. Angel Ledesma ====================================================== Nut. J. Angel Ledesma S. mailto:jledesma@spin.com.mx ~~~~~~~~~~~~~~~~~~~~~~~~ fax: (52 5) 679-6195 Instituto Nacional de Nutricion "SZ" A.P. 86-252, Mexico D.F., 14391 MEXICO Human Nutrition, WEB: http://spin.com.mx/~jledesma ICQ: 23275754 ====================================================== --- Thought for the day: Communist (n): one who has given up all hope of becoming a Capitalist. ========================================================================= Date: Thu, 18 Feb 1999 09:59:12 -0500 Reply-To: elennon@shrinerspfld.org Sender: Epi Info Discussion Group From: "Elise J. Lennon" Subject: Problem with Check Program MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit This is my first attempt at creating a questionnaire and then using the Check Program to customize data entry. One of my fields is a text field with 80 characters. Within the Check Program, I'm unable to get the full 80 characters. It seems to truncate the field at right margin of the screen, and doesn't allow it to go to the next line. Most likely there's a simple solution to this that evading me. Can someone help? Thanks, Elise Lennon, RN, MPH Clinical Research Coordinator Shriners Hospital for Children 516 Carew St. Springfield, MA 01104 elennon@shrinerspfld.org http://www.shrinerspfld.org ========================================================================= Date: Thu, 18 Feb 1999 09:06:00 -1000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Eiko Cusick Subject: Searching MIME-Version: 1.0 Content-Type: text/plain Hello, I am trying to figure out a way to search within a selection for only a few letters. For example, I want to find any ethnicity that has "hawaiian" in it and I am looking through selections that may read "hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how to do this kind of a search so I can find all people that have hawaiian in their background. Thank you for your help on this. Eiko ========================================================================= Date: Thu, 18 Feb 1999 15:26:17 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Susan Mackenzie Subject: Re: Searching Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Susan Mackenzie 02/18/99 03:26 PM It isn't possible to search for a sub-string in an Epi Info text field. We too have a need for such a feature and are hoping it will be incorporated in Epi 2000. Susan EikoC @ KAPIOLANI.ORG on 99/02/18 02:06:00 PM Please respond to EPI-INFO@LISTSERV.CDC.GOV To: EPI-INFO @ LISTSERV.CDC.GOV cc: (bcc: Susan Mackenzie) Subject: Searching Hello, I am trying to figure out a way to search within a selection for only a few letters. For example, I want to find any ethnicity that has "hawaiian" in it and I am looking through selections that may read "hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how to do this kind of a search so I can find all people that have hawaiian in their background. Thank you for your help on this. Eiko ========================================================================= Date: Thu, 18 Feb 1999 15:43:20 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Keith Heller Subject: Re: Searching MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit If you export the file to a statistics program such as SAS, you will be able to do this type of search easily. In SAS there is the Index function which will tell you if a specified set of characters in one argument(such as "red") is found in a second character argument(such as as "dark red"). Keith **************************************************************************** ***** Keith Heller, DDS, DrPH Phone: (734) 665-3810 (Home) Epidemiology, Dental Public Health (734) 647-2855 (Work) School of Public Health I Fax: (734) 764-3192 University of Michigan E-mail: kheller@umich.edu Ann Arbor, MI. 48109-2029 http://www.umich.edu/~kheller **************************************************************************** ***** -----Original Message----- From: Susan Mackenzie To: EPI-INFO@LISTSERV.CDC.GOV Date: Thursday, February 18, 1999 3:26 PM Subject: Re: Searching >Susan Mackenzie >02/18/99 03:26 PM > >It isn't possible to search for a sub-string in an Epi Info text field. We >too have a need for such a feature and are hoping it will be incorporated >in Epi 2000. > >Susan > > > > >EikoC @ KAPIOLANI.ORG on 99/02/18 02:06:00 PM > >Please respond to EPI-INFO@LISTSERV.CDC.GOV > >To: EPI-INFO @ LISTSERV.CDC.GOV >cc: (bcc: Susan Mackenzie) >Subject: Searching > > > > >Hello, >I am trying to figure out a way to search within a selection for only a few >letters. For example, I want to find any ethnicity that has "hawaiian" in >it and I am looking through selections that may read >"hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know >how >to do this kind of a search so I can find all people that have hawaiian in >their background. >Thank you for your help on this. >Eiko ========================================================================= Date: Thu, 18 Feb 1999 13:42:12 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Elaine Eby-Wilkens Subject: Re: Searching In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Please remove me from the epi-info emailing list. Thank You. At 09:06 AM 2/18/99 -1000, you wrote: >Hello, >I am trying to figure out a way to search within a selection for only a few >letters. For example, I want to find any ethnicity that has "hawaiian" in >it and I am looking through selections that may read >"hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how >to do this kind of a search so I can find all people that have hawaiian in >their background. > >Thank you for your help on this. > >Eiko > Elaine M Eby-Wilkens SRA III Division of Maternal-Fetal Medicine Med School: OB/GYN University of California, Davis ========================================================================= Date: Thu, 18 Feb 1999 15:33:22 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Re: Searching Comments: To: EikoC@KAPIOLANI.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable The relative ease or difficulty of dealing with your problem depends on = how much variance in the first letter of that race/ethnicity field. Let's = say you named that field RACE. You can check your first letter variance = by doing a FREQ RACE. If hawaiian appears in many rows of the resultant = frequency distribution, you may want to export the file to SAS as = suggested. If you don't have SAS, you could export to a spreadsheet, sort = by RACE, create a new field called HAWAIIAN, and auto-fill with YES or NO = depending on whether or not hawaiian was included in the mix of races = (this may be a tedious chore if you have a file with many records). You = could then import the file back into EPI/INFO, and SELECT HAWAIIAN=3D"Yes" good luck >>> Eiko Cusick 02/18/99 12:06PM >>> Hello, I am trying to figure out a way to search within a selection for only a = few letters. For example, I want to find any ethnicity that has "hawaiian" in it and I am looking through selections that may read "hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know = how to do this kind of a search so I can find all people that have hawaiian in their background. Thank you for your help on this. Eiko ========================================================================= Date: Fri, 19 Feb 1999 04:44:18 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Leona Bassein Subject: Re: Searching In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Of course hindsight is always better than foresight. Before collecting data (I know this of course because of trial and error and error and error...) it is always a good idea to plan the database carefully and avoid variables with concatenated codes in the same field. How wide is it? You might try dividing it into substrings of 2 letters and look at those which contain "ha" or "/h". Of course this means nobody has left a space, used capital letters or done anything else he/she shouldn't have. CHK files are terribly useful to avoid these errors. Good luck, Leona Bassein ================ At 09:06 18/02/99 -1000, you wrote: >Hello, >I am trying to figure out a way to search within a selection for only a few >letters. For example, I want to find any ethnicity that has "hawaiian" in >it and I am looking through selections that may read >"hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how >to do this kind of a search so I can find all people that have hawaiian in >their background. > >Thank you for your help on this. > >Eiko > > ========================================================================= Date: Fri, 19 Feb 1999 08:22:00 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jung, Betty C." Subject: Searching MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 RlJPTTpKdW5nLCBCZXR0eSBDLg0KVE86RXBpSW5mbyBMaXN0c2Vydg0KQ0M6SnVuZywgQmV0dHkg Qy4NClNVQkpFQ1Q6U2VhcmNoaW5nDQpEQVRFOiAwMi0xOS0xOTk5ICAgMDg6MjANClBSSU9SSVRZ Og0KQVRUQUNITUVOVDoNCg0Kr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+v r6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vrw0KMi8xOQ0KSXQgaXMgcG9zc2li bGUgdG8gZG8gYSB3aWxkY2FyZCBzZWFyY2guIFRyeSBTZWxlY3QgUkFDRT0iKndhaSINCkJldHR5 IEMuIEp1bmcNCg== ========================================================================= Date: Fri, 19 Feb 1999 08:47:12 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Searching MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" You can't search for the second example, but SELECT ETHNICITY[1,6] = "hawaii" should find the first one and all variants where the first 6 letters are "hawaii" -----Original Message----- From: Eiko Cusick [mailto:EikoC@KAPIOLANI.ORG] Sent: Thursday, February 18, 1999 11:06 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Searching Hello, I am trying to figure out a way to search within a selection for only a few letters. For example, I want to find any ethnicity that has "hawaiian" in it and I am looking through selections that may read "hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how to do this kind of a search so I can find all people that have hawaiian in their background. Thank you for your help on this. Eiko ========================================================================= Date: Fri, 19 Feb 1999 09:05:32 -0500 Reply-To: rhassad@lha.gsbc.com Sender: Epi Info Discussion Group From: RHassad Subject: Re: Searching MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii You guys are doing a great job. I need help with the following: 1. While in the analysis mode, how do I save a recoded variable? 2. How do I suppress the summary statistics when printing all frequencies (freq *)? Rossi ------------- Original Text From: "Dean, Andrew G." , on 2/19/99 8:47 AM: You can't search for the second example, but SELECT ETHNICITY[1,6] = "hawaii" should find the first one and all variants where the first 6 letters are "hawaii" -----Original Message----- From: Eiko Cusick [mailto:EikoC@KAPIOLANI.ORG] Sent: Thursday, February 18, 1999 11:06 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Searching Hello, I am trying to figure out a way to search within a selection for only a few letters. For example, I want to find any ethnicity that has "hawaiian" in it and I am looking through selections that may read "hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how to do this kind of a search so I can find all people that have hawaiian in their background. Thank you for your help on this. Eiko ========================================================================= Date: Fri, 19 Feb 1999 09:33:20 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Kevin Sullivan Subject: Re: Searching In-Reply-To: <3.0.5.16.19990219103021.08c7cc30@pop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Concerning searching a character variable for a specific string, you could use the substring feature in ANALYSIS. In the original e-mail, the user wanted to search the field ETHNICITY for the the string "hawaiian". If this string is first, then you could select with: SELECT ETHNICITY[1,8] = "hawaiian" However, as in the example, the string "hawaiian" may not start in position 1. While awkward, you could have other select statements such as: SELECT ETHNICITY[2,8] = "hawaiian" SELECT ETHNICITY[3,8] = "hawaiian" SELECT ETHNICITY[4,8] = "hawaiian" etc. Kevin At 04:44 AM 2/19/99 -0500, you wrote: >Of course hindsight is always better than foresight. Before collecting data >(I know this of course because of trial and error and error and error...) >it is always a good idea to plan the database carefully and avoid variables >with concatenated codes in the same field. How wide is it? You might try >dividing it into substrings of 2 letters and look at those which contain >"ha" or "/h". Of course this means nobody has left a space, used capital >letters or done anything else he/she shouldn't have. CHK files are terribly >useful to avoid these errors. > >Good luck, > >Leona Bassein > >================ > > >At 09:06 18/02/99 -1000, you wrote: >>Hello, >>I am trying to figure out a way to search within a selection for only a few >>letters. For example, I want to find any ethnicity that has "hawaiian" in >>it and I am looking through selections that may read >>"hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how >>to do this kind of a search so I can find all people that have hawaiian in >>their background. >> >>Thank you for your help on this. >> >>Eiko >> >> > > -------------------------------------------------------------------- | Kevin M. Sullivan, PhD, MPH, MHA | | Assistant Professor | | Departments of Pediatrics, Epidemiology, and International Health | | Emory University | | 1518 Clifton Road, NE, 4th floor | | Atlanta, GA 30322 | | e-mail: cdckms@sph.emory.edu | | Phone: 404-315-3796 | | Fax: 404-315-3850 | -------------------------------------------------------------------- ========================================================================= Date: Fri, 19 Feb 1999 12:24:41 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: Searching Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii From: Jamie Hockin on 02/19/99 12:24 PM Betty is right - this is an undocumented feature of Epi Info which we also discovered some time ago. The following also works: define hawaii # if RACE = "*wai" then hawaii = 1 else hawaii = 0 Jamie Hockin JUNG100W @ CDC.GOV on 99/02/19 08:22:00 AM Please respond to EPI-INFO@LISTSERV.CDC.GOV To: EPI-INFO @ LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: Searching Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable FROM:Jung, Betty C. TO:EpiInfo Listserv CC:Jung, Betty C. SUBJECT:Searching DATE: 02-19-1999 08:20 PRIORITY: ATTACHMENT: =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF =AF 2/19 It is possible to do a wildcard search. Try Select RACE=3D"*wai" Betty C. Jung = ========================================================================= Date: Fri, 19 Feb 1999 15:16:00 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jung, Betty C." Subject: Re: Searching MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable FROM:Jung, Betty C. TO:EpiInfo Listserv CC:Jung, Betty C. SUBJECT:Re: Searching DATE: 02-19-1999 15:13 PRIORITY: ATTACHMENT: =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF 2/19 To save recoded variable, do a route and write recfile. To suppress summary statistics write: Set statistics=3Doff hope this helps. Betty C. Jung=20 -------------------------------- FORWARDED FROM: Jung, Betty C. From: RHassad To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: Searching Date: 1999-02-19 09:05 Priority: 3 Message ID: 2ED854F2F4C7D21197F80000F840E81B -------------------------------------------------- You guys are doing a great job. I need help with the following: 1. While in the analysis mode, how do I save a recoded variable? 2. How do I suppress the summary statistics when printing all = frequencies (freq *)? Rossi ------------- Original Text From: "Dean, Andrew G." , on 2/19/99 8:47 AM: You can't search for the second example, but SELECT ETHNICITY[1,6] =3D "hawaii" should find the first one and all variants where the = first 6 letters are "hawaii" -----Original Message----- From: Eiko Cusick [mailto:EikoC@KAPIOLANI.ORG] Sent: Thursday, February 18, 1999 11:06 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Searching Hello, I am trying to figure out a way to search within a selection for only a few letters. For example, I want to find any ethnicity that has "hawaiian" in it and I am looking through selections that may read "hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how to do this kind of a search so I can find all people = that have hawaiian in their background. Thank you for your help on this. Eiko ========================================================================= Date: Fri, 19 Feb 1999 15:21:16 -0500 Reply-To: rhassad@lha.gsbc.com Sender: Epi Info Discussion Group From: RHassad Subject: Re: Searching MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Thanks Betty. ------------- Original Text From: "Jung, Betty C." , on 2/19/99 3:16 PM: FROM:Jung, Betty C. TO:EpiInfo Listserv CC:Jung, Betty C. SUBJECT:Re: Searching DATE: 02-19-1999 15:13 PRIORITY: ATTACHMENT: ---------------------------------------------------------------------------- 2/19 To save recoded variable, do a route and write recfile. To suppress summary statistics write: Set statistics=off hope this helps. Betty C. Jung -------------------------------- FORWARDED FROM: Jung, Betty C. From: RHassad To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: Searching Date: 1999-02-19 09:05 Priority: 3 Message ID: 2ED854F2F4C7D21197F80000F840E81B -------------------------------------------------- You guys are doing a great job. I need help with the following: 1. While in the analysis mode, how do I save a recoded variable? 2. How do I suppress the summary statistics when printing all frequencies (freq *)? Rossi ------------- Original Text From: "Dean, Andrew G." , on 2/19/99 8:47 AM: You can't search for the second example, but SELECT ETHNICITY[1,6] = "hawaii" should find the first one and all variants where the first 6 letters are "hawaii" -----Original Message----- From: Eiko Cusick [mailto:EikoC@KAPIOLANI.ORG] Sent: Thursday, February 18, 1999 11:06 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Searching Hello, I am trying to figure out a way to search within a selection for only a few letters. For example, I want to find any ethnicity that has "hawaiian" in it and I am looking through selections that may read "hawaiian/spanish/chinese" or "japanese/hawaiian" etc. Does anyone know how to do this kind of a search so I can find all people that have hawaiian in their background. Thank you for your help on this. Eiko From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9902B" ========================================================================= Date: Mon, 8 Feb 1999 11:22:32 -0500 Reply-To: rhassad@lha.gsbc.com Sender: Epi Info Discussion Group From: RHassad Subject: Re: European Dates Comments: To: gdaurat@club-internet.fr MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-type: text/plain; charset=ISO-8859-1 Hello, Could someone kindly guide me through importing an epi info data file into SPSS 8. ------------- Original Text From: "G=D0rald DAURAT" , on 2/5/99 2:11 PM: Huet, Natalie wrote: > > I have 2 variables DOB and EXAMDATE in my qes file. I would like the > participant's age (in months) to be calculated when I enter the EXAMDATE. > (i.e. How old is the person on the EXAMDATE?). All of the dates are in > European Format. > > Thank you Dear Nathalie You can actually do this, though it's not recommended by data base normalisation rules (i.e. you shouldn't keep variables than can be calculated using other variables) The right way would be to calculate ages in ANALYSIS. I suppose you prefer to calculate it when entering data on the field to help health workers. You could add an age ### variable to your qes file then restructure rec files using enter option 3 then in Check, go to the variable called examdate press F9 and within the block, type LET AGE =3D (examdate - DOB) div 365.25 then press esc In addition, you may go to age field, press F9 and add the following expression NOENTER then press esc again and F10 to quit. answer Y to the question "WRite to disk" (or similar) The result will be : the value of age will automaticaly appear when entering the dates and you'll be unable to change this value manually by entering another age. Dates format, either american or european, doesn't matter at all. There are other better solutions in order to display age without recording it, but it's a bit more tricky. Hope that helps. G Daurat Montpellier France ========================================================================= Date: Mon, 8 Feb 1999 10:32:16 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Stockdale, Donna MCRHD" Subject: importing files MIME-Version: 1.0 Content-Type: text/plain I have created a file in Excel and tried saving both as a *.dbf file and a *.wks file to import into EpiInfo. However when I view the file in Analysis or ENTER, the field containing the birthdate (DD/MM/YY in excel) contains the numerical date, eg. 25347, rather than the date format. I would appreciate some suggestions about what I can do to prevent this conversion? Thanks. Donna Stockdale ========================================================================= Date: Mon, 8 Feb 1999 17:47:24 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert-Jean FREUND Subject: Re: importing files In-Reply-To: <4910ED0A48D5D11199D70060B06BF484289E00@mcrhd.sk.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Be sure you saved as dbf III format in Excel It works without problem with Excel 97 Try to enter complete year e.g. 1998 instead of 98 in Excel Hope that helps \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Mon, 8 Feb 1999 09:55:01 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Re: importing files Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable You might want to try ensuring that the date field format in Excel is set = to MM/DD/YY before exporting it to .dbf format. I've also had similar = problems before when the first data record (not the column title row) in a = file is empty. I've actually had to make sure that the first data row is = complete (no blank fields), even if it's nonsensical data that I later F6 = in UPDATE of ANALYSIS. My imported .rec files have always been fine when = I've taken these steps. >>> "Stockdale, Donna MCRHD" 02/08/99 = 09:32AM >>> I have created a file in Excel and tried saving both as a *.dbf file and a *.wks file to import into EpiInfo. However when I view the file in Analysis or ENTER, the field containing the birthdate (DD/MM/YY in excel) contains the numerical date, eg. 25347, rather than the date format. I would appreciate some suggestions about what I can do to prevent this conversion? Thanks. Donna Stockdale ========================================================================= Date: Mon, 8 Feb 1999 11:43:07 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Helpdesk Subject: Re: importing files MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Donna, Sounds like you imported the Excel file correctly; however, EPI INFO is reading the DD/MM/YY as a text file. You will need to edit the date field in the .QES file, so the date will be read as DD/MM/YY. (you may need to set up the format of the date in a questionnaire if you only imported data as .REC file. There may not be a QES file associated with your imported data.) I hope this helps you. Let us know if it doesn't. This date conversion happens alot with Excel and Lotus. If you set up headers in a .QES file, it seems to prevent it. However, that can be time consuming. EPI INFO SUPPORT -----Original Message----- From: Stockdale, Donna MCRHD [mailto:Donna.Stockdale@MCRHD.SK.CA] Sent: Monday, February 08, 1999 11:32 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: importing files I have created a file in Excel and tried saving both as a *.dbf file and a *.wks file to import into EpiInfo. However when I view the file in Analysis or ENTER, the field containing the birthdate (DD/MM/YY in excel) contains the numerical date, eg. 25347, rather than the date format. I would appreciate some suggestions about what I can do to prevent this conversion? Thanks. Donna Stockdale ========================================================================= Date: Mon, 8 Feb 1999 12:06:27 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Stockdale, Donna MCRHD" Subject: Re: importing files MIME-Version: 1.0 Content-Type: text/plain Thanks to all for the suggestions. It doesn't seem to make a difference whether the file is IMPORTed as a .rec file or read in analysis as a .dbf file, the date appears in the format of MM/DD/YY, despite formatting the date in Excel as mm/dd/yy. (At least it is now in a DATE rather than numerical format!). I do have a .qes file with the date formatted as DD/MM/YY, but the file will not convert to the european date format in ENTER with revise file structure with revised .qes file. It doesn't matter for analysis but it would be helpful for the data entry person to have a dd/mm/yy format. If it can't be converted we shall work with it as it is. Thanks. Donna > -----Original Message----- > From: EPI Info Helpdesk [SMTP:epiinfo@CDC.GOV] > Sent: Monday, February 08, 1999 10:43 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: importing files > > Donna, > > Sounds like you imported the Excel file correctly; however, EPI INFO > is > reading the DD/MM/YY as a text file. You will need to edit the date > field > in the .QES file, so the date will be read as DD/MM/YY. (you may need > to > set up the format of the date in a questionnaire if you only imported > data > as .REC file. There may not be a QES file associated with your > imported > data.) I hope this helps you. Let us know if it doesn't. > > This date conversion happens alot with Excel and Lotus. If you set up > headers in a .QES file, it seems to prevent it. However, that can be > time > consuming. > > EPI INFO SUPPORT > > -----Original Message----- > From: Stockdale, Donna MCRHD [mailto:Donna.Stockdale@MCRHD.SK.CA] > Sent: Monday, February 08, 1999 11:32 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: importing files > > > I have created a file in Excel and tried saving both as a *.dbf file > and > a *.wks file to import into EpiInfo. However when I view the file in > Analysis or ENTER, the field containing the birthdate (DD/MM/YY in > excel) contains the numerical date, eg. 25347, rather than the date > format. > > I would appreciate some suggestions about what I can do to prevent > this > conversion? > > Thanks. > Donna Stockdale ========================================================================= Date: Tue, 9 Feb 1999 08:27:04 +0100 Reply-To: gilles DESVE Sender: Epi Info Discussion Group From: gilles DESVE Subject: Re: importing files MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit >It doesn't seem to make a difference whether the file is IMPORTed as a >.rec file or read in analysis as a .dbf file, the date appears in the >format of MM/DD/YY, despite formatting the date in Excel as mm/dd/yy. >(At least it is now in a DATE rather than numerical format!). It seem that reading DBF with analysis alway return date in MM/DD/YY . Setting date to european has no effect. The french 6.04c version of analysis convert the date directly to DD/MM/YYYY format when reading DBF file. If needed, I can send you the analysis.exe file. Gilles Desve, EpiConcept Systeme d'information en sante publique. 47 rue de charenton, 75012 PARIS Tel : +33 (0)1 53 02 40 60, Fax: +33 (0)1 53 02 40 62 www.epiconcept.fr, gilles@epiconcept.fr ========================================================================= Date: Tue, 9 Feb 1999 09:17:39 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: European Dates Comments: To: rhassad@lha.gsbc.com In-Reply-To: MIME-Version: 1.0 RHassad writes: >Hello, > >Could someone kindly guide me through importing an epi info data file into >SPSS 8. There are two approaches: 1. Export the EpiInfo file file to SPSS/PC format (using EXPORT). This actually creates an SPSS syntax file which you can edit to SPSS/8 syntax. BEWARE ... there is a bug in EXPORT. SPSS/PC has a limit of 8 characters in variable names and EpiInfo has a limit of 10 characters. EXPORT simple truncates the EpiInfo variable name to eight caharacters and this may create duplicate variable names and prevent SPSS from working with the file. 2. Export the data into a format that SPSS/8 can read (dBase, Lotus 123). Hope that helps Mark -- Mark Myatt ========================================================================= Date: Tue, 9 Feb 1999 10:35:15 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Some free public health software MIME-Version: 1.0 Dear all, I have just revised my WWW site. It now allows downloads of of a collection of free Windows hosted public health software written by me (with others). Packages available are: Epicalc 2000 -=-=-=-=-=-= A statistical calculator that works with pre-tabulated data. Some of the functions available in EpiCalc will be of general use but they have been chosen to be of interest to persons working with data from a public health or epidemiological context. FP Advisor -=-=-=-=-= A foodborne disease database that allows investigators to consider a wide range of disease possibilities (contained in the FPAdvisor database) in a foodborne disease investigation at computer speed. Presently, there is a tendency to consider only a handful of causative agents that are frequently involved in foodborne disease outbreaks. By entering known information such as the incubation period, specific symptoms, type of food, &c., the program will generate a limited list of disease possibilities. The investigator can then choose to view or print details of each disease possibility. Some can be readily ruled out while others may warrant laboratory or other investigative follow up. SampleXS -=-=-=-= Sample size calculator for cross-sectional surveys using simple random, systematic, or complex samples using the algorithm presented in "Cochran WG, Sampling Techniques (3rd Edition), Wiley, New York, 1977". SigmaD (BETA-2) -=-=-=-=-=-=-=- SigmaD is a computer program designed to assist field workers when standardising epidemiological measurements (e.g. of weight, height, and MUAC in anthropometric surveys) and implements the method for the standardisation of quantitative epidemiological measurements presented in "Habicht JP, Estandardizacion de metodos epidemiologicos cuantitativos sobre el terrano, Boletin de la Oficina Sanitaria Panamerica, 76: 375-384, 1974" To download any of this software or to find out more, point your browser at: http://www.myatt.demon.co.uk/index.htm If you experience any problems with this site, please contact me. Mark -- Mark Myatt ========================================================================= Date: Tue, 9 Feb 1999 09:38:58 -0500 Reply-To: rhassad@lha.gsbc.com Sender: Epi Info Discussion Group From: RHassad Subject: Re: importing files MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Thanks for all the help thus far. I have an epi info data set (but no epi info program), how can I read this directly in SPSS without first exporting to SPSS format using epi info. ------------- Original Text From: "Robert-Jean FREUND" , on 2/8/99 11:47 AM: Be sure you saved as dbf III format in Excel It works without problem with Excel 97 Try to enter complete year e.g. 1998 instead of 98 in Excel Hope that helps \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Tue, 9 Feb 1999 10:37:42 -0500 Reply-To: rhassad@lha.gsbc.com Sender: Epi Info Discussion Group From: RHassad Subject: Re: problem opening REC file in ANALYSIS MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii HELP! HELP! -- it's me again-- I am attempting to install epi info 6.04 I dowloaded the files to C:\epi604_3.exe I went to the DOS prompt and typed epi604_3.exe the extraction is completed (15 files) Please what do I do next? ------------- Original Text From: "Dean, Andrew G." , on 1/29/99 4:49 PM: It is possible to create a questionnaire so huge ( > 500 or 600 lines) or with total field size > 2000 characters, that Analysis can't read it. Enter will warn if this is the case, however. -----Original Message----- From: e c groh [mailto:ecgroh@JUNO.COM] Sent: Wednesday, January 27, 1999 7:43 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: problem opening REC file in ANALYSIS Sandra: did you create a new rec file from the qes file? You have to do that first, then exit and return via enter or enterx and THEN begin data entry. e.c.groh On Wed, 27 Jan 1999 14:07:01 +0530 sandra writes: >Dear All, > >I have a very strange problem. I have created questionnaire .qes and = >have entered data using the ENTER programme, but I cannot read the >.rec = >file using analysis. > >I can see the data in the ENTER programme and by opening the file in = >EPED but I cannot read it in ANALYSIS. > >Has any one faced a similar problem ? Are there any suggestions. > >Thanks in advance > >Sandra > ========================================================================= Date: Wed, 10 Feb 1999 09:02:58 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: problem opening REC file in ANALYSIS Comments: To: rhassad@lha.gsbc.com In-Reply-To: MIME-Version: 1.0 RHassad writes: >HELP! HELP! -- it's me again-- > >I am attempting to install epi info 6.04 > >I dowloaded the files to C:\epi604_3.exe >I went to the DOS prompt and typed epi604_3.exe >the extraction is completed (15 files) > >Please what do I do next? type: epi604_1 epi604_2 epi604_3 This will expand the installation files. Now type: install and follow the instruction on-screen. -- Mark Myatt ========================================================================= Date: Wed, 10 Feb 1999 09:20:52 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Pilar Serrano - Investigadora IDEADE Subject: Terremoto Colombia Comments: To: Adolfo Ariza In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Reciban todos un cordial saludo. Despues de los hechos ocurridos en la zona cafetera Colombiana, pretendemos disenar y poner a funcionar un sistema de vigilancia del estado nutricional, en plataforma epiinfo. Yo estare representado a la universidad, que brindara la asesoria correspondiente. Quisiera saber si alguno de ustedes tiene experiencia en sistemas de informacion en tragedias y si podrian, a la vez, asesorarme acerca de las variables mas significativas para complementar la informacion antropometrica. Agradezco la atencion prestada a la presente y las demostraciones de solidaridad para con los damnificados. Atentamente, Pilar Serrano Galvis Departamento de Nutrici=F3n y Bioqu=EDmica Faculta de Ciencias B=E1sicas Tel. 3 208320 Ext 4063 o 4124 Fax. 2 887932 ========================================================================= Date: Wed, 10 Feb 1999 12:21:46 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Thomas Fox Subject: importing Mime-Version: 1.0 Content-Type: text/plain I am having trouble importing files that originate in the Paradox (.db) format. I have attempted to export the .db to a .dbf (3&4), however epiinfo will not accept this. Epiinfo did accept this .db file as a fixed .txt file. After this I created the .qes file to match the new .rec file I just imported from the .txt file. Next I attempted to revise and update the .rec file with the new .qes file. It did not work. Days later, I attempted to import other .db files (as fixed .txt files) with no success at all. The inconsistency is baffling. I'm thinking parodox is just incompatible with epiinfo. Allow me to provide further evidence for this thinking. One week ago, I successfully imported a file that originated in .dbf format. I also developed the .qes, after importing, and was successful revising and updating the .rec file from the new .qes. I have also attempted these same procedures on other computers in my office with the same results. One other side note. Two days ago, Epiinfo would not import the file that originated as a .dbf file. However, the first thing the next day, I was successful in importing this same file. (possible human error). At this point I am unable to import original paradox .db files, as .dbf or .txt files. I would greatly appreciate any supportive suggestions. Tom ========================================================================= Date: Thu, 11 Feb 1999 09:54:15 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Torleif Ruud Subject: Problem with a loop MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To more experienced users of EPi Info, I am not succeeding in getting the subroutine SLOYFE to work as a loop (repeat it self) and do not understand what is wrong. I am thankful for help. read origfile.rec let mnd=0 * if (((d1+(30*mnd))=fd) and ((d2+(30*mnd))<=td)) then atend=erved if (((d1+(30*mnd))>=fd) and ((d2+(30*mnd))>td) and (td>=(d1+(30*mnd)))) \ then atend=til if (((d1+(30*mnd))>td) and ((d2+(30*mnd))>td)) then atend=0 select atend > 0 route newfile1.rec write recfile select GOTO SLOYFE :SLOYFE let mnd = (mnd + 1) if (((d1+(30*mnd))=fd) and ((d2+(30*mnd))<=td)) then atend=erved if (((d1+(30*mnd))>=fd) and ((d2+(30*mnd))>td) and (td>=(d1+(30*mnd)))) \ then atend=til if (((d1+(30*mnd))>td) and ((d2+(30*mnd))>td)) then atend=0 select atend > 0 route newfile2.rec write recfile select dos merge newfile1.rec newfile2.rec newfile3.rec 1 erase newfile1.rec erase newfile2.rec copy newfile3.rec newfile1.rec erase newfile3.rec if mnd < 5 then RETURN if mnd = 5 then GOTO ENDIT :ENDIT close origfile.rec QUIT -- Torleif Ruud, Kreklingen 1, 6860 Sandane, Norway Tel +47 5786 5683 (home office) Fax +47 5786 5943 (home office) E-mail: torleif@online.no http://home.sol.no/~torleif/index.htm ========================================================================= Date: Thu, 11 Feb 1999 10:20:43 +-100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Arnt Ole Ree Subject: SV: Problem with a loop MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Torleif, I think using "immediate if" will do the job: immediate if mnd < 5 then RETURN immediate if mnd = 5 then GOTO ENDIT :ENDIT Regards Arnt Ole Ree MD, MPH Urds vei 2, 3216 Sandefjord, NORWAY Tlf./fax +47 334 60794 E-mail: arnt.ole.ree@medtek.no ---------- Fra: Torleif Ruud[SMTP:torleif@ONLINE.NO] Sendt: 11. februar 1999 09:54 Ti&l: EPI-INFO@LISTSERV.CDC.GOV E&mne: Problem with a loop To more experienced users of EPi Info, I am not succeeding in getting the subroutine SLOYFE to work as a loop (repeat it self) and do not understand what is wrong. I am thankful for help. ========================================================================= Date: Thu, 11 Feb 1999 09:21:28 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: importing In-Reply-To: MIME-Version: 1.0 Thomas, make sure you use PARADOX to create a .DBF file (dBase III format). You should be able to read that in ANALYSIS. >I am having trouble importing files that originate in the Paradox (.db) >format. I have attempted to export the .db to a .dbf (3&4), however >epiinfo will not accept this. Epiinfo did accept this .db file as a fixed .txt >file. After this I created the .qes file to match the new .rec file I just >imported from the .txt file. Next I attempted to revise and update the .rec >file with the new .qes file. It did not work. Days later, I attempted to >import other .db files (as fixed .txt files) with no success at all. The >inconsistency is baffling. I'm thinking parodox is just incompatible with >epiinfo. Allow me to provide further evidence for this thinking. > One week ago, I successfully imported a file that originated in .dbf >format. I also developed the .qes, after importing, and was successful >revising and updating the .rec file from the new .qes. I have also >attempted these same procedures on other computers in my office with >the same results. > One other side note. Two days ago, Epiinfo would not import the file >that originated as a .dbf file. However, the first thing the next day, I was >successful in importing this same file. (possible human error). At this >point I am unable to import original paradox .db files, as .dbf or .txt files. > I would greatly appreciate any supportive suggestions. > >Tom -- Mark Myatt ========================================================================= Date: Thu, 11 Feb 1999 09:19:47 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: Problem with a loop In-Reply-To: <36C29AB6.BC4EBF1E@online.no> MIME-Version: 1.0 Torleif Ruud writes: >To more experienced users of EPi Info, > >I am not succeeding in getting the subroutine SLOYFE to work >as a loop (repeat it self) and do not understand what is >wrong. I am thankful for help. There appears to be some problems with the code ... >read origfile.rec >let mnd=0 >* >if (((d1+(30*mnd))if (((d1+(30*mnd))<=fd) and (fd<(d2+(30*mnd))) and >((d2+(30*mnd))<=td)) \ > then atend=0 >if (((d1+(30*mnd))>=fd) and ((d2+(30*mnd))<=td)) then >atend=erved >if (((d1+(30*mnd))>=fd) and ((d2+(30*mnd))>td) and >(td>=(d1+(30*mnd)))) \ > then atend=til >if (((d1+(30*mnd))>td) and ((d2+(30*mnd))>td)) then atend=0 >select atend > 0 >route newfile1.rec >write recfile >select >GOTO SLOYFE ^^^^^^^^^^^^ You can probably remove this line as control passed to the line following the label SLOYFE anyway. >:SLOYFE >let mnd = (mnd + 1) >if (((d1+(30*mnd))if (((d1+(30*mnd))<=fd) and (fd<(d2+(30*mnd))) and >((d2+(30*mnd))<=td)) \ > then atend=0 >if (((d1+(30*mnd))>=fd) and ((d2+(30*mnd))<=td)) then >atend=erved >if (((d1+(30*mnd))>=fd) and ((d2+(30*mnd))>td) and >(td>=(d1+(30*mnd)))) \ > then atend=til >if (((d1+(30*mnd))>td) and ((d2+(30*mnd))>td)) then atend=0 >select atend > 0 >route newfile2.rec >write recfile >select >dos merge newfile1.rec newfile2.rec newfile3.rec 1 >erase newfile1.rec >erase newfile2.rec >copy newfile3.rec newfile1.rec >erase newfile3.rec >if mnd < 5 then RETURN ^^^^^^^ This is probably better as GOTO SLOYFE The IF command should be IMMEDIATE IF >if mnd = 5 then GOTO ENDIT The IF command should be IMMEDIATE IF > >:ENDIT >close origfile.rec >QUIT > Hope that helps ... here is some code that lops OK for me ... type "MUAC,Sensitivity, Specificity" define cutoff ##.# global define binarymuac cutoff = 17.0 :loop if muaca <= cutoff then binarymuac = "+" else binarymuac = "-" report ss.rpt cutoff = cutoff + 0.5 immediate if cutoff <= 30.0 then goto loop route screen -- Mark Myatt ========================================================================= Date: Thu, 11 Feb 1999 05:16:49 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert Smith Subject: unsubscribe MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msCD6C61375017D13660640889" This is a cryptographically signed message in MIME format. --------------msCD6C61375017D13660640889 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit unsubscribe Robert Smith --------------msCD6C61375017D13660640889 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIILwYJKoZIhvcNAQcCoIIIIDCCCBwCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC Bp0wggQcMIIDhaADAgECAhASizUuO36v/MPWCcR7ccA6MA0GCSqGSIb3DQEBBAUAMGIxETAP BgNVBAcTCEludGVybmV0MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE0MDIGA1UECxMrVmVy aVNpZ24gQ2xhc3MgMSBDQSAtIEluZGl2aWR1YWwgU3Vic2NyaWJlcjAeFw05ODA0MjEwMDAw MDBaFw05OTA0MjEyMzU5NTlaMIIBGDERMA8GA1UEBxMISW50ZXJuZXQxFzAVBgNVBAoTDlZl cmlTaWduLCBJbmMuMTQwMgYDVQQLEytWZXJpU2lnbiBDbGFzcyAxIENBIC0gSW5kaXZpZHVh bCBTdWJzY3JpYmVyMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvQ1BT IEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk2MTMwMQYDVQQLEypEaWdpdGFsIElEIENs YXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxFTATBgNVBAMTDFJvYmVydCBTbWl0aDEg MB4GCSqGSIb3DQEJARYRc21pdGhyQGloMjAwMC5uZXQwXDANBgkqhkiG9w0BAQEFAANLADBI AkEA3nZ5upbUnd67HFb+z3C/6Dcbzwyl//lqcbHZw0mCu7zZ7LxfwcSoeYRYePogW4e89xjM 08T1hWCwaH0zU1zbjQIDAQABo4IBXTCCAVkwCQYDVR0TBAIwADCBrwYDVR0gBIGnMIAwgAYL YIZIAYb4RQEHAQEwgDAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQ UzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BT IGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24AAAAAAAAw EQYJYIZIAYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5 Mjk4NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjIx NDFiZWFkYjNjYzVmZjgyMWVhZTZkZjBkMjExNDk5YWJjYmI0NmUyZTc5ZjY1NDEwDQYJKoZI hvcNAQEEBQADgYEAW7SpsnetutknwlsiVpKhxBuVAxD7G/91pBw+KTi5Xm1kTZReLNOWONml udtozFNiyUaj5VVgk17b8xI8GYupDKu0MQZSy63DEoommihGjTlU2WU7OltWaOugGqME/y6S V3acLReJOUFnMwv/RzH5vCJ5P92YGszSO4UJPIIQkU0wggJ5MIIB4qADAgECAhBSHzUd8nB+ ACu+ylmHBNU5MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJp U2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0 aW9uIEF1dGhvcml0eTAeFw05NjA2MjcwMDAwMDBaFw05OTA2MjcyMzU5NTlaMGIxETAPBgNV BAcTCEludGVybmV0MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE0MDIGA1UECxMrVmVyaVNp Z24gQ2xhc3MgMSBDQSAtIEluZGl2aWR1YWwgU3Vic2NyaWJlcjCBnzANBgkqhkiG9w0BAQEF AAOBjQAwgYkCgYEAthSmz03QBQ3YyiPQb6q0KZJjjiz4b5bXLp12SxGxNo1XycP9HMa6/h4I ujPKleq+41vNBqi3eR1EKu1z8rFSg2gQcGSR1z5r+fddnRRDm26XRZiBR9Ety927ctdMP3Gq 4kDyVDm8Fu7PfOy62z9sKrMWsYYSna6TNNW41dD3PqkCAwEAAaMzMDEwDwYDVR0TBAgwBgEB /wIBATALBgNVHQ8EBAMCAQYwEQYJYIZIAYb4QgEBBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GB AMH69wLnV8oRdcacDPord0+HRRc749LB2g9YOY6ulZkDoaihOP55mpMXC5eGOcfKaDRmu8eI RfbIDAXuvpcl7+DUbuR/nXZczn26FKKuC5/7Z1tIpWclrxlkiPZy2CknqjcSarEoryeDGGVs je1Ank3EeKiG7OksUL+m+Q3bsKZKMYIBWjCCAVYCAQEwdjBiMREwDwYDVQQHEwhJbnRlcm5l dDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNDAyBgNVBAsTK1ZlcmlTaWduIENsYXNzIDEg Q0EgLSBJbmRpdmlkdWFsIFN1YnNjcmliZXICEBKLNS47fq/8w9YJxHtxwDowCQYFKw4DAhoF AKB9MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTk5MDIxMTEx MTY1MVowHgYJKoZIhvcNAQkPMREwDzANBggqhkiG9w0DAgIBKDAjBgkqhkiG9w0BCQQxFgQU +GO5gitqUgxySElbgUwxK+lrwXwwDQYJKoZIhvcNAQEBBQAEQIIda/9h+5j5//oK2ycMMmYg /3xUk4av4FRWCk/Q31zLLhs0/2IaWCghE+srket4CEYUXdW0FVnXGRIQKjUyM5k= --------------msCD6C61375017D13660640889-- ========================================================================= Date: Thu, 11 Feb 1999 14:18:26 -0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Lucas Gonzalez Santa Cruz Subject: Re: Colombia, nutrition, help needed MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="---- =_NextPart_000_01BE55C9.661B3880" ------ =_NextPart_000_01BE55C9.661B3880 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re this message in Spanish (see below for original), please let me = translate- summarize: *Dear list members: *The following is a request for help with a nutritional status = surveillance system, *that will be set up with EpiInfo, in the "coffe area" in Colombia. *I [Pilar, from Colombia] will be representing the University in a = counseling role. *She would like advice [from someone in the list or colleagues] about: *- information system in catastrophes. *- significant [important] variables for complementing nutritional = status. *[I understand she means variables other than the nutritional ones - but *I'm no expert so I'm not sure.] *Thanks for your help with this from the "damnificados", Her address is below. Hope this helps, Lucas Epid Surveillance - Canary Islands -*-*-* HERE's the message: Reciban todos un cordial saludo. Despues de los hechos ocurridos en la zona cafetera Colombiana, pretendemos disenar y poner a funcionar un sistema de vigilancia del estado nutricional, en plataforma epiinfo. Yo estare representado a la universidad, que brindara la asesoria correspondiente. Quisiera saber si alguno de ustedes tiene experiencia = en sistemas de informacion en tragedias y si podrian, a la vez, asesorarme acerca de las variables mas significativas para complementar = la informacion antropometrica. Agradezco la atencion prestada a la presente y las demostraciones de solidaridad para con los damnificados. Atentamente, Pilar Serrano Galvis Departamento de Nutrici=F3n y Bioqu=EDmica Faculta de Ciencias B=E1sicas Tel. 3 208320 Ext 4063 o 4124 Fax. 2 887932 ------ =_NextPart_000_01BE55C9.661B3880 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+Ih4OAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAENgAQAAgAAAAIAAgABBJAG ADgBAAABAAAADAAAAAMAADADAAAACwAPDgAAAAACAf8PAQAAAFEAAAAAAAAAgSsfpL6jEBmdbgDd AQ9UAgAAAABFcGkgSW5mbyBEaXNjdXNzaW9uIEdyb3VwAFNNVFAARVBJLUlORk9ATElTVFNFUlYu Q0RDLkdPVgAAAAAeAAIwAQAAAAUAAABTTVRQAAAAAB4AAzABAAAAGgAAAEVQSS1JTkZPQExJU1RT RVJWLkNEQy5HT1YAAAADABUMAQAAAAMA/g8GAAAAHgABMAEAAAAcAAAAJ0VwaSBJbmZvIERpc2N1 c3Npb24gR3JvdXAnAAIBCzABAAAAHwAAAFNNVFA6RVBJLUlORk9ATElTVFNFUlYuQ0RDLkdPVgAA AwAAOQAAAAALAEA6AQAAAAIB9g8BAAAABAAAAAAAAAOHNwEIgAcAGAAAAElQTS5NaWNyb3NvZnQg TWFpbC5Ob3RlADEIAQSAAQAlAAAAUkU6IENvbG9tYmlhLCBudXRyaXRpb24sIGhlbHAgbmVlZGVk AMkMAQWAAwAOAAAAzwcCAAsADgASABoABAAhAQEggAMADgAAAM8HAgALAA4ADwATAAQAFwEBCYAB ACEAAAAxN0VCMzIwRDlFQzFEMjExODgxMjQ0NDU1MzU0MDAwMADHBgEDkAYA5AYAABIAAAALACMA AAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAEAAOQBARAtkyVW+AR4AcAABAAAAJQAAAFJFOiBD b2xvbWJpYSwgbnV0cml0aW9uLCBoZWxwIG5lZWRlZAAAAAACAXEAAQAAABYAAAABvlXJZAsNMusY wZ4R0ogSREVTVAAAAAAeAB4MAQAAAAMAAABNUwAAHgAfDAEAAAAZAAAAV2luZG93cy9BRE1JTklT VFJBL0xVQ0FTAAAAAAMABhAW34xXAwAHEBcFAAAeAAgQAQAAAGUAAABSRVRISVNNRVNTQUdFSU5T UEFOSVNIKFNFRUJFTE9XRk9ST1JJR0lOQUwpLFBMRUFTRUxFVE1FVFJBTlNMQVRFLVNVTU1BUkla RToqREVBUkxJU1RNRU1CRVJTOipUSEVGT0xMAAAAAAIBCRABAAAAVwUAAFMFAABYCAAATFpGdZoa oFb/AAoBDwIVAqgF6wKDAFAC8gkCAGNoCsBzZXQyNwYABsMCgzIDxQIAcHJCcRHic3RlbQKDM3cC 5AcTAoB9CoAIzwnZO/EWDzI1NQKACoENsQtgwG5nMTAzNAr7FFENC/JjAEAH8GUgdGjFBAAgB4Fz YWcbAAuAhwYACrADAHNoICgRsPkbAGJlFaAH4AIQBcAFsIxpZwuAB0ApLCALUPRlYRGwIB5QBUAH gBsQLnIAcQtgE9AtCoVzdcZtAMAFEHplOgqFCoXsKkQeYAXAbAQAHtIG0MUEkHMgxipUaBsAAhA2 bB0RC4BnG+AEIGEgPRYQcQpQIjEdUiNwbHDOIAPwGyAkYW51HyAlsJ5pAiAHQCAgAZB0dQQgsSAw cnZlAxAY8WMbAPpzE7MsIUYbIB+AJZEjwBcc4SAgHsF1JYVFcGl8SW4CEB4gG/EbIBsAIt8FoA3Q GwAKwB5gIhviCFAXFaAG0AcwLiFGSSBbvlADEArAHiADUiyHXSlHfxYQE1AHkAnwJmAkEStSVe8D ACdwEaAlsHkb4iRwBaB+dQCAHQAkAgNgHlAtF1OlI3F3CGBsZCIBayvhqGR2aSfhWy5DcwNw/mUC IBvTK1IiEwWxFYEeUV5nJMEvEAGgCGB0ItctvxvhHVEAwCZiKAUb4mMfgNMecB8gb3AjcHMtFzgQ dQCQZwMAZjRgAHAFQFvdB3BwFbE7gS8QdiBxAaD/HlAEIB1SBaA74B5QB4AwJPsmHzpIWy2gMeAE gSbRQDDfICAjcQeABiI8iG8rUQXAvykBKzQ+SjVBBCA4EGI+UAUtJycucG5vIGV47nAEkAVANQAg RORFoQhwrTKgXSLoAHBrPQR5CGGPJUkbIy5DK1NkYW07NLBkb3MiKHYKhUhCQX00MGQv4QQgG0Ec 8y0WSJc6ABsFJVJzSr1MdTmQbnMKhSqRM8BTJ1o4EEP3AHAKwDFQSR9hQDBPhgqFFi04AFMRIEuQ RVJF/icEICtSG3UgxhnNE1BCEMcFkAVAGvBjaWJCkgRwf0qAQBExsQsgBzEgIAdAdU9KcC0WCoUh wHNwJMEgPw2wHqBXQSNwEXBXQW9jvwhwBRBXMgnwHqAkcHomgf85gSvQE9AfMCyHHeAodi/R/xPQ QDEEYFnRBAAJ8ArBMVD/O/A1UEvBHUAx4FawJoEFwP9XcQCQE8IkcFnxNFAdwCey+wcwWeFsCoUk 0UphPjRf4/5sHiBbcQtRAZA4U0VAKqD7ODJYjVlFMSbRFhAvqGKy3yRwW6Ex4DDkSeBkHiAksf8c 4AUQQDAKwGdzHnE1AAch/wqFBaEv4V8xV9AwETKgU2D8UXUEAAiRJHAboCKROvH9JGBsNtBFIVnx JxAT0A2w/1PRayEbAEVTayFhognwH8b/YJRZ0zg1X+JbYh8hG8BX0f8EIDFQbJE78EwAXREeIGdz /Sdweih2aZQKwB7xANAEkP85kFnjb/E8iG/iOwcmYDyA/wQgCrExoj2GIeJqBnBaO4HfOfE1EWMS LQcKhUEJwDQw/3MgBaBpU14BcMMv0mKhaXH/W5Iv1RsAMVB1El4zHyFf4v9Zwx/GBvBoMVsRNDB3 FluBv15iSfl6fl4BAZA9wmVKvd8KhS3TBlIfMUUwRwdANFBfT4YhwAqxg5RtE05jBFzuJxRAA6Ax UEImcCSwiIDtCYBtO2EKhUYA0DOgAZCtWeJDbpQEIEKJUTEAkE1PaFQdAGtwMyAB0DgWMwHQKoB4 BUA0MDZDjOBFMDQxMjSJ13jDa3AR4Dg4NzmNMCDcLxl/jUGQFRUxAJJwAAMAEBAAAAAAAwAREAAA AABAAAcwIC9v9MhVvgFAAAgwIC9v9MhVvgEeAD0AAQAAAAUAAABSRTogAAAAAFQQ ------ =_NextPart_000_01BE55C9.661B3880-- ========================================================================= Date: Thu, 11 Feb 1999 21:04:09 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Torleif Ruud Subject: On loops MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks to Mark and Arnt Ole for help with my problem with a loop. It worked when I put in IMMEDIATE. But there were some problems with the submission of my questions to the list, - I got several error messages, but still it was posted. Best regards, Torleif Ruud -- Torleif Ruud, Kreklingen 1, 6860 Sandane, Norway Tel +47 5786 5683 (home office) Fax +47 5786 5943 (home office) E-mail: torleif@online.no http://home.sol.no/~torleif/index.htm ========================================================================= Date: Thu, 11 Feb 1999 23:32:55 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Jens M. Lauritsen" Subject: Re: importing paradox files Comments: cc: Thomas Fox In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Many "obscure" errors have been seen to and from paradox files over the years. Just to mention one was an error in spss after having imported into spss a file, which by paradox was exported as epi-info. But the error was only in the danish translation of paradox and not if you used the US version. A recent development would be to try out an axcellent conversion program, which I believe you can try out in a free trial period. The name is StatTransfer Find a link to "StatTransfer" at www.stata.com We have changed policy here: from: epiinfo for dataentry and simple analyses and spss for further analysis to: continued use of epi-info inchanged and stata for further analysis I have found this change a relevant solution to many of the drawbacks of spss and excellent for analysis of biostatistical/epidemiological data. The only current drawback to the solution is that "recent" ph.d. students are reluctant to use the "dos 8.xxx" file naming convention. (They blame errors on epi-info instead of blaming their lack of experience). For this reason I have earlier on this list suggested epi-2000 to be as simple and yet complete as the current version of epi-info, but with the enhancements and easier control of printing, graphs etc. in the modern operating systems. Kindly Jens M. Lauritsen, Senior Registrar, PhD. Fyns Amt (County of Fyn), Health Service Division Initiative for Accident Prevention Oerbaekvej 100, DK5220 Odense Soe, Denmark Phone: +45 65561241 Fax: +45 6556 1205 e-mail: JML@dadlnet.dk (or: jel@sus.fyns-amt.dk) ========================================================================= Date: Fri, 12 Feb 1999 09:22:13 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Bounced mails on this list. In-Reply-To: <36C337B9.3BE1371B@online.no> MIME-Version: 1.0 Torleif Ruud writes: >Thanks to Mark and Arnt Ole for help with my problem with a >loop. >It worked when I put in IMMEDIATE. >But there were some problems with the submission of my >questions to the list, - I got several error messages, but >still it was posted. That's because some of the address on the list are dead and the list administrator has yet too get round to cleaning them out. Mark -- Mark Myatt ========================================================================= Date: Fri, 12 Feb 1999 12:37:53 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Bounced mails on this list. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We are trying, but sometimes we get temporary bounces from people who have automatic notices that they are away on vacation. -----Original Message----- From: Mark Myatt [mailto:mark@MYATT.DEMON.CO.UK] Sent: Friday, February 12, 1999 1:22 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Bounced mails on this list. Torleif Ruud writes: >Thanks to Mark and Arnt Ole for help with my problem with a >loop. >It worked when I put in IMMEDIATE. >But there were some problems with the submission of my >questions to the list, - I got several error messages, but >still it was posted. That's because some of the address on the list are dead and the list administrator has yet too get round to cleaning them out. Mark -- Mark Myatt From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9902A" ========================================================================= Date: Mon, 1 Feb 1999 09:24:56 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Arnold Bosman Subject: EPI INFO 6.04c under Windows NT? MIME-Version: 1.0 Content-Type: text/plain Hello Discussion group, Does anyone have experience with Epi Info version 6.04c under Windows NT? Our system-operator will switch from Windows for Workgroups 3.11to Windows NT during the next couple of months. Our Epi Info applications work well at this moment: Multi-user data entry and analysis present no problems. I do not know what to expect when the system changes to Windows NT. Can anyone advice me or share their experience with me? Thanks Arnold Bosman, medical epidemiologist Regional Public Health Service Rotterdam ========================================================================= Date: Mon, 1 Feb 1999 09:43:45 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: problem opening REC file in ANALYSIS Comments: To: rhassad@lha.gsbc.com In-Reply-To: MIME-Version: 1.0 RHassad writes: >Hi Dean, > >I urgently need some help. I have an EXCEL data set and would like to >perform analysis in Epi Info--- How do I inport the data? Save the file in EXCEL as a dbase III file. Analysis will read it directly. -- Mark Myatt ========================================================================= Date: Mon, 1 Feb 1999 09:45:41 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: EPI INFO 6.04c under Windows NT? In-Reply-To: <179AC2A1314AD211932300805FCCA41207B2F5@proxy.ggd.rotterdam.nl> MIME-Version: 1.0 Arnold Bosman writes: >Hello Discussion group, > > >Does anyone have experience with Epi Info version 6.04c under Windows NT? >Our system-operator will switch from Windows for Workgroups 3.11to Windows >NT during the next couple of months. Our Epi Info applications work well at >this moment: Multi-user data entry and analysis present no problems. > >I do not know what to expect when the system changes to Windows NT. Can >anyone advice me or share their experience with me? E-mail: P.Atkinson@cdsc.nthames.nhs.uk He has load of experience -- Mark Myatt ========================================================================= Date: Mon, 1 Feb 1999 14:15:42 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: Re: Domeasx _ Win95 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >X-POP3-Rcpt: sapsalta@ciunsa >X-Mailer: Internet Mail Service (5.5.2232.9) >Date: Fri, 29 Jan 1999 16:50:44 -0500 >Reply-To: Epi Info Discussion Group >Sender: Epi Info Discussion Group >From: "Dean, Andrew G." >Subject: Re: Domeasx _ Win95 >To: EPI-INFO@LISTSERV.CDC.GOV > >Does it work if you tell Windows 95 to reboot in DOS mode? > > I try to do it and work fine. But my system is in a LAN, and only run in LAN if run inside win95 and not in DOS mode. > > I upgrade operative system to win95. Now, a epi-info system >who use > DOMEASX not calculate anthropometric variables. > How i can resolve it? > Thank in advance > > Enrique Finetti > Hospital Materno Infantil > Salta - Argentina > sapsalta@ciunsa.edu.ar > > Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Mon, 1 Feb 1999 03:51:09 -0300 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: julietar MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01BE4D96.1A3A15C0" This is a multi-part message in MIME format. ------=_NextPart_000_000F_01BE4D96.1A3A15C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable suscribe epi info ribhvelez ------=_NextPart_000_000F_01BE4D96.1A3A15C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
suscribe epi info=20 ribhvelez
------=_NextPart_000_000F_01BE4D96.1A3A15C0-- ========================================================================= Date: Mon, 1 Feb 1999 15:32:39 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Bennett, Diane" Subject: FW: too much email MIME-Version: 1.0 Content-Type: text/plain > -----Original Message----- > From: Bennett, Diane > Sent: Monday, February 01, 1999 3:31 PM > To: 'epiinfor@listserv.cdc.gov' > Subject: too much email > > I tried to subscribe to the discussion group through the web page and > failed, and sent a message to say that I had no success. Someone then > sent me a message to say that I was now on the list. I am now getting > ridiculous messages that are not part of any discussion -- such as this > one from someone called julietar:" suscribe epi info ribhvelez". Is > having to see these really part of the discussion group? What I wanted > was to be able to log on and look at the discussions, not to receive > people's requests for subscriptions. What have I done wrong, and how can > I fix it? Thanks, Di Bennett ========================================================================= Date: Mon, 1 Feb 1999 13:12:11 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Sbragia, Ralph" Subject: Re: too much email MIME-Version: 1.0 Content-Type: text/plain Diane, You may or may not get several replies to your question, however, I am not sending this to the listserver in order to not crowd everyone's mail boxes with an off topic post. The message from julietar was from all indications an attempt to subscribe to the mailing list. Unfortunately, she?? sent her request to the actual list rather than the listserver. This happens rather regularly on most automated mailing lists that are not moderated whenever someone new to the process misunderstands the instructions for joining the list. One other item of note, from julietar's email address you can tell that it is an 'offshore' address (the .AR at the end). ".AR" is a domain from Argentina, so English may not even be this person's primary language. One last item, no matter how much mail you get, don't forget the most important email tool at your disposal: the key. Best Regards, Ralph G. Sbragia, CSP, CHST Construction Safety Department Los Angeles County Metropolitan Transportation Authority sbragiar@mta.net (work) or sbragiar@deltanet.com (home) -----Original Message----- From: Bennett, Diane [mailto:dib1@CDC.GOV] Sent: Monday, February 01, 1999 12:33 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: FW: too much email > -----Original Message----- > From: Bennett, Diane > Sent: Monday, February 01, 1999 3:31 PM > To: 'epiinfor@listserv.cdc.gov' > Subject: too much email > > I tried to subscribe to the discussion group through the web page and > failed, and sent a message to say that I had no success. Someone then > sent me a message to say that I was now on the list. I am now getting > ridiculous messages that are not part of any discussion -- such as this > one from someone called julietar:" suscribe epi info ribhvelez". Is > having to see these really part of the discussion group? What I wanted > was to be able to log on and look at the discussions, not to receive > people's requests for subscriptions. What have I done wrong, and how can > I fix it? Thanks, Di Bennett ========================================================================= Date: Mon, 1 Feb 1999 13:28:59 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Sbragia, Ralph" Subject: opps MIME-Version: 1.0 Content-Type: text/plain My apologies to Diane and the list, I could have sworn I changed the email address before I sent that out......Ah well, it's only Monday. Regards, Ralph G. Sbragia, CSP, CHST Construction Safety Department Los Angeles County Metropolitan Transportation Authority sbragiar@mta.net (work) or sbragiar@deltanet.com (home) ========================================================================= Date: Mon, 1 Feb 1999 16:54:10 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Domeasx _ Win95 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We will have a Windows version of the nutritional data entry program soon. -----Original Message----- From: Enrique Finetti [mailto:sapsalta@UNSA.EDU.AR] Sent: Sunday, January 31, 1999 10:16 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: Domeasx _ Win95 >X-POP3-Rcpt: sapsalta@ciunsa >X-Mailer: Internet Mail Service (5.5.2232.9) >Date: Fri, 29 Jan 1999 16:50:44 -0500 >Reply-To: Epi Info Discussion Group >Sender: Epi Info Discussion Group >From: "Dean, Andrew G." >Subject: Re: Domeasx _ Win95 >To: EPI-INFO@LISTSERV.CDC.GOV > >Does it work if you tell Windows 95 to reboot in DOS mode? > > I try to do it and work fine. But my system is in a LAN, and only run in LAN if run inside win95 and not in DOS mode. > > I upgrade operative system to win95. Now, a epi-info system >who use > DOMEASX not calculate anthropometric variables. > How i can resolve it? > Thank in advance > > Enrique Finetti > Hospital Materno Infantil > Salta - Argentina > sapsalta@ciunsa.edu.ar > > Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Tue, 2 Feb 1999 14:00:03 -0500 Reply-To: rhassad@lha.gsbc.com Sender: Epi Info Discussion Group From: RHassad Subject: SAVING RECODED VARIABLES IN EPI INFO MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Thanks for all the help to my previous question. How do I save info. (eg. a recoded variable) while in analysis mode of Epi Info? ------------- Original Text From: "Mark Myatt" , on 2/1/99 4:45 AM: Arnold Bosman writes: >Hello Discussion group, > > >Does anyone have experience with Epi Info version 6.04c under Windows NT? >Our system-operator will switch from Windows for Workgroups 3.11to Windows >NT during the next couple of months. Our Epi Info applications work well at >this moment: Multi-user data entry and analysis present no problems. > >I do not know what to expect when the system changes to Windows NT. Can >anyone advice me or share their experience with me? E-mail: P.Atkinson@cdsc.nthames.nhs.uk He has load of experience -- Mark Myatt ========================================================================= Date: Tue, 2 Feb 1999 14:36:25 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Re: SAVING RECODED VARIABLES IN EPI INFO Comments: To: rhassad@lha.gsbc.com Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable So, you've discovered one of the most frustrating things about Epi/Info? = Actually, it's pretty nice to be able to hit F10 and start again once = you've really screwed up your data. You can save your work in analysis in = at least two ways. I'll include what I think is the easiest way since = I've got to run. RECODEd and DEFINEd variables can be saved by creating a new .REC file. = You do this by first ROUTEing the data to a new .REC file. For example... You've worked in ANALYSIS on a file called DISEASE.REC. You've created = DEFINEd and RECODEd variables. Type ROUTE C:\EPI6\FILES\DISEASE2.REC = (customize to how you've organized your data files). When you hit enter = the OUTPUT prompt that usually reads "SCREEN" will contain your ROUTEd = path and filename. Next type WRITE RECFILE and include each variable you = want in the new file or a wildcard (*) to include all variables. When you = hit enter all the variables or the ones you choose in DISEASE.REC, = (including DEFINEd and RECODEd variables), will be saved in DISEASE2.REC = and you can READ and manipulate the new file just like any other .REC = file. Good luck >>> RHassad 02/02/99 12:00PM >>> Thanks for all the help to my previous question. How do I save info. (eg. a recoded variable) while in analysis mode of Epi Info? ------------- Original Text From: "Mark Myatt" , on 2/1/99 4:45 AM: Arnold Bosman writes: >Hello Discussion group, > > >Does anyone have experience with Epi Info version 6.04c under Windows NT? >Our system-operator will switch from Windows for Workgroups 3.11to = Windows >NT during the next couple of months. Our Epi Info applications work well at >this moment: Multi-user data entry and analysis present no problems. > >I do not know what to expect when the system changes to Windows NT. Can >anyone advice me or share their experience with me? E-mail: P.Atkinson@cdsc.nthames.nhs.uk=20 He has load of experience -- Mark Myatt ========================================================================= Date: Wed, 3 Feb 1999 10:42:00 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Lasater, Richard" Subject: Saving recorded variables MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable FROM:Lasater, Richard TO:epiinfo list CC: SUBJECT:Saving recorded variables PRIORITY: =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF You can also save the typed in syntax itself typing "save " = at the analysis command line.=20 The number lines saved can be altered by using the command "set = cmdstack =3D ##", the default is 20 (I think) but more is possible. "set cmdstack =3D ##" can also be placed in config.epi to make it your preference permanent. ========================================================================= Date: Wed, 3 Feb 1999 14:02:43 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Huet, Natalie" Subject: European Dates MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I have 2 variables DOB and EXAMDATE in my qes file. I would like the participant's age (in months) to be calculated when I enter the EXAMDATE. (i.e. How old is the person on the EXAMDATE?). All of the dates are in European Format. Thank you ========================================================================= Date: Wed, 3 Feb 1999 13:38:02 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Diana Echenique Subject: Re: European Dates Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Dear Natalie, The title of this e-mail is quite interesting "European Dates?". Oh well, = I have been getting all kind of e-mails and I am clueless of what they = are about. Please take me out of your list. I wish I could help = you...but you can help me...Take me off this List, Please! Thank you, Diana ========================================================================= Date: Wed, 3 Feb 1999 14:56:18 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: EPI Info Helpdesk Subject: Re: European Dates MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Hello Diana, Sorry about this. We will remove you from the list. Thanks Epi Info Technical Support -----Original Message----- From: Diana Echenique [mailto:DECHENIQ@DHH.STATE.LA.US] Sent: Wednesday, February 03, 1999 2:38 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: European Dates Dear Natalie, The title of this e-mail is quite interesting "European Dates?". Oh well, I have been getting all kind of e-mails and I am clueless of what they are about. Please take me out of your list. I wish I could help you...but you can help me...Take me off this List, Please! Thank you, Diana ========================================================================= Date: Wed, 3 Feb 1999 13:56:24 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Re: European Dates Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Are european dates formatted differently than MM/DD/YY or MM/DD/YYYY ? ========================================================================= Date: Wed, 3 Feb 1999 15:07:38 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Diana Echenique Subject: Re: European Dates Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I have no idea! Perhaps it is: 03 January, 1999. Di ========================================================================= Date: Wed, 3 Feb 1999 16:09:54 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Carl DeMarco Subject: Re: European Dates MIME-Version: 1.0 Content-Type: text/plain > Perhaps it is: 03 January, 1999. > yeah, right. but no comma. and numerically it'd be 03/01/99. so january 31 in eurodate would be 31/01/99. ya never know which format yer lookin at unless it's a date past the 12th. but we almost always use month first in this country. > -----Original Message----- > From: Epi Info Discussion Group [mailto:EPI-INFO@LISTSERV.CDC.GOV]On > Behalf Of Diana Echenique > Sent: Wednesday, February 03, 1999 4:08 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: European Dates > > > I have no idea! > > > Di > ========================================================================= Date: Wed, 3 Feb 1999 15:24:43 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Diana Echenique Subject: Re: European Dates Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Tel me one thing...What is it all about? I keep getting all of these = e-mails and I have no clue of what is going on and why am I receiving = them? Where do you work at? I am all confuse! Diana ========================================================================= Date: Wed, 3 Feb 1999 16:37:23 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Carl DeMarco Subject: Re: European Dates MIME-Version: 1.0 Content-Type: text/plain It's a list serve for people who use Epiinfo. We post questions to the list serve and they are automaically distibutd to other Epi users world wide who also subscribe to the list serve. This gives them the opportunity to see our questions and, if possible answer them, thereby solving problems people are having with Epi without the expense of long distance or international calls to the help desk. I keep all the questions and their answers in a separate file i created for the purpose in case i can't do something one day in Epi, and i know that the issue has been dealt with onthe list serve. i go to my file, find the question (or similar one) and then look at the responses. If you're doing a lot of work with Epiinfo, it is advisable to subscribe and read all the posts because they will inevitably be useful to you. > -----Original Message----- > From: Epi Info Discussion Group [mailto:EPI-INFO@LISTSERV.CDC.GOV]On > Behalf Of Diana Echenique > Sent: Wednesday, February 03, 1999 4:25 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: European Dates > > > Tel me one thing...What is it all about? I keep getting all > of these e-mails and I have no clue of what is going on and > why am I receiving them? Where do you work at? I am all confuse! > > Diana > ========================================================================= Date: Wed, 3 Feb 1999 17:02:26 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Bennett, Diane" Subject: Re: European Dates MIME-Version: 1.0 Content-Type: text/plain Probaby someone else has replied by now, but yes, in Europe we always use DD/MM/YY (or, now, DD/MM/YYYY). > -----Original Message----- > From: Matt Snell [SMTP:snellm@SLRMC.ORG] > Sent: Wednesday, February 03, 1999 3:56 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: European Dates > > Are european dates formatted differently than MM/DD/YY or MM/DD/YYYY ? ========================================================================= Date: Wed, 3 Feb 1999 16:06:54 -0600 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Diana Echenique Subject: Re: European Dates Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Thank you...I am going to start a file with all the questions. Di ========================================================================= Date: Wed, 3 Feb 1999 15:35:20 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Re: European Dates Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable You can create calculated fields in a couple of ways in epi/info. You can = have the field entered automatically while you're ENTERing data or you can = perform the calculations in ANALYSIS with a DEFINED variable. My = preference is the latter. Here is an example (I'll include tips as = paranthetical notes you don't get confused. READ your file DEFINE AGE ###.## (This will create a numberic field with two decimal = points. I like decimal points because I feel that I get a more accurate = picture of the person's age. Otherwise epi/info will round up) AGE=3D((EXAMDATE-DOB)/365)*12 (Parantheses are important. This will = return the age of the person in months) (If you want to save your work...) SAVE (Path and file name of your choice) .PGM (This will save up to the past 20 commands that you've typed in, unless = you were wise and SET CMDSTACK=3D100) The next time you READ the file and want to get the AGE, you will need to = RUN (your program).PGM (You may want to open your .PGM file in EPED and = clean up the extraneous commands before RUNning it). You can also set a calculated field to be filled while ENTERing the data. = I've got to run now, but may have some time to explain tomorrow if you're = interested. ========================================================================= Date: Wed, 3 Feb 1999 18:15:36 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Bennett, Diane" Subject: Re: European Dates MIME-Version: 1.0 Content-Type: text/plain Dear Epi-info technical support, I too would like to be removed from this list. If there is a way to look at the discussions occasionally, and to enter them when I have something useful to contribute, i would love to do that, but despite the usefullness of the delete key, I haven't the time at this point to read and delete, and the topic and the sender are not informative enough to let me know I don't have to read the message. Thanks for putting me on the list, but this is not what I wanted. Di B > -----Original Message----- > From: EPI Info Helpdesk [SMTP:epiinfo@CDC.GOV] > Sent: Wednesday, February 03, 1999 2:56 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: European Dates > > Hello Diana, > > Sorry about this. We will remove you from the list. > > Thanks > Epi Info Technical Support > > -----Original Message----- > From: Diana Echenique [mailto:DECHENIQ@DHH.STATE.LA.US] > Sent: Wednesday, February 03, 1999 2:38 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: European Dates > > > Dear Natalie, > > The title of this e-mail is quite interesting "European Dates?". Oh well, > I have been getting all kind of e-mails and I am clueless of what they are > about. Please take me out of your list. I wish I could help you...but > you > can help me...Take me off this List, Please! > > Thank you, > > > Diana ========================================================================= Date: Wed, 3 Feb 1999 22:44:21 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Bredin Subject: CRHA Epi Info Users MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit My apologies to non Calgary subscribers. If you work within the CRHA (Calgary Regional Health Authority) and are using Epi Info, please contact Mark.Bredin@CRHA-Health.Ab.Ca regarding a Epi Info Y2K project. Regards, Mark Bredin ========================================================================= Date: Thu, 4 Feb 1999 11:10:34 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: European Dates In-Reply-To: MIME-Version: 1.0 Matt Snell writes: >Are european dates formatted differently than MM/DD/YY or MM/DD/YYYY ? Yes, they have the day first
and
which seems logical to us old-worlders. Mark -- Mark Myatt ========================================================================= Date: Thu, 4 Feb 1999 11:05:00 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: European Dates In-Reply-To: MIME-Version: 1.0 Huet, Natalie writes: >I have 2 variables DOB and EXAMDATE in my qes file. I would like the >participant's age (in months) to be calculated when I enter the EXAMDATE. >(i.e. How old is the person on the EXAMDATE?). All of the dates are in >European Format. The commands: define days ##### days = examdate - dob gives the age in days. thisL define years ##.# years = (examdate - dob) / 365.25 Hope that helps. Mark -- Mark Myatt ========================================================================= Date: Fri, 5 Feb 1999 11:11:33 -0800 Reply-To: gdaurat@club-internet.fr Sender: Epi Info Discussion Group From: Gérald DAURAT Subject: Re: European Dates MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Huet, Natalie wrote: > > I have 2 variables DOB and EXAMDATE in my qes file. I would like the > participant's age (in months) to be calculated when I enter the EXAMDATE. > (i.e. How old is the person on the EXAMDATE?). All of the dates are in > European Format. > > Thank you Dear Nathalie You can actually do this, though it's not recommended by data base normalisation rules (i.e. you shouldn't keep variables than can be calculated using other variables) The right way would be to calculate ages in ANALYSIS. I suppose you prefer to calculate it when entering data on the field to help health workers. You could add an age ### variable to your qes file then restructure rec files using enter option 3 then in Check, go to the variable called examdate press F9 and within the block, type LET AGE = (examdate - DOB) div 365.25 then press esc In addition, you may go to age field, press F9 and add the following expression NOENTER then press esc again and F10 to quit. answer Y to the question "WRite to disk" (or similar) The result will be : the value of age will automaticaly appear when entering the dates and you'll be unable to change this value manually by entering another age. Dates format, either american or european, doesn't matter at all. There are other better solutions in order to display age without recording it, but it's a bit more tricky. Hope that helps. G Daurat Montpellier France ========================================================================= Date: Fri, 5 Feb 1999 15:23:23 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: European Dates MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Define agemo #### Agemo = (examdate-DOB)/30 This is approximate, or you can use the average length of a month (I never averaged it out) rather than 30. -----Original Message----- From: Huet, Natalie [mailto:ndh6@CDC.GOV] Sent: Wednesday, February 03, 1999 11:03 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: European Dates I have 2 variables DOB and EXAMDATE in my qes file. I would like the participant's age (in months) to be calculated when I enter the EXAMDATE. (i.e. How old is the person on the EXAMDATE?). All of the dates are in European Format. Thank you From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9901E" ========================================================================= Date: Fri, 29 Jan 1999 16:49:31 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: problem opening REC file in ANALYSIS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" It is possible to create a questionnaire so huge ( > 500 or 600 lines) or with total field size > 2000 characters, that Analysis can't read it. Enter will warn if this is the case, however. -----Original Message----- From: e c groh [mailto:ecgroh@JUNO.COM] Sent: Wednesday, January 27, 1999 7:43 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: problem opening REC file in ANALYSIS Sandra: did you create a new rec file from the qes file? You have to do that first, then exit and return via enter or enterx and THEN begin data entry. e.c.groh On Wed, 27 Jan 1999 14:07:01 +0530 sandra writes: >Dear All, > >I have a very strange problem. I have created questionnaire .qes and = >have entered data using the ENTER programme, but I cannot read the >.rec = >file using analysis. > >I can see the data in the ENTER programme and by opening the file in = >EPED but I cannot read it in ANALYSIS. > >Has any one faced a similar problem ? Are there any suggestions. > >Thanks in advance > >Sandra > ========================================================================= Date: Fri, 29 Jan 1999 16:50:44 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Domeasx _ Win95 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Does it work if you tell Windows 95 to reboot in DOS mode? -----Original Message----- From: Enrique Finetti [mailto:sapsalta@UNSA.EDU.AR] Sent: Tuesday, January 26, 1999 5:11 PM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Domeasx _ Win95 I upgrade operative system to win95. Now, a epi-info system who use DOMEASX not calculate anthropometric variables. How i can resolve it? Thank in advance Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Fri, 29 Jan 1999 17:12:35 -0500 Reply-To: rhassad@lha.gsbc.com Sender: Epi Info Discussion Group From: RHassad Subject: Re: problem opening REC file in ANALYSIS MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Hi Dean, I urgently need some help. I have an EXCEL data set and would like to perform analysis in Epi Info--- How do I inport the data? ------------- Original Text From: "Dean, Andrew G." , on 1/29/99 4:49 PM: It is possible to create a questionnaire so huge ( > 500 or 600 lines) or with total field size > 2000 characters, that Analysis can't read it. Enter will warn if this is the case, however. -----Original Message----- From: e c groh [mailto:ecgroh@JUNO.COM] Sent: Wednesday, January 27, 1999 7:43 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Re: problem opening REC file in ANALYSIS Sandra: did you create a new rec file from the qes file? You have to do that first, then exit and return via enter or enterx and THEN begin data entry. e.c.groh On Wed, 27 Jan 1999 14:07:01 +0530 sandra writes: >Dear All, > >I have a very strange problem. I have created questionnaire .qes and = >have entered data using the ENTER programme, but I cannot read the >.rec = >file using analysis. > >I can see the data in the ENTER programme and by opening the file in = >EPED but I cannot read it in ANALYSIS. > >Has any one faced a similar problem ? Are there any suggestions. > >Thanks in advance > >Sandra > ========================================================================= Date: Fri, 29 Jan 1999 17:30:18 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Bennett, Diane" Subject: Re: problem opening REC file in ANALYSIS MIME-Version: 1.0 Content-Type: text/plain It's true about huge questionnaires, but I have found that if this is true, the dataset created by the huge questionnaire is usually so huge that you can't read the dataset in EPED either, or so I've found. Di > -----Original Message----- > From: Dean, Andrew G. [SMTP:agd1@CDC.GOV] > Sent: Friday, January 29, 1999 4:50 PM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: problem opening REC file in ANALYSIS > > It is possible to create a questionnaire so huge ( > 500 or 600 lines) or > with total field size > 2000 characters, that Analysis can't read it. > Enter will warn if this is the case, however. > > -----Original Message----- > From: e c groh [mailto:ecgroh@JUNO.COM] > Sent: Wednesday, January 27, 1999 7:43 AM > To: EPI-INFO@LISTSERV.CDC.GOV > Subject: Re: problem opening REC file in ANALYSIS > > Sandra: > > did you create a new rec file from the qes file? You have > to > do that > first, then exit and return via enter or enterx and THEN > begin data > entry. > > e.c.groh > > On Wed, 27 Jan 1999 14:07:01 +0530 sandra > writes: > >Dear All, > > > >I have a very strange problem. I have created > questionnaire > .qes and = > >have entered data using the ENTER programme, but I cannot > read the > >.rec = > >file using analysis. > > > >I can see the data in the ENTER programme and by opening > the file in = > >EPED but I cannot read it in ANALYSIS. > > > >Has any one faced a similar problem ? Are there any > suggestions. > > > >Thanks in advance > > > >Sandra > > From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9901D" ========================================================================= Date: Fri, 22 Jan 1999 10:22:39 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Problems with EpiTable and EpiNut on Fast Machines Fixed MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" EpiNut and EpiTable in version 6.04 b-to-c and 6.04b fail to run on some fast Pentium machines due to an error in the compiler that causes a timing loop to exceed the allowed value for an integer. The telltale symptom is an Error 200 message immediately on attempting to run the programs. We have been able to fix this problem with the aid of a compiler patch obtained from the Internet, but we would like a few people to test the programs and make sure that they give the same results as the previous versions and that all functions work. If you would like to test copies of the corrected programs and give us your conclusions, please send me an email: Agd1@cdc.gov Andy Dean Epi Info Development Team ========================================================================= Date: Sun, 24 Jan 1999 14:59:26 CST Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Robert H. Hutcheson" Subject: EpiInfo and The HP722C Desk Jet Hello. I cannot figure out how to use EpiInfo Ver 6.04b which has been updated to 2000 compliant to print to my HP722C DeskJet. It has never driven this printer with any versions of EpiInfo Perhaps if anyone has solved this perhaps with CONFIG.EPI you could post it to me or the list. Help if you can! Robert Hutcheson RHHutchesonJr@juno.com ========================================================================= Date: Mon, 25 Jan 1999 10:10:43 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert-Jean FREUND Subject: Re: EpiInfo and The HP722C Desk Jet In-Reply-To: <19990124.145927.16478.0.RHHutchesonJr@juno.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I personnally no longer use direct DOS printing since this might be complex sometimes (lack of DOS compatibility for new HP printers, lack of appropriate driver, network problems, etc..) I create either from Epi6 or EpiMap CGM, PCX or BMP files for graphics and maps CGM reveals to be excellent since it is a vectorial format and it does not modify significantly colors in EpiMap Then I insert in Word or PowerPoint without any problem then print using standard Windows facilities available on any machine whatever is the configuration. Moreover, if you insert with a link in Word or PowerPoint, your DOC or PPT document will be updated any time you update the ouriginal graphics or map files Hope that helps A 14:59 24/01/1999 CST, vous avez =E9crit : >Hello. I cannot figure out how to use EpiInfo Ver 6.04b which has been >updated to 2000 compliant to print to my HP722C DeskJet. It has never >driven this printer with any versions of EpiInfo >Perhaps if anyone has solved this perhaps with CONFIG.EPI you could post >it to me or the list. Help if you can! >Robert Hutcheson >RHHutchesonJr@juno.com > \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | =20 | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Mon, 25 Jan 1999 09:04:09 +0000 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Mark Myatt Subject: Re: EpiInfo and The HP722C Desk Jet In-Reply-To: <19990124.145927.16478.0.RHHutchesonJr@juno.com> MIME-Version: 1.0 Robert H. Hutcheson writes: >Hello. I cannot figure out how to use EpiInfo Ver 6.04b which has been >updated to 2000 compliant to print to my HP722C DeskJet. It has never >driven this printer with any versions of EpiInfo >Perhaps if anyone has solved this perhaps with CONFIG.EPI you could post >it to me or the list. Help if you can! >Robert Hutcheson >RHHutchesonJr@juno.com Try adding: SET PRINTER = $DJ or: SET PRINTER = $DJC you will need to have $DJ.BGI or $DJC.BGI in your EPI6 directory for this to work. If you haven't got these files then use the install program. Mark -- Mark Myatt ========================================================================= Date: Wed, 27 Jan 1999 14:07:01 +0530 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: sandra Subject: problem opening REC file in ANALYSIS MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear All, I have a very strange problem. I have created questionnaire .qes and = have entered data using the ENTER programme, but I cannot read the .rec = file using analysis. I can see the data in the ENTER programme and by opening the file in = EPED but I cannot read it in ANALYSIS. Has any one faced a similar problem ? Are there any suggestions. Thanks in advance Sandra ========================================================================= Date: Wed, 27 Jan 1999 09:10:51 +0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Enrique Finetti Subject: Domeasx _ Win95 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I upgrade operative system to win95. Now, a epi-info system who use DOMEASX not calculate anthropometric variables. How i can resolve it? Thank in advance Enrique Finetti Hospital Materno Infantil Salta - Argentina sapsalta@ciunsa.edu.ar ========================================================================= Date: Wed, 27 Jan 1999 10:43:09 EST Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: e c groh Subject: Re: problem opening REC file in ANALYSIS Sandra: did you create a new rec file from the qes file? You have to do that first, then exit and return via enter or enterx and THEN begin data entry. e.c.groh On Wed, 27 Jan 1999 14:07:01 +0530 sandra writes: >Dear All, > >I have a very strange problem. I have created questionnaire .qes and = >have entered data using the ENTER programme, but I cannot read the >.rec = >file using analysis. > >I can see the data in the ENTER programme and by opening the file in = >EPED but I cannot read it in ANALYSIS. > >Has any one faced a similar problem ? Are there any suggestions. > >Thanks in advance > >Sandra > ========================================================================= Date: Wed, 27 Jan 1999 11:06:32 -0700 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Matt Snell Subject: Re: problem opening REC file in ANALYSIS Comments: To: sandra@DANPCB.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sandra, If you have ENTERed data into the .rec file, and can view the data from = ENTER, I'm assuming you have created a .rec file. When you are in = ANALYSIS, can you view that the .rec file is present in the correct = subdirectory? I apologize if you already know this, but you can view the = .rec files in directories by typing at the COMMAND line in ANALYSIS READ = C: (if you are on a network, you may have to read another directory) and = pressing enter. =20 Whenever this problem comes up, the first thing I do is check the = directory and path where my file is. If it's not where I thought it was, = I will usually find it in C:\EPI6, the system directory. If that doesn't work, and you can attach the .rec file to an email, you = are welcome to email it to me to find out what's going on. snellm@slrmc.org=20 good luck. >>> sandra 01/27/99 01:37AM >>> Dear All, I have a very strange problem. I have created questionnaire .qes and have = entered data using the ENTER programme, but I cannot read the .rec file = using analysis. I can see the data in the ENTER programme and by opening the file in EPED = but I cannot read it in ANALYSIS. Has any one faced a similar problem ? Are there any suggestions. Thanks in advance Sandra ========================================================================= Date: Wed, 27 Jan 1999 14:32:44 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "B. Gerstman" Subject: problem opening REC file in ANALYSIS MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 >Message text written by Epi Info Discussion Participant Dear All, I have a very strange problem. I have created questionnaire .qes and have= entered data using the ENTER programme, but I cannot read the .rec file using analysis. I can see the data in the ENTER programme and by opening the file in EPED= but I cannot read it in ANALYSIS. Has any one faced a similar problem ? Are there any suggestions. Thanks in advance Sandra < Is it possible that the REC file has become corrupted? Opening a REC file= in EPED can corrupt a file if you inadvertently enter a character (including a blank space) into the critical header portion of the file. Bud Gerstman San Jose, California, USA ========================================================================= Date: Wed, 27 Jan 1999 11:24:33 -0800 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Steven Dubnoff Subject: Announce: Stat/Transfer supports Epi Info MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit We are pleased to announce that Stat/Transfer Version Five supports Epi Info. Stat/Transfer provides an easy and economical way to move data between leading statistical packages, such as SAS, SPSS, and Stata, databases, such as Access, dBASE, and Paradox, and Spreadsheets, such as 1-2-3 and Excel. Further information and a fully functional demo are available from: http://www.stattransfer.com Best wishes, Steve -- ---------------------------------------------------------------- Steven Dubnoff sdubnoff@circlesys.com Circle Systems We make your data instantly usable. Download Stat/Transfer from http://www.stattransfer.com 1001 Fourth Avenue, #3200 (206) 682-3783 Seattle, WA 98154 Fax (206) 328-4788 ========================================================================= Date: Wed, 27 Jan 1999 19:36:49 CST Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Robert H. Hutcheson" Subject: Re: problem opening REC file in ANALYSIS Sandra: Your header is probably damaged. Sometimes the following works: FIRST make a COPY of your *.REC file and *.QES file and make changes ONLY on the Copies which must have different names, like so COPY ORIG.REC TEST1.REC COPY ORIG.QES TEST2.QES Now use ENTER to make an empty TEST2.REC FILE from TEST2.QES Now replace the Header of TEST1.REC with the HEADER of TEST2.REC IF you dont know how to do that, enlist the help of a friend. On Wed, 27 Jan 1999 14:07:01 +0530 sandra writes: >Dear All, > >I have a very strange problem. I have created questionnaire .qes and = >have entered data using the ENTER programme, but I cannot read the >.rec = >file using analysis. > >I can see the data in the ENTER programme and by opening the file in = >EPED but I cannot read it in ANALYSIS. > >Has any one faced a similar problem ? Are there any suggestions. > >Thanks in advance > >Sandra > From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9901C" ========================================================================= Date: Tue, 19 Jan 1999 13:52:24 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jayanth Devasundaram MIME-Version: 1.0 Content-Type: text/plain Hi all, I have a few questions which may already have been answered on the list. If they have been, I apologize! 1. When is the Beta version of epi-info 2000 available? 2a. Is epi map included or is that a separate module? 2b. In epimap, is there a facility for geocoding addresses to create point themes? 2c. Is spatial analysis possible within the GIS module? 3. Does epi-info 2000 have color charting/histogram capability with adjustable fonts, pallettes, legends, and scales? Thank you for your indulgence Jay Devasundaram ========================================================================= Date: Thu, 21 Jan 1999 09:09:27 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Year 2000 Compliance Issues with Epi 6.xx Comments: To: Neil Maizlish MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" We get lots of questions on this one, so let me answer it for the Epi Info Discussion Group Listserv as well. There is an upgrade for Epi Info 6.04b, called the Epi Info b-to-c upgrade, on the Web site at www.cdc.gov/epo/epi/epiinfo.htm , the central download page. Basically, you download the update file, make sure that you have first installed 6.04b, and then log into the Epi6 directory where you installed 6.04b. From this directory, run the EXE file called 4BUPDATE.EXE (the update). It will expand into a number of files and ask if you wish to replace previous files. Answer "y" to each of a number of prompts, and the upgrade is ready to use. It provides new files for most of the programs-the ones that use dates. Instructions for converting previous data files from two-digit years to four digits are included in a file called READBTOC.TXT. The updated system has been certified by CDC's Year 2000 Compliance authority as Year-2000 compliant. If your are being asked to fill out forms by your Information Technology people, perhaps this will be a starting place. Any applications that you may have created should be upgraded, since previous data files and PGM and CHK files will not necessarily become Year 2000 safe until they are inspected and probably revised. Data files can be revised with the help of the utility provided and READBTOC.TXT. Other places that may need revision include the use of substrings in PGM file, for example, YEAR = ADMDATE[7,2], which will give a 2-digit year from an mm/dd/yy field, but will always return 19 or 20 from an mm/dd/yyyy or dd/mm/yyyy field. If YEAR is defined as DEFINE YEAR ##, this should be changed to DEFINE YEAR ####, and the assignment should be YEAR=ADMDATE[7,4]. -----Original Message----- From: Neil Maizlish [mailto:neil@telcel.net.ve] Sent: Thursday, January 21, 1999 4:04 AM To: Andrew Dean Subject: Epi Info 6.04 - Year 2000 I've been out of the loop lately on Y2K issues with Epi Info 6.04. Iv'e been using 6.04b (January 1997) which I downloaded a while ago. To see if anything worked I used a format for which I got inconsistent results over the millenium. Check files seem to reject Y2K dates altogether, but in analysis I got some results that seem reasonable with very simple test files. However, my batch programs in ANALYSIS with WIZARD didn't work. I'm sure this must be old hat to you, but could you re-send the message on this topic or just let me know if a newer version of 6.04x was released and all I need to do is download it. Also, because I work in Spanish, if you are aware of Y2K developments in the Spanish version and have a contact I'd appreciate that, too. I'm now back in Venezuela so please send to my Venezuelan e-mail server. neil@telcel.net.ve I know this will all be made moot with Epi Info 2000, which I have an ALPHA2 version. I've started to get to know it, but in the meantime I'm stuck. Thanks. USA: Venezuela: Neil Maizlish Neil Maizlish PO Box 7140 Centro de Estudios en Salud de los Trabajadores Berkeley, CA 94707 Escuela de Malariologia (510) 525-4939 Av. Bermudez Sur Maracay 2101A, VENEZUELA Tel (043) 321001 Fax (043) 324566 From: L-Soft list server at CDC (1.8d) [LISTSERV@LISTSERV.CDC.GOV] Sent: Friday, March 23, 2001 11:01 AM To: Steven S Yoon Subject: File: "EPI-INFO LOG9901A" ========================================================================= Date: Wed, 6 Jan 1999 11:50:56 +0100 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Robert-Jean FREUND Subject: Problems running Epi 6 and EpiMap on a new P II 300 machine Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Dear list members, I encountered some problems with new machines equipped with Intel P II 300mhz processor and an AGP 8 Mb videoboard : 1- running EpiMap with Windows 98 results in a kind of damaged screen with a blank bar in the bottom of the screen but EpiMap still works restarting the machine only in DOS allows a normal appearance of the screen with EpiMap 2- impossible to run EpiTable and EpiNut (run time error) The hint with the F1 key works only when I restart the machine in DOS Does anybody know about that and give some help ? Thanks Robert \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Wed, 6 Jan 1999 11:03:01 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: "Dean, Andrew G." Subject: Re: Problems running Epi 6 and EpiMap on a new P II 300 machine Comments: cc: "Arner, Tom G." MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" I can run Epi Map 2 without problems on my 266 mhz laptop with Windows 98 (upgrade). We have had some difficulty running Epi Map 2 under NT, and have done some fixing, but have not yet made the results available on the web site. The problem in NT is that sometimes the cursor is confined to the upper half of the screen, although this can be fixed temporarily by going into "Edit Annotations" mode and coming back out to the main screen. After we finish testing the fixed version, we will put it up on the web site. Not sure what the problem is with EpiTable and EpiNut. Perhaps Denis Coulombier will have an idea. -----Original Message----- From: Robert-Jean FREUND [mailto:rjfreund@NEWNETRA.ENSP.FR] Sent: Wednesday, January 06, 1999 2:51 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Problems running Epi 6 and EpiMap on a new P II 300 machine Dear list members, I encountered some problems with new machines equipped with Intel P II 300mhz processor and an AGP 8 Mb videoboard : 1- running EpiMap with Windows 98 results in a kind of damaged screen with a blank bar in the bottom of the screen but EpiMap still works restarting the machine only in DOS allows a normal appearance of the screen with EpiMap 2- impossible to run EpiTable and EpiNut (run time error) The hint with the F1 key works only when I restart the machine in DOS Does anybody know about that and give some help ? Thanks Robert \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------| ========================================================================= Date: Wed, 6 Jan 1999 14:43:18 -0500 Reply-To: Epi Info Discussion Group Sender: Epi Info Discussion Group From: Jamie Hockin Subject: Re: Problems running Epi 6 and EpiMap on a new P II 300 machine Mime-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable From: Jamie Hockin on 01/06/99 02:43 PM I have just installed Epi 6.04c (from the CDC CD-ROM) on a Dell Pentium= II 266 laptop and Epitable will not run - same run time error as Robert Fr= eund has reported. Others at LCDC have found the same problem as they upgrad= ed to Pentium II's. Some DOS software (like Gideon) have problems with too= much memory available; I have tried Gideon's solution of limiting the memory available to Epi Info and that doesn't help. We're using Mark Myatt's EpiCalc 2000 to get around this. I prefer it o= ver EpiTable, primarily because it saves your tables. ---------------------- Jamie Hockin MD,MSc -------------------------- Director, Field Epidemiology _ Directeur, Programme de formation Training Program _|\ en =E9pid=E9miologie d'intervention= LCDC, Health Canada :| \ LLCM, Sant=E9 Canada PL 0602B Tunney's Pasture | LP 0602B Pr=E9 Tunney Ottawa ON K1A 0L2, Canada Ottawa (Ontario) K1A 0L2, Canada Jamie_Hockin@hc-sc.gc.ca 613 957-1764 FAX: 613 941-6028 http://www.hc-sc.gc.ca/hpb/lcdc/survlnce/fetp agd1 @ CDC.GOV on 99/01/06 11:03:01 AM Please respond to EPI-INFO@LISTSERV.CDC.GOV To: EPI-INFO @ LISTSERV.CDC.GOV cc: (bcc: Jamie Hockin) Subject: Re: Problems running Epi 6 and EpiMap on a new P II 300 machi= ne = Content-type: text/plain; charset=us-ascii I can run Epi Map 2 without problems on my 266 mhz laptop with Windows 98 (upgrade). We have had some difficulty running Epi Map 2 under NT, and have done some fixing, but have not yet made the results available on the web site. The problem in NT is that sometimes the cursor is confined to the upper half of the screen, although this can be fixed temporarily by going into "Edit Annotations" mode and coming back out to the main screen. After we finish testing the fixed version, we will put it up on the web site. Not sure what the problem is with EpiTable and EpiNut. Perhaps Denis Coulombier will have an idea. -----Original Message----- From: Robert-Jean FREUND [mailto:rjfreund@NEWNETRA.ENSP.FR] Sent: Wednesday, January 06, 1999 2:51 AM To: EPI-INFO@LISTSERV.CDC.GOV Subject: Problems running Epi 6 and EpiMap on a new P II 300 machine Dear list members, I encountered some problems with new machines equipped with Intel P II 300mhz processor and an AGP 8 Mb videoboard : 1- running EpiMap with Windows 98 results in a kind of damaged screen with a blank bar in the bottom of the screen but EpiMap still works restarting the machine only in DOS allows a normal appearance of the screen with EpiMap 2- impossible to run EpiTable and EpiNut (run time error) The hint with the F1 key works only when I restart the machine in DOS Does anybody know about that and give some help ? Thanks Robert \\|// (o o) |-----------------o00o-(_)-o00o--------------------| | Robert J.FREUND Epidemiologiste, Professeur | | Ecole Nationale de la Sante Publique | | Av Prof Leon Bernard 35043 RENNES-Cedex FRANCE | | tel 33(0)2 99 02 28 62 fax 33(0)2 99 02 26 23 | | rjfreund@ensp.fr http://www.ensp.fr | |--------------------------------------------------|