Dear all,
When I try to export my data into SAS, all my variables appear into a single column (in SAS). What could be happening?
When I export the data into Excel and then to SAS it does work perfect. Is there any difference from exporting a data file directly from EpiData into SAS other than EpiData into Excel and then SAS?
Thanks in advance for your help.
Rafael
The SAS export creates two files, xxx.txt which has your data and xxx.sas which is the data step to read the data. The .txt file does not have delimiters (i.e. no spaces or commas separate the data). So it may look like a single column with everything mashed together. What do you get when you run the data step?
Jamie
On 2010-10-13, Raphael wrote:
When I try to export my data into SAS, all my variables appear into a single column (in SAS). What could be happening?
When I export the data into Excel and then to SAS it does work perfect. Is there any difference from exporting a data file directly from EpiData into SAS other than EpiData into Excel and then SAS?
Hey Jamie,
As you mentioned, I get all my data into a single column...
Rafael
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Wednesday, October 13, 2010 10:39:38 PM Subject: Re: [EpiData-list] Exporting problems
The SAS export creates two files, xxx.txt which has your data and xxx.sas which is the data step to read the data. The .txt file does not have delimiters (i.e. no spaces or commas separate the data). So it may look like a single column with everything mashed together. What do you get when you run the data step?
Jamie
On 2010-10-13, Raphael wrote:
When I try to export my data into SAS, all my variables appear into a single column (in SAS). What could be happening?
When I export the data into Excel and then to SAS it does work perfect. Is there any difference from exporting a data file directly from EpiData into SAS other than EpiData into Excel and then SAS?
_______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
But you get 2 files, right? The one ending in .sas has the commands (data step in SAS terminology) to read the .txt file. You don't get a SAS data file until you run the data step in the .sas file. You need the data step to tell SAS which fields are in which columns. If that isn't working for you, just keep doing the export to Excel. Jamie
As you mentioned, I get all my data into a single column...
Rafael
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Wednesday, October 13, 2010 10:39:38 PM Subject: Re: [EpiData-list] Exporting problems
The SAS export creates two files, xxx.txt which has your data and xxx.sas which is the data step to read the data. The .txt file does not have delimiters (i.e. no spaces or commas separate the data). So it may look like a single column with everything mashed together. What do you get when you run the data step?
Hey Jamie,
Thanks for your help. I did manage to organize my dataset into columns.
Rafael
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Friday, October 15, 2010 8:49:27 AM Subject: Re: [EpiData-list] Exporting problems
But you get 2 files, right? The one ending in .sas has the commands (data step in SAS terminology) to read the .txt file. You don't get a SAS data file until you run the data step in the .sas file. You need the data step to tell SAS which fields are in which columns. If that isn't working for you, just keep doing the export to Excel. Jamie
As you mentioned, I get all my data into a single column...
Rafael
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Wednesday, October 13, 2010 10:39:38 PM Subject: Re: [EpiData-list] Exporting problems
The SAS export creates two files, xxx.txt which has your data and xxx.sas which is the data step to read the data. The .txt file does not have delimiters (i.e. no spaces or commas separate the data). So it may look like a single column with everything mashed together. What do you get when you run the data step?
_______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Thanks Jamie:
I have the same problems exporting to SPSS. These recommendations apply also to an SPSS exporting?
Regards,
2010/10/15 epidata-list@lists.umanitoba.ca:
Hey Jamie,
Thanks for your help. I did manage to organize my dataset into columns.
Rafael
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Friday, October 15, 2010 8:49:27 AM Subject: Re: [EpiData-list] Exporting problems
But you get 2 files, right? The one ending in .sas has the commands (data step in SAS terminology) to read the .txt file. You don't get a SAS data file until you run the data step in the .sas file. You need the data step to tell SAS which fields are in which columns. If that isn't working for you, just keep doing the export to Excel. Jamie
As you mentioned, I get all my data into a single column...
Rafael
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Wednesday, October 13, 2010 10:39:38 PM Subject: Re: [EpiData-list] Exporting problems
The SAS export creates two files, xxx.txt which has your data and xxx.sas which is the data step to read the data. The .txt file does not have delimiters (i.e. no spaces or commas separate the data). So it may look like a single column with everything mashed together. What do you get when you run the data step?
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list _______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Yes. SPSS export creates 2 files.
xxxx.txt has all the data as a text file with no delimiters and xxxx.sps has the short SPSS program to read the data and, if you wish, save an SPSS data file. You need to look at the .sps file to see what commands it is using. In particular, look at the .txt file and the commands to be sure that the columns line up.
When reading plain text files in SPSS or SAS, you have to specify what columns are used for each variable, the type of variable, and number of decimal places. The short program in the .sps or .sas file do this for you.
SPSS can easily read STATA data files. You might find it easier to export to STATA and use commands like this in SPSS:
get stata data="c:\data\xxxx.dta". exe.
With your version of SPSS, you probably also have the option of using menu commands to get the data. It has been many years since I used SPSS on a PC. This will be MUCH easier if you have data in STATA format.
Jamie
On 2010-10-17, at 9:31 AM, epidata-list@lists.umanitoba.ca wrote:
I have the same problems exporting to SPSS. These recommendations apply also to an SPSS exporting?
In testing the latest manager:
EpiData Manager Program Version: 0.5.6 Core version: 0.5.1 Revision: 194 FPC Version: 2.4.0 Platform: i386-Win32 Filename: XML Version: 0 Field count: 0 Record count: 0
I found that the number of sections possible to make is not unlimited. I could make only 5 sections, nr 6 could not be edited to give it a name. Yours, Louk Meertens.
On 2010-10-20 10:27, epidata-list@lists.umanitoba.ca wrote:
In testing the latest manager:
EpiData Manager Program Version: 0.5.6 Core version: 0.5.1 Revision: 194 FPC Version: 2.4.0 Platform: i386-Win32 Filename: XML Version: 0 Field count: 0 Record count: 0I found that the number of sections possible to make is not unlimited. I could make only 5 sections, nr 6 could not be edited to give it a name.
Please create a bug-report on the bugtracker:
http://www.epidata.info/flyspray/
Kind regards, Torsten Bonde Christiansen. EpiData Association.
Sorry Torsten Bonde Christiansen,
I created an account on FLYSPRAY and logged in but it is completely unclear to me how to create a new bugreport on those screens !
You have my info, Ileave it to you. Greets, louk meertens. -----------------------------------------------------
On 2010-10-20 10:27, epidata-list@lists.umanitoba.ca wrote:
In testing the latest manager:
EpiData Manager Program Version: 0.5.6 Core version: 0.5.1 Revision: 194 FPC Version: 2.4.0 Platform: i386-Win32 Filename: XML Version: 0 Field count: 0 Record count: 0I found that the number of sections possible to make is not unlimited. I could make only 5 sections, nr 6 could not be edited to give it a name.
Please create a bug-report on the bugtracker:
http://www.epidata.info/flyspray/
Kind regards, Torsten Bonde Christiansen. EpiData Association. _______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
On 2010-10-20 11:40, epidata-list@lists.umanitoba.ca wrote:
Sorry Torsten Bonde Christiansen,
I created an account on FLYSPRAY and logged in but it is completely unclear to me how to create a new bugreport on those screens !
I'm sorry to hear that. It is out intent to move users to report problem on the flyspray bugtracker, since this gives a better chance of documenting changes and fixes with the program. Perhaps when you have the time take a look around the site and if in doubt about what to do, please feel free to ask.
You have my info, Ileave it to you.
From the information you have given I cannot reproduce the problems you describe. There is no limit (program wise) to how many sections it is possible to create, however it is know that on Windows machines, at times creating sections can be a bit tricky - eg. moving the mouse outside the program window (while creating the section) will do strange things.
Kind regards, Torsten Bonde Christiansen. EpiData Association.
Thanks Jamie. I'm very glad of your helpful response.
A hug from Dominican Republic!!!
2010/10/17 epidata-list@lists.umanitoba.ca:
Yes. SPSS export creates 2 files.
xxxx.txt has all the data as a text file with no delimiters and xxxx.sps has the short SPSS program to read the data and, if you wish, save an SPSS data file. You need to look at the .sps file to see what commands it is using. In particular, look at the .txt file and the commands to be sure that the columns line up.
When reading plain text files in SPSS or SAS, you have to specify what columns are used for each variable, the type of variable, and number of decimal places. The short program in the .sps or .sas file do this for you.
SPSS can easily read STATA data files. You might find it easier to export to STATA and use commands like this in SPSS:
get stata data="c:\data\xxxx.dta". exe.
With your version of SPSS, you probably also have the option of using menu commands to get the data. It has been many years since I used SPSS on a PC. This will be MUCH easier if you have data in STATA format.
Jamie
On 2010-10-17, at 9:31 AM, epidata-list@lists.umanitoba.ca wrote:
I have the same problems exporting to SPSS. These recommendations apply also to an SPSS exporting?
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
participants (1)
-
epidata-list＠lists.umanitoba.ca