> I sent past message related to "field definition error in line
> 640" message.
> I tried to retype the QES form. So each five questions, I
> switched the
> QES file into REC file and did "checks" for it. I kept doing the
> same
> procedure, and I passed the line 640.
We should know more about the contents of the qes file to answer, e.g.:
1. How many lines in total
2. Hovw many fields are you planning
3. Are you using the "first word" or automatic options for creation of fields.
4. which build and version of EpiData
5. Have you tried also with the v3.1 release candidate ?
6. Does preview of the same file work
If you have as many fields as you indicate the error is either because you
have more than 1000 lines in the qes file (which v3.1. will issue a warning
for) or the automatic numbering of fields with similar names ran out of
possible combinations.
Happy new year to everyone
Jens Lauritsen
Limits:
* EpiData is a single user program. Workaround: Enter data on one PC and distribute copies for reading of data to other PC's.
* Number of Records in a file (currently around 200.000).
* All fields must fit within 999 lines of text.
- but: You can combine files which each has that many lines (RELATE function
-------- Message d'origine--------
De: epidata-list-bounces(a)lists.umanitoba.ca de la part de epidata-list(a)lists.umanitoba.ca
Date: mer. 29/12/2004 09:33
À: epidata-list(a)lists.umanitoba.ca
Cc:
Objet: [EpiData-list] Field definition error
Hello again!
I sent past message related to "field definition error in line 640" message.
I tried to retype the QES form. So each five questions, I switched the
QES file into REC file and did "checks" for it. I kept doing the same
procedure, and I passed the line 640.
Later on, the message showed up again, and please note here that I was
at line 1007, which means EpiData read line 640 already before and there
was no problem.
What happened now? Help!!
Thank you and best regards
/Ziad
--
Ziad El-Khatib
Clinical Cancer Epidemiology
Z5:01, Karolinska Institutet
17 176 Stockholm
Sweden
Telephone: +46-8-517 72 946
Fax: +46-8-517 79 621
Mobile: +46-73-776 48 59
_______________________________________________
EpiData-list mailing list
EpiData-list(a)lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Hello again!
I sent past message related to "field definition error in line 640" message.
I tried to retype the QES form. So each five questions, I switched the
QES file into REC file and did "checks" for it. I kept doing the same
procedure, and I passed the line 640.
Later on, the message showed up again, and please note here that I was
at line 1007, which means EpiData read line 640 already before and there
was no problem.
What happened now? Help!!
Thank you and best regards
/Ziad
--
Ziad El-Khatib
Clinical Cancer Epidemiology
Z5:01, Karolinska Institutet
17 176 Stockholm
Sweden
Telephone: +46-8-517 72 946
Fax: +46-8-517 79 621
Mobile: +46-73-776 48 59
Hello!
I tried to run a REC file, I was getting this error message:
"The field definition in line 593 could not be read or interpreted"
This does not show when I "preview" the QES file. The field mentionned above is a number field (##).Everything looks ok for me.
Any tips?
Thank you in advance!
Happy & Safe 2005!
/Ziad
--
Ziad El-Khatib
Clinical Cancer Epidemiology
Z5:01, Karolinska Institutet
17 176 Stockholm
Sweden
Telephone: +46-8-517 72 946
Fax: +46-8-517 79 621
Mobile: +46-73-776 48 59
The first thing to do when getting messages such as
"Error in the data file <filename>"
Would be to check if the latest backup copy you made gives the same
answer (I assume everyone are taking regular backups).
If you have no backup copy of the file in question and you have
exported the data to SAS, just make SAS save the file as a delimited
file and get it back via the qes file, which you have hopefully a copy
of.
An error often occurring is that users are saving other filetypes on
top of data due to Windows NOT showing complete file name, but excluding
extensions. Therefore one can by mistake think that there "save as .not
file " (e.g. yourfile.not), but it was actually a .rec file (e.g.
yourfile.rec).
To exclude that possibility set up your windows to always show
extensions for all types, also known files. Ask someone if you do not
know how to- it is an option in explorer for folders.
regards
Jens Lauritsen
EpiData initiator and coordinator.
Build 16 of analysis has been uploaded.
Added or modified
update shows which values are changed with if statements.
if started with a pgm file, that file will be executed.
internal representation of float variable changed from double to extended
Testsystem improved (e.g. try startnist.pgm)
Bug removal and modification:
String variables of length 1 are saved correctly
negative values in result variables fixed
lre() function corrected for negative values
Calculation of 10,25,75 and 90 percentiles corrected
recode function corrected to include limits btw. groups
Various interface problems
Adapted Commands.htm and Howto.htm file.
Download from Http://www.epidata.dk/testing.php
Remaining issues before release as v1 are:
Implementing a system to handle incorrect data when reading (e.g. years
like 0203)
Some aspects of reading dbf files - report errors.
Table command - simplifying output for stratified tables
Printing can be a problem accross printers - report problems.
Defining Boolean variables impossible (<Y>) due to interference
with html language, use integer instead.
But for many standard types of analysis and basic graphs it works quite
well.
Regards
Jens Lauritsen
Coordinator and initiator of EpiData
EpiData Association, Odense, Denmark
I will be back at my desk on Tuesday 22/12/2004 morning. Until then I
will have little opportunity to access my E-mail.
Anything regarding the:
Inter-Agency EMERGENCY ENVIRONMENTAL HEALTH FORUM
Please send your message again to interagency(a)lshtm.ac.uk
If there is anything other requiring urgent attention, please contact:
Rebecca.Collins(a)lshtm.ac.uk +44 020 7927 22 14 or
Rachel.Clarke(a)lshtm.ac.uk +44 020 7927 22 14
Kind regards
Kristof
>>> epidata-list 12/17/04 18:20 >>>
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..."
I am a new user of EpiData and I have successfully created data files
and exported to SAS for analysis. One of the .rec files I recently
created will not open and I get the following error message:
Error in the data file <filename>
The field definition in line 3 could not be read or interpreted.
Any advice on how to correct this problem is appreciated.
Dear Ziad,
Could you please email me a copy? - My email address is NWilson(a)iuatld.org.
Thanks and regards
Nevin
Dr.Nevin Wilson, M.B., B.S.,
Junior TB Consultant
International Union Against Tuberculosis
and Lung Disease (The Union)
68, Boulevard Saint-Michel
75006 Paris, France
Mobile : +91 94430 26848
Tele/Fax: +91 4262 266022
email: NWilson(a)iuatld.org
website: www.iuatld.org
-----Original Message-----
From: epidata-list(a)lists.umanitoba.ca
[mailto:epidata-list@lists.umanitoba.ca]
Sent: Friday, November 26, 2004 1:15 PM
To: epidata-list(a)lists.umanitoba.ca
Subject: [EpiData-list] EpiData guideline - released for testing
Hello!
The file is done now and I am sending it to test it.
If someone is interested to have a copy, please write me back with your
email address so I can email it to you (it is around 5.5Mb size) in PDF
format.
It is free for distribution as well!
And anyone is welcome to write back with questions and/or suggestions!
Note: I have intention to go further in guidelines development in case there
is interest and fund (maybe?) to keep the work on?
Best regards!
/Ziad
Karolinska Institute
Stockholm - Sweden
To handle "jumps reset 9" for string fields this would have to be settled
after the values are filled in. That is if the jump is to field "endnote1",
then there could be a
endnote1
before entry
>IF (Q14=55) THEN
> CLEAR Q15B
> CLEAR Q16B
>ENDIF
end
end
Jens M. Lauritsen
The EpiData Association,
ps. The list does not disclose users e-mail adresses to minimise spam. If
someone wishes to have direct comments you must add the e-mail directly in
the text - as some did yesterday, but I suggest to do it in a way spam
systems will not (should not) catch, e.g. "info at epidata.dk" that is
put " at " instead of @