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
Caution! This message was sent from outside the University of Manitoba.
Interesting error, Vegard
Please see a mail I have sent you directly
Bw Jens Lauritsen
Hent BlueMail til Androidhttps://bluemail.me Den 5. feb. 2025, fra 22.47, EpiData support and user community <epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca> skrev:
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.mmhttp://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.2http://4.6.0.2, Menu shell and analysis runs EpiDatstat Classic 2.2.3.187http://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
________________________________
EpiData-list mailing list -- epidata-list@lists.umanitoba.ca To unsubscribe send an email to epidata-list-leave@lists.umanitoba.ca
Caution! This message was sent from outside the University of Manitoba.
Possibly this was due to about 10 date errors in the data, eg 01/08/0024. EpiData classic is not strong on "obscure" dates.
Vegard will report if the problem was solved by finding this in the data, which I received encrypted.
My strategy was finally A. Read the epx file into modern analysis B. Calculate x as difference of inn and outdate C. Browse records where x was negative or larger than 100 D. Look at dates and find the correct year E. Manually edit the data F. Compare with previous data (duplicate entry test ) in manager (or new analysis G. That is all - ready to test the menu system again.
(After about two hours of various thoughts and attempts)
Best wishes Jens Lauritsen EpiData Association
Hent BlueMail til Androidhttps://bluemail.me Den 6. feb. 2025, fra 12.32, EpiData support and user community <epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca> skrev:
Caution! This message was sent from outside the University of Manitoba.
Interesting error, Vegard
Please see a mail I have sent you directly
Bw Jens Lauritsen
Hent BlueMail til Androidhttps://bluemail.me Den 5. feb. 2025, fra 22.47, EpiData support and user community <epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca> skrev:
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.mmhttp://dd.mmhttp://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.2http://4.6.0.2http://4.6.0.2, Menu shell and analysis runs EpiDatstat Classic 2.2.3.187http://2.2.3.187http://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
________________________________
EpiData-list mailing list -- epidata-list@lists.umanitoba.ca To unsubscribe send an email to epidata-list-leave@lists.umanitoba.ca ________________________________
EpiData-list mailing list -- epidata-list@lists.umanitoba.ca To unsubscribe send an email to epidata-list-leave@lists.umanitoba.ca
Caution! This message was sent from outside the University of Manitoba.
Thanks to Jens for helping me out.
Lesson learnt from this: 1. The data are entered with Entryclient v 4.6.0.2 with the constraint on variable "outdate" >="indate". When the operator uses the <Enter> key to navigate, they cannot continue if the condition is not met. However, they can still continue if they use the mouse to navigate to the next input field! 2. The variable "length of stay" is calculated and displayed in the entry client. Due to the possible error above, this is risky business. I think it would be safer to avoid calculated fields in such a system, and do all the calculations in Analysis
Best Regards, Vegard Hoegli MD, MPH
7. feb. 2025 kl. 01:23 skrev EpiData support and user community <epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca>:
Caution! This message was sent from outside the University of Manitoba.
Possibly this was due to about 10 date errors in the data, eg 01/08/0024. EpiData classic is not strong on "obscure" dates.
Vegard will report if the problem was solved by finding this in the data, which I received encrypted.
My strategy was finally A. Read the epx file into modern analysis B. Calculate x as difference of inn and outdate C. Browse records where x was negative or larger than 100 D. Look at dates and find the correct year E. Manually edit the data F. Compare with previous data (duplicate entry test ) in manager (or new analysis G. That is all - ready to test the menu system again.
(After about two hours of various thoughts and attempts)
Best wishes Jens Lauritsen EpiData Association
Hent BlueMail til Androidhttps://bluemail.me Den 6. feb. 2025, fra 12.32, EpiData support and user community <epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca<mailto:epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca>> skrev:
Caution! This message was sent from outside the University of Manitoba.
Interesting error, Vegard
Please see a mail I have sent you directly
Bw Jens Lauritsen
Hent BlueMail til Androidhttps://bluemail.me Den 5. feb. 2025, fra 22.47, EpiData support and user community <epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca<mailto:epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca>> skrev:
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.mmhttp://dd.mmhttp://dd.mmhttp://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.2http://4.6.0.2http://4.6.0.2, Menu shell and analysis runs EpiDatstat Classic 2.2.3.187http://2.2.3.187http://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
________________________________
EpiData-list mailing list -- epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca To unsubscribe send an email to epidata-list-leave@lists.umanitoba.camailto:epidata-list-leave@lists.umanitoba.ca ________________________________
EpiData-list mailing list -- epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca To unsubscribe send an email to epidata-list-leave@lists.umanitoba.camailto:epidata-list-leave@lists.umanitoba.ca _______________________________________________ EpiData-list mailing list -- epidata-list@lists.umanitoba.camailto:epidata-list@lists.umanitoba.ca To unsubscribe send an email to epidata-list-leave@lists.umanitoba.camailto:epidata-list-leave@lists.umanitoba.ca
participants (1)
-
EpiData support and user community