February 2025 - EpiData-list - University of Manitoba Mailing Lists

Writing .PGM files for New EpiDataanalysis?
by EpiData support and user community 15 Feb '25

15 Feb '25

Caution! This message was sent from outside the University of Manitoba. Dear list, I am experiencing a fairly steep learning curve trying to write quite basic .pgm script files for the new post-2018 EpiData Analysis guided by the introductory text on the epidata website and the commands.html reference. I have searched the web for relevant tutorials, courses or examples, but cannot find any. Could anybody on the list be willing to share some programming examples for example on the examples page on Epidata.dk (or elsewhere)? BTW: Does the new Analysis allow for a parallel to the user input command in Classic: globalvariable=trim("?Input value?") Thanks for any hints or links. Regards, Vegard Hoegli MD, MPH

1 6

PGM-file with date formulas crashes
by EpiData support and user community 07 Feb '25

07 Feb '25

Caution! This message was sent from outside the University of Manitoba. Dear list, 4 years ago I made a menu-driven activity monitoring system for a community health center based on the menu system designed by Jens Lauritsenand Hans Rieder with additional help from Jamie Hockin. Thank you for your generous help! The system has been in stable production at 2 sites in Norway since then, with very little need for support. Now, however, reports (.pgm-files) which includes date functions suddenly crash with this output: Invalid argument/mathematical expression PGM Error: Operation aborted One of the actual commands : Select year(startdate)= @rappaar On experimenting with different functions, it seems like the function no longer accepts date values. The EntryClient display dates in the format: dd.mm.yyyy, while Analysis displays dd/mm/yyyy, but this does not seem to be a problem. The report ran smoothly with data up to 2023, the same .epx datafile updated with 2024-data (about 3200 records) fails. Dataentry works fine, using EntryClient v 4.6.0.2, Menu shell and analysis runs EpiDatstat Classic 2.2.3.187 Since the problem arises in a file that used to work fine, I suspected that there must be a registration error. However,I have browsed and searched the dataset for missing or unexpected input but cannot find anything. If any of you have a hint where to look (or suggest a work-around, I would be grateful. Thank you in advance! Vegard Hoegli MD, MPH

1 3

join
by EpiData support and user community 05 Feb '25

05 Feb '25

Caution! This message was sent from outside the University of Manitoba.

1 0