Perhaps one could press just "enter" key without any number (known 999
treated as missing by EpiData) rather than leaving it blank.
If you leave it blank without pressing enter EpiData may not recognise it as
missing consequently SPSS will not. You will also need to chance the
missing code 9 or 999 to SPSS missing code.
On 17/01/2008, epidata-list-request@lists.umanitoba.ca <
epidata-list-request@lists.umanitoba.ca> wrote:
Send EpiData-list mailing list submissions to
epidata-list@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@lists.umanitoba.ca
You can reach the person managing the list at
epidata-list-owner@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:
- Export to SPSS messed up by missing data
(epidata-list@lists.umanitoba.ca)
- Re: Export to SPSS messed up by missing data
(epidata-list@lists.umanitoba.ca)
Message: 1
Date: Wed, 16 Jan 2008 15:50:29 -0500
From: epidata-list@lists.umanitoba.ca
Subject: [EpiData-list] Export to SPSS messed up by missing data
To: "EpiData List" epidata-list@lists.umanitoba.ca
Message-ID:
73dc8140801161250k4c49d36bge7101df054e1727e@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Hello folks. I just noticed that when I export to SPSS, things can end up
either missing or in the wrong columns when there are empty fields in the
.rec file. Here's a simple example I generated to test it. I created a
.qes file that looks like this:
{string1} String variable 1 __________
{num1} Numeric variable 1 ##
{datevar1} Date variable 1 <yyyy/mm/dd>
{string2} String variable 2 __________
{num2} Numeric variable 2 ##
{datevar2} Date variable 2 <yyyy/mm/dd>
{string3} String variable 3 __________
{num3} Numeric variable 3 ##
{datevar3} Date variable 3 <yyyy/mm/dd>
Then I entered a couple rows of data, with complete data on row 1, but
incomplete data on row 2 (num1 and datevar 1 were left blank).
When I export to Excel, I get the following (which is correct):
STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3
DATEVAR3
record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3
06/01/2008
rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23
02/01/2008
But if I export to SPSS, I get this, which is not correct:
STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3
DATEVAR3
record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3
01/06/2008
rec 2.1 . . 2201/01/20 8 . 2301/02/20
8 .
My first thought was that SPSS 16 is lousing things up. (I've been forced
to upgrade from v15 due to an institutional decision, and I've noticed
several other problems with v16). But the same problem occurred when I
tried on another machine running SPSS 11.
Has anyone else run into this? I didn't find any mention of it in the
archives.
What I'm doing for now to circumvent the problem is this:
- Exporting to SPSS to get syntax for all the variable and value labels
- Exporting to Excel to get the data into a format I can read with SPSS
- Creating syntax to import the Excel file, then adding the variable and
value label syntax generated by exporting to SPSS.
It's not terribly more complicated than a straight export to SPSS, but it
would be nice if I could do it in one step.
By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2, 4
gigs of memory IIRC).
Thanks,
Bruce
--
Bruce Weaver
bweaver@lakeheadu.ca
www.angelfire.com/wv/bwhomedir
"When all else fails, RTFM."
Message: 2
Date: Thu, 17 Jan 2008 09:34:49 +0100
From: epidata-list@lists.umanitoba.ca
Subject: Re: [EpiData-list] Export to SPSS messed up by missing data
To: epidata-list@lists.umanitoba.ca
Message-ID: 478F1329.8000402@fifas.de
Content-Type: text/plain; charset="iso-8859-1"
Hello Bruce,
I had a similar problem, when I exported strings with a length of 80
characters, which is the maximum. The datalist-syntax for spss was wrong
and imported only 79 (!) characters, so that the following variables
started one column to the left. If the following variable is numeric
with the lenght 1, it will be missing.
Regards
Juergen
epidata-list@lists.umanitoba.ca schrieb:
Hello folks. I just noticed that when I export to SPSS, things can end
up
either missing or in the wrong columns when there are empty fields in
the
.rec file. Here's a simple example I generated to test it. I created a
.qes file that looks like this:
{string1} String variable 1 __________
{num1} Numeric variable 1 ##
{datevar1} Date variable 1 <yyyy/mm/dd>
{string2} String variable 2 __________
{num2} Numeric variable 2 ##
{datevar2} Date variable 2 <yyyy/mm/dd>
{string3} String variable 3 __________
{num3} Numeric variable 3 ##
{datevar3} Date variable 3 <yyyy/mm/dd>
Then I entered a couple rows of data, with complete data on row 1, but
incomplete data on row 2 (num1 and datevar 1 were left blank).
When I export to Excel, I get the following (which is correct):
STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3
DATEVAR3
record 1.1 1 06/01/2008 record 1.2 2 . rec 1.3 3
06/01/2008
rec 2.1 . . rec 2.2 22 01/01/2008 rec 2.3 23
02/01/2008
But if I export to SPSS, I get this, which is not correct:
STRING1 NUM1 DATEVAR1 STRING2 NUM2 DATEVAR2 STRING3 NUM3
DATEVAR3
record 1.1 1 01/06/2008 record 1.2 2 01/16/2008 rec 1.3 3
01/06/2008
rec 2.1 . . 2201/01/20 8 . 2301/02/20
8 .
My first thought was that SPSS 16 is lousing things up. (I've been
forced
to upgrade from v15 due to an institutional decision, and I've noticed
several other problems with v16). But the same problem occurred when I
tried on another machine running SPSS 11.
Has anyone else run into this? I didn't find any mention of it in the
archives.
What I'm doing for now to circumvent the problem is this:
- Exporting to SPSS to get syntax for all the variable and value labels
- Exporting to Excel to get the data into a format I can read with SPSS
- Creating syntax to import the Excel file, then adding the variable
and
value label syntax generated by exporting to SPSS.
It's not terribly more complicated than a straight export to SPSS, but
it
would be nice if I could do it in one step.
By the way, I'm running EpiData 3.1 on a ThinkPad (XP Professional, SP2,
4
gigs of memory IIRC).
Thanks,
Bruce
--
Freiburger Institut fuer angewandte Sozialwissenschaft e.V.
FIFAS
Erasmusstr. 16, D-79098 Freiburg
Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493
Web: www.fifas.de
E-Mail: info@fifas.de
EpiData-list@lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
End of EpiData-list Digest, Vol 51, Issue 3