Im using epidata entry and after almost a 1000 records Im trying to export
the data to Stata to start some initial analysis. However, when exporting to
Stata format a warning comes and no data are exported. The warning is...
Invalid data in record #889, filed sintocol, Export concluded.
I tryed to export ot other formats such as dbase an sas and spss... the
problem only happans when exporting to stata format!
I opened epidataentry and checked the register 889 and it did not seemed to
have anything wrong wiht it. Later I tryed to delete this register and the
error still coming!
Abraço forte e que a força esteja com você,
Bono Branger gave an example of an existing problem with Epidata
Analysis. The problem relates to the median (P50) for life-tables.
I am aware of the "non-fixing" of the problem. Obviously we will fix
this problem, but you must also be aware of the nature of the project.
We are NOT a company, we do not get any license fees from the users. We
are fixing problems within certain timelimits and priorities.
Just now - as I have informed on this list - the priority is to rewrite
some core modules for long term sustainability. We will get to the p50
Reproducible errors should be reported to the bug tracking system - for
which you find the address on the website epidata.dk (Mantis system).
Anyone not satisfied with the principles can at any time choose not to
use the software and buy (expensive) commercial software.
As part of telling of the most recent implementation of SPC Control
graphs while attending a quality assurance conference/forum in Berlin
(http://internationalforum.bmj.com/) last week I produced a "Statistical
Process Control Graphs in 5 minutes" - a link is placed near the top on
Please comment whether you find the text appropritate. (e.g. whether it
should be 10 rather than 5 minutes). See front page of EpiData or this
regards Jens Lauritsen
Im facing a little problem which so far I could not find a work around. Any
sugestions would be welcome.
I have tow datasets which come from different sources... I intended to join
them side-by-side with epidata entry to keep on going wiht the data update.
I know that the second one would update some stuff in the firts one, at
least for the majority of the observations.
Both of the have a unique identifier which is a variable called num. However
in the first set num is like this...
while in the second one num is like this...
For any software these would be different numbers but given that I know that
2007 is the yaer and 1 is january and 244 or 133 is the sequence within the
month I know that the second dataset have num in the inverse order.
Concatenating the datasets like this would be just as append because no
observatiosn would match. I tought in recode the numbers but this would be
same as digitizing all again. Nay sugestions?
Abraço forte e que a força esteja com você,
Version 2.2 has been released for public downloads today. You can get it
The file is provided as a setup exe file, but also as already installed,
where all files are contained in a zip file.
Since last public release in november 2008 quite many aspects have been
improved or adapted. In particular the whole SPC (Statistical Process
Control) graph system has been extended with more options and more
efficient layout. Also a grid for creating SPC graphs from scratch has
been implemented. - is available from the graph menu.
Some set commands have changed, such that users can be forced to update
any specified ini file that was created with the former version. An
extension is the possibility for the user to create preference options
for all commands, example:
set option tables = "/t /r /c"
would define that all tables done with the command "tables" will be
added the options /t /r and /c
Just today an error with stratified tables and small sample sizes was
reported - the error is now fixed. The problem was that some strata
would be combined incorrectly. Analysis done previously should be
repeated with the new version and proper control. Please report any
To see all changes go to the file:
Commands are all as previously documented in the command reference,
which will open when you press F1.
Please notice that the release of this depends on donated funding, as
documented on the page:
Users should update to this version of analysis, since some of the bugs
removed could affect results. The development continues with further
online documentation and teaching materials as well as core module
restructuring, such as announced on the list recently.
I have recently "upgraded" to SPSS v17. My exports from EpiData to SPSS
format no longer work.
The error messages I get in the SPSS syntax editor are:
14 DATA LIST Unrecognized text appears on the DATA LIST command where a
variable name was expected. Text: TO
69 VARIABLE LABELS This command is not permitted before the beginning of
file definition commands.
137 execute This command is not valid before a working file has been
Can someone suggest a resolution?
Health Data Analyst
Region of Waterloo Public Health
As part of the transition it was suggested to name all help files which
has the type "html" to be released with extension html instead of htm -
which is now used for EpiData Analysis.
eg. commands.htm would be commands.html, start.htm would be start.html etc.
If this poses problems to anyone let us know on the list.