- EpiData-list - University of Manitoba Mailing Lists

Re: [EpiData-list] Access violation when comparing duplicate files
by EpiData development and support 09 Jul '15

09 Jul '15

Thank you for your reply 1. I use version 2.0.4.43 for Mac Program Version: 2.0.4.43 r1156 Core version: 2.0.0.0 r1161 FPC Version: 2.6.4 Platform: i386-Darwin 2. Both dataforms have the same identical 10 sections. I have created 1 dataform with 10 sections and let 2 people insert data parallel. 3. I haven’t defined any key, but I have defined an ID as a variable for each subject. However, it is not used for coupling the two files. This is what I did: Document -> Compare duplicate files -> (the new window pops up) -> Click on “Compare” -> Click on “Add files” -> select those 2 files -> select the sections I would like to compare Thank you so much. Suparee Boonmanunt > > ------------------------------ > > Message: 2 > Date: Wed, 08 Jul 2015 12:20:51 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > Subject: Re: [EpiData-list] Access violation when comparing duplicate > files > Message-ID: <88C2E6EF-3317-4256-81A5-212A9B9228BF(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8 > > Please inform us of: > 1 the version of manager You are using. > 2 are you working with sections on one dataform or a related system with fields and sections on all dataforms > 3 have you defined a key, and if so is that used for coupling of the two project files? > > You get the version from the help menu "copy version " > > /Jens Lauritsen, Epidata association. > > On 8. jul. 2015 12.09.45 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: >> Dear all, >> >> I am trying to compare the duplicate files. I did it for each section. >> In some sections with small number of fields and just integer, the >> comparison goes well. But in other sections with larger number of >> fields, the program always shows the message ?Access violation? and ask >> whether I will ignore it and continue and kill the program. >> I always choose to ignore and the program seems to work on something. >> But nothing has really happened. >> >> Should I just wait, because the program is still working? Or should I >> fix something in the entries? >> >> I would be very grateful if someone could suggest me what to do. >> >> Kind regards, >> Suparee >> _______________________________________________ >> 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 140, Issue 4 > ********************************************

1 1

Access violation when comparing duplicate files
by EpiData development and support 08 Jul '15

08 Jul '15

Dear all, I am trying to compare the duplicate files. I did it for each section. In some sections with small number of fields and just integer, the comparison goes well. But in other sections with larger number of fields, the program always shows the message “Access violation” and ask whether I will ignore it and continue and kill the program. I always choose to ignore and the program seems to work on something. But nothing has really happened. Should I just wait, because the program is still working? Or should I fix something in the entries? I would be very grateful if someone could suggest me what to do. Kind regards, Suparee

1 1

EntryClient 2.0.3.15: Problem with lack of update of existing records
by EpiData development and support 07 Jul '15

07 Jul '15

In a specific project where we wanted to enter one field extra following extract and import of hospital records the following two problems emerged. Both aspects will be fixed in August. Just now there is a pause in development until August. Be reassured that we do all we can to solve such issues since they are in essense what we call "show stoppers" of using the software - unless we manage to find and fix the cause. Which we - expressed with modesty - have done until now. Apart from a special issue in estimation of certain lifetables in EpiData Analysis. But for that one have decided to fix it as part of the rewriting of the software to the "epx based" standa The current two issues relates to: EpiData Entry Client Program Version: 2.0.3.15 r481, Core version: 2.0.0.0 r1161, FPC Version: 2.6.4, Platform: i386-Win32 1. Lack of "value changed" upon entry in existing field with currently no information in that field Normally when you use the value label box (F9) to select values and change a value, then the current record is marked internally as edited. Upon change to the next record the system should ask "save record". But apparently this does not happen, the EntryClient just moves to the next record without saving the value 2. The standard behaviour of EpiData software when a user moves a given window to a new "non-default" position is that next time that window is opened it will be placed in that same position. This is currently not the done with EntryClient for the value label box and the "confirm change to records" box. The remedy until fixed was the following: I added an integer field of length 1. Then I changed the range to 1-1 and added mustenter requirement. In other words the only possible entry is a 1 (one). This shows that sometimes combinations of attributes can give problems, which we - unfortunately - have not identified yet. When we see such situations they are then added to the list of structured testing, which we apply before public release. The list is increasing with increased number of handled special situations. The solution could only be identified by a structured "trial and error" process, where I managed to find the cause, which can then be remedied. Unfortunately in some situations it is very difficult to create such a process. In particular when an issue is only present in some versions. An example of this is the 32/64 bit windows v8.1 issue which have struck some users and another issue where we have seen that a given epx related file works very well in Linux and Mac, but in Windows 7 creates an access violation on attempt to edit an existing record. . Any structured input to solving such problems is highly welcomed. Regards Jens Lauritsen EpiData Association Denmark.

1 0

Searching the List Archives
by EpiData development and support 03 Jul '15

03 Jul '15

Would there be a way to set up the EpiData-list Archives to implement a search function? As they are set up now: Archive View by: Downloadable version Second quarter 2015: [1][ Thread ] [2][ Subject ] [3][ Author ] [4][ Date ] [5][ Gzip'd Text 20 KB ] First quarter 2015: [6][ Thread ] [7][ Subject ] [8][ Author ] [9][ Date ] [10][ Gzip'd Text 14 KB ] they appear to be not very user-friendly if one tries to look for something specific. Thanks for considering, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: [11]http://www.tbrieder.org References 1. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/thread.html 2. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/subject.html 3. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/author.html 4. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2/date.html 5. http://lists.umanitoba.ca/pipermail/epidata-list/2015q2.txt.gz 6. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/thread.html 7. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/subject.html 8. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/author.html 9. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1/date.html 10. http://lists.umanitoba.ca/pipermail/epidata-list/2015q1.txt.gz 11. http://www.tbrieder.org/

1 4

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 13
by EpiData development and support 30 Jun '15

30 Jun '15

Thanks, that was the case. The chk file was not residing in the same folder as the rec file. martin On 27 June 2015 at 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. Version 3.1 used to keep the value labels in documents|view > data (EpiData development and support) > 2. Re: Version 3.1 used to keep the value labels in > documents|view data (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 26 Jun 2015 17:19:46 +0000 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Version 3.1 used to keep the value labels in > documents|view data > Message-ID: > <CAMUv7ZSFxFB0rP==gK55_pTa6K3gfiygH=KpHpmpY= > L0tj5hag(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I am using Epidata 3.1,When I open the data in Document | View data, from > Edit, I see the the data are checked to "Show labels", but the labels are > not shown. That means when I export to say, Stata, I don't have the > labels. I remember this used to work. Is there anything I am doing wrong? > > > regards > > -- > Martin Alhassan Adjuik > Statistician > Cell : +233 (0) 243714441 > madjuik(a)gmail.com > > > ------------------------------ > > Message: 2 > Date: Sat, 27 Jun 2015 12:32:41 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > Subject: Re: [EpiData-list] Version 3.1 used to keep the value labels > in documents|view data > Message-ID: <7C0F38CC-BD35-4DD9-9D98-64BEA7F6B5E5(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8 > > Most likely your chk file is not residing in the same folder as your rec > file or has a different name. > Regards jens Lauritsen > Epidata association > > On 26. jun. 2015 19.19.46 CEST, EpiData development and support < > epidata-list(a)lists.umanitoba.ca> wrote: > >I am using Epidata 3.1,When I open the data in Document | View data, > >from > >Edit, I see the the data are checked to "Show labels", but the labels > >are > >not shown. That means when I export to say, Stata, I don't have the > >labels. I remember this used to work. Is there anything I am doing > >wrong? > > > > > >regards > > > >-- > >Martin Alhassan Adjuik > >Statistician > >Cell : +233 (0) 243714441 > >madjuik(a)gmail.com > >_______________________________________________ > >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 139, Issue 13 > ********************************************* > -- Martin Alhassan Adjuik Statistician Cell : +233 (0) 243714441 madjuik(a)gmail.com

1 0

Re: [EpiData-list] Importing data to Epidata (v.2.0.5.51)
by EpiData development and support 28 Jun '15

28 Jun '15

Thank you very much Jamie, your help was indeed very helpful. I believe it also makes sense to convert yes/no/NA cells to have a numerical value e.g. 1,2,3 ? Is there a way to change the field type afterwards other than touching the XML code and if so, is it wise/dangerous? Pekka Jamie wrote: > > I have found that import from the clipboard works well if the Excel data > are prepared for the import. Here is what I do. > > In Excel, format the columns they way you want them to appear in EpiData > (text columns, numbers with set decimal places, dates as YYYY/MM/DD is > best). > I usually then format the columns to fit the data > No spaces in your column names - these should be valid EpiData field names > for consistency > Make sure that the first and last rows of data are complete; I often put > dummy data in these and then delete the records in EpiData. I believe the > main thing here is to have valid data (not empty cells) in the last column > of data for the first and/or last rows. > Ideally, have no blank cells - put missing values in. This is probably not > necessary, as EpiData handles empty cells well. > > > You may find that fields are not the length that you want. You can safely > edit these fields to change the size. Text, number and data fields should > all come through with the correct type. > > I don?t know of any simple way to convert data for an Excel column to > coded values with ?value labels?. Unless your data set is massive, there is > no real penalty to keeping the values in full. > > When I had to automate repeated conversion of messy Excel data to EpiData, > I made a new sheet within the Excel file and used formulas to put copies of > the original data into the new sheet, with all of the cleaning. For > example, we had some inconsistencies in coding province, so I used a lookup > table to convert the original values (Ontario, Ont, ON) to be consistent > (ON). This is one way to do your data coding, by the way, but you still > cannot automate getting the value labels into EpiData. In my case, the data > set was small and existing data might change, so I just kept importing the > whole thing. You can also just convert the new data, import to a new > EpiData project and then append this to your complete project. > > You will have problems with import from the clipboard if you have commas > in your text fields. In my testing, the import fails without an error > message. > > EpiData is very fussy about importing data, as it should be, since it does > such a good job of maintaining the integrity of data when you use it for > data entry. Import of csv data does work, but you have to be very sure to > have clean data and to not have stray delimiters in your data. In any case, > your data should be in good shape since it originates in a database (what > database?? Maybe there is another more direct way to get into EpiData) > --? > Jamie > > Pekka wrote: > What I want to do is to import a spreadsheet with field labels and data to > Epidata. The spreasheet contains field names on the top row and records on > the following rows. Once I have imported the initial data, I would like to > ammend the records with additional fields, i.e. have the initial > spreadsheet data as the seed data in records. I think this is a very normal > practice to do, but I have run into several difficulties: > > 1. I have tried to import the spreadsheet with "File/Import file" but I > don't seem to get it working. I have turned the spreasheet from Excel to > CSV, but the dialogue box that opens doesn't recognize data. I made a > workaround by copying a part of the spreadsheet and used "File/Import from > clipboard" and that did work. The downside is that you have to do it part > by part, and the fundamental problem is why it doesn't work in the first > place. Is Epidata Manager very picky as to what field separators are used > in CSV? I have tried changing field separators but with no luck. Clipboard > seems to be the only workaround, but even still I have to do it in parts. > (I am using Ubuntu and the latest Linux 64-bit version) > > 2. With the copy-paste method I noticed that Epidata was smartly able to > interpret some fields with the right type (e.g. date, but not all > date-fields, but I believe this is the issue of my spreadsheet), but not > all. I have not discovered a way to change the field type afterwards, is it > at all possible? The only hack I figured out was to manually change the > field type in XML code directly, but I would be very hesitant to do it. If > I touch XML code directly, will that mess up everything, or is it the > simple fix to the problem? > > 3. Value-labels: My spreadsheet contains no value labels, obviously. It has > for example field "Country of origin" and the value is string "Nepal". Is > there a way for me to easily convert strings of text into value labels as a > part of the import process? String values are consistent (the spreadsheet > is an output file from a database), so I should imagine it would be > possible do so. > > 4. Provided I get questions 1,2 and 3 adequately resolved, I should be fine > with the initial data import. But what do I do if I want to later import > additional records from the same spreadsheet structure to my Epidata > project? Is this something that Append is supposed to do? There I have the > same issue with the spreadsheet compatibility: The CSV file does not open > in a recognisable way, hence I haven't been able to play around and test it > either. > > > >

1 4

Version 3.1 used to keep the value labels in documents|view data
by EpiData development and support 27 Jun '15

27 Jun '15

I am using Epidata 3.1,When I open the data in Document | View data, from Edit, I see the the data are checked to "Show labels", but the labels are not shown. That means when I export to say, Stata, I don't have the labels. I remember this used to work. Is there anything I am doing wrong? regards -- Martin Alhassan Adjuik Statistician Cell : +233 (0) 243714441 madjuik(a)gmail.com

1 1

transfer questionnaire created in Mac version (2) to same version in PC?
by EpiData development and support 25 Jun '15

25 Jun '15

Dear friends apologies for this is a very simple question - may be I missed it in the documentation I would like to create a questionnaire on my Mac then take it to the field where there will be PCs. Will this work? Also using the data entry tool for PCs with a questionnaire created in the MAC programme? grateful for your advice Hilary

1 2

Importing data to Epidata (v.2.0.5.51)
by EpiData development and support 23 Jun '15

23 Jun '15

Hello, I am a newcomer to Epidata, so I apologize if my questions are not sophisticated. I am exploring the latest version and it is fantastic with many ingenious features, great work and great programming philosophy, thank you! As the version is new, I understand that the documentation is not yet fully developed, and hence if someone can help me with these questions, I think they can be of use to many others as well. What I want to do is to import a spreadsheet with field labels and data to Epidata. The spreasheet contains field names on the top row and records on the following rows. Once I have imported the initial data, I would like to ammend the records with additional fields, i.e. have the initial spreadsheet data as the seed data in records. I think this is a very normal practice to do, but I have run into several difficulties: 1. I have tried to import the spreadsheet with "File/Import file" but I don't seem to get it working. I have turned the spreasheet from Excel to CSV, but the dialogue box that opens doesn't recognize data. I made a workaround by copying a part of the spreadsheet and used "File/Import from clipboard" and that did work. The downside is that you have to do it part by part, and the fundamental problem is why it doesn't work in the first place. Is Epidata Manager very picky as to what field separators are used in CSV? I have tried changing field separators but with no luck. Clipboard seems to be the only workaround, but even still I have to do it in parts. (I am using Ubuntu and the latest Linux 64-bit version) 2. With the copy-paste method I noticed that Epidata was smartly able to interpret some fields with the right type (e.g. date, but not all date-fields, but I believe this is the issue of my spreadsheet), but not all. I have not discovered a way to change the field type afterwards, is it at all possible? The only hack I figured out was to manually change the field type in XML code directly, but I would be very hesitant to do it. If I touch XML code directly, will that mess up everything, or is it the simple fix to the problem? 3. Value-labels: My spreadsheet contains no value labels, obviously. It has for example field "Country of origin" and the value is string "Nepal". Is there a way for me to easily convert strings of text into value labels as a part of the import process? String values are consistent (the spreadsheet is an output file from a database), so I should imagine it would be possible do so. 4. Provided I get questions 1,2 and 3 adequately resolved, I should be fine with the initial data import. But what do I do if I want to later import additional records from the same spreadsheet structure to my Epidata project? Is this something that Append is supposed to do? There I have the same issue with the spreadsheet compatibility: The CSV file does not open in a recognisable way, hence I haven't been able to play around and test it either. Help is much appreciated, thank you! Pekka

1 1

EpiData Project: Current development focus and Strategy over next 1-2 years
by EpiData development and support 22 Jun '15

22 Jun '15

Development these months is focused on getting towards compliance with the legal regulations on access to data containing health information. In short this concerns: - definition of users and what they can do (change structure, modify users, export data ....) - logging of which users did what The total development list contains as well: - inclusion of scripting during Entry. Could be used for user defined functions such as summation af scales or reading of data from external lookup software). - rewriting of Analysis based on the new xml file format. And extension with more specific functions for routine reporting. A number of International Standards describe requirements of user control and logging in detail (piles of descriptions). This is difficult legal and technical documentation. For those using ISO standards this referes to ISO 27001 and 27002. A formal certification with an external auditing body would be a huge investment and NOT possible within the economic constrains of the EpiData project. Just as an example rewriting from one standard to another would cost 5000 Euro. Which is better spent on development. But implementation of the principles is required to secure continued use in some countries and some situations. E.g. for research in pharmaceutical products. More news will follow on this development, which is also dependent on continued donation of funding for the development of the EpiData software products. The remaining development is expected to take about 2-2½ years. Software will be released as open-source, when specific modules are ready with all decided functionality. The reason for working in this way is that before principles are settled it is a highly fragile situation. There is however continued correspondance and exchange of components with other users applying the Free-Pascal solution in Lazarus, which is the basis of EntryClient and Manager programming. Regards Jens Lauritsen EpiData Association.

1 0