- EpiData-list - University of Manitoba Mailing Lists

(no subject)
by epidata-list＠lists.umanitoba.ca 29 Sep '14

29 Sep '14

Dear ALL, I have a data set where some patients have more than one entry (visit) i.e. same patient with different visit dates, while some have only one entry (visit). I would like to select only the first visit from each patient (The variables to use are id_unique and visit_date) Regards Walter

1 3

SV: [EpiData-list] Epidata Manager key unique handling
by epidata-list＠lists.umanitoba.ca 19 Sep '14

19 Sep '14

All you have to do, is to define a key, which you find under project properties. After definition of a key, only one observation can be entered for each value. In entryclient a key is always what was "key unique" in Classic Epidata 3.1. Regards Jens Lauritsen epidata-list(a)lists.umanitoba.ca skrev: >Dear all, > >I have tried to use epidata manager & client. The Entry client is not indicating on duplicate entry of id field as in Epi data classic 3.1. Please let me know if there is any option to give message just after entering the key field and stop the entry to next fields. > >Thanks & best regards, >Rasool Bux > >________________________________ > >This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately. >_______________________________________________ >EpiData-list mailing list >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 5

Is there a web tutorial for Epidata manager?
by epidata-list＠lists.umanitoba.ca 15 Sep '14

15 Sep '14

Dear Jens, Is there a web-tutorial for Epidata manager and Client? It would be of great help Basic things are simple to figure out as they are simple if you know the epidata entry 3.1 More advanced work requires some help! regards Thambu

1 0

Epidata Manager key unique handling
by epidata-list＠lists.umanitoba.ca 12 Sep '14

12 Sep '14

Dear all, I have tried to use epidata manager & client. The Entry client is not indicating on duplicate entry of id field as in Epi data classic 3.1. Please let me know if there is any option to give message just after entering the key field and stop the entry to next fields. Thanks & best regards, Rasool Bux ________________________________ This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.

1 0

transferring a field value
by epidata-list＠lists.umanitoba.ca 09 Sep '14

09 Sep '14

Dear Epidata users I am facing a problem transferring a field value from a parent file to a child file. In the parent file I have initial SRQ (srqinit) and I want the same value to appear in the chiled file. I did the following: In the parent file before file Define Gsrqinit ## Global srqinit MUSTENTER AFTER ENTRY LET Gsrqinit=srqinit END END In the child file BEFORE RECORD srqinit=varsrqinit END However, this doesn't seem to work. Your help will be most appreciated. Mohammed -- *---------------------------------------------------------*

1 1

Relational database
by epidata-list＠lists.umanitoba.ca 09 Sep '14

09 Sep '14

Hi there I have created a relational database for two files. A pre-entry data file (parent file) and an intake file (child file). the relate command is working well. However, when finishing information entry in the child file and go back to the main file using F10 , EpiData doesn't take me automatically to a new parent file but to the previous file and a new parent file will only open when using the navigation bottom. Also when I fill in the second parent file and automatically move to the child file, I found the information entered for the previous child file. Hope you can help me solving this problem Thanks Mohamed -- *---------------------------------------------------------*

1 0

Which type of testing is good for securing stable software and enhance development ?
by epidata-list＠lists.umanitoba.ca 30 Jul '14

30 Jul '14

Dear all As you can see in the recent days communication on the list aspects of the "relate" system has been tested and in a collaborating process btw. V. Høgli and T.Christiansen, the issue of a wrongly place information window was clarified. This is exactly the type of correspondence which is helpful to the development. So therefore I encourage with time and interest in the future function and stable software developed to take part. It does not mean that all should spent days and weeks, but just a small exercise of say half an hour twice a week is not much for each of you. regards Jens Lauritsen EpiData Software Initiator and coordinator Denmark

1 0

Re: EpiData-list Digest, Vol 129, Issue 9
by epidata-list＠lists.umanitoba.ca 30 Jul '14

30 Jul '14

Torsten, Seems you located the problem:-) Funny though, the same phenomenon appears in Windows 7. The "show all button" is greyed out, but the other fix - Selecting Edit - Default windows position before I open any project, and then restart EDM fixes the problem. Glad if this testing can be useful. Regards, Vegard Høgli Torsten Bonde Christiansen wrote: > The reason why the program freeze at step 7) is because the window for > "Define Key" appears > outside your monitor. This happens due to a programming error from my side. > > You can see the window if you right-click the Manager icon in the dock > and select "Show All...". > ... > An easy fix for this is to use the "Default window position" which will > reset the position of ALL > windows within EpiData Manager. Then the next time you click "Define > Key" you should have > the window positioned properly. > > Kind regards, > Torsten Bonde Christiansen. > EpiData Association. > > > > On 2014-07-22 23:48, epidata-list(a)lists.umanitoba.ca wrote: > > "Then set as key" - embarrassed to admit - Still don't get it: > > Here's exactly what I do: > > 1. Define new project > > 2. Save as myfile (even tried without save first) > > 3. click on Dataform 1 > > 4. Define field name IDNO Integer length 4 > > 5. Apply, then close field properties pane > > 6. Select IDNO field with select tool (small boxes appear enclosing > > selected field) > > 7. Click on Dataform button (or menu item) - then choose Define key > > 8. Freeze - Nothing happens, not possible to define new dataform, not > able > > to save or edit field, have to kill process in program manager (windows), > > small green plus sign when hovering mouse over field (OSX). > > > > Where do I go wrong? anyway: apparent program freeze should be replaced > by > > error message if I do something in the wrong order, like for example: > when > > I tried to add a child dataform first, i get the error message: must > create > > at least one key first. > > > > Vegard > > > > > >> on Jul 22, Jamie wrote: > >> > > I have not had this problem (OSX-Mavericks). On Dataform1, I define an > >> integer field. Then set as key. add a related dataform and my key field > >> shows up on the new form. When you add a field to Dataform1, the Relate > tab > >> appears. You have to define a related dataform firstThen ; then the > Relate > >> tab shows up. > >> > >> Jamie > >> > >> > > _______________________________________________ > > 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 129, Issue 9 > ******************************************** >

1 0

Auto Response
by epidata-list＠lists.umanitoba.ca 29 Jul '14

29 Jul '14

1 0

Re: EpiData-list Digest, Vol 129, Issue 5
by epidata-list＠lists.umanitoba.ca 29 Jul '14

29 Jul '14

"Then set as key" - embarrassed to admit - Still don't get it: Here's exactly what I do: 1. Define new project 2. Save as myfile (even tried without save first) 3. click on Dataform 1 4. Define field name IDNO Integer length 4 5. Apply, then close field properties pane 6. Select IDNO field with select tool (small boxes appear enclosing selected field) 7. Click on Dataform button (or menu item) - then choose Define key 8. Freeze - Nothing happens, not possible to define new dataform, not able to save or edit field, have to kill process in program manager (windows), small green plus sign when hovering mouse over field (OSX). Where do I go wrong? anyway: apparent program freeze should be replaced by error message if I do something in the wrong order, like for example: when I tried to add a child dataform first, i get the error message: must create at least one key first. Vegard > on Jul 22, Jamie wrote: > I have not had this problem (OSX-Mavericks). On Dataform1, I define an > integer field. Then set as key. add a related dataform and my key field > shows up on the new form. When you add a field to Dataform1, the Relate tab > appears. You have to define a related dataform firstThen ; then the Relate > tab shows up. > > Jamie > >

1 2