- EpiData-list - University of Manitoba Mailing Lists

Problem exporting data to SAS
by epidata-list＠lists.umanitoba.ca 01 Jul '10

01 Jul '10

Dear members, I am currently setting up my database and faced one problem that I can't figure out. I entered some real data and exported to SAS. However, most variables are coming as missing (.), but very few are coming with the labels. I am thinking that it's something related to the checks on EpiData and not a SAS problem. If anyone could help me I would appreciate. Following attached is the .rec file. Thanks in advance, Rafael

1 1

Files won't open on remote computer
by epidata-list＠lists.umanitoba.ca 30 Jun '10

30 Jun '10

I create qes/rec/chk files with 1 respondent and send to a data capturer via email. She has problems opening the files in EpiData. We are both on Version 3.1 / Windows based. Any ideas what could be causing this? She can make the files on her machine with no problem and send them to me. Regards -- Mark Webb Line +27 (21) 786 4379 Cell +27 (72) 199 1000 Fax to email +27 (86) 5513075 Skype webbmark Email targetlinkmark(a)gmail.com

1 2

Myanmar fonts recognition in Epidata
by epidata-list＠lists.umanitoba.ca 26 Jun '10

26 Jun '10

Hello, everybody. I would like to work through the data in Myanmar language in Epidata (e.g. patient address). But Epidata cannot recognize Myanmar font. Does anybody know how to make Epidata recognize and work with Myanmar Font? Thank you. Zaw Myo Tun Myanmar

1 1

Combine data file
by epidata-list＠lists.umanitoba.ca 24 Jun '10

24 Jun '10

Hello! Me and my collague are working parallell with the same data materiel and would like to combine the to data files into one. We have labeled the files so they go from 1 - 45 and would like them to combine in the right order. How is this to be done? Much grateful for your help! Agnes

1 1

new test release of EpiData Manager available (reading and saving data structures)
by epidata-list＠lists.umanitoba.ca 09 Jun '10

09 Jun '10

Dear All Next test release of the EpiData Manager is now ready for testing. Added functionality is: 1. open existing data file (without data) - reads Stata dta and Rec files 2. save data as an EpiData project XML file (*.epx) - this will contain all definitions and in next release also the data 3 read a project file again. Please discuss function in general on this list and report reproducible errors to the flyspray database In the announced release plan this is point b and part of point c: a. Test placement of fields in data entry forms. Move fields, add sections. Only one form is allowed. Edit variable labels (questions). b. Include previous data structures on a form. Will import EpiData (rec) and Stata (dta) files. c. Write data files and export data structures to rec file and dta files d. Start development of a dedicated entry client. e. Add definition and editing of category labels (value labels). f. Add to data forms the possibility of translating labels and questions See http://www.epidata.dk/testing.php for the operating systems Linux, Mac and Windows. ---------------------------------------------------------------------- When you first start the application you will see two sections, which can be moved, edited and deleted. these contain further definitions and guidance. Torsten Christiansen and Jens Lauritsen EpiData Association

1 3

Ruwan Ratnayake est absent.
by epidata-list＠lists.umanitoba.ca 09 Jun '10

09 Jun '10

Je serai absent(e) à partir du 2010-06-09 de retour le 2010-06-14. Veuillez prendre note que je serai absente de mon bureau le 9 à 14 juin. Please note that I will be out of the office from June 9-14.

1 0

EpiData Entry Help file
by epidata-list＠lists.umanitoba.ca 03 Jun '10

03 Jun '10

Colleagues: The EpiData Entry Help file is no more accessible in Windows Vista and Windows 7 as Microsoft has changed how help files work. It can be fixed easily with a Microsoft patch for either OS: Windows Vista: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6eb… Windows 7: http://www.microsoft.com/downloads/details.aspx?FamilyID=258aa5ec-e3d9-4228… ...as long as it is a 32-bit machine. With Windows 7, 64-bit, I am unable to fix the problem (even after fiddling with the registry as per MS instructions). Anybody with an idea how to fix it? Thanks, -- 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 0

SV: EpiData-list Digest, Vol 79, Issue 4
by epidata-list＠lists.umanitoba.ca 30 May '10

30 May '10

Hello, and thank you very much all of you; Jonas, Hans and Zaw Myo Tun for your kindness to give me advice on my question on "How to change the title of en already existing qes- and rec.file without loosing data". I followed the instructions given from Jonas and it worked ! I also did the same with the check.file that belonged to these qes and rec.files and it worked also. Before i changed the title, I added 4 new variables to my qes .fiel and than I followed the instuctions in the Help file and Tools -->Revise DataFile. Best regards Susann Regber ________________________________________ Från: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] för epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Skickat: den 28 maj 2010 19:01 Till: epidata-list(a)lists.umanitoba.ca Ämne: EpiData-list Digest, Vol 79, Issue 4 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Re: question about changing title of qes fil and rec file (epidata-list(a)lists.umanitoba.ca) 2. Ans: changing title of qes file and rec file (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Thu, 27 May 2010 19:13:07 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] question about changing title of qes fil and rec file To: epidata-list(a)lists.umanitoba.ca Message-ID: <4BFEA823.4040509(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Dear Susann: "Title", "File Label" or "File name"? Title: Change the title in the QES file, save the file, do not make a REC file, but 4. Enter data, and you will be prompted to adjust the REC file to the new QES file Label: Read the REC file in EpiData analysis, and use the command "labeldata", eg. labeldata "My new label for the data file" File name: Just rename both QES and REC file in Explorer. Regards, Hans On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > Hello > > I would like to change the title of an existing QES- file and REC file- without losing data. Is it possible ? How can I do that ? > > Susann > > Susann Regber > Pediatric nurse, MPH, > PHD-student > Nordic School of Public Health > Tel.: +46 (0)31 69 39 01 > Mobile: +46(0) 738 19 04 19 > E-mail: susann.regber(a)nhv.se > Homepage: www.nhv.se > > P.O. Box 12133, SE-402 42 Gothenburg > > > -- 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 ------------------------------ Message: 2 Date: Fri, 28 May 2010 11:15:08 +0630 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Ans: changing title of qes file and rec file To: epidata-list(a)lists.umanitoba.ca Message-ID: <AANLkTikwI8k7wSNVeEpM-CPQ6n_kbsl66nVK0YAN1GP5(a)mail.gmail.com> Content-Type: text/plain; charset=windows-1252 Hello, I assume what you mean by "Title in qes and rec file" is what you typed in .qes file from which .rec file was made. If so, you can easily edit the "Title" in qes file as you want. Please be sure that the field names and definitions are not changed. Then, revise the old rec file with the newly edited qes file (by going to Tools --> revise data file). By doing so, your data won't be harmed. best regards, Zaw Myo Tun Zaw Myo Tun | Integrated HIV Care Program International Union Against Tuberculosis and Lung Disease The Union?s office in Myanmar No. 36, 27th street | between 72nd & 73rd streets Chan Aye Thar Zan Township | Mandalay | Myanmar Tel: +95 2 71082 | Fax: +95 2 71082 drzmyotun(a)gmail.com | www.theunion.org On 5/27/10, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Re: new test release of EpiData Manager available > (epidata-list(a)lists.umanitoba.ca) > 2. question about changing title of qes fil and rec file > (epidata-list(a)lists.umanitoba.ca) > 3. Ang: [EpiData-list] question about changing title of qes fil > and rec file (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 26 May 2010 16:32:16 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] new test release of EpiData Manager > available > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP93E23D8FE0C4EDD9B68189FDE90(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > Sections will be great to have! Everything described works on a Mac. > Placement of sections sometimes fails to open the dialogue box to name the > section, rendering the section as a white box, but not editable. > > Jamie Hockin > > On 2010-05-25, at 6:12 PM, epidata-list(a)lists.umanitoba.ca wrote: > >> The development of the EpiData Manager has now come to a new stage, where >> test versions will be released with shorter intervals. The release will >> happen in these steps: >> a. Test placement of fields in data entry forms. Move fields, add >> sections. Only one form is allowed. Edit variable labels (questions). > > > > ------------------------------ > > Message: 2 > Date: Thu, 27 May 2010 08:28:20 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] question about changing title of qes fil and > rec file > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: <42EF964FD9CDE2479936BC6F837DC80B0827E6A3(a)loke.nhv.se> > Content-Type: text/plain; charset="us-ascii" > > Hello > > I would like to change the title of an existing QES- file and REC file- > without losing data. Is it possible ? How can I do that ? > > Susann > > Susann Regber > Pediatric nurse, MPH, > PHD-student > Nordic School of Public Health > Tel.: +46 (0)31 69 39 01 > Mobile: +46(0) 738 19 04 19 > E-mail: susann.regber(a)nhv.se > Homepage: www.nhv.se > > P.O. Box 12133, SE-402 42 Gothenburg > > > > ------------------------------ > > Message: 3 > Date: Thu, 27 May 2010 12:11:12 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Ang: [EpiData-list] question about changing title of qes fil > and rec file > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <OFA31131DD.3F5D22A7-ONC1257730.0037F54B-C1257730.0037F550(a)sll.se> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi > > You can change the name of the ques and rec files directely in the folder > (ie with files closed). It is important that you have exactly identical > names of the qes and rec files. I would recommend that you first make a copy > of the original qes and rec (right-click --> copy. Right-click again --> > paste) files and then change the names of the copies (they will br named > "Copy of yourfile.qes" and "Copy of yourfile.rec" > > Sincerely > > Jonas Malmstedt, MD > Department of Vascular Surgery, N1:06 > Karolinska University Hospital > SE-171 76 Stockholm > +46-(0)8-517 76895 > +46-(0)70-484 1455 > > > > -----epidata-list-bounces(a)lists.umanitoba.ca skrev: ----- > > > Till: "epidata-list(a)lists.umanitoba.ca" <epidata-list(a)lists.umanitoba.ca> > Fr?n: epidata-list(a)lists.umanitoba.ca > S?nt av: epidata-list-bounces(a)lists.umanitoba.ca > Datum: 2010/05/27 10.28 > ?rende: [EpiData-list] question about changing title of qes fil and rec file > > Hello > > I would like to change the title of an existing QES- file and REC file- > without losing data. Is it possible ? How can I do that ? > > Susann > > Susann Regber > Pediatric nurse, MPH, > PHD-student > Nordic School of Public Health > Tel.: +46 (0)31 69 39 01 > Mobile: +46(0) 738 19 04 19 > E-mail: susann.regber(a)nhv.se > Homepage: www.nhv.se > > P.O. Box 12133, SE-402 42 Gothenburg > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 79, Issue 3 > ******************************************* > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 79, Issue 4 *******************************************

1 0

Ans: changing title of qes file and rec file
by epidata-list＠lists.umanitoba.ca 27 May '10

27 May '10

Hello, I assume what you mean by "Title in qes and rec file" is what you typed in .qes file from which .rec file was made. If so, you can easily edit the "Title" in qes file as you want. Please be sure that the field names and definitions are not changed. Then, revise the old rec file with the newly edited qes file (by going to Tools --> revise data file). By doing so, your data won't be harmed. best regards, Zaw Myo Tun Zaw Myo Tun | Integrated HIV Care Program International Union Against Tuberculosis and Lung Disease The Union’s office in Myanmar No. 36, 27th street | between 72nd & 73rd streets Chan Aye Thar Zan Township | Mandalay | Myanmar Tel: +95 2 71082 | Fax: +95 2 71082 drzmyotun(a)gmail.com | www.theunion.org On 5/27/10, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Re: new test release of EpiData Manager available > (epidata-list(a)lists.umanitoba.ca) > 2. question about changing title of qes fil and rec file > (epidata-list(a)lists.umanitoba.ca) > 3. Ang: [EpiData-list] question about changing title of qes fil > and rec file (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 26 May 2010 16:32:16 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] new test release of EpiData Manager > available > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP93E23D8FE0C4EDD9B68189FDE90(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > Sections will be great to have! Everything described works on a Mac. > Placement of sections sometimes fails to open the dialogue box to name the > section, rendering the section as a white box, but not editable. > > Jamie Hockin > > On 2010-05-25, at 6:12 PM, epidata-list(a)lists.umanitoba.ca wrote: > >> The development of the EpiData Manager has now come to a new stage, where >> test versions will be released with shorter intervals. The release will >> happen in these steps: >> a. Test placement of fields in data entry forms. Move fields, add >> sections. Only one form is allowed. Edit variable labels (questions). > > > > ------------------------------ > > Message: 2 > Date: Thu, 27 May 2010 08:28:20 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] question about changing title of qes fil and > rec file > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: <42EF964FD9CDE2479936BC6F837DC80B0827E6A3(a)loke.nhv.se> > Content-Type: text/plain; charset="us-ascii" > > Hello > > I would like to change the title of an existing QES- file and REC file- > without losing data. Is it possible ? How can I do that ? > > Susann > > Susann Regber > Pediatric nurse, MPH, > PHD-student > Nordic School of Public Health > Tel.: +46 (0)31 69 39 01 > Mobile: +46(0) 738 19 04 19 > E-mail: susann.regber(a)nhv.se > Homepage: www.nhv.se > > P.O. Box 12133, SE-402 42 Gothenburg > > > > ------------------------------ > > Message: 3 > Date: Thu, 27 May 2010 12:11:12 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Ang: [EpiData-list] question about changing title of qes fil > and rec file > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <OFA31131DD.3F5D22A7-ONC1257730.0037F54B-C1257730.0037F550(a)sll.se> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi > > You can change the name of the ques and rec files directely in the folder > (ie with files closed). It is important that you have exactly identical > names of the qes and rec files. I would recommend that you first make a copy > of the original qes and rec (right-click --> copy. Right-click again --> > paste) files and then change the names of the copies (they will br named > "Copy of yourfile.qes" and "Copy of yourfile.rec" > > Sincerely > > Jonas Malmstedt, MD > Department of Vascular Surgery, N1:06 > Karolinska University Hospital > SE-171 76 Stockholm > +46-(0)8-517 76895 > +46-(0)70-484 1455 > > > > -----epidata-list-bounces(a)lists.umanitoba.ca skrev: ----- > > > Till: "epidata-list(a)lists.umanitoba.ca" <epidata-list(a)lists.umanitoba.ca> > Från: epidata-list(a)lists.umanitoba.ca > Sänt av: epidata-list-bounces(a)lists.umanitoba.ca > Datum: 2010/05/27 10.28 > Ärende: [EpiData-list] question about changing title of qes fil and rec file > > Hello > > I would like to change the title of an existing QES- file and REC file- > without losing data. Is it possible ? How can I do that ? > > Susann > > Susann Regber > Pediatric nurse, MPH, > PHD-student > Nordic School of Public Health > Tel.: +46 (0)31 69 39 01 > Mobile: +46(0) 738 19 04 19 > E-mail: susann.regber(a)nhv.se > Homepage: www.nhv.se > > P.O. Box 12133, SE-402 42 Gothenburg > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 79, Issue 3 > ******************************************* >

1 0

question about changing title of qes fil and rec file
by epidata-list＠lists.umanitoba.ca 27 May '10

27 May '10

Hello I would like to change the title of an existing QES- file and REC file- without losing data. Is it possible ? How can I do that ? Susann Susann Regber Pediatric nurse, MPH, PHD-student Nordic School of Public Health Tel.: +46 (0)31 69 39 01 Mobile: +46(0) 738 19 04 19 E-mail: susann.regber(a)nhv.se Homepage: www.nhv.se P.O. Box 12133, SE-402 42 Gothenburg

1 2

new test release of EpiData Manager available
by epidata-list＠lists.umanitoba.ca 26 May '10

26 May '10

Dear All Due to funding received (and more expected) the development phase has been lengthened to summer 2011 allowing for the continuation of T.Christiansen to work fulltime on the restructuring. All programming is now done in Freepascal and Lazarus. The development of the EpiData Manager has now come to a new stage, where test versions will be released with shorter intervals. The release will happen in these steps: a. Test placement of fields in data entry forms. Move fields, add sections. Only one form is allowed. Edit variable labels (questions). b. Include previous data structures on a form. Will import rec files and dta (stata) files. c. Write data files and export data structures to rec file and dta files d. Start development of a dedicated entry client. e. Add definition and editing of category labels (value labels). f. Add to data forms the possibility of translating labels and questions If all goes well points a-f will be ready within the next few months. After this a new planning sequence will include relational aspects and multi entry forms of the same project, user access control and other coming aspects. The first new release mentioned above (a) was released earlier today from http://www.epidata.dk/testing.php for the operating systems Linux, Mac and Windows. It will seem as a backstep in relation to the previous test version, but we are approaching the same level with a completely new final XML data file structure. The new structure will accomodate all we would like and will be visible in the next stage (b), where users can see the xml structure. ---------------------------------------------------------------------- This first release is covering what happens in the definition of a single data form. Including the addition of new fields, new sections and heading lines. A section is a sub-division of a single data entry form. A section has NOT been used previously in EpiData software and contains a number of fields. Jumps will allow jumps between sections and user access control will be at the section level. When you first start the application you will see two sections, which can be moved, edited and deleted. Jens Lauritsen EpiData Association

1 2

EpiData Manager v0.5
by epidata-list＠lists.umanitoba.ca 26 May '10

26 May '10

Good to see progress with the Manager. I have some questions and thought that this would be the appropriate forum rather than the flyspray bug reporting system. At present, is the string variable created equivalent to the variable created in Entry with the underscore? If so, will uppercase strings be supported? Is it possible to resize the section box after its creation other than through the advanced tab and changing the numbers therein? Is it possible to copy and paste fields with a view to subsequent amendment of field names? This is important with a view to rapid data-form creation. I've done a test and it seems to work. I'll post a query on flyspray with regards to opening the Help file within the Manager which I can't do. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 0

Introduction document and help in the new Manager
by epidata-list＠lists.umanitoba.ca 26 May '10

26 May '10

The manager contains a "help" menu. On this two entries are found. : 1 short introduction 2 show shortcuts The first one (introduction) will check first if the file "epidatamanagerintro.pdf" is present in the location on your computer, where you stored the manager exe file. If so the file is opened in the local pdf reader. If not present the standard internet browser will open the document: http://epidata.dk/downloads/epidatamanagerintro.pdf If you then save the file in the same folder as the exe file, the local copy will be opened thereafter. 2 show shortcuts This will open the "wiki" documentation system directly via internet. If you have no current internet connection an error will appear in your browser. regards Jens Lauritsen EpiData Association

1 0

Few Clarifications about New Epidata Manager Developments
by epidata-list＠lists.umanitoba.ca 08 May '10

08 May '10

Dear Jens, It is heartening to hear that further developments of Epidata are going on. I just have few points (apprehensions) which I want to share with you. The ability to correct the data file by a text editor (in new system) sounds wonderful but existing system is also good. 1. Will the new system continue support the already developed relation databases in Epidata Entry ? Will it be downward compatible with the relational databases systems already working well in Epidata Entry 3.1 and Analysis 2.3 ? 2. The QES, CHK, REC file system was comparatively simple and one could change it whenever wanted, without being a software professional (programmer). With regards, Dr. Shavinder Singh

1 0

status april 2010 for rewriting of core and EpiData Manager
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

Dear all Since release of last trial version of the new EpiData Manager in January around 1000 copies have been downloaded from the testing.php website at epidata.dk. Since then we (Torsten Christiansen and I) have worked on ways of implementing the more subtle parts of the old rec file system in the new format, which is described at http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat:xml_v0 The description is not completely up to date, but will be updated soon. The challenge was to also include relate, encryption and principles for translation of data forms in a structured way. This has now been completed and I expect a new release for testing within some weeks. In the final file format all contents will be contained in one physical file formulated in XML and in compliance with the w3c.org validator for an xml file. The basic blocks implemented will be: - user access control block - a list of control structures, e.g. specification of relationship btw. files - a list of tables contained (each like an old rec file) - in each table a number of sections - in each section a number of fields. - each field having a number of attributes, such as type (integer, string etc), controls etc. The file will contain the combination of all current rec and chk files for a given project. User control will be at the section level. Many users will now think "Oh-no" they changed the simplicity principle of REC-CHK-QES and created a monster system with many problems. This is however NOT the case. For a simple project the file content structure is of no interest to the user and will appear simple. But by containing all in one physcal file it should become much easier to keep track of the data for a given project. Basicly with the new structure files can also be edited in a standard editor. The complete rewriting is expected to be completed in about one year from now, and funding is still welcomed for the process. regards Jens Lauritsen EpiData Association

1 0

Access violation error with Codebook command in EpiData (second try)
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

Hi! When trying to create a Codebook I get an access violation error. I have tried to carefully revise the check file with no result. The error seems to be related to only fields named with the pattern "xxxcom" which all are string variables. -If I choose all fields before "xxxcom" the Codebook for those variables will be created without error. -If I only check "xxxcom" --> access violation -If I check variables before and after "xxxcom" --> access violation -If I check only variables after "xxxcom" -->no error Error message: "Access violation at address 00403347 in module 'EpiData.exe' Read of address 393938FB" Epidata 3.1 (270108) Windows XP Pro Thanks for help Jonas Malmstedt, MD Department of Vascular Surgery, N1:06 Karolinska University Hospital SE-171 76 Stockholm PS I have also noticed another problem: smtimes EpiData Will not read *.not and *.rec files. I get an error telling me that the file name are not valid or the file is used. When I try to open the same file not NotePad - no problem! DS

1 1

Re: EpiData-list Digest, Vol 78, Issue 17
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

When you prepare the rec file for double entry better to leave the box "Match by record" unchecked. However if the double entry appears to slow or cause some frustration, perhaps it might be better to use copy structure and enter the data for comparison. Tieble On 29 April 2010 18:06, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. RE: Double Entry for Related Files > (epidata-list(a)lists.umanitoba.ca) > 2. Access violation error with Codebook command in EpiData > (second try) (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Apr 2010 13:48:41 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] RE: Double Entry for Related Files > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <679902537E215D43805DEA9BE833090E042A5B80(a)NORCEX1.norc.org> > Content-Type: text/plain; charset="us-ascii" > > I understand the two different methods of double-entering data, and I do > indeed want to "prepare for double-entry". The problem is that when I > go to prepare the questionnaire for double entry, I can only choose to > prepare either the parent OR the child file. If I choose the parent > file, then a double-entry file is only created for the parent file - > when I open it to double enter the data, it relates to the original > child file, so it opens the parent double entry file along with the > original child file. Since only one of the two files is a double entry > file, the program thinks I am entering the data for the first time, and > does not compare the alues entered to the values from the original file. > > > > > I cannot seem to find a way to prepare both the parent and the child > file for double entry together. If I prepare them for double entry > separately, I run into similar problems. > > > > Sam > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Tue, 27 Apr 2010 19:13:58 +0200 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: Re: [EpiData-list] Double Entry for Related Files > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: <4BD71B56.7020800(a)tbrieder.org> > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > Hi Sam: > > > > There are two approaches to double-enter: 1) independently, 2) the > second file depending on the first. You seemingly chose the latter > ("prepare for double-entry"). If you choose that option, you must enter > the records in the same sequence (I believe) and the value of each field > in the second record will be compared to the corresponding one in the > first and a discordance reported, so you can verify. Thus, no need to > enter twice. > > > > Alternatively, you enter your related file pairs independently between > first and second entry. You must have a unique identifier in both the > parent and the child file. The sequence then doesn't matter of course. > > > After you have entered parent1-child1 and parent2-child1, you validate > > parent1-vs-parent2 on the unique identifier, then child1-vs-child2 on > that identifier. > > > > Hans > > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > > > Hi, > > > > > > I have a questionnaire that uses two related .rec files for data > entry. > > > I want to double enter the data by checking for discrepancies as the > > > data is entered the second time. Is it possible to do this for > > > questionnaires that span two .rec files? When I try to prepare for > > > double entry, the program creates a "file1_dbl.rec" file, but relates > > > it to the "file2.rec" file rather than creating a "file2_dbl.rec" file > > > > to compare against. > > > > > > I am thinking that I will just have to un-relate the file, and enter > > > and double-enter the survey in two parts, but any help would be > appreciated. > > > > > > Thanks, > > > > > > Sam > > > > > > > -- > > 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 > > > > > > > > > > > > > > > > -- > > Samuel Haddaway > > Research Assistant, International Projects > > National Opinion Research Center > > haddaway-sam(a)norc.org > > Phone: 301.634.9423 > > > > > > ------------------------------ > > Message: 2 > Date: Wed, 28 Apr 2010 21:50:13 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Access violation error with Codebook command > in EpiData (second try) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <OF120C2D35.551C97A0-ONC1257713.006CF7D1-C1257713.006CF7D4(a)sll.se> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi! > When trying to create a Codebook I get an access violation error. I have > tried to carefully revise the check file with no result. The error seems to > be related to only fields named with the pattern "xxxcom" which all are > string variables. > -If I choose all fields before "xxxcom" the Codebook for those variables > will be created without error. > -If I only check "xxxcom" --> access violation > -If I check variables before and after "xxxcom" --> access violation > -If I check only variables after "xxxcom" -->no error > > Error message: > "Access violation at address 00403347 in module 'EpiData.exe' Read of > address 393938FB" > > Epidata 3.1 (270108) > Windows XP Pro > > Thanks for help > > Jonas Malmstedt, MD > Department of Vascular Surgery, N1:06 > Karolinska University Hospital > SE-171 76 Stockholm > > PS I have also noticed another problem: smtimes EpiData Will not read *.not > and *.rec files. I get an error telling me that the file name are not valid > or the file is used. When I try to open the same file not NotePad - no > problem! DS > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 78, Issue 17 > ******************************************** >

1 0

RE: Double Entry for Related Files
by epidata-list＠lists.umanitoba.ca 29 Apr '10

29 Apr '10

Sam, I thought about you related file problem and perhaps there is a workaround. I thougth for example of edaverse event notification of medication use. Each patient is using one or more medications and while using these may have two or more events simultaneously such as rash nausea and vomiting. Each event will be a record in a related file. But the unique identifier is the patient record and may cause trouble in double entry. Perhaps if each related record may be a combination, you me be able to run double entry independently. Example: Main qes file --- ID ##### name ___ sex___ medication ___ related file ---- ID ##### event __ eventID ________ description _____ Related chk file eventID before entry let eventID = ID + event end end If patient 123 has three events then eventID would be 123a 123b and 123c and may uniquely identify the events and double entry may be possible by this eventID. I did not test it although. But this means you would have to type all again if you already typed it all. Or perhaps exporting editing and importing may make this easier. kind regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com/ - sistema operacional

1 0

RE: Double Entry for Related Files
by epidata-list＠lists.umanitoba.ca 28 Apr '10

28 Apr '10

I understand the two different methods of double-entering data, and I do indeed want to "prepare for double-entry". The problem is that when I go to prepare the questionnaire for double entry, I can only choose to prepare either the parent OR the child file. If I choose the parent file, then a double-entry file is only created for the parent file - when I open it to double enter the data, it relates to the original child file, so it opens the parent double entry file along with the original child file. Since only one of the two files is a double entry file, the program thinks I am entering the data for the first time, and does not compare the alues entered to the values from the original file. I cannot seem to find a way to prepare both the parent and the child file for double entry together. If I prepare them for double entry separately, I run into similar problems. Sam ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Apr 2010 19:13:58 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Double Entry for Related Files To: epidata-list(a)lists.umanitoba.ca Message-ID: <4BD71B56.7020800(a)tbrieder.org> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Sam: There are two approaches to double-enter: 1) independently, 2) the second file depending on the first. You seemingly chose the latter ("prepare for double-entry"). If you choose that option, you must enter the records in the same sequence (I believe) and the value of each field in the second record will be compared to the corresponding one in the first and a discordance reported, so you can verify. Thus, no need to enter twice. Alternatively, you enter your related file pairs independently between first and second entry. You must have a unique identifier in both the parent and the child file. The sequence then doesn't matter of course. After you have entered parent1-child1 and parent2-child1, you validate parent1-vs-parent2 on the unique identifier, then child1-vs-child2 on that identifier. Hans On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > Hi, > > I have a questionnaire that uses two related .rec files for data entry. > I want to double enter the data by checking for discrepancies as the > data is entered the second time. Is it possible to do this for > questionnaires that span two .rec files? When I try to prepare for > double entry, the program creates a "file1_dbl.rec" file, but relates > it to the "file2.rec" file rather than creating a "file2_dbl.rec" file > to compare against. > > I am thinking that I will just have to un-relate the file, and enter > and double-enter the survey in two parts, but any help would be appreciated. > > Thanks, > > Sam > -- 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 -- Samuel Haddaway Research Assistant, International Projects National Opinion Research Center haddaway-sam(a)norc.org Phone: 301.634.9423

1 0

Related files and conditional chk
by epidata-list＠lists.umanitoba.ca 28 Apr '10

28 Apr '10

Hello epidata friends, Im occasionally reading emails in the list about limitations in the related rec files. The last I remember was about double entry, which I did not read a proposition of solution. Here goes another problems that I could not solve yet. Im working with a dataset entry with two purposes: 1) to estimate a trajectory of a particular liver enzyme over time while patients is under therapy and 2) estimate the risk of liver toxicity while in therapy. The tow objectives are time dependent. In the first objective the possible result is a graph with a line conecting dots which represents the enzyme values in each time point. The second is a cox model or a exponential survival model which the outcome is liver toxicity due to therapy. In this one, the medications may change over time. Therefore I was imagining creating a main recfile with clinical characteristics of each patient that are permanent, that is, do not change over time such as HIV serology status, and create tow related recfiles with 1) data about each liver panel with correspondent date and 2) the medication in use with initial date and end date with the end status (cure, default, death etc); both may be fed with several data from different dates for each patient. Now ... one common problem with dates is that very often typing mistakes make dates incompatible such as: 1) the second liver panel was collected BEFORE the first. 2) The end of medication was registered BEFORE the beginning or the second medication started BEFORE the end of the first. To control this sort of mistake is easy with conditional checking when the dates are in the same recfile. But if I make related files the conditional checking with dates should be done in the same field (or different fields) in different records. That is ... I should ask epidata to go in other record with the same key (ID) and check if the collection date is before or after the date of this open record. The question is ... is this possible? Does anyone have a sugestion to workaround (possibly having all the dates in the main recfile and related file)? An example: ******** Main qesfile ID #### name _____ hiv # start <dd/mm/yyyy> end <dd/mm/yyyy> toxicity # ******* First related file - liver panel ID #### coldate <dd/mm/yyyy> panelnum # alt #### ast #### ****** Secodn related file - medication ID #### TBdrugs _______ HIVdrugs _______ combstart <dd/mm/yyyy> combend <dd/mm/yyyy> outcome # Kind regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com/ - sistema operacional

1 0

Access violation error with Codebook command in EpiData 3.1
by epidata-list＠lists.umanitoba.ca 27 Apr '10

27 Apr '10

1 0

Double Entry for Related Files
by epidata-list＠lists.umanitoba.ca 27 Apr '10

27 Apr '10

Hi, I have a questionnaire that uses two related .rec files for data entry. I want to double enter the data by checking for discrepancies as the data is entered the second time. Is it possible to do this for questionnaires that span two .rec files? When I try to prepare for double entry, the program creates a "file1_dbl.rec" file, but relates it to the "file2.rec" file rather than creating a "file2_dbl.rec" file to compare against. I am thinking that I will just have to un-relate the file, and enter and double-enter the survey in two parts, but any help would be appreciated. Thanks, Sam -- Samuel Haddaway Research Assistant, International Projects National Opinion Research Center haddaway-sam(a)norc.org Phone: 301.634.9423

1 1

Year with two digits
by epidata-list＠lists.umanitoba.ca 27 Apr '10

27 Apr '10

Hello Epidata Friends, I know this will sound repetitive and passed over but Im not finding a workaround. I have a very ancient rec file created by EPI6, this dataset was abandoned in 1999. My intention was to update the rec and chk file for new data to come in and update the up to 2009. I was trying to export using epidata entry tool to Stata and do several editing within Stata and then import it again from Stata to epidata to keep on feeding the dataset. My problem is that the dates of birth and follow-up start are configured as dd/mm/yy , that is Year with tow digits. When I open the data from within Stata, weird dates come. Just the years look weird such as 01apr2020. All the years are 2020 or 2019 and I know the yars may range from 1986 to 1999. It seems that is not only a problem to add the 19.. before the dates year so far. So I guess, since Epidata does not accept dates with tow year digits, it is exporting with error. Therefore Im accepting any suggestions to workaround. kind regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com/ - sistema operacional

1 2

Access violation error with Codebook command in EpiData 3.1
by epidata-list＠lists.umanitoba.ca 26 Apr '10

26 Apr '10

1 0

EpiData Entry and multiple simultaneous users
by epidata-list＠lists.umanitoba.ca 26 Apr '10

26 Apr '10

Hi there, I have multiple data entry clerks entering data on different Epidata REC files. Because of data entry back-log I wish to get additional staff to enter data on the said REC files simultaneously. I have overcome this problem by "splitting" (more like copying the file REC to another terminal) the database REC file (with its CHK and QES) so that 2 staff could enter the data at same time. The problem is that when we assign a unique studyid, in say RECfile#1, RECfile#2 can't counter check if that studyid is being duplicated. Could someone show me how to share a common REC file for simultaneous data entry? I know Epidata can't be run through a network server, or linked to a server database, like MS SQL sever, or MySQL databases. If it can could you show me how to do this? or even place the REC files on the network drive and share them for data entry, is this possible? How? Regards,SK > Date: Sun, 25 Apr 2010 12:00:24 -0500 > From: epidata-list-request(a)lists.umanitoba.ca > Subject: EpiData-list Digest, Vol 78, Issue 13 > To: epidata-list(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. Ruwan Ratnayake est absent. (epidata-list(a)lists.umanitoba.ca) > 2. Re: EpiData-list Digest, Vol 78, Issue 12 > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 24 Apr 2010 13:44:57 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Ruwan Ratnayake est absent. > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <OF83D77D4E.69B1BB66-ON8525770F.00618016-8525770F.00618016@isn.rtss.qc..ca> > > Content-Type: text/plain; charset=ISO-8859-1 > > > Je serai absent(e) à partir du 2010-04-16 de retour le 2010-05-10. > > Veuillez prendre note que je serai absente de mon bureau le 19 avril à 10 > mai. > > Please note that I will be out of the office from April 19 to May 10. > > ------------------------------ > > Message: 2 > Date: Sat, 24 Apr 2010 19:19:35 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 78, Issue 12 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <o2gbf1bb7701004241119t3102aa00o39bbd86094e5dfed(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Claire, > > At each time you finish entering a record, you will be asked "do you want > the record on disk?" > When you click or press return key the record is saved. > Step 1: please go to File then > Close the form > Step 2 : go to " 5.Document" then > View to view your data entered. > Step 3: go to "6. Export Data" chose from the drop menu Excel then follow > on screen guide. > Step 4: your file will be exported to Excel where your original rec.file is > located. > > Please let me know if I misunderstood your request and hoping this will > help. > > Best wishes > > Tieble > London, UK > On 24 April 2010 18:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > > > 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. Saving Data... (epidata-list(a)lists.umanitoba.ca) > > 2. Re: Saving Data... (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 23 Apr 2010 16:58:35 -0400 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] Saving Data... > > To: <epidata-list(a)lists.umanitoba.ca> > > Message-ID: > > < > > A5951E9003DBA34C9151CEAF8257F9E6054BE54A(a)INFLEXX-EXCHANGE.Inflexxion.com> > > > > Content-Type: text/plain; charset="us-ascii" > > > > Good Day, > > > > > > > > I have been searching the archived emails and help offerings to try to > > solve this problem and I have not been able to find the help I am > > looking for. > > > > > > > > I am presently running EpiData 3.1 with Windows Vista. > > > > > > > > I have created a questionnaire and loaded the values for the > > questionnaire. I clicked on the "Enter Data" button. I entered my > > data. Now, the only menu buttons I have at the top of the screen are > > the following: "FILE", "GOTO", "FILTER", "WINDOW", "HELP". Nowhere in > > any of these drop-down menus is the option to either save the data I > > have entered, or to export it (preferably to Excel) so that it can be > > saved there. > > > > > > > > Please advise. Thank you! > > > > > > > > > > > > Claire Johnson, MSW > > > > Research Coordinator > > > > Inflexxion, Inc. > > > > T (617) 332 6028 x242 > > F (617) 332 1820 > > > > www.inflexxion.com > > > > > > > > This message may contain information that is privileged, confidential > > and exempt from disclosure under applicable law. If the reader of this > > message is not the intended recipient, or an agent responsible for > > delivering it to the intended recipient, you are hereby notified that > > you have received this electronic message in error and that any review, > > dissemination, distribution or copying of this message is strictly > > prohibited. If you have received this electronic message in error, > > please notify us immediately by telephone in the United States at > > 617-332-6028, and delete the original message from your system. Thank > > you. > > > > > > > >

1 2

Re: EpiData-list Digest, Vol 78, Issue 12
by epidata-list＠lists.umanitoba.ca 24 Apr '10

24 Apr '10

Hi Claire, At each time you finish entering a record, you will be asked "do you want the record on disk?" When you click or press return key the record is saved. Step 1: please go to File then > Close the form Step 2 : go to " 5.Document" then > View to view your data entered. Step 3: go to "6. Export Data" chose from the drop menu Excel then follow on screen guide. Step 4: your file will be exported to Excel where your original rec.file is located. Please let me know if I misunderstood your request and hoping this will help. Best wishes Tieble London, UK On 24 April 2010 18:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Saving Data... (epidata-list(a)lists.umanitoba.ca) > 2. Re: Saving Data... (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 23 Apr 2010 16:58:35 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Saving Data... > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > < > A5951E9003DBA34C9151CEAF8257F9E6054BE54A(a)INFLEXX-EXCHANGE.Inflexxion.com> > > Content-Type: text/plain; charset="us-ascii" > > Good Day, > > > > I have been searching the archived emails and help offerings to try to > solve this problem and I have not been able to find the help I am > looking for. > > > > I am presently running EpiData 3.1 with Windows Vista. > > > > I have created a questionnaire and loaded the values for the > questionnaire. I clicked on the "Enter Data" button. I entered my > data. Now, the only menu buttons I have at the top of the screen are > the following: "FILE", "GOTO", "FILTER", "WINDOW", "HELP". Nowhere in > any of these drop-down menus is the option to either save the data I > have entered, or to export it (preferably to Excel) so that it can be > saved there. > > > > Please advise. Thank you! > > > > > > Claire Johnson, MSW > > Research Coordinator > > Inflexxion, Inc. > > T (617) 332 6028 x242 > F (617) 332 1820 > > www.inflexxion.com > > > > This message may contain information that is privileged, confidential > and exempt from disclosure under applicable law. If the reader of this > message is not the intended recipient, or an agent responsible for > delivering it to the intended recipient, you are hereby notified that > you have received this electronic message in error and that any review, > dissemination, distribution or copying of this message is strictly > prohibited. If you have received this electronic message in error, > please notify us immediately by telephone in the United States at > 617-332-6028, and delete the original message from your system. Thank > you. > > > >

1 0

Ruwan Ratnayake est absent.
by epidata-list＠lists.umanitoba.ca 24 Apr '10

24 Apr '10

Je serai absent(e) à partir du 2010-04-16 de retour le 2010-05-10. Veuillez prendre note que je serai absente de mon bureau le 19 avril à 10 mai. Please note that I will be out of the office from April 19 to May 10.

1 0

Saving Data...
by epidata-list＠lists.umanitoba.ca 23 Apr '10

23 Apr '10

Good Day, I have been searching the archived emails and help offerings to try to solve this problem and I have not been able to find the help I am looking for. I am presently running EpiData 3.1 with Windows Vista. I have created a questionnaire and loaded the values for the questionnaire. I clicked on the "Enter Data" button. I entered my data. Now, the only menu buttons I have at the top of the screen are the following: "FILE", "GOTO", "FILTER", "WINDOW", "HELP". Nowhere in any of these drop-down menus is the option to either save the data I have entered, or to export it (preferably to Excel) so that it can be saved there. Please advise. Thank you! Claire Johnson, MSW Research Coordinator Inflexxion, Inc. T (617) 332 6028 x242 F (617) 332 1820 www.inflexxion.com This message may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this electronic message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this electronic message in error, please notify us immediately by telephone in the United States at 617-332-6028, and delete the original message from your system. Thank you.

1 1

Re: EpiData-list Digest, Vol 78, Issue 10
by epidata-list＠lists.umanitoba.ca 12 Apr '10

12 Apr '10

On 4/11/10, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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..." > -- Sent from my mobile device SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 -------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

Re: EpiData-list Digest, Vol 78, Issue 7
by epidata-list＠lists.umanitoba.ca 11 Apr '10

11 Apr '10

Thanks Jamie, You repsonse adequately answered my question. I appreciate this. Regards, Maruf Sanni (Research Officer) National Centre for Technology Management Training and Research Department P M B 012 Obafemi Awolowo University Ile Ife Nigeria +2348057070192 maruf.sanni(a)nacetem.org --- On Thu, 4/8/10, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> wrote: From: epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Subject: EpiData-list Digest, Vol 78, Issue 7 To: epidata-list(a)lists.umanitoba.ca Date: Thursday, April 8, 2010, 10:01 AM 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. Re: EpiData-list Digest, Vol 78, Issue 6 (epidata-list(a)lists.umanitoba.ca) 2. Re: Re: EpiData-list Digest, Vol 78, Issue 6 (epidata-list(a)lists.umanitoba.ca) 3. Ruwan Ratnayake est absent. (epidata-list(a)lists.umanitoba.ca) 4. adding variables to existing rec. file (epidata-list(a)lists.umanitoba.ca) 5. Vedr.: [EpiData-list] adding variables to existing rec. file (epidata-list(a)lists.umanitoba.ca) 6. adding variables to existing rec. file (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 7 Apr 2010 10:30:38 -0700 (PDT) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re: EpiData-list Digest, Vol 78, Issue 6 To: epidata-list(a)lists.umanitoba.ca Message-ID: <273384.54006.qm(a)web30205.mail.mud.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Thanks a lot Jamie, But pls do you know the function of the " *100+ " between market ID and shop ID? Maruf Sanni (Research Officer) National Centre for Technology Management Training and Research Department P M B 012 Obafemi Awolowo University Ile Ife Nigeria +2348057070192 maruf.sanni(a)nacetem.org --- On Wed, 4/7/10, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> wrote: From: epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Subject: EpiData-list Digest, Vol 78, Issue 6 To: epidata-list(a)lists.umanitoba.ca Date: Wednesday, April 7, 2010, 10:00 AM 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. command (epidata-list(a)lists.umanitoba.ca) 2. Re: command (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 7 Apr 2010 01:26:40 -0700 (PDT) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] command To: epidata-list(a)lists.umanitoba.ca Message-ID: <574231.70254.qm(a)web30208.mail.mud.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Please, does any body understand whether this ("market ID*100+shop ID") is a command or not? If it is a command, what exactly would it achieve or do? Thanks, Maruf Sanni (Research Officer) National Centre for Technology Management Training and Research Department P M B 012 Obafemi Awolowo University Ile Ife Nigeria +2348057070192 maruf.sanni(a)nacetem.org ------------------------------ Message: 2 Date: Wed, 7 Apr 2010 09:14:04 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] command To: epidata-list(a)lists.umanitoba.ca Message-ID: <BLU0-SMTP756BCBDA32DB07F8641A0BFD170(a)phx.gbl> Content-Type: text/plain; charset=us-ascii It it not an EpiData command, but looks like part of the syntax to create a single variable that identifies a particular shop: msid = marketID*100 * shopID Note - no spaces... Jamie Ottawa On 2010-04-07, Maruf wrote: > Please, does any body understand whether this ("market ID*100+shop ID") is a command or not? > If it is a command, what exactly would it achieve or do? ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 78, Issue 6 ******************************************* ------------------------------ Message: 2 Date: Wed, 7 Apr 2010 13:45:06 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 78, Issue 6 To: epidata-list(a)lists.umanitoba.ca Message-ID: <BLU0-SMTP2360AAC41EC25899DBCB28FD170(a)phx.gbl> Content-Type: text/plain; charset=us-ascii Say market ID is 3 and shop ID is 25. Then the code for the market/shop combination is 3 * 100 + 25 (3 times 100 plus 25) = 325 Of course, this only works if the IDs are numbers. Jamie > But pls do you know the function of the " *100+ " > between market ID and shop ID? ------------------------------ Message: 3 Date: Wed, 7 Apr 2010 13:33:36 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Ruwan Ratnayake est absent. To: epidata-list(a)lists.umanitoba.ca Message-ID: <OF95C0675E.9EE5D497-ON852576FE.006075F9-852576FE.006075F9(a)isn.rtss.qc.ca> Content-Type: text/plain; charset=ISO-8859-1 Je serai absent(e) à partir du 2010-04-07 de retour le 2010-04-08. Veuillez prendre note que je serai absente de mon bureau le 7 avril. I will be out of the office on April 7. ------------------------------ Message: 4 Date: Thu, 08 Apr 2010 11:27:12 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] adding variables to existing rec. file To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <4BBDBD90.958F.00EB.0(a)med.uni-tuebingen.de> Content-Type: text/plain; charset=UTF-8 Can anyone give me advice on how to add a variable to an existing rec file when data entry during an ongoing cohort study without loosing the recorded data entries? Thanks Philipp Dr. Philipp Zanger, MD DTM DEpi Internist / Tropenmedizin Institut fÃ¼r Tropenmedizin WilhelmstraÃŸe 27 72074 TÃ¼bingen Tel.: 0049-(0)7071-29-82365 Fax: 0049-(0)7071-29-5267 ------------------------------ Message: 5 Date: Thu, 8 Apr 2010 11:48:19 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Vedr.: [EpiData-list] adding variables to existing rec. file To: epidata-list(a)lists.umanitoba.ca Message-ID: <OF11AB7F1A.52E1C803-ONC12576FF.0035912B-C12576FF.0035E41B(a)ipm.hosp.dk> Content-Type: text/plain; charset="ISO-8859-1" Hi Pihilipp, Not to difficult: Revise the qes file with the new variable Next time you open the rec file it will notice that the qes file has changed (must be in the same directory) and will offer to update the rec file. Accept this - no data are lost If neccesary you can then also revise the chk file with relevant info about the new variable. Voila. Kind regards Claus Holst Copenhagen epidata-list(a)lists.umanitoba.ca Sendt af: epidata-list-bounces(a)lists.umanitoba.ca 08-04-2010 11:27 Til <epidata-list(a)lists.umanitoba.ca> cc Emne [EpiData-list] adding variables to existing rec. file Can anyone give me advice on how to add a variable to an existing rec file when data entry during an ongoing cohort study without loosing the recorded data entries? Thanks Philipp Dr. Philipp Zanger, MD DTM DEpi Internist / Tropenmedizin Institut für Tropenmedizin Wilhelmstraße 27 72074 Tübingen Tel.: 0049-(0)7071-29-82365 Fax: 0049-(0)7071-29-5267 _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list ------------------------------ Message: 6 Date: Thu, 08 Apr 2010 12:55:13 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] adding variables to existing rec. file To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <4BBDD231.958F.00EB.0(a)med.uni-tuebingen.de> Content-Type: text/plain; charset=UTF-8 Thank you Claus! Putting them into the same directory solved my problem! I really like EpiData! Philipp Dr. Philipp Zanger, MD DTM DEpi Internist / Tropenmedizin Institut fÃ¼r Tropenmedizin WilhelmstraÃŸe 27 72074 TÃ¼bingen Tel.: 0049-(0)7071-29-82365 Fax: 0049-(0)7071-29-5267 ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 78, Issue 7 *******************************************

1 0

Data missing after merge - any ideas?
by epidata-list＠lists.umanitoba.ca 09 Apr '10

09 Apr '10

Hello everyone, I have two files - one fairly large (9000 records, 51 fields) and a second one with 500 records, and the same 51 fields. I can read and manipulate both files in Epidata Analysis but when I try to merge them using the common field of ID number, the second one has all missing variables, except the common field of ID number. I can't think what I'm doing wrong. Any guidance would be very helpful! Thanks, Susie Foster

1 2

adding variables to existing rec. file
by epidata-list＠lists.umanitoba.ca 08 Apr '10

08 Apr '10

Can anyone give me advice on how to add a variable to an existing rec file when data entry during an ongoing cohort study without loosing the recorded data entries? Thanks Philipp Dr. Philipp Zanger, MD DTM DEpi Internist / Tropenmedizin Institut für Tropenmedizin Wilhelmstraße 27 72074 Tübingen Tel.: 0049-(0)7071-29-82365 Fax: 0049-(0)7071-29-5267

1 2

Re: EpiData-list Digest, Vol 78, Issue 6
by epidata-list＠lists.umanitoba.ca 07 Apr '10

07 Apr '10

Thanks a lot Jamie, But pls do you know the function of the " *100+ " between market ID and shop ID? Maruf Sanni (Research Officer) National Centre for Technology Management Training and Research Department P M B 012 Obafemi Awolowo University Ile Ife Nigeria +2348057070192 maruf.sanni(a)nacetem.org --- On Wed, 4/7/10, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> wrote: From: epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Subject: EpiData-list Digest, Vol 78, Issue 6 To: epidata-list(a)lists.umanitoba.ca Date: Wednesday, April 7, 2010, 10:00 AM 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. command (epidata-list(a)lists.umanitoba.ca) 2. Re: command (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 7 Apr 2010 01:26:40 -0700 (PDT) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] command To: epidata-list(a)lists.umanitoba.ca Message-ID: <574231.70254.qm(a)web30208.mail.mud.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Please, does any body understand whether this ("market ID*100+shop ID") is a command or not? If it is a command, what exactly would it achieve or do? Thanks, Maruf Sanni (Research Officer) National Centre for Technology Management Training and Research Department P M B 012 Obafemi Awolowo University Ile Ife Nigeria +2348057070192 maruf.sanni(a)nacetem.org ------------------------------ Message: 2 Date: Wed, 7 Apr 2010 09:14:04 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] command To: epidata-list(a)lists.umanitoba.ca Message-ID: <BLU0-SMTP756BCBDA32DB07F8641A0BFD170(a)phx.gbl> Content-Type: text/plain; charset=us-ascii It it not an EpiData command, but looks like part of the syntax to create a single variable that identifies a particular shop: msid = marketID*100 * shopID Note - no spaces... Jamie Ottawa On 2010-04-07, Maruf wrote: > Please, does any body understand whether this ("market ID*100+shop ID") is a command or not? > If it is a command, what exactly would it achieve or do? ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 78, Issue 6 *******************************************

1 1

Ruwan Ratnayake est absent.
by epidata-list＠lists.umanitoba.ca 07 Apr '10

07 Apr '10

Je serai absent(e) à partir du 2010-04-07 de retour le 2010-04-08. Veuillez prendre note que je serai absente de mon bureau le 7 avril. I will be out of the office on April 7.

1 0

command
by epidata-list＠lists.umanitoba.ca 07 Apr '10

07 Apr '10

Please, does any body understand whether this ("market ID*100+shop ID") is a command or not? If it is a command, what exactly would it achieve or do? Thanks, Maruf Sanni (Research Officer) National Centre for Technology Management Training and Research Department P M B 012 Obafemi Awolowo University Ile Ife Nigeria +2348057070192 maruf.sanni(a)nacetem.org

1 1

Re: EpiData-list Digest, Vol 78, Issue 4
by epidata-list＠lists.umanitoba.ca 05 Apr '10

05 Apr '10

Similarly you can also get the mergevar with the following commands below: cd "D:\bernard\epidemio" dir read fille merge fiche /file=pere/table /update/updateall Good luck Tieble On 5 April 2010 18:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Re: Re: [EpiData-list] Related files > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 04 Apr 2010 22:09:11 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: Re: [EpiData-list] Related files > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4BB8F1E7.9040603(a)tbrieder.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > An alternative is reading in the child file first, if the child file has > multiple entries for the same parent file: > > read "d:\bernard\epidemio\fille.rec" > merge fiche /file=pere.rec" /table > > This uses the "pere" file as a look-up table (see Help file in analysis) > and "fiche" needs to be unique only in the parent but not the child file, > > Hans > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > > The correct way to read these files into analysis is: > > > > read "d:\bernard\epidemio\fille.rec" > > merge fiche /file=ere.rec" > > > > merge requires key unique in the file it reads. > > > > Jamie Hockin > > Ottawa > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 78, Issue 4 > ******************************************* >

1 0

Related files
by epidata-list＠lists.umanitoba.ca 04 Apr '10

04 Apr '10

Hello, I have two related files : The first “pere.rec with : - QES File Fiche #### var1 ## var2 ## - CHK File fiche key unique end var2 if var2=1 then relate fiche pere.rec endif if var2<>1 then gotowrite endif end The second “fille.rec” with : - QES File fiche #### var3 ## var4 ## - CHK File fiche key end These two related files are correct to entry. But, in analysis, the commands : Read "D:\Bernard\Epidemio\pere.rec" merge fiche /file=”fille.rec" Reponse of software : Non-unique key in: D:\Bernard\Epidemio\fille.rec It is the same problem with “key unique” and “key” with “1” at the end. Thank you your help. Bernard Branger, France _____ J’utilise la version gratuite de SPAMfighter <http://www.spamfighter.com/lfr> pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 1455 courriels spam. Optimisez votre PC trop lent <http://www.spamfighter.com/SLOW-PCfighter/Lang_FR/?cid=sigfr>

1 2

Res: EpiData-list Digest, Vol 78, Issue 1
by epidata-list＠lists.umanitoba.ca 02 Apr '10

02 Apr '10

Hello Pedro Emmanuel and all EpiData friends. I think it might be a keyboard problem. I have experienced some similar problem when writing in LaTeX (in a Sweave file for R). Don't remember well in which UTF-8 (with RKWard and Kile under Linux) or ISO-8859-1 encoding what looked in screen and paper like ">" didn't work like such operator. I guess I solved the problem by converting the code and retype the ">"s. Hope it helps :-) Fúlvio B. Nedel Curso de Medicina, Universidade de Santa Cruz do Sul Brasil ----- Mensagem original ---- De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Para: epidata-list(a)lists.umanitoba.ca Enviadas: Quinta-feira, 1 de Abril de 2010 14:00:28 Assunto: EpiData-list Digest, Vol 78, Issue 1 Observação: a mensagem encaminhada está anexada. 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. Exporting to epidata format - not valid boolean expression (epidata-list(a)lists.umanitoba.ca) 2. Exporting to epidata format - not valid boolean expression BUG??? (epidata-list(a)lists.umanitoba.ca) ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com

1 0

Exporting to epidata format - not valid boolean expression BUG???
by epidata-list＠lists.umanitoba.ca 01 Apr '10

01 Apr '10

Hello EpiData friends, I just sent an email about an error "invalid boolean expression" when trying to export to EpiData format with EpiData entry with filters. I guess that I found an unexpected bug. When I use the following filters the export is OK (alt1 is numeric variable formated as ####.##). alt1 <> 42 alt1 = 42 But when I use the following filters the export give this error. alt1 >= 42 alt1 <= 42 alt1 > 42 alt1 < 42 Therefore, I guess there is something to do with the > or < signs! Did anyone experience such an error before? Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil ---------- Forwarded message ---------- From: Pedro Emmanuel Alvarenga Americano do Brasil < emmanuel.brasil(a)gmail.com> Date: 2010/4/1 Subject: Exporting to epidata format - not valid boolean expression To: epidata-list(a)lists.umanitoba.ca Hello EpiData friends, Im having a little trouble that I would appreciate very much some help. I have a rec file which I would like to create a subset. I tried to use the EpiData entry data export, using the filter option. When I set the filter such as: hepato <> 2 it is ok. But when I set the filter as alt1 >= 42 ... or I set the filter as ... (alt >= 42) or (hepato <> 2) I get an error saying this is not a valid boolean expression. I tried in several different ways and I couldnt figure out what Im doing worng. Any tip? Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil

1 0

Exporting to epidata format - not valid boolean expression
by epidata-list＠lists.umanitoba.ca 01 Apr '10

01 Apr '10

Hello EpiData friends, Im having a little trouble that I would appreciate very much some help. I have a rec file which I would like to create a subset. I tried to use the EpiData entry data export, using the filter option. When I set the filter such as: hepato <> 2 it is ok. But when I set the filter as alt1 >= 42 ... or I set the filter as ... (alt >= 42) or (hepato <> 2) I get an error saying this is not a valid boolean expression. I tried in several different ways and I couldnt figure out what Im doing worng. Any tip? Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil

1 0

Linking Epidata to an online database
by epidata-list＠lists.umanitoba.ca 26 Mar '10

26 Mar '10

Hi Are there any of you who have experience with linking Epidata to an online database? If so, how did you manage to do so and how did it work? I am to start up a large study where several subinvestigators will have to enter data from there own computer on a daily basis. I think it would be an advantage to the data management, if we did not have to merge all the datafiles manually, but instead enter them into an online database after each entry session. Thank you, for your help!

1 2

Can Epi Data present text in Kiswahili
by epidata-list＠lists.umanitoba.ca 23 Mar '10

23 Mar '10

We would like to have both english and kiswahili presented in the data entry screen. Is this possible?? Thanks. Conrad

1 0

Re: EpiData-list Digest, Vol 77, Issue 12
by epidata-list＠lists.umanitoba.ca 22 Mar '10

22 Mar '10

Dear Hans, Thank you for asking; indeed the idno is key unique 1 in file.rec1 and key unique 2 in file.rec2 and file.rec 3. I have tested the files using different computers (at least 3) they all work fine (sorry for not stating this in my previous request). However, the error occurs and continues to occur when I use my lap top (Vista) and yet this is my main tool to design the entire database. Clearly, the error may not be associated with EpiData; but something to do with my laptop (with Vista, in particular). Are there any solutions or just ignore it? Kind regards Tieble On 21 March 2010 17:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Re: "Cannot apply opGT to missing operands" > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 20 Mar 2010 21:26:16 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] "Cannot apply opGT to missing operands" > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4BA52F68.6030302(a)tbrieder.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear Tieble: > > Just to get it out of the way (apologies if it is too trivial a > question): is your idno KEY UNIQUE in file1.rec and KEY in file2.rec? I > am asking because I simulated it and get no error message. > > Hans > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: > > Dear colleagues, > > > > Is there a possible solution to avoid the error message > > "Error in IF expression; Cannot apply opGT to missing operands" > > during data entry under the check commands below? > > NB: (values and labels 0=No; 1=Yes) for varsv1 > > > > varsv1 > > COMMENT LEGAL USE label_varsv1 > > MUSTENTER > > TYPE COMMENT > > AFTER ENTRY > > IF varsv1=1 THEN > > GOTO WRITE > > ENDIF > > IF varsv1=0 THEN > > RELATE idno file2.rec > > ENDIF > > END > > END > > I am not sure if this error message is related to a bug or typo. > > Your help would be very appreciated. > > > > Tieble > > London, UK > > > > > > -- > 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 > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 77, Issue 12 > ******************************************** >

1 1

"Cannot apply opGT to missing operands"
by epidata-list＠lists.umanitoba.ca 20 Mar '10

20 Mar '10

Dear colleagues, Is there a possible solution to avoid the error message "Error in IF expression; Cannot apply opGT to missing operands" during data entry under the check commands below? NB: (values and labels 0=No; 1=Yes) for varsv1 varsv1 COMMENT LEGAL USE label_varsv1 MUSTENTER TYPE COMMENT AFTER ENTRY IF varsv1=1 THEN GOTO WRITE ENDIF IF varsv1=0 THEN RELATE idno file2.rec ENDIF END END I am not sure if this error message is related to a bug or typo. Your help would be very appreciated. Tieble London, UK

1 1

Text editor for EpiData Analysis programs
by epidata-list＠lists.umanitoba.ca 18 Mar '10

18 Mar '10

Jens and I gave last week a course for operations research fellows in The Union's training program. One colleague pointed us to the excellent free Crimson text editor (http://www.crimsoneditor.com/). Jens wrote then the necessary key and language components that can be inserted into the editor to read and edit EpiData programs color-coded to reduce errors if you wish to edit your analysis programs outside the native EpiData Analysis text editor. I can strongly recommend it. Visit the EpiData website http://www.epidata.dk/download.php page and look at the bottom for utilities. Hans PS: Thank you, Zaw, for pointing us to the editor, and thank you Jens, to make it particularly useful for EpiData Analysis programs.

1 2

Re: EpiData-list Digest, Vol 77, Issue 8
by epidata-list＠lists.umanitoba.ca 18 Mar '10

18 Mar '10

Hi Jamie, Thank you very much; it worked in my hands and I managed to reproduce it successfully. I will try to apply it to the entire multilevel database Tieble London, UK On 17 March 2010 17:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Change the colour of data entry form; and entering contact > number for each person (epidata-list(a)lists.umanitoba.ca) > 2. Re: Change the colour of data entry form; and entering > contact number for each person (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Mar 2010 19:41:03 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Change the colour of data entry form; and > entering contact number for each person > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <bf1bb7701003161241o6a547b5fxd5d665ca74b6398b(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear colleagues, > > I am designing relational database and would like the data entry staff > to be able to enter the identification number (idno) and not to have to > type > in the contact number of each idno (person). The field for the contact > number should be field automatically for each idno. More importantly, it > should start with one for each idno. > > For example for idno 001 contact 1; 2; 3; 4; 5; 6; 7; 8; 9; 10 > for idno 002 contact 1; 2; 3; > ..................................100 > > Clearly, given that idno is a string; I have tried the following command > which > IDNO > AFTER ENTRY > IF IDNO=IDNO THEN > LET CONTACTNUM=1+RECORDCOUNT > ENDIF > END > The result is not different from automatic contact number. > Any suggestions will be appreciated. > > Thank you for your time and suggestions > > Tieble > > > ------------------------------ > > Message: 2 > Date: Tue, 16 Mar 2010 19:30:09 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Change the colour of data entry form; and > entering contact number for each person > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP90051533776303A978B93FFD2D0(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > Here is one solution that requires you to have a field in the main case > .rec file that holds the number of contacts entered so far. It may not be > perfect, but should work for data entry and record review just fine. > > There are 4 files in my example > main.qes - the Main case file > main.chk > contact.qes - the Contact file > contact.chk > > The .chk files pass the highest contact number back and forth using the > global variable xcon and the data entry person cannot change the contact > number. > > The "before record" block in contact.chk increments xcon to give the next > contact number, but this only gets saved back to main.rec when a new record > is saved. If only existing records are revised and saved, the number of > contacts does not change. > > This is a example of related files communicating with each other through a > global variable. > > I hope this helps. >

1 0

Change the colour of data entry form; and entering contact number for each person
by epidata-list＠lists.umanitoba.ca 16 Mar '10

16 Mar '10

Dear colleagues, I am designing relational database and would like the data entry staff to be able to enter the identification number (idno) and not to have to type in the contact number of each idno (person). The field for the contact number should be field automatically for each idno. More importantly, it should start with one for each idno. For example for idno 001 contact 1; 2; 3; 4; 5; 6; 7; 8; 9; 10 for idno 002 contact 1; 2; 3; ..................................100 Clearly, given that idno is a string; I have tried the following command which IDNO AFTER ENTRY IF IDNO=IDNO THEN LET CONTACTNUM=1+RECORDCOUNT ENDIF END The result is not different from automatic contact number. Any suggestions will be appreciated. Thank you for your time and suggestions Tieble

1 1

Re: Re: FW: Suggestion for automatic checks in new Epidata manager
by epidata-list＠lists.umanitoba.ca 12 Mar '10

12 Mar '10

Hi I would like to share my experience on the following suggestion by Jamie < A great addon or standalone module will be a simple XML editor for recxml files, to be used at our own risk. I don't know if such things exist in other areas, but there must be.> I have only recently started using epidata (Epidata Entry, the stable release) and must say the simple check file format was a great relief. The one thing lacking in the check file editor was lack of tools that can assist while writing the Check file codes (syntax highlighting). What i did was to start using a third party text editor (notepad++) and created a custom scheme that included coloured codes for if-then loops, various commands, comments shading etc. Immediately I was able to collapse the if-then loops, check if my commands were complete etc. I found it quite helpful in writing the CHK code. I can see if there is a way that it can be shared with the group. >From here on, I am afraid a wishlist starts :-) Having a XML editor within Epidata Manager I believe is a great idea. As a personal choice, for an XML editor for Epidata, I would like to have the following features w.r.t. check code: 1. Assistance that creates a termination code as soon as a command is inserted. Will help in creating compete codes 2. Syntax highlighting: Will decrease spelling mistakes and omission of closing sections (use of multiple brackets, END, ENDIF etc ), 3. Variable list: Will decrease spelling mistakes ! 4. Command list and assistance: type initial letters and the possible commands come as a dropdown ! An XML template can also probably be developed that has sections on: 1. Legal values and codes 2. Missing values 3. Before file commands 4. Before Record commands 5. Variable specific Commands: Calculations, If-then loops, Hide, Unhide, Key Unique 6. After Record commands 7. After File Commands But I agree that this would be probably a very low priority task. Wishlist ends ! Regards Vivek

1 0

Suggestion for automatic checks in new Epidata manager
by epidata-list＠lists.umanitoba.ca 11 Mar '10

11 Mar '10

Hi All, Jens was here at Epicentre to discuss some of the future plans for Epidata, and we had a brief overview of Epidata manager. As someone who writes qes/chk files using a text editor, I was disappointed to hear that it would not be possible to do this using Epidata manager (although the possibilty is there to import pre written qes files). In discussion with Jens, we talked about a solution to how a pre-written chk file can also be incorporated with Epidata manager. My suggestion is to have a data dictionary, where you not only specify the variable name, variable label, value labels and the data format, but you also add attributes for missing values, range checks , legal values etc. The dictionary could be a CSV file, that can be easily created using excel. Something along the lines of ..... Ideally however, what I would like is to have more flexibility, where you can assign the same attribute to the variables concerned in one statement, rather than listing one by one as a above, for example For all variables whose value 9 should be treated as missing, the attribute missing can given using for example the for loop as in stata, for gender locat type case { missing=9 } Also for those variables that share the same labels, you should be able to define one label and then assign to the variable concerned. Once the dictionary is imported into Epidata manager, you can then use the graphics device to organise the data entry screen. Food for thought, I hope? All the best Sarala

1 2

Can Epi Data be used on a Macbook
by epidata-list＠lists.umanitoba.ca 04 Mar '10

04 Mar '10

Just wondering if Epi Data can be run on a Apple Mac machine. Any experiences?? Thanks for any input Conrad

1 4

Re: [EpiData-list] Outbreak analysis/gnerating attack rate tables
by epidata-list＠lists.umanitoba.ca 02 Mar '10

02 Mar '10

thanks Jamie - that is great. Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 2/03/2010 2:42 p.m. >>> You can do this using the menus. When you select TABLES on the Analysis task bar, the dialogue box you get can be expanded by dragging the lower left corner. Then the full set of options appears. You can check Compact for the Table Type and then choose RR or OR, etc. Jamie Hockin Ottawa -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smx.co.nz ______________________________________________________________________________

1 0

Outbreak analysis/gnerating attack rate tables
by epidata-list＠lists.umanitoba.ca 01 Mar '10

01 Mar '10

Hi I have recently upgraded to version 2.2.171 of epidata analysis. I mainly use Epidata analysis to analyse disease outbreaks and with this new version I am finding it more difficult to ask for the attack rate table that is such a useful tool. Perhaps I am getting confused because I have not used epidata analysis for a while, but I thought that in earlier versions, it was possible to select an attack rate table (with relative risk, CI and pvalue for all exposures of interest) using options from the analysis menu. This time I had to search around the help menu and try and find the code. The code I used was tables SICK VARIABLE 1 VARIABLE 2 etc /CT/oa. Is there some way I can ask for this table through the menus? The reason I am asking is that I want to show other people in our unit how to use epidata to create an attack rate table and I think they will find it easier to go through a menu. thanks very much Christine istinfo/epidata ( 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..." Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smx.co.nz ______________________________________________________________________________

1 1

remove me from this list
by epidata-list＠lists.umanitoba.ca 23 Feb '10

23 Feb '10

remove me from this list

1 0

Status and plans for development (as of February 2010)
by epidata-list＠lists.umanitoba.ca 22 Feb '10

22 Feb '10

This is a brief status of developments - (rather technical in content) It is reassuring to see, that the interest in testing is rather large (Approximate download counts for latest version: Linux 50 , Mac 75 and Windows 300). Few comments have been given on the list, but I take that as a positive indication - I hope I am right, otherwise please notify on the list. The short story is: We are definitely moving forward - the basic way of working in graphic mode with data definition is more or less in place. But we must spend time on implementing related data structures and finding a final data structure. Therefore the first EpiData Entry Client based on the new principles will not come out until some time from now. The longer story is: During the most recent decade use of standardised data formats in public sectors and research has become an increasingly important issue. The idea of this is that data should be usable in any application and system based on published verifiable standards (XML based). XML is one of the structured information formats for machine readable information published by the W3C organisation - and is very complex - other ones from W3C are css and html. The published standards for XML based data documentation and storage of data as such are unfortunately plenty, a few of these are DDI (see DDI-alliance.org), CDISC ODM (see cdisc.org), SDMX (see sdmx.org). It seems as medicine, national statistics and the social sciences each have developed their own. The only common denominator seems to be in relation to overall descriptions such as "title", "contributor", abstract etc. These terms are well known from citations and are based on a metadata set called Dublin Core Metadata (see http://dublincore.org/specifications/). For implementation of a XML based file format in the EpiData Software it would seem obvious to NOT develop a new one, but instead use one or more of the mentioned ones. Therefore there have been discussions with data documentation specialists at the Danish Data Archives (see http://samfund.dda.dk/default-en.asp). Following these discussions and after studying several published standards it has been decided that the EpiData Software XML format will conform to the overall principles of the mentioned standards, but also that we must work with a restricted set of these. The nature of the EpiData project is to be focused on simplicity and we must stick to this principle. Otherwise we would be lost in months of generalisation, of no interest to the general user and also completely unrealistic within the economical and personal resources available. The time frame for the next phases are uncertain, but I will give orientation on this list as improvements are made and obstacles removed. Most likely there will be a meeting in the second week of March in Paris for detailed discussions on some of these issues. More information on that later. regards Jens Lauritsen EpiData Association

1 0

Re: Copy and Paste an Entry
by epidata-list＠lists.umanitoba.ca 17 Feb '10

17 Feb '10

Hello YC, Though i appreciate the solution YMP is giving you, i think you can also think of using the repeat command, since it is more easy play around with. With that you can be able to enter a field once and the next recode the field comes with the previous entry as a default which just needs your confirmation. All the best Edson BN On Tue, Feb 16, 2010 at 10:00 AM, <epidata-list-request(a)lists.umanitoba.ca>wrote: > 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. RE: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > 2. Re: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Feb 2010 18:51:52 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] Copy and Paste an Entry? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <00bf01caae67$8ee97710$acbc6530$@martin-prevel@ird.fr> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I think the best way to get round this problem is to have a relational data > base with two files: > (i) the "Master" file with patient's information > (ii) the related file with daily information > > There are several examples of such related data entry and how it works on > the Epidata website > > Hope this helps > > YMP > > > -----Message d'origine----- > De : epidata-list-bounces(a)lists.umanitoba.ca [mailto: > epidata-list-bounces(a)lists.umanitoba.ca] De la part de > epidata-list(a)lists.umanitoba.ca > Envoyé : lundi 15 février 2010 17:38 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] Copy and Paste an Entry? > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > entering data for patients at a hospital by day, and each time I enter a > new day's entry I have to re-type the patients' information. Is there a way > to copy a previous entry for a patient and paste it on the new entry? > Please help me as this adds a large amount of time to my work. > > Thank you, > YC > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Feb 2010 13:22:33 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Copy and Paste an Entry? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP79433833F8433A3AF41361FD4A0(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > See the example titled "Relate example - Clinical Study with four forms" on > the Examples page - click on the link on the main page at epidata.dk > This is how to structure the related files. > See the example titled "Relate example - Household, Person, Visit" to see > how to copy information from one entry screen to another--you do this with > GLOBAL variables. > > This is a very common set up for clinical records. > > Jamie Hockin > Ottawa > > On 2010-02-15, at 11:40 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > > entering data for patients at a hospital by day, and each time I enter a > > new day's entry I have to re-type the patients' information. Is there a > way > > to copy a previous entry for a patient and paste it on the new entry? > > Please help me as this adds a large amount of time to my work. > > > > Thank you, > > YC > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 76, Issue 3 > ******************************************* > -- Edson Byamukama Po Box 12027 Kampala, Uganda Office : +256 414251025 Mobile: +256 712202650

1 0

Re: EpiData-list Digest, Vol 76, Issue 3
by epidata-list＠lists.umanitoba.ca 16 Feb '10

16 Feb '10

Hi there, As I am not sure what information you have in your hands, I assume you could add check before the data entry and chose the *repeat* option for the required field information. Consequently, the information will remain until you changed it. Best wishes Tieble On 16 February 2010 18:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. RE: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > 2. Re: Copy and Paste an Entry? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Feb 2010 18:51:52 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] Copy and Paste an Entry? > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <00bf01caae67$8ee97710$acbc6530$@martin-prevel@ird.fr> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I think the best way to get round this problem is to have a relational data > base with two files: > (i) the "Master" file with patient's information > (ii) the related file with daily information > > There are several examples of such related data entry and how it works on > the Epidata website > > Hope this helps > > YMP > > > -----Message d'origine----- > De : epidata-list-bounces(a)lists.umanitoba.ca [mailto: > epidata-list-bounces(a)lists.umanitoba.ca] De la part de > epidata-list(a)lists.umanitoba.ca > Envoyé : lundi 15 février 2010 17:38 > À : epidata-list(a)lists.umanitoba.ca > Objet : [EpiData-list] Copy and Paste an Entry? > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > entering data for patients at a hospital by day, and each time I enter a > new day's entry I have to re-type the patients' information. Is there a way > to copy a previous entry for a patient and paste it on the new entry? > Please help me as this adds a large amount of time to my work. > > Thank you, > YC > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Feb 2010 13:22:33 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Copy and Paste an Entry? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP79433833F8433A3AF41361FD4A0(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > See the example titled "Relate example - Clinical Study with four forms" on > the Examples page - click on the link on the main page at epidata.dk > This is how to structure the related files. > See the example titled "Relate example - Household, Person, Visit" to see > how to copy information from one entry screen to another--you do this with > GLOBAL variables. > > This is a very common set up for clinical records. > > Jamie Hockin > Ottawa > > On 2010-02-15, at 11:40 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > > > Hello. I was wondering if it is possible to copy and paste an entry? I am > > entering data for patients at a hospital by day, and each time I enter a > > new day's entry I have to re-type the patients' information. Is there a > way > > to copy a previous entry for a patient and paste it on the new entry? > > Please help me as this adds a large amount of time to my work. > > > > Thank you, > > YC > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 76, Issue 3 > ******************************************* >

1 0

Copy and Paste an Entry?
by epidata-list＠lists.umanitoba.ca 15 Feb '10

15 Feb '10

Hello. I was wondering if it is possible to copy and paste an entry? I am entering data for patients at a hospital by day, and each time I enter a new day's entry I have to re-type the patients' information. Is there a way to copy a previous entry for a patient and paste it on the new entry? Please help me as this adds a large amount of time to my work. Thank you, YC

1 1

Copy and Paste an Entry?
by epidata-list＠lists.umanitoba.ca 15 Feb '10

15 Feb '10

Hello. I was wondering if it is possible to copy and paste an entry? I am entering data for patients at a hospital by day, and each time I enter a new day's entry I have to re-type the patients' information. Is there a way to copy a previous entry for a patient and paste it on the new entry? Please help me as this adds a large amount of time to my work. Thank you, YC

1 1

Export to excel with Filter using Checkcode
by epidata-list＠lists.umanitoba.ca 08 Feb '10

08 Feb '10

Hi Just sharing my experience with the users here in calling Export command of Epic from check file in Epidata The Dos command looks like this c:\EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081919_FARI.xls filter="fari1yes2n=1" DELETED REPLACE However when I try the same in the check file, the filter did not get applied My check file looks like this sourcedir = "d:\ves101\" INVES2 = COPY(INVESTIGAT,1,3) mth2 = string(month(today)) d2 = string(day(today)) hr2 = string(hr) mins3 = string(mins2) recfile = sourcedir+"ves101.rec" fariout = sourcedir+INVES2+mth2+d2+hr2+mins3+"_FARI.xls" execute c:\epic.exe "e excel @recfile @fariout filter="fari1yes2n=1" DELETED REPLACE" wait The EpiC.log file shows the following Command: EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081928_FARI.xls DELETED REPLACE 2/8/2010 7:29:15 PM Exporting d:\ves101\ves101.rec to d:\ves101\VIV02081928_FARI.xls Exports to: Excel Records: All Filter: None Deleted records in inputfile are included in export 7 records with 18 fields exported I can see that the " " around the Filter are creating the problem. Single quotes did not work Command: EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081952_FARI.xls filter='fari1yes2n=1' DELETED REPLACE 2/8/2010 7:52:25 PM Exporting d:\ves101\ves101.rec to d:\ves101\VIV02081952_FARI.xls Exports to: Excel Records: All Filter: 'fari1yes2n=1' Deleted records in inputfile are included in export 0 records with 18 fields exported Finally what did the trick was simply to remove the "" execute c:\epic.exe "e excel @recfile @fariout filter=fari1yes2n=1 DELETED REPLACE" wait EpiC Log shows: Command: EpiC e excel d:\ves101\ves101.rec d:\ves101\VIV02081955_FARI.xls filter=fari1yes2n=1 DELETED REPLACE 2/8/2010 7:54:38 PM Exporting d:\ves101\ves101.rec to d:\ves101\VIV02081955_FARI.xls Exports to: Excel Records: All Filter: fari1yes2n=1 Deleted records in inputfile are included in export 5 records with 18 fields exported I hope this information would be of use to some of the members. Am psoting it as searching through the archives did not yield much. Another thing I noted was that the Zip files created by EpiC can not be opened by WinRAR or PkZIP on my machine though EPiC can extract the same just fine. Thanks ,Dr. Vivek Gupta, MBBS, MD (Community Medicine)All India Institute of Medical Sciences New Delhi. Phone: (+91)9899410420 Alt. E-mail: drvivek(dot)gupta(at)gmail(dot)com

1 0

Ruwan Ratnayake est absent.
by epidata-list＠lists.umanitoba.ca 29 Jan '10

29 Jan '10

Je serai absent(e) du Ven 22/01/2010 au Mer 17/02/2010. Bonjour! Veuillez prendre note que je serai absente de mon bureau le 25 janvier au 15 février. I will be out of the office from January 25-February 15. I will reply to your message upon my return. Ruwan

1 0

entering arabic letters
by epidata-list＠lists.umanitoba.ca 29 Jan '10

29 Jan '10

Dear All, At our office, we are using epidata since 2003 for our local applications. Using MS office 2003, windows XP, we were entering our data using epidata3.1 in English version, but we have kept some variables for entering names using Arabic letters. Later, the .rec file was exported to excel in order to search for duplicates using the Arabic letters. It has worked. Yesterday, we had a new desktop with MS office 2007. That function of entering data using Arabic letters has disappeared. Do you have any idea why this happened? And how can we solve this matter? Sincerely Nada Ghosn, Eman Chamas, Epidemiological Surveillance Program Ministry of Public Health Beirut Lebanon

1 2

testing manager version 0.3.2.9
by epidata-list＠lists.umanitoba.ca 28 Jan '10

28 Jan '10

Heemskerk 28/01/2010 Hello JENS and ALL, While testing this I got a message when I tried to read a DBF file, it says that it is a corrupted ZIPfile !! In true it is a perfect DBF file made by EPIDATA 3.1. Reading TXT, CSV, REC, QES files works perfect. Shifting the fields on the screen with the mouse : OK. Would appreciate more explanation about the SETTINGS, not all clear to me. A possibility to change the type of an already existing field would be nice.. I add a recxml file that contains some remarks. Yours, Louk. <?xml version="1.0"?> <EPIDATA> <SETTINGS> <VERSION>0</VERSION> <DATESEP>/</DATESEP> <DECIMALSEP>.</DECIMALSEP> <MISSINGMARK>.</MISSINGMARK> </SETTINGS> <METADATA> <LABELS> </LABELS> </METADATA> <FIELDS> <FIELD TYPE="15"> <NAME>label_1</NAME> <TAG>F1</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="31" Y="19"/> <LABEL X="31" Y="19">Label text to clarify PURPOSE file.</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_2</NAME> <TAG>F2</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="31" Y="43"/> <LABEL X="31" Y="43">++++++++++++++++++++++++++++++++++++</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="1"> <NAME>V1-short string</NAME> <TAG>F3</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="68"/> <LABEL X="130" Y="73">[SHORTY]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="1"> <NAME>V2-long string100</NAME> <TAG>F4</TAG> <LENGTH>100</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="118"/> <LABEL X="123" Y="123">[VERYlong]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_5</NAME> <TAG>F5</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="144"/> <LABEL X="198" Y="144">Very nice that such a long field is possible !!!!.</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="0"> <NAME>V3-Integer</NAME> <TAG>F6</TAG> <LENGTH>4</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="194"/> <LABEL X="133" Y="199">[Number]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="6"> <NAME>V4-Floaty</NAME> <TAG>F7</TAG> <LENGTH>11</LENGTH> <DECIMALS>6</DECIMALS> <POS X="198" Y="224"/> <LABEL X="130" Y="229">[Floatfield]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="11"> <NAME>V5-Holiday</NAME> <TAG>F8</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="267"/> <LABEL X="112" Y="272">[Normaldate]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="16"> <NAME>V6-THISDAY</NAME> <TAG>F9</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="297"/> <LABEL X="120" Y="302">[Todayfield]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="12"> <NAME>V7-IDfield</NAME> <TAG>F10</TAG> <LENGTH>4</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="350"/> <LABEL X="74" Y="355">[RECORDNUMBER]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_3</NAME> <TAG>F11</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="72" Y="399"/> <LABEL X="72" Y="399">NOTE ! Each time when I click in a field , this field moves one pixel to the bottom. !!!</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_4</NAME> <TAG>F12</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="143" Y="428"/> <LABEL X="143" Y="428">Writing the FIEDLABELS between square brackets keeps the aspect tidy...</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> </FIELDS> <RECORDS> </RECORDS> </EPIDATA>

1 0

updated manager
by epidata-list＠lists.umanitoba.ca 26 Jan '10

26 Jan '10

An updated manager has been placed on the testing.php page now. Changes are shown on that page. Basicly bug-fixes for what was reported on the list since last week. e.g.: labels snap onto nearby fields access violation when using encrypted fields adapted and documented use of keyboard shortcuts If you place the pdf introduction document (also from testing.php) in a subfolder to the exe, you can call the pdf from the help menu (possibly not on Mac). Work will now concentrate on the first prototype of a dedicated EntryClient, after which adding checks and controls is in the workplan. The manager will only be fixed for reproducible bugs until an EntryClient exists. regards Jens Lauritsen EpiData Association

1 0

New EpiData Manager ready for (next) test
by epidata-list＠lists.umanitoba.ca 23 Jan '10

23 Jan '10

The EpiData Data Manager will gradually replace the existing EpiData Entry software as development goes on. Why change to EpiData Manager ? Since release of first EpiData software in 1999 many aspects have changed. The main reasons for development of the new strategy are: • New users are increasingly ”graphicly” oriented and focused on mouse usage. ◦ not understanding the well known qes-chk-rec principle • There is a need for multiplatform development (Linux, Mac, Windows, PDA …..) • Font management is changing to UTF-8 to avoid nationalisation problems • We wish to implement GCP (Good Clinical Practice) required for many medical data projects. This demands encryption and logging of editing at a very detailed level. • There should be a common ”engine” for all EpiData software, such that handling of data and metadata (labels etc.) are based on the same internal routines. • When doing data entry it should not be immediately easy to change rules or structure for data entry personnel. Therefore a dedicated EpiData EntryClient will be developed – serving only data entry. How will a project manager see the new strategy ? The work process is more clearly divided into what the manager does and what the data entry persons do. The EpiData Manager is a tool for the project person, which: • Defines data structures, adds metadata (labels and definitions), documents data and exports for analysis. • Updates data with new fields, changed formats for fields (e.g. More decimals) and is used for control of data. • There is a choice of using computers with either Linux, Mac or Windows A short introduction document is found next to where the test application can be downloaded. See http://www.epidata.dk/testing.php Apart from fixing many bugs, the new version now includes an editor, a revised interface and allows for pasting from a qes file or the editor. Next phase is to add checks and develop the Entry Client. For the planning please comment on the new release, which includes an editor. Also we should have a discussion on which are the "core" check commands that almost everyone uses and which are enhanced. regards Jens Lauritsen EpiData Association

1 5

Epidata and check
by epidata-list＠lists.umanitoba.ca 22 Jan '10

22 Jan '10

I am having a small problem with Epidata. I have this field with place for 2 numbers. How do I check that this field contains something? I need this because from this field I have to make a jump depending on whether this field is blank or not. Thank You. Venlig hilsen/Kind regards Antonio Sylvester

1 1

additional core commands
by epidata-list＠lists.umanitoba.ca 22 Jan '10

22 Jan '10

Hello Please add these very important commands: 'comment legal show' 'comment legal use' confirm Thanks For implementation in the first updated entry client we need to define a basic core set of basic check commands Suggestion: (please comment): backup value label, legal, range and missing value definitions type comment jump / goto hide topofpage mustenter repeat message (help) key unique Did I miss any ? The core set of check commands will be part of the main recxml file, whereas further specifications will be contained in a separate (chk) file. regards Jens Lauritsen EpiData Association _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list Steve Blum

1 1

Which check commands do you consider as the basic ones ?
by epidata-list＠lists.umanitoba.ca 22 Jan '10

22 Jan '10

For implementation in the first updated entry client we need to define a basic core set of basic check commands Suggestion: (please comment): backup value label, legal, range and missing value definitions type comment jump / goto hide topofpage mustenter repeat message (help) key unique Did I miss any ? The core set of check commands will be part of the main recxml file, whereas further specifications will be contained in a separate (chk) file. regards Jens Lauritsen EpiData Association

1 1

EpiData-list
by epidata-list＠lists.umanitoba.ca 01 Jan '10

01 Jan '10

Good Happy Year for EPIDATA ! Thanks to Jens and his team for continuing EpiData development. Two small questions still relevant : - regression line (in or out of scatter plot) : this is very important for the teacher in statistics ++ - true P50 in lifetable : when ? Thank you for your work. Bernard BRANGER, Nantes, France -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 1154 courriels spam. Nous avons en ce moment 6 millions d’utilisateurs de par le monde entier. Les utlisateurs payants n’ont pas ce message. Vous pouvez télécharger la version gratuite: http://www.spamfighter.com/lfr

1 0

EpiData Manager text editor
by epidata-list＠lists.umanitoba.ca 31 Dec '09

31 Dec '09

Thanks to Jens and his team for continuing EpiData development. I think new users would require a text editor which gives the different data formats as EpiData Entry currently does via the field pick list because new users would not be sufficiently familiar to use the correct field formats when using some other text editor. In addition, the editor used in EpiData Entry is a rather nice editor, superior (in my opinion) to Notepad which perhaps most users would otherwise utilise. The Manager seems to have the look and feel of the Windows Epi-Info with the disadvantage in an outbreak situation of a lack of speed of database construction if restricted to function keys and/or mouse clicks while users may also not like having to utilise more than one package to construct a database. ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 0

Re: EpiData-list Digest, Vol 74, Issue 5
by epidata-list＠lists.umanitoba.ca 29 Dec '09

29 Dec '09

Hello Everybody, Thank's for the new release and the great work done. I was wondering if it would be possible to edit qes file as in the previous epidata entry? I think this function is useful to quickly design a new data structure. Best Regards Olivier Hacquet, Paris, France epidata-list-request(a)lists.umanitoba.ca a écrit : > 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. First public test of the EpiData Manager available for Mac, > Linux and Windows (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 21 Dec 2009 22:50:30 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] First public test of the EpiData Manager > available for Mac, Linux and Windows > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4B2FEDA6.5010608(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Dear all > > Early October I announced the new XML format and mid November followed > up with a six point strategy. The first part of this is now ready for > testing. > > The overall design of the future EpiData software has now evolved to > this decision: > a. EpiData Manager: data and project manager > b. EpiData Entry Client: data entry client > c. EpiData Analysis: analysis and reporting > (plus epic for some batch operations) > > The products are not ready yet in the new rebuilt versions, but just now > you are welcome to test and comment on the first public test release > version of the EpiData Manager. > > The test release supports operating systems. (Win, Mac, Linux) in 32 and > 64 bit versions. > Please download from: Http://www.epidata.dk/testing.php > > Just download and unzip (un-tar etc) the file, which contains only one > exe file. > > What you can test is: > a read datafiles in supported formats (qes, rec, dta, dbf, csv ..) > look at the dataform created based on the contents of the read file. > b. create a new datastructure from scratch > add fields by clicking on a toolbar or using command keys > c. move fields around with the mouse (does not work in Mac yet) > d. save files in the new recxml file documented on the wiki. See the > testing.php page. > > Please discuss the interface design, implementation and test results in > your opinion on this list. Reproducible errors can be reported to the > bug-reporting database. See the testing.php page. > > Development continues with more aspects. Just using say 15 minutes > should tell you whether the new principle is intuitive or not. > > Meanwhile I am starting a quest for more funding to continue > developments beyond the current plans ending quite soon. Any ideas for > funding or donations are welcomed. It seems to me we should all try to > get funding to secure the current staff (one person plus partial > payments for a few others) for another year before the whole package is > ready for general release as open-source in a sustainable way. The > current test release should work as a "proof of concept" in relation to > the shift and release for several operating systems. > > regards > Jens Lauritsen > EpiData Association > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 74, Issue 5 > ******************************************* > >

1 1

Epidata Manager exe file not opening
by epidata-list＠lists.umanitoba.ca 29 Dec '09

29 Dec '09

Dear Jens, I wanted to test the new Epidata Manager. The archive when extracted does not open. When I click the exe file the message displayed is as follows; "epidatamanager.exe is not a valid Win32 application" I an using Pentium with Win XP. Any suggsetions / Dr. Shavinder Singh Deptt. Community Medicine,

1 1

Amy MacArthur is out of the office.
by epidata-list＠lists.umanitoba.ca 28 Dec '09

28 Dec '09

I will be out of the office starting 24/12/2009 and will not return until 29/12/2009. I will respond to your message when I return. Happy holidays!

1 0

New test version of EpiData Manager uploaded.
by epidata-list＠lists.umanitoba.ca 23 Dec '09

23 Dec '09

Dear EpiData list. Today a new version (0.2.2.6) of the new EpiData Manager has been uploaded to the testing page of the epidata website: http://epidata.dk/testing.php The new version includes the following updates/additions: * The settings form have been updated to support more features. The form is divided into a Basic page, for normal users, and an Advanced page, for experience users. * Shortcuts have been updated/added. Edit selected field = F9, Align options = F11, Show structure = F12. * Default folder (for dialogs) can be set by double-clicking the status bar (information is not yet shown anywhere). * Internal data engine updated. In addition the file size for the Mac OS X version have been greatly reduced, making downloading easier/faster. With kind regards, Torsten Bonde Christiansen. EpiData Software Developer.

1 0

First public test of the EpiData Manager available for Mac, Linux and Windows
by epidata-list＠lists.umanitoba.ca 21 Dec '09

21 Dec '09

Dear all Early October I announced the new XML format and mid November followed up with a six point strategy. The first part of this is now ready for testing. The overall design of the future EpiData software has now evolved to this decision: a. EpiData Manager: data and project manager b. EpiData Entry Client: data entry client c. EpiData Analysis: analysis and reporting (plus epic for some batch operations) The products are not ready yet in the new rebuilt versions, but just now you are welcome to test and comment on the first public test release version of the EpiData Manager. The test release supports operating systems. (Win, Mac, Linux) in 32 and 64 bit versions. Please download from: Http://www.epidata.dk/testing.php Just download and unzip (un-tar etc) the file, which contains only one exe file. What you can test is: a read datafiles in supported formats (qes, rec, dta, dbf, csv ..) look at the dataform created based on the contents of the read file. b. create a new datastructure from scratch add fields by clicking on a toolbar or using command keys c. move fields around with the mouse (does not work in Mac yet) d. save files in the new recxml file documented on the wiki. See the testing.php page. Please discuss the interface design, implementation and test results in your opinion on this list. Reproducible errors can be reported to the bug-reporting database. See the testing.php page. Development continues with more aspects. Just using say 15 minutes should tell you whether the new principle is intuitive or not. Meanwhile I am starting a quest for more funding to continue developments beyond the current plans ending quite soon. Any ideas for funding or donations are welcomed. It seems to me we should all try to get funding to secure the current staff (one person plus partial payments for a few others) for another year before the whole package is ready for general release as open-source in a sustainable way. The current test release should work as a "proof of concept" in relation to the shift and release for several operating systems. regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 74, Issue 3
by epidata-list＠lists.umanitoba.ca 12 Dec '09

12 Dec '09

One way of doing this will be to create a relational database structure. Please visit help menu in EpiData or post few portion of the data so one can design it if you need further assistance. Tieble 2009/12/10 <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. Re: Visits (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 10 Dec 2009 13:13:06 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Visits > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4B20E5D2.14974.9DABD88(a)loukmeertens.hetnet.nl> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello Silvano, > You might find some usefull ideas in the examples you can download from > the EPIDATA > site. > > Postoperative infections > > Click on this link and dwnload there the examles named POWI. Although it is > in DUTCH > language, the CHECK/files will be understdable by any one. > Hope this helps you. > Gretings, Louk. > > email direct: loukmeertens(a)hetnet.nl > ===================================================================== > > To: <epidata-list(a)lists.umanitoba.ca> > Date sent: Wed, 9 Dec 2009 11:07:28 -0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Visits > > Hi, > > I have a questionnaire that split in 3 files. > > The first file refers to general data; > The second file refers to the postoperative period; > The third refers to the visits made to the patient. Such > visits may be 4 or more. > > I wish I could enter the data of visits, using the files 1 > and 2 with the patient's personal information. > > There is an example (House) on page Epi date but could not > reproduce. > > Could anyone help me? > > Can I send the files I built, if necessary. > > Thank you, > > -------------------------------------- > Silvano Cesar da Costa > Departamento de Estatística > Universidade Estadual de Londrina > Fone: 3371-4346 > -------------------------------------- > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 74, Issue 3 > ******************************************* >

1 0

Visits
by epidata-list＠lists.umanitoba.ca 10 Dec '09

10 Dec '09

Hi, I have a questionnaire that split in 3 files. The first file refers to general data; The second file refers to the postoperative period; The third refers to the visits made to the patient. Such visits may be 4 or more. I wish I could enter the data of visits, using the files 1 and 2 with the patient's personal information. There is an example (House) on page Epi date but could not reproduce. Could anyone help me? Can I send the files I built, if necessary. Thank you, -------------------------------------- Silvano Cesar da Costa Departamento de Estatística Universidade Estadual de Londrina Fone: 3371-4346 --------------------------------------

1 2

preventing duplicate entries
by epidata-list＠lists.umanitoba.ca 09 Dec '09

09 Dec '09

I am entering daily visit counts to walk-in clinics in our area. There are 6 clinics or sites. So a record is uniquely identified by site and date. Is there a way to prevent the entry of records with a site-date combination that duplicates a site-date combination that already exists in the database? Thanks. --Chris -- Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 425 Robinson Street, Binghamton, NY 13901 cryanatbinghamtondotedu "If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea." [Antoine de St. Exupery]

1 6

Calculating age
by epidata-list＠lists.umanitoba.ca 27 Nov '09

27 Nov '09

Hello, I have a little problam calculating intervals like age from two dates using formula LET AGE=ROUND(INT(TODAY-DOB)/365.25) It returns the value rounded to the nearest whole number, which is a problem in records of people with birthday 6 and more months (183 days and more) from today's date, as it makes them one year older.. Is there any way to get result rounded towards zero? Kind regards Eva

1 3

Time and time differences - recording of time variables
by epidata-list＠lists.umanitoba.ca 27 Nov '09

27 Nov '09

Projects where I needed date and time were - Study on surgeries with start time and end time of surgery (some of which started before midnight and went on to the next day) - Study on patients in intensive care units in which date and time of arrival and discharge was available up to minutes I think having two fields is fine . However, it would be handy to have functions to convert hours.minutes.seconds into a fraction of day which then can be added to a date which finally allows to calculate differences and things like that. with best wishes marcel *********** Marcel Zwahlen Institute of Social and Preventive Medicine University Bern, Switzerland phone ++41-31-631.3554 facsimile ++41-31-631.3520 http://www.ispm.unibe.ch/ -----Ursprüngliche Nachricht----- Von: epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca <mailto:epidata-list@lists.umanitoba.ca> ] Gesendet: Mittwoch, 25. November 2009 13:12 An: epidata-list(a)lists.umanitoba.ca Betreff: [EpiData-list] Time and time differences - recording of time variables As part of current development there is an issue of how time is best represented in data. Recent years have added a date-time field to some database systems. In most cases for entry these are rather cumbersome to work with in practice in my experience. The suggestion is to add one time field: hh.mm.ss that is a time field with 6 digits. examples: Entered recorded 1 01.00.00 (one o'clock at night) 122 12.20.00 (20 minutes past twelwe) 182045 18.20.45 (20 minutes,45 seconds after 18 hours) Functions will be needed e.g. to calculate time in hours, minutes or seconds from day1 time1 to day2 time2. Or conversion of an imported date-time value to separate the date into one field and the time into another. Users are encouraged to give examples and discuss here on the list regarding: a. Needs for recording of time b. Examples of practical situations where this was needed c. In what format would users prefer recording. Also whether there seems to be a need for a combined date-time field. regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 73, Issue 5
by epidata-list＠lists.umanitoba.ca 26 Nov '09

26 Nov '09

As a general principle, it might be clearer and accomplishes the same thing if boolean fields are not used at all, but handle such things with a label block, using a numeric field: label yesno 0 No 1 Yes 8 "Does not apply" 9 "Missing response" end Hans epidata-list-request(a)lists.umanitoba.ca wrote: > Today's Topics: > > 1. jumps don't work (epidata-list(a)lists.umanitoba.ca) > 2. Re: jumps don't work (epidata-list(a)lists.umanitoba.ca) > -- 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 0

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

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

23 Oct '09

Dear All, Thank you for your kind considerations and replies! Best regards ziad On Fri, Oct 23, 2009 at 7:00 PM, <epidata-list-request(a)lists.umanitoba.ca> wrote: > > 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. Re: Re: EpiData-list Digest, Vol 72, Issue 7 > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Relational data (epidata-list(a)lists.umanitoba.ca) > 3. AW: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > (epidata-list(a)lists.umanitoba.ca) > 4. Re: Rename fields (epidata-list(a)lists.umanitoba.ca) > > MIME-version: 1.0 > Content-type: message/rfc822 > > Date: Thu, 22 Oct 2009 19:24:18 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > To: epidata-list(a)lists.umanitoba.ca > Message-id: <q0874s2gsqxtuof.221020091924(a)mail.zimi.ch> > MIME-version: 1.0 > Content-type: text/plain; charset=ISO-8859-1 > Content-transfer-encoding: 7BIT > Precedence: list > Message: 1 > > I guess, you have to go back to your REC file, go to Tools | Rename fields, and change each of the two fields to names with 8 or fewer characters. While it is nice that EpiData offers a maximum field length of 10, it might be wise (as example shows) not to exhaust the maximum if the data are to be analyzed in other software limiting the allowable length to 8. > > Hans > > epidata-list(a)lists.umanitoba.ca wrote: > > Hi! > > I have had 2 date related vaiables called "datebase1" and "datebase2" > > in EpiData. When exported them into STATA, they are showing as > > "datebase" and "datebase" and both variables contain the same value > > now which is not correct. > > > > It might be due to the total number of characters for the variable > > name, but my question is how can I fix it? > > > > > > Best regards > > ziad > -- > Hans L Rieder, MD, MPH > Web: http://www.tbrieder.org > > > > MIME-version: 1.0 > Content-type: message/rfc822 > > Date: Thu, 22 Oct 2009 18:19:07 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: Relational data > To: epidata-list(a)lists.umanitoba.ca > Message-id: <bf1bb7700910221019x66fae18fu8701efc4679ae0c7(a)mail.gmail.com> > MIME-version: 1.0 > Content-type: text/plain; charset=ISO-8859-1 > Content-transfer-encoding: 7BIT > Precedence: list > Message: 2 > > Dear Ziad, > > Perhaps it may be better to merge the files to produce one file of > observations (all levels should be included). If you decide to go through > this route, please remember that this can be done in EpiData Analysis using > the MERGE command. > > Best wishes > > Tieble > > 2009/10/22 <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. Re: EpiData-list Digest, Vol 72, Issue 7 > > (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 22 Oct 2009 08:15:08 +0200 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: > > <897a5cf60910212315r4894a4b8t6cd37fa5668cbd6f(a)mail.gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Hi! > > I have had 2 date related vaiables called "datebase1" and "datebase2" > > in EpiData. When exported them into STATA, they are showing as > > "datebase" and "datebase" and both variables contain the same value > > now which is not correct. > > > > It might be due to the total number of characters for the variable > > name, but my question is how can I fix it? > > > > > > Best regards > > ziad > > > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 72, Issue 8 > > ******************************************* > > > > > MIME-version: 1.0 > Content-type: message/rfc822 > > Date: Thu, 22 Oct 2009 20:12:21 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: AW: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > To: epidata-list(a)lists.umanitoba.ca > Message-id: <2B0BDB25934D824280073BE8D73FBB980C8D33(a)mx01.ispm.unibe.ch> > MIME-version: 1.0 > Content-type: text/plain; charset=iso-8859-1 > Content-transfer-encoding: quoted-printable > Precedence: list > Message: 3 > References: <200910181700.n9IH09lG005149(a)electra.cc.umanitoba.ca> <897a5cf60910212315r4894a4b8t6cd37fa5668cbd6f(a)mail.gmail.com> > > In the export function to Stata there is an Option you can chose...you = > need to chose Stata version 8 (or higher) then variable names do not get = > truncated to 8 characters. > I think that will work > Marcel > > *********** > Marcel Zwahlen > Institute of Social and Preventive Medicine > University Bern, Switzerland > phone ++41-31-631.3554 > facsimile ++41-31-631.3520 > http://www.ispm.unibe.ch/=20 > =20 > > > -----Urspr=FCngliche Nachricht----- > Von: epidata-list(a)lists.umanitoba.ca = > [mailto:epidata-list@lists.umanitoba.ca]=20 > Gesendet: Donnerstag, 22. Oktober 2009 08:15 > An: epidata-list(a)lists.umanitoba.ca > Betreff: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > > Hi! > I have had 2 date related vaiables called "datebase1" and "datebase2" > in EpiData. When exported them into STATA, they are showing as = > "datebase" and "datebase" and both variables contain the same value now = > which is not correct. > > It might be due to the total number of characters for the variable name, = > but my question is how can I fix it? > > > Best regards > ziad > > > > > MIME-version: 1.0 > Content-type: message/rfc822 > > Date: Thu, 22 Oct 2009 22:42:16 -0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: Rename fields > To: epidata-list(a)lists.umanitoba.ca > Message-id: <a37cfb5a0910221742r78ad51ctc0e1b9af5f73cc48(a)mail.gmail.com> > MIME-version: 1.0 > Content-type: text/plain; charset=ISO-8859-1 > Content-transfer-encoding: quoted-printable > Precedence: list > Message: 4 > > Ziad, > > First of all always backup your data before doing dangerous things such as > renaming variables. > > That is simple. The first sugestion is to use EpiData entry tools menu... > there is something like rename fields(my menus are in portuguese) ... this > may help. > > Another solution is to export two splits of the dataset to stata, one > containing the first the datebase but without the second datebase and a > second dataset with only the unique identifier and the second datebase. > Later, already with stata, you may rename the varibles and merge the two > datasets side by side with the unique identifier. > > Best regards, > > Abra=E7o forte e que a for=E7a esteja com voc=EA, > > Dr. Pedro Emmanuel A. A. do Brasil > Instituto de Pesquisa Cl=EDnica Evandro Chagas > Funda=E7=E3o Oswaldo Cruz > Rio de Janeiro - Brasil > > > 2009/10/22 <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. Re: EpiData-list Digest, Vol 72, Issue 7 > > (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 22 Oct 2009 08:15:08 +0200 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: > > <897a5cf60910212315r4894a4b8t6cd37fa5668cbd6f(a)mail.gmail.com> > > Content-Type: text/plain; charset=3DISO-8859-1 > > > > Hi! > > I have had 2 date related vaiables called "datebase1" and "datebase2" > > in EpiData. When exported them into STATA, they are showing as > > "datebase" and "datebase" and both variables contain the same value > > now which is not correct. > > > > It might be due to the total number of characters for the variable > > name, but my question is how can I fix it? > > > > > > Best regards > > ziad > > > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 72, Issue 8 > > ******************************************* > > > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list >

1 0

Re: Rename fields
by epidata-list＠lists.umanitoba.ca 22 Oct '09

22 Oct '09

Ziad, First of all always backup your data before doing dangerous things such as renaming variables. That is simple. The first sugestion is to use EpiData entry tools menu... there is something like rename fields(my menus are in portuguese) ... this may help. Another solution is to export two splits of the dataset to stata, one containing the first the datebase but without the second datebase and a second dataset with only the unique identifier and the second datebase. Later, already with stata, you may rename the varibles and merge the two datasets side by side with the unique identifier. Best regards, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil 2009/10/22 <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. Re: EpiData-list Digest, Vol 72, Issue 7 > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 22 Oct 2009 08:15:08 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <897a5cf60910212315r4894a4b8t6cd37fa5668cbd6f(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi! > I have had 2 date related vaiables called "datebase1" and "datebase2" > in EpiData. When exported them into STATA, they are showing as > "datebase" and "datebase" and both variables contain the same value > now which is not correct. > > It might be due to the total number of characters for the variable > name, but my question is how can I fix it? > > > Best regards > ziad > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 72, Issue 8 > ******************************************* >

1 0

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

22 Oct '09

Hi! I have had 2 date related vaiables called "datebase1" and "datebase2" in EpiData. When exported them into STATA, they are showing as "datebase" and "datebase" and both variables contain the same value now which is not correct. It might be due to the total number of characters for the variable name, but my question is how can I fix it? Best regards ziad

1 1

Re: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7
by epidata-list＠lists.umanitoba.ca 22 Oct '09

22 Oct '09

I guess, you have to go back to your REC file, go to Tools | Rename fields, and change each of the two fields to names with 8 or fewer characters. While it is nice that EpiData offers a maximum field length of 10, it might be wise (as example shows) not to exhaust the maximum if the data are to be analyzed in other software limiting the allowable length to 8. Hans epidata-list(a)lists.umanitoba.ca wrote: > Hi! > I have had 2 date related vaiables called "datebase1" and "datebase2" > in EpiData. When exported them into STATA, they are showing as > "datebase" and "datebase" and both variables contain the same value > now which is not correct. > > It might be due to the total number of characters for the variable > name, but my question is how can I fix it? > > > Best regards > ziad -- Hans L Rieder, MD, MPH Web: http://www.tbrieder.org

1 0

Re: Relational data
by epidata-list＠lists.umanitoba.ca 22 Oct '09

22 Oct '09

Dear Ziad, Perhaps it may be better to merge the files to produce one file of observations (all levels should be included). If you decide to go through this route, please remember that this can be done in EpiData Analysis using the MERGE command. Best wishes Tieble 2009/10/22 <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. Re: EpiData-list Digest, Vol 72, Issue 7 > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 22 Oct 2009 08:15:08 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <897a5cf60910212315r4894a4b8t6cd37fa5668cbd6f(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi! > I have had 2 date related vaiables called "datebase1" and "datebase2" > in EpiData. When exported them into STATA, they are showing as > "datebase" and "datebase" and both variables contain the same value > now which is not correct. > > It might be due to the total number of characters for the variable > name, but my question is how can I fix it? > > > Best regards > ziad > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 72, Issue 8 > ******************************************* >

1 0

Core test - clarification of &
by epidata-list＠lists.umanitoba.ca 18 Oct '09

18 Oct '09

Correction to last message: An ampersand (&) does translate to & when it appears in a .qes file / header of .rec, but it does not get translated when it appears in DATA, i.e. a text field that contains "A & B" -- Jamie Hockin

1 0

Core Test
by epidata-list＠lists.umanitoba.ca 18 Oct '09

18 Oct '09

The module is not correctly handling special characters in creating recxml files. Two examples I've found so far. 1. " translates to &qout; rather than " 2. & is not translated to & sample .qes lines are: a var # 1 = "some text" b var # Factor A & Factor B either of these causes failure on reading the recxml -- Jamie Hockin

1 0

Re: Backup data file
by epidata-list＠lists.umanitoba.ca 18 Oct '09

18 Oct '09

Thank you for your prompt reply, however the screen with backup option (i.e. with the destination) does not appear at all. The only message that I get from both menus document and export is "file not found". I have no problem performing the backup on other computers on which I installed the Epidata program. However for some reason the message "file not found" occurs only on the computers where I do not have permission to install the program. Is there any solution to this problem? Clearly I have tried to write a short program to backup, unfortunately that did not work too. Your help will be appreciated Kind regards Tieble 2009/10/16 <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. Backup data file (epidata-list(a)lists.umanitoba.ca) > 2. Re: Backup data file (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 15 Oct 2009 18:35:14 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Backup data file > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <bf1bb7700910151035u36e2d874vf7d16b6d04fb56a(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I will appreciate it if anyone could provide me with some advice in > creating > a backup in Epidata. Every time, I try to use the menu to backup the > following message appears "File Not Found". > Clearly, I did not encounter any problem creating the backup file/data in > the EpiData programs installed on my PCs (laptop and desktop). But I am > having difficulty in backing up the rec. file created on a company's > computer. > > Kind regards > > Tieble > > > ------------------------------ > > Message: 2 > Date: Thu, 15 Oct 2009 18:52:27 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Backup data file > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4AD7A7AB.6020705(a)sympatico.ca> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Check the Destination directory in the box that opens up with Backup. It > may point to a directory for which you do not have write access. > > I will appreciate it if anyone could provide me with some advice in > creating > > a backup in Epidata. Every time, I try to use the menu to backup the > > following message appears "File Not Found". > > Clearly, I did not encounter any problem creating the backup file/data in > > the EpiData programs installed on my PCs (laptop and desktop). But I am > > having difficulty in backing up the rec. file created on a company's > > computer. > > > > Kind regards > > > > Tieble > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 72, Issue 6 > ******************************************* >

1 0

Backup data file
by epidata-list＠lists.umanitoba.ca 15 Oct '09

15 Oct '09

I will appreciate it if anyone could provide me with some advice in creating a backup in Epidata. Every time, I try to use the menu to backup the following message appears "File Not Found". Clearly, I did not encounter any problem creating the backup file/data in the EpiData programs installed on my PCs (laptop and desktop). But I am having difficulty in backing up the rec. file created on a company's computer. Kind regards Tieble

1 1

EpiData software core module Version 0.2.1 build 99
by epidata-list＠lists.umanitoba.ca 12 Oct '09

12 Oct '09

To: EpiData software development team EpiData software core module Version 0.2.1 build 99: Exporting to EpiData REC file and reading exported file in EpiData Analysis 2.2.1.171: File: Num fields = 65 Num data fields = 65 Num records = 37635 1) All field labels are front-truncated 2) CHK file seems correct -- 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 0