- EpiData-list - University of Manitoba Mailing Lists

Reading and closing files with EpiData
by epidata-list＠lists.umanitoba.ca 14 Jan '07

14 Jan '07

Dear Marc, > Also, I did not follow why the Read opened this file, and then I could > not close it? > > read "c:\epi_info\hosp\hsample.mdb > malformed string > . read "c:\epi_info\hosp\hsample.mdb" > No, data will be lost - Close first > . close read "c:\epi_info\hosp\hsample.mdb" > Syntax error It seems to me that you are triying to open an ACCESS file using EPiData. EpiData does not read ACCESS files. Still it trys, and the consequence is this: malformed string message. Once you have open a data set, Epidata does not allow you to open another without closing the first. This is because EpiData trys to prevent you of losing any changes you have done in your first data set. Only if you activily close you first data set you can open a second. The reason for the third message: Syntax error is that the syntax for closing a data set is just CLOSE. I hope it helps. Pedro Arias EpiData Translator > Thanks > Marc > L.A. > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 39, Issue 9 > *******************************************

1 0

Read files
by epidata-list＠lists.umanitoba.ca 14 Jan '07

14 Jan '07

EpiData Analysis does not read Access files, export it into a format that can be read (REC, CSV, DBF) Hans read "c:\epi_info\hosp\hsample.mdb malformed string . read "c:\epi_info\hosp\hsample.mdb" No, data will be lost - Close first . close read "c:\epi_info\hosp\hsample.mdb" Syntax error Thanks Marc L.A. -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

quesitons re Browse and Read/Close
by epidata-list＠lists.umanitoba.ca 13 Jan '07

13 Jan '07

I just started using Epidata. In my first Browse I could not move the screen completely to the right to see the command. Is there a limit to the number of characters the screen can display on any given line? Also, I did not follow why the Read opened this file, and then I could not close it? read "c:\epi_info\hosp\hsample.mdb malformed string . read "c:\epi_info\hosp\hsample.mdb" No, data will be lost - Close first . close read "c:\epi_info\hosp\hsample.mdb" Syntax error Thanks Marc L.A.

1 0

Regarding automatically filling of fields
by epidata-list＠lists.umanitoba.ca 13 Jan '07

13 Jan '07

Just a comment to MUSTENTER and NOENTER MUSTENTER prevents people from skipping inadvertently a field NOENTER prevents people from getting into the field and inadvertently change it (The role of the command MUSTENTER and NOENTER is not fully clear to me, = However, they have to be included in this fashion) To Jamie, Jens Lauritsen, Hans and all of you that follow this thread = and came with many helpful suggestions 'Thanks'. Hans -- Hans L Rieder, MD, MPH Jetzikofenstr. 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

Re: Regarding automatically filling of fields and colloborative efforts
by epidata-list＠lists.umanitoba.ca 13 Jan '07

13 Jan '07

1. Regarding automatically filling of fields > After trying different models, I managed to create a Syntax that allow me to enter data in one field and get automatically related data filled up in two other fields. I had to split the helping REC file into two files. The Key variable in the first file was the brand (say Aspirin) and the second variable was the Generic name (say ASA), and in the second file the Key variable was the generic name and the second variable the ATC code. > This is a very good example of how "good examples" develop with assistance. Please wrap up this example and send for inclusion as a worked example for placement on www.epidata.dk/examples.php E.g. just a zip file with the qes, chk and rec files and a pdf file showing the screen. Much like the "Yves" example, a good example was created. By combining efforts in this way many people learn and gets inspiration. Another way of giving inspiration is to work out "flyers" in collaboration with me, such as http://www.epidata.dk/php/downloadc.php?file=epidataflyer_general.pdf Projects or institutions having examples or ideas are much welcomed to suggest this. Best by writing to "info at epidata.dk " I hope during the 2007 it will be possible to get a WIKI started with mutual responsibility among users. Some aspects of this has been started, but the whole organisation is not ready for general use yet. A WIKI is an open editing system based on contributions from a broad base of users. Examples are: www.wikipedia.org, http://www.freepascal.org/wiki or https://wiki.ubuntu.com/. An example for use in EpiData would be introduction texts developed in local language, such as the one announced earlier on epidata-list by Bernard Branger and located at http://www.reseau-naissance.fr/medias/epidata_guide_2006.pdf and http://www.reseau-naissance.fr/medias/epidata_guide_controle.pdf which could be kept locally and then with a link in the wiki or added as text to the wiki. The difference from text on the EpiData main site is that the editing and placement on the WIKI needs no work from my part. In contrast to the main site where I (or another dedicated person) have to do something to add texts. Kind regards Jens Lauritsen EpiData Association

1 0

Regarding automatically filling of fields
by epidata-list＠lists.umanitoba.ca 12 Jan '07

12 Jan '07

To Jamie, Jens Lauritsen, Hans and all of you that follow this thread and came with many helpful suggestions 'Thanks'. After trying different models, I managed to create a Syntax that allow me to enter data in one field and get automatically related data filled up in two other fields. I had to split the helping REC file into two files. The Key variable in the first file was the brand (say Aspirin) and the second variable was the Generic name (say ASA), and in the second file the Key variable was the generic name and the second variable the ATC code. If somebody may give a feed back, I will appreciate it. The two 'Helping files' look like this: Brand-Generic (MedGen.REC) MedNvn Aspirin MedGen acetylic salicylic acid MedNvn Beuron MedGen acetaminophen MedNvn Efferalgan MedGen acetaminophen MedNvn Panadol MedGen acetaminophen MedNvn Paralen MedGen acetaminophen MedNvn Tyelenol MedGen acetaminophen Generic-ATC (MedATC.REC) MedGen acetylic salicylic acid MedATC n02ba01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 MedGen acetaminophen MedATC n02be01 The CHK file of my qustionnaire (MedicineQues.CHK): MedNvn MUSTENTER COMMENT LEGAL MedGen.rec Show TYPE COMMENT MedGen END MedGen COMMENT LEGAL MedATC.rec Show TYPE COMMENT MedATC END MedATC NOENTER End (The role of the command MUSTENTER and NOENTER is not fully clear to me, However, they have to be included in this fashion) The CHK file of the Brand-Generic database (MedGen.CHK): MedNvn KEY 1 END MedGen KEY 2 END The CHK file of the Generic-ATC database (MedATC.CHK): MedNvn KEY 1 END MedATC KEY 2 END My QESTIONNAIRE file (MedicineQues.QES): MedNvn the name of the Drug ___________________ MedGen The Generic name ___________________ MedATC The ATC code _____________ AnyFild Any field # *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 0

String functions
by epidata-list＠lists.umanitoba.ca 11 Jan '07

11 Jan '07

Hello Epidata Listers. My colleague and I are new to the data entry development game and can't figure out the string functions. Our study id is a combination of one letter and 3 numbers. I'd like for the letter to always be capitalized. It seems that the following might be appropriate somehow: function Upper(S: string): string Returns a string containing the same text as S, but with all letters converted to upper case. but I don't understand how it works. Where do I put the function? Do I replace "S" with the variable name "id"? I've tried several variations but since I don't understand the logic, I don't know how to debug my syntax errors. I'd appreciate any help you could give! Thanks, Kristine ------------------------------------- Kristine Hopkins, Ph.D. Population Research Center 1 University Station, G1800 Austin, TX 78712 ph: 512.471.8313 fax: 512.471.4886

1 1

(sin asunto)
by epidata-list＠lists.umanitoba.ca 10 Jan '07

10 Jan '07

1 0

Regarding automatically filling of fields
by epidata-list＠lists.umanitoba.ca 09 Jan '07

09 Jan '07

Once again This syntax work when data entered to one field and a second field being automaticaly filled up. What is the syntax for a following third field (ATC code) to be filled after the entering into the first field??? The CHK file of my qustionnaire (MedicineQues.CHK): MedNvn MUSTENTER COMMENT LEGAL MedGenATC.rec SHOW TYPE COMMENT MedGen END MedGen NOENTER END The CHK file of the Brand-Generic-ATC database (MedGenATC.CHK): MedNvn KEY 1 END MedGen KEY 2 END My QES file (MedicineQues.QES): MedNvn the name of the Drug ___________________ MedGen The Generic name ___________________ MedATC The ATC code _____________ AnyFild Any field # and my REC of the Brand-Generic-ATC database (MedGenATC.REC): (I took only 6 cases for illustration) MedNvn Aspirin MedGen acetylic salicylic acid n02ba01 MedNvn Beuron MedGen acetaminophen n02be01 MedNvn Efferalgan MedGen acetaminophen n02be01 MedNvn Panadol MedGen acetaminophen n02be01 MedNvn Paralen MedGen acetaminophen n02be01 MedNvn Tyelenol MedGen acetaminophen n02be01 *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 2

Regarding automatically filling of fields
by epidata-list＠lists.umanitoba.ca 08 Jan '07

08 Jan '07

The CHK file of my qustionnaire (MedicineQues.CHK): MedNvn MUSTENTER COMMENT LEGAL MedGenATC.rec SHOW TYPE COMMENT MedGen END MedGen NOENTER END The CHK file of the Brand-Generic-ATC database (MedGenATC.CHK): MedNvn KEY 1 END MedGen KEY 2 END My QES file (MedicineQues.QES): MedNvn the name of the Drug ___________________ MedGen The Generic name ___________________ MedATC The ATC code _____________ AnyFild Any field # and my REC of the Brand-Generic-ATC database (MedGenATC.REC): (I took only 6 cases for illustration) MedNvn Aspirin MedGen acetylic salicylic acid n02ba01 MedNvn Beuron MedGen acetaminophen n02be01 MedNvn Efferalgan MedGen acetaminophen n02be01 MedNvn Panadol MedGen acetaminophen n02be01 MedNvn Paralen MedGen acetaminophen n02be01 MedNvn Tyelenol MedGen acetaminophen n02be01 *¸..· ´¨)) -:¦:- * ¸.·´ . (( -:¦:- * Ishay * -:¦:- ´·.. ..·´ ((¸¸.·´* -:¦:-

1 0