Using stand alone reports compared to enabler: Difference between revisions
From EnablerWiki
Jump to navigationJump to search
mNo edit summary |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Created: 30 January 2009. Last Reviewed: 30 January 2009 | |||
When configured to use Enabler for reporting. The reporting is performed by either winpos.exe or infoctrl.exe, hosted within those applications themselves. | When configured to use Enabler for reporting. The reporting is performed by either winpos.exe or infoctrl.exe, hosted within those applications themselves. | ||
Latest revision as of 23:56, 21 April 2009
Created: 30 January 2009. Last Reviewed: 30 January 2009
When configured to use Enabler for reporting. The reporting is performed by either winpos.exe or infoctrl.exe, hosted within those applications themselves.
When configured to use standalone. The reporting is performed by infenblr.exe, a dedicated windows application that does nothing but run reports.
infenblr.exe was introduced as there were issues with running reports from within POS/BO.
Both mechanisms ultimately execute the same logic etc contained within islrept.dll, so it is not like we are doing it one way for the PO/BO apps and one way for standalone. Just that the standalone application has nothing else in it, just the running of the reports.
