EpiData-list February 2012

epidata-list@lists.umanitoba.ca

1 participants
13 discussions

Version 1.1 of Manager and EntryClient release

by epidata-list＠lists.umanitoba.ca

Today we have released new versions of EpiData Manager and EpiData EntryClient. As with the first public release of Manager and EntryClient, this release has been packed in an installer which should work for Mac, Windows and Linux. The changes made are in short: * An issue with saving project files where pathnames/filename contained non-ASCII characters. * Fixed a number of bugs related to importing data. * Fixed a number of bugs related to saving colour settings in EntryClient. The updated versions are available from the download page on http://www.epidata.dk The release is part of the new principle, where a given new version first is placed as a beta version on the testing page and then moved to a public release on the download page if no problems show up. Therefore the v1.1 placed on the download page today is the same as the beta version placed for about a week on the testing page. On the testing page you will then find two versions: a. the next version to be released in general (such as v1.1) b. The current development (alpha) version, which you can consider a temporary "how far is the development currently" - users testing obviously must recognise that changes will occur during development. In all cases do not use the versions on the testing page for production work - only to influence development and test whether future releases have solved the problems identified. Kind regards, Torsten Bonde Christiansen, Jens M. Lauritsen. EpiData Association.

12 years, 1 month

Reading and writing in EPIDATA ANALYSIS V 2.2.2.178

by epidata-list＠lists.umanitoba.ca

22 feb 2012 Hello Jens and Kirsten, Working with this new Epidata Analysis (V 2.2.2.178) I found the following oddities: Reading files: .EPZ files went OK .EPX files were not accepted, the files were made by the latest MANAGER program from an imported normal RECfile. Writing files: An .EPZ file was subsequently saved with SAVEDATA into a .RECfile. This recfile was well accepted and loaded in EpidataAnalysis and also in ANALYSIS from EPI6, and also in ENTERX from EPI6, but the structure of the file was very strange: In each record a lot of space was added at the end of the record. This extra space did not hamper using the file. Also this was not accounted for in the filesize in the file system of my WINDOWS XP (SP 3). have a good day, Louk Meertens.

12 years, 2 months

Merge & Relate issue

by epidata-list＠lists.umanitoba.ca

Good morning to all the list, I'm experiencing a problem with my own epidata questionnaire setup, defined as follows: MENU.qst - Q1.qst ----Q1_1qst - Q2.qst MENU is just a initial menu that allows the user to select the questionnaire they want to enter or edit. Depending on entered number, the user is redirected using a IF…ELSE construct, like this: IF selection = 1 THEN RELATE code q1 1 ENDIF IF selection = 2 THEN RELATE code q2 1 ENDIF In MENU.qst, Q1.qst and Q2.qst there is a key, defined in each case as KEY UNIQUE 1, while Q1_1 is related to Q1 using the same key as Q1, but is defined as KEY 1. When I try to merge together Q1 and Q2 everything goes fine, but when I try to export the data in Excel format the process exits with an error about the newly generated checkfile. In particular, the problem lies in the fact that the key in the new checkfile is defined simply as KEY 1, and not as KEY UNIQUE 1. However, to relate Q1 to Q2 needs the key to be defined as UNIQUE. I don't see any reason why while merging the new checkfile defines the key as not unique, since the codes are still unique also in the merged file. There is any workaroud for this? Thank you, Dario Vianello

12 years, 2 months

EpiData-list mailing list submissions

by epidata-list＠lists.umanitoba.ca

<epidata-list(a)lists.umanitoba.ca>

12 years, 2 months

help with double data entry in EpiData

by epidata-list＠lists.umanitoba.ca

This is a question about double data entry in EpiData : We commonly use EpiData to do double data entry. We use Tools > Prepare Double Entry Verification and select the field ID for matching records. When we open the *_dbl file for data entry, a box usually opens stating 'double data entry verification mode / data compared with *.rec / compared by Field ID'. What does it mean when that box does not open ? Are we simply entering records into the _dbl file without comparing fields from the *.rec file ? Recently we have experienced the box opening *and* the box NOT opening when selecting the same _dbl file for data entry. How can we know for certain that all records in the _dbl file have been verified - even when the box does not open. Thanks in advance.

12 years, 2 months

First alpha release of Manager and EntryClient

by epidata-list＠lists.umanitoba.ca

Dear List. As we told in a previous mail, we are moving towards a new schedule for releasing our programs. This move has been completed today with the first release of our development branch for Manager and EntryClient. As stated, these releases are experimental versions of the programs and should not be used for "real" data in an everyday production. However we do encourage you to download the programs, test the new features and give us feedback on what you think is missing, not working etc. The alpha relases are placed for download in a seperate section on the testing <http://epidata.dk/testing.php#alpha> page of out website. There is a link for both EpiData Manager and EpiData EntryClient which list the added features, not already included in the stable/beta releases. Kind regards, Torsten Bonde Christiansen, Jens M. Lauritsen EpiData Association

12 years, 2 months

Posting to List

by epidata-list＠lists.umanitoba.ca

sunnygm74(a)gmail.com

12 years, 2 months

Submission of variable name

by epidata-list＠lists.umanitoba.ca

Hello Torsten & Jens, Thanks for the beta version release in this month.I have some few submission for the new epi data entry software. 1. Currently it is difficult to have the variable name appear on the screen as compared to old version EpiData. where for instance want to design a screen like: Qid Questionnaire ID Q1 Gender of respondent. With this current one, the variable name does not appear only the variable label. Is it possible to include check box in the basic menu to include the variable name, instead of the current form. 2. Is it possible to have a function to make a screen design in a roster format, so that if you are capturing data for household you can design the screen as you see it. eg. Name Age Sex. Household member 1 2 3 4 . . 10. With this function, it will make capturing data in table format easy. Hoping to read from you soon, as we test the beta version V1.1.1. Regards, Sedzro On Fri, Feb 10, 2012 at 6: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. New test versions of Manager and EntryClient > (epidata-list(a)lists.umanitoba.ca) > 2. New Entry Client and Manager versions > (epidata-list(a)lists.umanitoba.ca) > 3. Re: New Entry Client and Manager versions > (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Cc: > Date: Fri, 10 Feb 2012 12:17:42 +0100 > Subject: [EpiData-list] New test versions of Manager and EntryClient > Dear List. > > We have released a new test releases of EpiData Manager and EpiData > EntryClient. > > Since we released version 1.0 of Manager and EntryClient a number of > issues have been raised by > users. We have addressed most of these issues and we encourage you to > download, test and give your > feedback to the list on whether you find the issues resolved or not. > > In addition to these bug fixes, we are planning for a new release schedule > of our programs. > This is because we wish to reflect our development cycle in how we release > the programs. > > What does this mean? > For most parts: not much. But it gives us a possiblity to release updates > faster and respond > quicker to new reported issues. It also gives those of you who wishes to > see the latest and > greatest features being developed right now, a chance to test and try the > programs in an early > alpha stage. > > The release of software is devided into three stages (show here in reverse > development order): > 1) Stable: This is the version we have tested, tried and generally > consider to be stable for > for production/read projects. > If a bug is reported finding the cause and fixing it has highest priority > in the development. > This will be available for general download on http://www.epidata.dk/* > *download.php <http://www.epidata.dk/download.php> > > 2) Beta: This version is based on the stable version, but with reported > bugs from the stable > version fixed. Usually no new features are included. > This will be available for general download on > http://www.epidata.dk/testing.**php <http://www.epidata.dk/testing.php> > > 3) Development/Alpha: This version is a direct copy of what is being > developed at the moment. > There is NO guarantee this version will be backward compatible and > could break other > dependancies. > However, this gives you as a user the oppertunity to try out the > latest and greates features > we are developing at the moment. Although this is in general > considered an unstable release, > we do still aim for it to be working at all times (and hopefully > backward compatible.) > > Todays release is a Beta release and hence is placed in the testing page < > http://epidata.dk/testing.php**> of our website. If no major > bugs are reported we will release the this beta version as a stable > release in a short period of time. > > Changes from version 1.0 (Stable) to 1.1.1 (Beta): > > Manager and EntryClient: > * Fixed bug where non-US path/filenames causes save/load errors on Windows > OS. > * Fixed bug where config file failed to save on non-US Windows OS. > * Fixed bug where version information in XML file was incorrect (was 0 > should be 1). > * Fixed bug where using jumps with boolean field would cause error on load > of file. > * Fixed bug where saving data on rare occations could create invalid XML > syntax in .epx file. > > Manager: > * Fixed two bugs where program could cause access violation when closing a > project. > * Fixed bug where importing data files could cause crash. > * Fixed bug in importing .rec/chk files, where value part of a valuelabel > was surrounded by quotes (") > * Added import of floating-point valuelabels from .rec/chk files. > > EntryClient: > * Auto calculated fields did not mark a record as modified > * Fixed bug in search where clicking "Find" did not find any records. > * Fixed bug where colours chosen in settings were not saved. > * Fixed bug where "recent files" were not case sensitive on Linux and Mac > OS X. > * Changed default colours for active field. > * Changed search List/Find to not include initial value of > Repeat/DefaultValue field. (Result is that clicking Ctrl+L on a new record > gives a complete list of the dataset) > > Kind regards, > Torsten Bonde Christiansen. > Jens Lauritsen. > > > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Cc: > Date: Fri, 10 Feb 2012 13:32:44 +0100 > Subject: [EpiData-list] New Entry Client and Manager versions > When will there be new releases for Entry Client and Manager for Mac? > I think it's great that there are two seperate programs now, but I miss > some of the functionalities of EpiData Entry (lookup in one .rec file while > working in another and coding an integer as key unique through the GUI). > > I hope anybody knows!? > > -- > Kind regards, > Remco La Rivière > > > ** > > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Cc: > Date: Fri, 10 Feb 2012 08:22:30 -0500 > Subject: Re: [EpiData-list] New Entry Client and Manager versions > The Mac versions are on the website (release and test) for some time now. > They work well. > Jamie > > On 2012-02-10, at 7:32 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > When will there be new releases for Entry Client and Manager for Mac? > > I think it's great that there are two seperate programs now, but I miss > > some of the functionalities of EpiData Entry (lookup in one .rec file > while > > working in another and coding an integer as key unique through the GUI). > > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > -- ............ * MENSAH KOJO SEDZRO* Postal P.O.Box AS 387| Ashaiman -Tema | Ghana Skype: rasbesa web rasbesafari.blogspot.com House : +233-303-300789 Cell : +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.

12 years, 2 months

New Entry Client and Manager versions

by epidata-list＠lists.umanitoba.ca

When will there be new releases for Entry Client and Manager for Mac? I think it's great that there are two seperate programs now, but I miss some of the functionalities of EpiData Entry (lookup in one .rec file while working in another and coding an integer as key unique through the GUI). I hope anybody knows!? -- Kind regards, Remco La Rivière **

12 years, 2 months

New test versions of Manager and EntryClient

by epidata-list＠lists.umanitoba.ca

Dear List. We have released a new test releases of EpiData Manager and EpiData EntryClient. Since we released version 1.0 of Manager and EntryClient a number of issues have been raised by users. We have addressed most of these issues and we encourage you to download, test and give your feedback to the list on whether you find the issues resolved or not. In addition to these bug fixes, we are planning for a new release schedule of our programs. This is because we wish to reflect our development cycle in how we release the programs. What does this mean? For most parts: not much. But it gives us a possiblity to release updates faster and respond quicker to new reported issues. It also gives those of you who wishes to see the latest and greatest features being developed right now, a chance to test and try the programs in an early alpha stage. The release of software is devided into three stages (show here in reverse development order): 1) Stable: This is the version we have tested, tried and generally consider to be stable for for production/read projects. If a bug is reported finding the cause and fixing it has highest priority in the development. This will be available for general download on http://www.epidata.dk/download.php 2) Beta: This version is based on the stable version, but with reported bugs from the stable version fixed. Usually no new features are included. This will be available for general download on http://www.epidata.dk/testing.php 3) Development/Alpha: This version is a direct copy of what is being developed at the moment. There is NO guarantee this version will be backward compatible and could break other dependancies. However, this gives you as a user the oppertunity to try out the latest and greates features we are developing at the moment. Although this is in general considered an unstable release, we do still aim for it to be working at all times (and hopefully backward compatible.) Todays release is a Beta release and hence is placed in the testing page <http://epidata.dk/testing.php> of our website. If no major bugs are reported we will release the this beta version as a stable release in a short period of time. Changes from version 1.0 (Stable) to 1.1.1 (Beta): Manager and EntryClient: * Fixed bug where non-US path/filenames causes save/load errors on Windows OS. * Fixed bug where config file failed to save on non-US Windows OS. * Fixed bug where version information in XML file was incorrect (was 0 should be 1). * Fixed bug where using jumps with boolean field would cause error on load of file. * Fixed bug where saving data on rare occations could create invalid XML syntax in .epx file. Manager: * Fixed two bugs where program could cause access violation when closing a project. * Fixed bug where importing data files could cause crash. * Fixed bug in importing .rec/chk files, where value part of a valuelabel was surrounded by quotes (") * Added import of floating-point valuelabels from .rec/chk files. EntryClient: * Auto calculated fields did not mark a record as modified * Fixed bug in search where clicking "Find" did not find any records. * Fixed bug where colours chosen in settings were not saved. * Fixed bug where "recent files" were not case sensitive on Linux and Mac OS X. * Changed default colours for active field. * Changed search List/Find to not include initial value of Repeat/DefaultValue field. (Result is that clicking Ctrl+L on a new record gives a complete list of the dataset) Kind regards, Torsten Bonde Christiansen. Jens Lauritsen.

12 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list February 2012