- EpiData-list - University of Manitoba Mailing Lists

jumps don't work
by epidata-list＠lists.umanitoba.ca 25 Nov '09

25 Nov '09

I have epidata 3.1 and am attempting to program skips using jumps in the check file. Here's part of the .qes file sdwfull Are sidewalks fully installed on both sides of the street? <Y> sdwgaps location gaps ________________________________________________________________________ ________ sdwbfr buffer between sidewalk and street? <Y> +++++++++++++++++++++++++++++++++++++ here's the .chk file sdwfull JUMPS 1 sdwbfr 0 sdwgaps END END ++++++++++++++++++++++++++++++++++++ Here's the codebook: sdwfull ------------- Are sidewalks fully installed on both sides of the street? type: Boolean jumps: 1>sdwbfr,0>sdwgaps missing: 0/0 unique values: 0 It doesn't matter if I enter 1,0, Y,y,N,n in sdwfull, the cursor goes to the next field, the skipnextfield does not seem to work either. I've tried putting the jump statements in quotes, and making sure that there is a space after the comma. I apologize if I'm missing some basic syntax, but I've looked at the documentation and examples. Thank you, david Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. ______________________________________________________________________ Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. This email has been scanned using Webroot Email Security. ______________________________________________________________________

1 1

Using time
by epidata-list＠lists.umanitoba.ca 23 Nov '09

23 Nov '09

Hi, I have two variables that use the hours. One with the start time of surgery and another with the time of completion of surgery. How do I get with the times and calculate the time of surgery. Thanks, -------------------------------------- Silvano Cesar da Costa Departamento de Estatística Universidade Estadual de Londrina Fone: 3371-4346 --------------------------------------

1 1

status and news on current development
by epidata-list＠lists.umanitoba.ca 14 Nov '09

14 Nov '09

Dear all Early October I wrote about the new XML format and informed of a new test application "After a few weeks of comments on the format a new test application will be created.". As I have informed later in October the decision was made to create a test and verifying application instead. This has now been completed and the next steps of development are: 1. Develop a database builder, which will support: a. reading something resembling the "old qes file" b. visual building of a datafile structure (like the old epi6 "macro's" c. data entry definition of data structure, metadata and field attributes . field attributes are e.g. confirm, mustenter, top of form 2. Develop a data entry tool based on the new XML structure 3. Add to the entry tool GCP principles (transaction logging) 4. Add to Analysis documentation features not needed during dataentry 5. Add to the builder script based entry control. E.g. after entry .... if then ..... etc 6. Add to the entry tool handling of script based control. The principles of defining data entry systems and the entry control process will be defined in these levels: a . basic level - only field types and field labels are defined. (currently: create datafile from qes file) b. add metadata at field, file and study level (value labels/comment legal, missing data definitions etc.). c. add control at field and file level (mustenter, repeat, dataform colour, jumps etc) d. add scripting (before file, after file, after entry) The intention is to add translation very early in this process. The list will be informed at appropriate times. All test applications will be placed on the epidata.dk/testing.php. Documentation of the XML structures are found at: http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat_xml Documentation of the test application for file structures will be placed in the wiki as well (later). Two seminars are expected (if all goes as planned during the first half of 2010): a. Technical programming seminar with the purpose of defining a plug-in principle for the entry tool as well as analysis. b. Public oriented seminar focused on datadocumentation principles, celebration of the first 10 years of EpiData Software development, release of the source code for all above as open-source and strategic decisions on funding and resources for future developments. regards Jens Lauritsen EpiData Association

1 0

Revision of check commands during entry - and bugs in Entry
by epidata-list＠lists.umanitoba.ca 04 Nov '09

04 Nov '09

Dear all A number of bugs have been reported on part of EpiData Entry recently. Some of these are known and others new. All reporting done to the Flyspray database and/or discussed on this list are very important inputs to the re-writing of software which includes a new Entry-Client. The new client will use the proposed "XML" based data format, but will also fix known issues. Currently the development is focused on quality issues of reading and writing data files. The decision has been made to rely on "in-house" quality assurance where we construct a number of "difficult to read files", and document that these can be read, exported to all supported formats, read again with proper testing of values, field formats etc. This strategy is much less error-prone than relying on user-reporting of testing. The similar report for EpiData Analysis is always available at: http://www.epidata.dk/php/downloadc.php?file=epidata_analysis_validate.pdf --------------------------------------------------------- Currently we are looking at all the Check file commands to decide how and which of these should be continued or discontinued. Currently NO commands are on the "discontinue list". But some commands might be challenged. When doing so, the EpiData list will be oriented. There are three types of current check file contents: a. Metadata descriptions (study label, file label, field labels, category/value labels, missing value definitions). b. Data Entry attributes at field or file level: (range, legal, mustenter, top of form, no-enter, type comment etc) (file level: type comment allfields ....etc) c. Scripting commands : (jumps, goto, if ... then ... before file, after file, relate .....) Basicly the three levels a,b,c also reflect the user groups. From quick studies almost without metadata, labels are added (a), attributes added (b) and then further controls (c). A proper visually oriented filebuilder will be developed to assist users in the definition of these levels. Documentation of the new file format is shown at: http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat_xml Regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 72, Issue 13
by epidata-list＠lists.umanitoba.ca 29 Oct '09

29 Oct '09

Thanks for the suggestions; I also found that this error occurs when trying to schedule a profile on Windows Vista. I will try the suggestions given best regards martin 2009/10/29 <epidata-list-request(a)lists.umanitoba.ca> > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Lost all my code as a result of a system error > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Lost all my code as a result of a system error > (epidata-list(a)lists.umanitoba.ca) > 3. Re: Lost all my code as a result of a system error > (epidata-list(a)lists.umanitoba.ca) > 4. Does the "999 limit of text" apply to both the QES and CHK > files? (epidata-list(a)lists.umanitoba.ca) > 5. Re: Does the "999 limit of text" apply to both the QES and > CHK files? (epidata-list(a)lists.umanitoba.ca) > 6. Bug in Epidata Entry? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Oct 2009 17:06:53 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Lost all my code as a result of a system error > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <8eafc6ae0910281006o2020ecc7uf28b754908ed56ca(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Yesterday I was working on a questionnaire (over 300 variables) and at an > advanced stage, got this message "Access violation at address 0048AC7 in > module Epidata.exe. Read of address 00000000". I lost the whole work > after > it will not allow me to save. I started anew but this time I backed up the > chk file at different stages of the developmeent of code (has a lot of skip > patterns and replace of values in all places which have been skipped). The > problem has appeared occurred agian and naturally have lost the code I was > building from this afternoon. Has this happened to anyone before and if > so > how did you resolve it? > > Thanks in advance > > Martin > > -- > Martin Alhassan Adjuik > Statistician (INESS) > INDEPTH Network Secretariat > Accra > Office : +233 (0) 21 521670 > Cell : +233 (0) 243714441 > martin.adjuik(a)indepth-network.org > madjuik(a)gmail.com > > > ------------------------------ > > Message: 2 > Date: Wed, 28 Oct 2009 14:26:08 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Lost all my code as a result of a system > error > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4AE88CC0.6080808(a)ix.netcom.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Maybe some limit of file size was exceeded. Not sure if this is still > correct but look at: > > http://lists.umanitoba.ca/mailman/htdig/epidata-list/2007q4/000857.html > > Peter Geddes > > epidata-list(a)lists.umanitoba.ca wrote: > > Yesterday I was working on a questionnaire (over 300 variables) and at an > > advanced stage, got this message "Access violation at address 0048AC7 in > > module Epidata.exe. Read of address 00000000". I lost the whole work > after > > it will not allow me to save. I started anew but this time I backed up > the > > chk file at different stages of the developmeent of code (has a lot of > skip > > patterns and replace of values in all places which have been skipped). > The > > problem has appeared occurred agian and naturally have lost the code I > was > > building from this afternoon. Has this happened to anyone before and if > so > > how did you resolve it? > > > > Thanks in advance > > > > Martin > > > > > > > ------------------------------ > > Message: 3 > Date: Thu, 29 Oct 2009 02:49:15 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Lost all my code as a result of a system > error > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <44e66f9b0910281749i15b16734nc7b828dc3fec699c(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Try developing the chk file in a text editor (notepad will do) rather than > using Epidata. > > Annemieke van Middelkoop > > On Wed, Oct 28, 2009 at 8:26 PM, <epidata-list(a)lists.umanitoba.ca> wrote: > > > Maybe some limit of file size was exceeded. Not sure if this is still > > correct but look at: > > > > http://lists.umanitoba.ca/mailman/htdig/epidata-list/2007q4/000857.html > > > > Peter Geddes > > > > epidata-list(a)lists.umanitoba.ca wrote: > > > Yesterday I was working on a questionnaire (over 300 variables) and at > an > > > advanced stage, got this message "Access violation at address 0048AC7 > in > > > module Epidata.exe. Read of address 00000000". I lost the whole work > > after > > > it will not allow me to save. I started anew but this time I backed up > > the > > > chk file at different stages of the developmeent of code (has a lot of > > skip > > > patterns and replace of values in all places which have been skipped). > > The > > > problem has appeared occurred agian and naturally have lost the code I > > was > > > building from this afternoon. Has this happened to anyone before and > if > > so > > > how did you resolve it? > > > > > > Thanks in advance > > > > > > Martin > > > > > > > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > ------------------------------ > > Message: 4 > Date: Thu, 29 Oct 2009 10:52:51 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Does the "999 limit of text" apply to both the > QES and CHK files? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <8eafc6ae0910290352v25b23c14t7a9c44040071d50a(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > In the data entry module ts is advised that "All fields must fit within 999 > lines of text" Does this apply to the qes as well as chk files? > > regards > > martin > > -- > Martin Alhassan Adjuik > Statistician (INESS) > INDEPTH Network Secretariat > Office : +233 (0) 21 521670 > Cell : +233 (0) 243714441 > martin.adjuik(a)indepth-network.org > madjuik(a)gmail.com > > > ------------------------------ > > Message: 5 > Date: Thu, 29 Oct 2009 08:06:29 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Does the "999 limit of text" apply to both > the QES and CHK files? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4AE98545.20303(a)sympatico.ca> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 999 lines only applies to qes files. > > > In the data entry module ts is advised that "All fields must fit within > 999 > > lines of text" Does this apply to the qes as well as chk files? > > > > > > ------------------------------ > > Message: 6 > Date: Thu, 29 Oct 2009 15:10:28 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Bug in Epidata Entry? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4AE9A254.7030402(a)fifas.de> > Content-Type: text/plain; charset="iso-8859-15" > > Hi, > > I programmed a lot of diffent entryforms in Epidata but now I sometimes > get a errormessage "window has no scrollbars", when I try to open a > rec-file in epidata entry by doubleclicking it in windows-explorer (Win > XP, SP3). This only happened with files, that use a big data-file for a > "comment legal" command in the chk-file (icd-code table with 14000 > entries). > > It seems to work, when I start epidata as a window (not maximized!) and > then open the rec-file. Or if I closed epidata entry before as a window > (not maximized) and then double click the rec-file in win-explorer. > > If I close epidata maximized, the parameters in the epidata.ini-file are: > > ... > MainWinTop=-4 > MainWinLeft=-4 > MainWinBot=998 > MainWinRight=1284 > MainWinMax=1 > ... > > (My monitor resolution is 1280x1024). > > Is this a bug in Epidata entry? Does anybody had similar problems? > > Greetings > > Juergen >

1 0

Bug in Epidata Entry?
by epidata-list＠lists.umanitoba.ca 29 Oct '09

29 Oct '09

Hi, I programmed a lot of diffent entryforms in Epidata but now I sometimes get a errormessage "window has no scrollbars", when I try to open a rec-file in epidata entry by doubleclicking it in windows-explorer (Win XP, SP3). This only happened with files, that use a big data-file for a "comment legal" command in the chk-file (icd-code table with 14000 entries). It seems to work, when I start epidata as a window (not maximized!) and then open the rec-file. Or if I closed epidata entry before as a window (not maximized) and then double click the rec-file in win-explorer. If I close epidata maximized, the parameters in the epidata.ini-file are: ... MainWinTop=-4 MainWinLeft=-4 MainWinBot=998 MainWinRight=1284 MainWinMax=1 ... (My monitor resolution is 1280x1024). Is this a bug in Epidata entry? Does anybody had similar problems? Greetings Juergen

1 0

Does the "999 limit of text" apply to both the QES and CHK files?
by epidata-list＠lists.umanitoba.ca 29 Oct '09

29 Oct '09

In the data entry module ts is advised that "All fields must fit within 999 lines of text" Does this apply to the qes as well as chk files? regards martin -- Martin Alhassan Adjuik Statistician (INESS) INDEPTH Network Secretariat Office : +233 (0) 21 521670 Cell : +233 (0) 243714441 martin.adjuik(a)indepth-network.org madjuik(a)gmail.com

1 1

Lost all my code as a result of a system error
by epidata-list＠lists.umanitoba.ca 28 Oct '09

28 Oct '09

Yesterday I was working on a questionnaire (over 300 variables) and at an advanced stage, got this message "Access violation at address 0048AC7 in module Epidata.exe. Read of address 00000000". I lost the whole work after it will not allow me to save. I started anew but this time I backed up the chk file at different stages of the developmeent of code (has a lot of skip patterns and replace of values in all places which have been skipped). The problem has appeared occurred agian and naturally have lost the code I was building from this afternoon. Has this happened to anyone before and if so how did you resolve it? Thanks in advance Martin -- Martin Alhassan Adjuik Statistician (INESS) INDEPTH Network Secretariat Accra Office : +233 (0) 21 521670 Cell : +233 (0) 243714441 martin.adjuik(a)indepth-network.org madjuik(a)gmail.com

1 2

EpiData-list Selection of cases with special digits within a longer variable
by epidata-list＠lists.umanitoba.ca 27 Oct '09

27 Oct '09

...or do in EpiData analysis: select substr(cpr,5,4)="1940" savedata "1940_only.rec" /replace Hans Do this: define cprtxt __________ // string of length 10 define yrtxt __ // string of length 2 cprtxt = cpr yrtxt = copy(cprtxt,5,2) // digits 5 & 6 select yrtxt = "40" This can also be done in a single line, if you have no other use for the year of birth: select copy(cpr,5,6)="40" Jamie Hockin 2009/10/27 Jes Lindholt wrote: > In Denmark, we have the unique CPR number consisting of birthdate (ddmmyy) > followed by 4 numbers. If I have to select a population born in fx 1940 from > a larger epidata-fil, I consider to use the export facility, but then need > an observation filter only selecting those born in 1940, which means those > numbered 40, in position 5 and 6 in the 10 digit CPR variable. Do anybody > have knowledge of a relevant syntax for that? > -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 1

Selection of cases with special digits within a longer variable
by epidata-list＠lists.umanitoba.ca 27 Oct '09

27 Oct '09

In Denmark, we have the unique CPR number consisting of birthdate (ddmmyy) followed by 4 numbers. If I have to select a population born in fx 1940 from a larger epidata-fil, I consider to use the export facility, but then need an observation filter only selecting those born in 1940, which means those numbered 40, in position 5 and 6 in the 10 digit CPR variable. Do anybody have knowledge of a relevant syntax for that? Yours sincerely Jes Lindholt Ass. professor, PhD Vascular Research Unit Viborg Hospital, Denmark E-mail: jes.s.lindholt(a)viborg.rm.dk

1 1