hello
I am sure this has a simple answr but its quite annoying. I cannot copy my tables from epidata into word
How do i do this
thanks Bankole Olatosi PhD(c), MS, MPHResearch Associate, South Carolina Rural Health Research Center,Columbia, SC Tel: 803-251-6317Fax: 803-251-6399 PhD Candidate Health Services Policy and Management,Norman Arnold School of Public Health,University of South Carolina
_________________________________________________________________
Stay in touch with old friends and meet new ones with Windows Live Spaces
http://spaces.live.com/signup.aspx
Help: copying graphs/tables from Epidata into word
For graphs it is quite easy:
After creating a graph a copy is always placed on the clipboard, so:
1. create a graph - and make sure it is visible in the output window
(close edit graph if you requested edit).
2. start wordprocessor, drawing programme, presentation programme etc.
3. press ctrl+v - and the graph is copied into the current open programme.
If your pc is not too old you can have EpiData Analysis and the word
processor open at the same time and switch btw. them by pressing alt+tab
keys.
Regarding tables:
Is the development now such that default copying (ctrl+c) should be html
formatted rather than text formatted ?
Now: Shift+Ctrl+C: html formatted. Ctrl+C: tab delimited copying.
We are experimenting with a "mouse over" effect, such that if the mouse
is over a table or graph in output, then it would be nice that
"right-click" would enable "copy table" or "copy graph".
regards
Jens lauritsen
EpiData Association
Shavinder Singh has made some comments which are welcomed, but also
necessitates some clarifications.
The document put on the testing.php page is NOT a list of commands. It
is a somewhat internal technical
document created with the intent to write an overview of which options
will be in which commands.
The reference to the commands is the same as users from version 1.0 of
EpiData Analysis.
Regarding the comments on dates I will only add that maybe we should
change the name of date functions
from to
year(datevariable) yearval(datevariable)
day(datevariable) dayval(datevariable)
month(datevariable) monthval(datevariable)
since now there is a conflict with variable names date, year and month,
which users often will use.
Also we should implement some sort of warning to users when they use for
a variable name
an internal name. E.g. neither of "or and if" will ever work as a
variable name
Regards
Jens Lauritsen
EpiData Association
Dear Jens,
Some feedback about the document 2.1 about unification and. Here is some feed back from user of EPI6 and Epidata and Epi analysis. There is lots of good function for fine-tuning of the output from analysis. The commonly used commands like FREQ, TABLES, and MEANS would be able to produce tailored output as per the needs.
Few suggestions;
1. FREQ v1 produces the frequency table only. The summary measures such as observations, mean, SD, SE, minimum, maximum, 25th 50th 75th percentile are not shown.
The provision of these details is helpful in examining a quantitative variable in detail.
EPI6 had the facility of shutting the frequency table (esp. if it was too big) and print only the summary measures.
The syntax was, FREQ v1 /n
Kindly explore the possibility of this switch with FREQ command and the following switch also is so handy (EPI6). Another function was frequency weighted counts on variable
FREQ v1 /SUM=v2, where v1 is a categorical and v2 is numerical variable.
Is tab v1 /w=wvar same command or different, is not clear ?
2. Describe command gives the summary measures to some extent. This command has not been activated in the ver 1.1 of Epi Analysis.
3. MEANS command needs thorough overall. It requires the conversions of both the variables as
numerical. The categorical variables are not numerical variables. Hence this should be changed accordingly. The (/q or quite) quite switch closes the output totally. Actually this should omit the display of tables only. The summary measures should be displayed as was the case with EPI6 command MEANS v1 v2 /n
4. Dates remain a sour issue with EPI Analysis, though there is lot of help available from the
Epidata team members especially Jamie. Is it possible to use SET option to define the date
command such as SET DATE FORMAT =mm/dd/yyyy or SET DATE format=dd/mm/yyyy
We use most of the time only one type of date format. Then date or date range selection would become simple like simply typing the date variable. mm/dd/yyyy (If this does not make sense from programmers point of view, kindly forgive me)
5. The help manual As EPI ANALYSIS evolves in future, a well-written command reference becomes a necessity esp. keeping in mind the beginners. For example, SET options are clear to experienced user but not to the beginners.
Scatter graphs with regression line drawn or an option to draw it like /r
6. Many commands listed in the command reference 1.1 are not implemented yet.
The EPI ANALYSIS would be a wonderful product is most of these options are actually implemented. Keep up this good work.
With regards,
Dr. Shavinder Singh
It works perfectly. Thanks very much.
-----Original Message-----
From: epidata-list-bounces(a)lists.umanitoba.ca
[mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of
epidata-list(a)lists.umanitoba.ca
Sent: Tuesday, October 17, 2006 4:16 PM
To: epidata-list(a)lists.umanitoba.ca
Subject: Re: [EpiData-list] help with week + year combination
Small change to your code below. Will that work?
Jamie
> I am hoping I can get some help with epidata and use of year and
> week.
>
>
Before file
DEFINE WEEKS ##
DEFINE YEARS ####
DEFINE WEEK ####.##
end
DATEFROM
MUSTENTER
AFTER ENTRY
LET WEEKS = WEEKNUM(DATEFROM) + 1
LET YEARS = YEAR(DATEFROM)
LET WEEK = float(YEARS)+float(WEEKS)/100
END
END
If you want WEEK as a string, try:
let week = string(years)+"-"+copy(string(100+weeks),2,2)
(week is a string of length 7)
This will yield WEEK like the following
"2006-01"
"2006-52"
_______________________________________________
EpiData-list mailing list
EpiData-list(a)lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Hello all,
I am hoping I can get some help with epidata and use of year and week.
I currently work on a weekly report that numbers the weeks. However,
we've come full circle one year, and I don't want the data to combine
week 42 from last year with week 42 from this year. I have tried a
number of different fixes, but nothing seems to work. I wanted to
convert the 'week' field to a text, and just put "6-" in front of the
week, but it just doesn't work! I've tried making week and year defined
variables, then putting them together, but that doesn't work either.
I've changed the week field from a numeric to text, hoping that would
help, but it doesn't. For various reasons, creating a separate year
variable is not a good idea, so I've nixed that. Any assistance you can
provide would be appreciated. Here is the code I have right now, and it
doesn't work:
DATEFROM
MUSTENTER
AFTER ENTRY
DEFINE WEEKS ##
DEFINE YEARS ####
LET WEEKS = WEEKNUM(DATEFROM) + 1
LET YEARS = YEAR(DATEFROM)
LET WEEK = string(YEARS)+string(WEEKS)
END
END
Thanks in advance
Cas Tayor
DEWS Co-ordinator
Cell #03008582627
All you have to do is to run the whole sps file in SPSS
not only the save command. By running all the commands
(the complete syntax file) you create a dataset, which
will then be saved as an SPSS systemfile.
Regards
Jens Lauritsen
EpiData Association
<http://www.gmx.net/de/go/dsl>
Following the discussion on the list and some "offline" correspondance
with dedicated users I created a combined document with the current
decision. Those among the list members interested in development issues
can follow the link on the testing page
http://www.epidata.dk/testing.php which is where such documents will be
placed from now on.
As an example a standard table will look like this and adding an option
/SD will sort descending on values of row and column variables:
. tab ill vanilla
ILL Ill?
VANILLA Ice Cream:Vanilla: N Y Total
N 18 3 21
Y 11 43 54
Total 29 46 75
. tab ill vanilla /sd
ILL Ill?
VANILLA Ice Cream:Vanilla: Y N Total
Y 43 11 54
N 3 18 21
Total 46 29 75
There is also a link on the testing page to the documentation system now
used for all internal specification of development. Issues from the
internal working plan are not shown to the public before we have a
solution. But the issues are moved to a public list when a solution has
been found. For bugs reported by users in the system the issues will be
publicly available at all times.
regards
Jens Lauritsen
EpiData Association
Hi,
I have a problem outputting significance levels (p-values) for the
bivariate correlation in a correlation matrix. I wrote a program:
cor Y X Z T M A 5 x 5 correlation matrix is computed showing
the correlations between the various variables. In addition the total
number of observation is indicated at the end of the correlation
matrix. However, there no significance levels for the correlations
between the variables. I need your assistance in outputting the
significance levels in addition to the correlations.
Thanks.
Achilles Katamba
Uganda
Hi,
I've a problem with the SPSS export function in EPIDATA. It creates a syntax file *.sps, which have to executed in SPSS to gain the *.sav file.
For this purpose it is necessary to uncomment the last line of the syntax code. After this SPSS produces the following error code:
>Error # 105. Command name: SAVE
>This command is not valid before a working file has been defined.
>This command not executed.
But how can I define a working file before I have the exported data?
Have anybody a soultion for this problem?
Thanks in advance.
Greetings.
Benjamin Wecker
--
GMX DSL-Flatrate 0,- Euro* - Überall, wo DSL verfügbar ist!
NEU: Jetzt bis zu 16.000 kBit/s! http://www.gmx.net/de/go/dsl