- EpiData-list - University of Manitoba Mailing Lists

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

02 Mar '05

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

1 0

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

01 Mar '05

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

1 0

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

01 Mar '05

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

1 0

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

28 Feb '05

Hello, I am using epidata 3.1 for data entry in a CMB project. Followings are some questions: 1. Is it possible to make the numbers right alignment in the field box after entry. 2. In our dataset, the width of some numeric fields is 2. When "08" is entered, "8" is saved. But in the double entry verification, if "08" is entered again, the dialog box will told you "non matching value,the original value is 8, new value is 08" .How to solve this problem? 3. Our check file is about 138kb, question file 56kb, and about 20,000 records is expected to be entered. Is the check file too large? And will it meet some difficulties when entering so many records? Thank you very much Best regards, Yali Zhang Department of Clinical Epidemiology Beijing Hui Long Guan Hospital Beijing Suicide Research and Prevention Center Beijing 10096 P.R.C Fax: 86-10-82951150 E-mail:zhang_bsrpc@hotmail.com _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

1 0

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

24 Feb '05

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

1 0

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

22 Feb '05

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

1 0

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

22 Feb '05

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

1 0

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

22 Feb '05

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

1 0

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

10 Feb '05

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

1 0

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

09 Feb '05

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

1 0