Command line and demonstration
Greetings. 2 things.
1. I saw an example from Epidata which looked like this: c:\epidata\epidatastat myreport.pgm
I haven't tried this but, does this mean that epidatastat will execute the .pgm???
I would lke to see all components of EpiData, analysis, editor etc. to be Able to for example: EpiENTER <file.rec>, EpiEDITOR <*.pgm>, EpiSIS <myreport.pgm> etc.
Why? When developing systems using MENUs it seems to be better to 'hide' from the General user the database, reports .pgm etc. Selecting EpiData and then option 4 Exposes databases etc. to perhaps a not so sophisticated user.
2. I work for the CDC/Global AIDS Program and I think I have managed folks to Investigate placing EpiData, analysis etc. into what we call a software development Tool kit.
I have been asked if I would conduct a 'brown bag' demonstration etc. I do not think I have enough experience as yet to do the software justice, expecially Analysis. Is there someone out there who would like to discuss this with me?
Thanks and stay safe, kelly
EpiData can take program parameters. If you run "epidata.exe mydatafile.rec" then EpiData will run and immediately open the data file mydatafile.rec for data entry. If you run "epidata.exe myqesfile.qes" then EpiData will open with myqesfile.qes in an editor window. Please see the EpiData help file for more information, search for "program parameters" in the index of the help file.
EpiDataStat (analysis) takes pgm-files as program parameter, so running "epidatastat.exe myprogram.pgm" will open EpiDataStat and run the myprogram.pgm file.
Regards Michael Bruus EpiData Association
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Wednesday, April 06, 2005 4:23 PM Subject: [EpiData-list] Command line and demonstration
Greetings. 2 things.
1. I saw an example from Epidata which looked like this: c:\epidata\epidatastat myreport.pgm
I haven't tried this but, does this mean that epidatastat will execute the .pgm???
I would lke to see all components of EpiData, analysis, editor etc. to be Able to for example: EpiENTER <file.rec>, EpiEDITOR <*.pgm>, EpiSIS <myreport.pgm> etc.
Why? When developing systems using MENUs it seems to be better to 'hide' from the General user the database, reports .pgm etc. Selecting EpiData and then option 4 Exposes databases etc. to perhaps a not so sophisticated user.
2. I work for the CDC/Global AIDS Program and I think I have managed folks to Investigate placing EpiData, analysis etc. into what we call a software development Tool kit.
I have been asked if I would conduct a 'brown bag' demonstration etc. I do not think I have enough experience as yet to do the software justice, expecially Analysis. Is there someone out there who would like to discuss this with me?
Thanks and stay safe, kelly _______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
I am not sure whether this is partially of help. EpiData Promoters have developed a mini-course on EpiData and EpiData Analysis for beginners up to intermediate level, based on our experience with this software in the operations research courses of The Union. This is prepared on a CD-ROM, but to avoid shipping costs we have also placed it today on the web:
www.tbrieder.org
Regards,
Hans L Rieder
----- Original Message ----- From: epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Wednesday, April 06, 2005 16:23 Subject: [EpiData-list] Command line and demonstration
Greetings. 2 things.
1. I saw an example from Epidata which looked like this: c:\epidata\epidatastat myreport.pgm
I haven't tried this but, does this mean that epidatastat will execute the .pgm???
I would lke to see all components of EpiData, analysis, editor etc. to be Able to for example: EpiENTER <file.rec>, EpiEDITOR <*.pgm>, EpiSIS <myreport.pgm> etc.
Why? When developing systems using MENUs it seems to be better to 'hide' from the General user the database, reports .pgm etc. Selecting EpiData and then option 4 Exposes databases etc. to perhaps a not so sophisticated user.
2. I work for the CDC/Global AIDS Program and I think I have managed folks to Investigate placing EpiData, analysis etc. into what we call a software development Tool kit.
I have been asked if I would conduct a 'brown bag' demonstration etc. I do not think I have enough experience as yet to do the software justice, expecially Analysis. Is there someone out there who would like to discuss this with me?
Thanks and stay safe, kelly
participants (1)
-
epidata-list＠lists.umanitoba.ca