[EpiData-list] EpiData classic v3.1 in 2020? Under 64bit?
EpiData development and support
epidata-list at lists.umanitoba.ca
Wed May 6 21:30:20 CDT 2020
I had no problem with GLOBAL variables in a quick test with EpiData 3.1 downloaded just today, running Windows 10.
Things to check:
Have you defined the globals in a BEFORE RECORD block? It may work in a BEFORE FILE block as well, if that is even the correct usage. It has been a long time.
Have you done this in all of the .chk files where you want to use the global variable?
In the parent file.chk
DEFINE X # GLOBAL
X = SOMEVAR
In the child file.chk
DEFINE X # GLOBAL
SOMEVAR = X
> On May 1, 2020, at 15:48
> HOWEVER, one important feature no longer seemed to be working under Windows 7 pro 64bit: DEFINEd variables were only locally available (i.e. in the same record), but not GLOBALly (i.e. across RELATEd tables).
> Is anything known about this problem, or even a work-around?
> This would be important, because:
> 1- EpiData v3.1 uses a parsimonious language easy to retain e.g. for researchers who only occasionally are in the situation to program themselves a data entry tool (but then typically like to get it working quickly w/o learning new software);
> 2- According to http://www.epidata.dk/download.php <http://www.epidata.dk/download.php> (accessed today), "In special situations or when a given function is not yet developed in Manager, EntryClient and Analysis you could need ... EpiData (Classic) Entry v3.1 (get it here) (only for programmed checks, before/after end blocks)". HOWEVER, MANY will find essential what can be done with BEFORE/AFTER FILE/RECORD/(field) blocks and apparently can not (yet?) be done with v4.6;
> 3- The feature "DEFINE variable GLOBAL" is necessary for multiple-level hierarchies and longitudinal databases (and it proved feasible and effective when I did it 10 years ago under Windows 7 pro 32bit, communicating only by email between North-America and sub-Saharan Africa).
> Thanks in advance
More information about the EpiData-list