Thank you Rafael,
Sorry I just managed to look at the URL attached file and used the Stat/Transfer to import it as SAS or Stata file and the output is in agreement of what you saw previously.
However, I will try it again using EpiC and get back to you.
Take care and get back to you on Tuesday or Wednesday when I can access the computer.
Tieble
On 3 July 2010 18:00, 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:
- Re: Re: EpiData-list Digest, Vol 81, Issue 2 (epidata-list@lists.umanitoba.ca)
- Re: Re: EpiData-list Digest, Vol 81, Issue 2 (epidata-list@lists.umanitoba.ca)
Message: 1 Date: Fri, 2 Jul 2010 14:21:47 -0400 (EDT) From: epidata-list@lists.umanitoba.ca Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 81, Issue 2 To: epidata-list@lists.umanitoba.ca Message-ID: 1973065110.949481278094907507.JavaMail.root@simcoe.cs.uoguelph.ca Content-Type: text/plain; charset=utf-8
Hi Tieble,
Thanks a lot for your reply. I did use EpiData export tool to send the file to SAS. I did try to export to Excel and I had no issues with it. What do you mean by posting lines of real data?
Thanks again,
Rafael ----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Friday, July 2, 2010 5:42:40 AM GMT -05:00 US/Canada Eastern Subject: [EpiData-list] Re: EpiData-list Digest, Vol 81, Issue 2
Hi Rafael, Did you try to export into another package such as Stata, or Excel, and so on? How did you export your data into SAS (using EpiData export tool or Stata Transfer)? Brief, I suggest that you reconsider another package (such as Stata). Assuming that you have already done this, then second suggestion is to post a chunk of few lines of fake or your real data then you may get appropriate help.
Thank you Tieble, London, UK
On 2 July 2010 02:52, 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:
- Re: new test release of EpiData Manager available (paste text as fields and read qes) (epidata-list@lists.umanitoba.ca)
- Problem exporting data to SAS (epidata-list@lists.umanitoba.ca)
Message: 1 Date: Thu, 01 Jul 2010 21:34:27 +0200 From: epidata-list@lists.umanitoba.ca Subject: Re: [EpiData-list] new test release of EpiData Manager available (paste text as fields and read qes) To: epidata-list@lists.umanitoba.ca Message-ID: 4C2CEDC3.6010808@epidata.dk Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I am quite sure everyone can understand the amount of work involved in the current rewriting and the need to focus and set the scope for development at a realistic level.
One of the aspects that I currently consider not needed is the development of an editor. Power users will each have their own preference for an editor and for the EpiData Manager we can optimise usage of the clipboard instead of developing a new editor.
Another issue is the need for documentation tools. My current understanding is that we do need:
- double entry verification (comparing two files and showing differences)
- count by id function (show a list of how many times a given id is
contained in a number of files)
- data verification according to controls built into a given data file. e.g. whether all mustenter, range and value label definitions are
met
- verification of keys (unique) and listing of observations not meeting
the defined key
And I also think these should be part of the Manager, whereas other functions such as: codebook, listing and viewing data should be part of analysis.
Comments on these aspects and the announced development phase sequence are welcomed on this list.
The next development phases are: a. Prevent double naming of fields on a dataform b. Develop first test release of a dedicated Entry Client. c. Add timed backup and date named zip file copy to Entry Client function. d. Add control of entry (mustenter, range, value labels) to Entry Client. e. Add multilanguage capability to dataform definition and entry client.
regards Jens Lauritsen EpiData Association
Message: 2 Date: Thu, 1 Jul 2010 21:40:27 -0400 (EDT) From: epidata-list@lists.umanitoba.ca Subject: [EpiData-list] Problem exporting data to SAS To: epidata-list@lists.umanitoba.ca Message-ID: <
1871457764.860511278034827330.JavaMail.root@simcoe.cs.uoguelph.ca>
Content-Type: text/plain; charset="utf-8"
Dear members,
I am currently setting up my database and faced one problem that I can't figure out. I entered some real data and exported to SAS. However, most variables are coming as missing (.), but very few are coming with the labels. I am thinking that it's something related to the checks on
EpiData
and not a SAS problem. If anyone could help me I would appreciate.
Following
attached is the .rec file.
Thanks in advance,
Rafael
epidata-list@lists.umanitoba.ca
-
epidata-list＠lists.umanitoba.ca