Dear Pierre-Yves:
I hope that "DATE" is only symbolically meant here, and not the actual name of your variable - it would be an illegal name (variables cannot have the name of a legal function)
Hans
On 03-Nov-22 10:16, EpiData development and support wrote:
I want to calculate intervals between 2 different pregnancies. In my .chk, I have put this command:
BEFORE FILE TYPE COMMENT ALLFIELDS RED END
INTERVALLE AFTER ENTRY INTERVALLE=((DATE - DATE1)/ 30) END END
And IT DOES NOT WORK I you can help. Thanks Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion _____
From: epidata-list-request@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Mon, 03 Jan 2022 22:00:18 +0400 Subject: EpiData-list Digest, Vol 202, Issue 1
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: 1. BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support) 2. Re: BIG PROBLEMS TO UPDATE A CHK FILE (EpiData development and support)
Message: 1 Date: Mon, 03 Jan 2022 13:19:13 +0400 From: EpiData development and support epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Subject: [EpiData-list] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: 20220103091913.c8c2eafa@smail.chu-reunion.fr Content-Type: text/plain; charset="UTF-8" We are changing year, so I am creating a "RU22.REC" with the root RU21.QES file (to replace the RU21.REC one)
- The other years I went in RU21.CHK and renamed it RU22.CHK and it worked
When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct 2) SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK BUT IT GIVES ME A VERTICAL QUESTIONNAIRE LIKE A VERY LONG SNAKE, VERY BAD TO MAKE A DATA RECORD HOW COULD I THROUGH THE "SAVEDATA" PROCEDURE HAVE AN HORIZONTAL (NORMAL) QUESTIONNAIRE Thank you very much for your help ALSO: HAPPY NEW YEAR Dr Pierre-Yves Robillard R?animation n?onatale et pediatrique, n?onatologie Centre Hospitalier R?gional Groupe Hospitalier Sud-R?union BP 350. 97448 Saint-Pierre cedex Ile de la r?union
Message: 2 Date: Mon, 3 Jan 2022 08:58:42 -0500 From: EpiData development and support epidata-list@lists.umanitoba.ca To: EpiData development and support epidata-list@lists.umanitoba.ca Subject: Re: [EpiData-list] BIG PROBLEMS TO UPDATE A CHK FILE Message-ID: 28A45B95-FE40-4966-A975-72FCCD1A533D@bell.net Content-Type: text/plain; charset=us-ascii Have you tried using the .REC file from 1) with the .CHK file from 2)? Normally, I would have done pretty much the same as you, but like this: Use the windows command line to copy files, in this order. copy ru21.qes ru22.qes Run EpiData to create ru22.rec from ru22.qes copy ru21.chk ru22.chk Jamie
On Jan 3, 2022, at 4:19 AM, EpiData development and support epidata-list@lists.umanitoba.ca wrote:
- The other years I went in RU21.CHK and renamed it RU22.CHK and it worked
When I do this now, I have 3 pages of errors on CHK (which is exactly the same which works with RU21) quite impossible to correct
- SECOND OPTION: I went on Epidata analysis and created without any problem RU22.rec Through the procedure
SAVEDATA c:\data\RU22.REC. with an automatic transfer of the RU21.CHK to RU22.CHK
________________________________________ EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 202, Issue 1