- EpiData-list - University of Manitoba Mailing Lists

EpiData Analysis build 134 ready for testing
by epidata-list＠lists.umanitoba.ca 20 Apr '08

20 Apr '08

Many minor problems have now (hopefully) been solved in build 134 of EpiData Analysis. Which is available from the usual testing page: www.epidata.dk/testing.php Some issues remain: - small data / zero cell inaccuracies (Most likely not solved, but better information should be developed) - update had to be disabled in this build - a major rewrite is needed before stable function use EpiData Entry for changes to data instead. - some wishes reported to Mantis database - The user base seems divided in where to put some aspects in the menu system: - should logfiles be in file menu or results - should edit setup ini be in file menu or edit Issues solved: Version 2.0.0 build 134 * Extended or adapted function * CIPLOT: adapted to changed order of variables and defaults new plot with confidence intervals for proportions (e.g. cases in subgroups of other variables) * BAR and Histogram: Y axis can be scaled as percent: Option /PCT * Weight variables can be non-integer in tables * merge accepts comparing upper string with string key * Update disabled this build (inconsistent behaviour must be rewritten) * Documentation * Command reference updated (F1) * added quick guide (see F1) * Bugs * Upper string variables written as standard string * Various bugs removed For those wishing to test or comment on the adapted menu system, please see www.epidata.dk/testing.php to get the updated build. Following testing we are approaching release as v2.1 with first translations in Spanish and French. I do acknowledge in particular Gilles Desve for the adaptation of the multinational translation module and Jamie Hockin, Pedro Arias, Peron (Juan Carlos Merino), Bjørnar Nyen, Hans L. Rieder and Neville Verlander for discussions and inputs. But also the EpiData-list discussants in general. In the previous year the Association of Public Health Epidemiologists in Ontario have established an important expert panel, which have been very active in the specification of the CIplot command and other recent aspects. More on this latter collaboration will be announced later. Update is not permanently disabled, but has shown many problems. Therefore I am considering NOT to wait a full rewrite of update, but instead disabling update, to be able to release v2.1 with translation. Comments welcomed on this aspect also. Regards Jens Lauritsen EpiData Association

1 0

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 19 Apr '08

19 Apr '08

I will be out of the office starting 04/19/2008 and will not return until 04/23/2008. If you require immediate assistance, please contact Celina Sousa at extension 5300. Thanks and have a great day, Alyshia

1 0

Count n days between dates?
by epidata-list＠lists.umanitoba.ca 19 Apr '08

19 Apr '08

Dear EpiData lister, it might be simple question, how is it possible to have var 'ndays' showing the number of days between 2 dates, any tips? Thank you in advance and best regards ziad

1 1

Re: Command line help--thank you
by epidata-list＠lists.umanitoba.ca 19 Apr '08

19 Apr '08

Dear Jens Many thanks for the help. Much appreciated. SK -----Original Message----- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 16 Apr 2008 7:21 pm Subject: EpiData-list Digest, Vol 54, Issue 6 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..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Re: Re: New user trying to implement a check algoritm (epidata-list(a)lists.umanitoba.ca) 2. Re: Worked examples of EpiData Analysis: command line (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Apr 2008 20:44:53 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Re: New user trying to implement a check algoritm To: epidata-list(a)lists.umanitoba.ca Message-ID: <48054C05.4050809(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Range checks do work on string variables, since EpiData just compares the internal values. However, EpiData will not care whether the strings have non-numeric values within this range. For example, the following will pass the RANGE test: 1993ABCDEFGH since this is 12 digits and internally any string starting with "1993" will lie between "1992xxxxxxxx" and "2018xxxxxxxx" EpiData will detect an error and assign a missing value to PRNx variables when this happens. The default option is to NOT notify you of errors in check files at data entry, so you should also check that CHECKSUM <> . If only the last digit (the checksum value) is bad, CHECKSUM <> PRN12 will tell you there is an error In my experience, the internal precision of EpiData will let you use 12-digit integers. The RANGE checks will then work fine and entry of non numbers is impossible. So another way to guarantee entry in this range is define preQ2A ____________ global preQ2 Range 1991...... etc preQ2A = string(preQ2) and work everything on preQ2A, since it is easy to pick apart strings using the COPY function. Where you can get into trouble with long integers is when you start to do arithmetic with them. Jamie Gustaf wrote: > I've now redefined preQ2 to be a string variable, but the RANGE check > still works. How is this possible? > > preQ2 > RANGE 199201010001 201801010001 > END ------------------------------ Message: 2 Date: Tue, 15 Apr 2008 20:57:01 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Worked examples of EpiData Analysis: command line To: epidata-list(a)lists.umanitoba.ca Message-ID: <48054EDD.2070706(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed There is no / before the if This is a case of EpiData having somewhat simpler and more natural syntax. The / is reserved for options. So: list idno sr if idno < 10 There is only one option with list (/no to not show record numbers), so: list idno sr /no if idno < 10 Syntax for this use of IF is in the command reference under "temporary selection" The error messages with syntax problems are sometimes misleading. Jamie SK wrote: > here is what I did and the error message: > . read > Loading data F:\EpiExam\blood.rec, please wait.. > File name : F:\EpiExam\blood.rec > Fields: 5 Total records: 2166 Included: 2166 > . List?????? idno? sr? /if idno<10 > = sign expected at idno > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 54, Issue 6 *******************************************

1 0

Worked examples of EpiData Analysis: command line
by epidata-list＠lists.umanitoba.ca 15 Apr '08

15 Apr '08

Dear all I wish to use EpiData Analysis editor to write a program to help users prepare a standard statistical report from data they will be collecting in Epidata Entry. I have used SAS so am not new to command line programing. I have looked at the command line help in Analysis, but it does not have examples of the codes used: e.g. for the list command, I wish to use a selection of records IF a condition is met: list v1 v2 v3 /if v1<10 here is what I did and the error message: . read Loading data F:\EpiExam\blood.rec, please wait.. File name : F:\EpiExam\blood.rec Fields: 5 Total records: 2166 Included: 2166 . List?????? idno? sr? /if idno<10 = sign expected at idno Could someone help me out and send me an example where command lines are used for common analysis with options as well. Again many thanks for the help, SK South Africa

1 1

Re: New user trying to implement a check algoritm
by epidata-list＠lists.umanitoba.ca 15 Apr '08

15 Apr '08

Comment 1: Hi Gustav, What an coincidence. Today we have been doing something similar with the Danish cpr-nr which is 10 digit 'ddmmyyzzz'. When we treated this as a numeric fiels with 10 digits our algorithms broke down when the date was after the 21. I think that the problem is that the largest integer in many pc languages (here Delphi/pascal) for an integer systems is The MaxInt constant gives the largest allowed value for an Integer. The value is normally (2^32)-1 = 2147483647 If you use a float you will get other problems. The solution for us was to store the complete personal number af a string variable and then extract the relevant number using substr and real. Best wishes Claus Seniorstatistician Claus Holst Institute of Preventive Medicine Center for Health and Society Copenhagen The institute: http://www.ipm.regionh.dk EU projects: http://www.nugenob.org http://www.diogenes-eu.org/ Comment 2: In EpiData we recently changed default max length for integers to be 9 digits and to have the same default in as well analysis and entry. (Although for analysis if you use gen command the length would be 4) The reason for the limitation of length of integer being smaller than the MaxInt constant mentioned by Claus Holst. This is due to the founding of the rec file format in Epi Info v6, which handled integers until the length of 4 as true integers, but stored larger integers internally as floats. We can discuss if the length of 9 is sufficient. But it is my experience in all software that merging on large integers tends to give problems of precision. Therefore my suggested solution for Gustav's problem would be as Claus Holst also suggests to use a string variable. In extension (but not related to the integer/string problem) the algoritm for the luhn algorithm (http://en.wikipedia.org/wiki/Luhn_algorithm) could be implemented as a user written CHK command based on the procedures written for EpiData Entry. This is documented on the page www.epidata.dk/documentation.php with two examples: Soundex, Metaphone and Gumm algoritms. regards Jens Lauritsen EpiData Association

1 2

Re: EpiData-list Digest, Vol 54, Issue 2
by epidata-list＠lists.umanitoba.ca 14 Apr '08

14 Apr '08

Dear Epidata Users Many thanks for the input you all gave me about packaging Epidata with the data folders. Much appreciated. Kind regards, SK -----Original Message----- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Thu, 10 Apr 2008 7:24 pm Subject: EpiData-list Digest, Vol 54, Issue 2 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..." EpiData-list mailing list ___________________________________ Today's Topics: 1. EpiData-list Digest, Vol 54, Issue 1 Attach files to executable (epidata-list(a)lists.umanitoba.ca) 2. Re: How to package Epidate Software with desired data entry files (epidata-list(a)lists.umanitoba.ca) 3. Re: How to package Epidata Software with desired data entry files (epidata-list(a)lists.umanitoba.ca) 4. How to package Epidata Software with desired data entry files (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Wed, 9 Apr 2008 15:49:31 -0300 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData-list Digest, Vol 54, Issue 1 Attach files to executable To: epidata-list(a)lists.umanitoba.ca Message-ID: <a37cfb5a0804091149g599b97f0ydd5409f612fd881a(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Dear SK, I did a similar thing many years ago. I hope it works for you even nowadays. Lets assume that Epidata can just be pasted at some place such as c:\ (wich is reasonable and works fine wiht me - as far as know epidata does not require any system files). Then, I sugest that you delete the Epidata sample files and place your files in this same directory where the sample files were. This would make the one who is starting Epidata for the first time to see your files instead of the sample files if the short cut does not work. So naw U have a c:/epidata with your files in c:/epidata/samples. Make a shortcut on your desktop that point to c:\epidata\samples\<myproject>.rec, and be sure that this short cut has the option "open with" pointing to the epidata executable in c:\epidata\. Test it. If it is fine follow next... Then, you should have a progrma such as winzip or winrar. This programs can make executable files that self-exctrat to a prespecified place such as c:/. I dont remeber exactly how it is but look for options to meke self extract files. So, if when the user executes them the file extratcs the whole folder or whatever you put in them to the prespecified place. You also may want to input a password at the files to be extratcted, winzip for shure does that. Then when you sand an email for your mates, with these two files, one zipped selfextracted (.exe) and a shortcut wiht the following tip - paste both files ate your desktop, execute the .exe file, execute the shortcut. The magic should work... at least it did with me. Best Regards, Pedro Emmanuel Brasil ------------------------------ Message: 2 Date: Wed, 09 Apr 2008 20:39:05 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re: How to package Epidate Software with desired data entry files To: epidata-list(a)lists.umanitoba.ca Message-ID: <47FD0D49.1010107(a)soziologie.uni-freiburg.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 1. You can have a look at the epidata command line options and then add a batch file (.bat) to your zipped package. there is no need to install epidata, but you can simply let the users unpack the .zip to a folder on their desktop and double click the batch file. 2. More convenient way is to use an installer software like http://nsis.sourceforge.net/Main_Page (you can create desktop shortcuts and things like that). But be aware of user rights, common desktop systems in professional setups dont allow installations in programm directory or are even more restricted. so people may have to call an administrator to install the package. hope this helps, markus jenki epidata-list-request(a)lists.umanitoba.ca schrieb: > 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..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. How to package Epidata Software with desired data entry files > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 08 Apr 2008 13:42:29 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to package Epidata Software with desired > data entry files > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <8CA67B70CD54729-D58-2F4(a)MBLK-D29.sysops.aol.com> > Content-Type: text/plain; charset="us-ascii" > > Hi there, > > I am embarking on a project to keep an in-patient child admissions/discharge database in all district hospitals in our Province. I have designed the database and created data entry files (QES|CHK|REC|EIX) and put them into a folder (IPDatabase). Now what I wish to do is package this folder into the EpiData Entry|Analysis software (*.exe setup files); so that the users could just click the installation and have the software installed in a default WinXP Program directory directly, and with this would go the IPDatabase folder with all the data entry files. > 1. The user (data capturer) will then start data entry by going to the folder to pick up the .REC file in the IPDatabase folder, but first he will have to start up Epidata Entry.. > 2 Or create a desktop shortcut that will directly link up with the data entry process; without even staritng up the EpiData Entry software--desired outcome > > Why am I doing this?--well, I have users who have difficulties understanding difference between installation of the software and using the data entry file. One precess that will get the objectives met: capture data without having to think about the process. > > I hope this is a possibility? > > Many thanks in advance. > > SK > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 54, Issue 1 > ******************************************* > ------------------------------ Message: 3 Date: Wed, 09 Apr 2008 18:58:39 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How to package Epidata Software with desired data entry files To: epidata-list(a)lists.umanitoba.ca Message-ID: <47FD4A1F.70603(a)sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed There are many solutions as some have already sent you. When packaging EpiData and Analysis up, you can use the shortcut/batch files mentioned to load Analysis so that it launches with an HTML file. This is the way it gets loaded the first time after it is installed. If you are at all familiar with command lines and simple HTML, have a look at the file in (on my computer) c:\program files\epidata\docs\en\startepi.htm This HTML file provides a way to launch a menu system with Analysis. You can provide options such as - Enter Data - launches Enter yourfile.rec - Analyze Data - execute the READ yourfile command and then lets the user use Analysis commands - you can even package up what commands should be used. However, these are not techniques for the novice. Have a look at startepi.htm to get an idea of how this works and then decide how sophisticated you want to make things (i.e. how easy/fool proof for your users) Jamie epidata-list(a)lists.umanitoba.ca wrote: > Hi there, > > I am embarking on a project to keep an in-patient child admissions/discharge database in all district hospitals in our Province. I have designed the database and created data entry files (QES|CHK|REC|EIX) and put them into a folder (IPDatabase). Now what I wish to do is package this folder into the EpiData Entry|Analysis software (*.exe setup files); so that the users could just click the installation and have the software installed in a default WinXP Program directory directly, and with this would go the IPDatabase folder with all the data entry files. > 1. The user (data capturer) will then start data entry by going to the folder to pick up the .REC file in the IPDatabase folder, but first he will have to start up Epidata Entry.. > 2 Or create a desktop shortcut that will directly link up with the data entry process; without even staritng up the EpiData Entry software--desired outcome > > Why am I doing this?--well, I have users who have difficulties understanding difference between installation of the software and using the data entry file. One precess that will get the objectives met: capture data without having to think about the process. > > I hope this is a possibility? > > Many thanks in advance. > > SK > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > ------------------------------ Message: 4 Date: Thu, 10 Apr 2008 10:51:49 +0100 (BST) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] How to package Epidata Software with desired data entry files To: epidata-list(a)lists.umanitoba.ca Message-ID: <287335.55799.qm(a)web25003.mail.ukl.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 SK asked about “intelligent” setup on pc’s for users without IT knowledge. Basically install EpiData Entry on your computer and create the data entry files. You can run the basic EpiData Entry and EpiData Analysis without installation of the programmes. Package the data entry files (Qes, Chk, Rec, Eix) and only the EpiData.exe file (not the setup_epidata.exe file which does not need to be installed to run the program. Zip them and send them to the users. For the users: Unzip the files into a created folder (IPDatabase in your case) In that folder, double click EpiData.exe, EpiData Entry opens, then go to “Enter Data” and open the created folder, and open the *.rec file for data entry. Second possibility is to create a link on the desktop and add the name of the datafile as a parameter e.g. “epidata.exe c:\ip\IPDatabase.rec” Additionally you could you could automate backup and exit EpiData Entry by adding the following block to the chk file. For the backup to work you must manually create the backup folder. AFTER FILE BACKUP c:\ip\backup zip ip DATE QUIT END Regards, Biggie Mabaera Maseru, Lesotho --------------------------------- Yahoo! for Good helps you make a difference ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 54, Issue 2 *******************************************

1 0

New user trying to implement a check algorithm
by epidata-list＠lists.umanitoba.ca 11 Apr '08

11 Apr '08

Hi all, I'm a new user of EpiData. At the moment, I'm making a data entry system for a medical questionnaire. In this questionnaire, a 12 digit personal identification number should be entered. The first 8 digits of this number is the birthday, the following 3 digits carry some obscure meaning (gender being one of them), and the last digit is a control number calculated from the previous 11 digits by the luhn algorithm (http://en.wikipedia.org/wiki/Luhn_algorithm). I've been trying to implement this algorithm in EpiData (see below), but when I try to use this check file, EipData doesn't like it, claiming the "FLOAT(copy(preQ2s,1,1))"-expressions are too wide. Any suggestions on how to solve this in a more elegant way? Many thanks in advance, Gustaf ------ Algorithm. "preQ2" is the variable name for the specific question, defined as a 12 digit number (############)------------ preQ2 RANGE 199201010001 201801010001 DEFINE pnr1 _ DEFINE pnr2 _ DEFINE pnr3 _ DEFINE pnr4 _ DEFINE pnr5 _ DEFINE pnr6 _ DEFINE pnr7 _ DEFINE pnr8 _ DEFINE pnr9 _ DEFINE pnr10 _ DEFINE pnr11 _ DEFINE pnr12 _ DEFINE preQ2s ____________ DEFINE checkSum ## preQ2s=string(preQ2) pnr1=FLOAT(copy(preQ2s,1,1)) pnr2=FLOAT(copy(preQ2s,2,2)) pnr3=FLOAT(copy(preQ2s,3,3)) pnr4=FLOAT(copy(preQ2s,4,4)) pnr5=FLOAT(copy(preQ2s,5,5)) pnr6=FLOAT(copy(preQ2s,6,6)) pnr7=FLOAT(copy(preQ2s,7,7)) pnr8=FLOAT(copy(preQ2s,8,8)) pnr9=FLOAT(copy(preQ2s,9,9)) pnr10=FLOAT(copy(preQ2s,10,10)) pnr11=FLOAT(copy(preQ2s,11,11)) pnr12=FLOAT(copy(preQ2s,12,12)) IF (pnr3>4) THEN pnr3=pnr3*2-9 ELSE pnr3=pnr3*2 ENDIF IF (pnr5>4) THEN pnr5=pnr5*2-9 ELSE pnr5=pnr5*2 ENDIF IF (pnr7>4) THEN pnr7=pnr7*2-9 ELSE pnr7=pnr7*2 ENDIF IF (pnr9>4) THEN pnr9=pnr9*2-9 ELSE pnr9=pnr9*2 ENDIF IF (pnr11>4) THEN pnr11=pnr11*2-9 ELSE pnr11=pnr11*2 ENDIF checkSum=pnr3+pnr4+pnr5+pnr6+pnr7+pnr8+pnr9+pnr10+pnr11 IF (checkSum=10*int(checkSum)) THEN checkSum=checkSum/10 ELSE checkSum=10*(TRUNC(checkSum/10)+1)-checkSum ENDIF IF (pnr12<>checkSum) THEN HELP "felaktigt PersonNummer" TYPE=ERROR GOTO preQ2 ENDIF END -- Gustaf Rydevik, M.Sci. tel: +46(0)703 051 451 address:Essingetorget 40,112 66 Stockholm, SE skype:gustaf_rydevik

1 1

How to package Epidata Software with desired data entry files
by epidata-list＠lists.umanitoba.ca 10 Apr '08

10 Apr '08

SK asked about intelligent setup on pcs for users without IT knowledge. Basically install EpiData Entry on your computer and create the data entry files. You can run the basic EpiData Entry and EpiData Analysis without installation of the programmes. Package the data entry files (Qes, Chk, Rec, Eix) and only the EpiData.exe file (not the setup_epidata.exe file which does not need to be installed to run the program. Zip them and send them to the users. For the users: Unzip the files into a created folder (IPDatabase in your case) In that folder, double click EpiData.exe, EpiData Entry opens, then go to Enter Data and open the created folder, and open the *.rec file for data entry. Second possibility is to create a link on the desktop and add the name of the datafile as a parameter e.g. epidata.exe c:\ip\IPDatabase.rec Additionally you could you could automate backup and exit EpiData Entry by adding the following block to the chk file. For the backup to work you must manually create the backup folder. AFTER FILE BACKUP c:\ip\backup zip ip DATE QUIT END Regards, Biggie Mabaera Maseru, Lesotho --------------------------------- Yahoo! for Good helps you make a difference

1 0

How to package Epidata Software with desired data entry files
by epidata-list＠lists.umanitoba.ca 09 Apr '08

09 Apr '08

Hi there, I am embarking on a project to keep an in-patient child admissions/discharge database in all district hospitals in our Province. I have designed the database and created data entry files (QES|CHK|REC|EIX) and put them into a folder (IPDatabase). Now what I wish to do is package this folder into the EpiData Entry|Analysis software (*.exe setup files); so that the users could just click the installation and have the software installed in a default WinXP Program directory directly, and with this would go the IPDatabase folder with all the data entry files. 1. The user (data capturer) will then start data entry by going to the folder to pick up the .REC file in the IPDatabase folder, but first he will have to start up Epidata Entry.. 2 Or create a desktop shortcut that will directly link up with the data entry process; without even staritng up the EpiData Entry software--desired outcome Why am I doing this?--well, I have users who have difficulties understanding difference between installation of the software and using the data entry file. One precess that will get the objectives met: capture data without having to think about the process. I hope this is a possibility? Many thanks in advance. SK

1 1