General information
Category:
Reports & Report designer
Title:
Report Listener Strategy?
Environment versions
Network:
Windows 2008 Server
I'm just now seriously getting into using report listeners. Have read
the excellent writeups by Cathy Pountney, Doug Hennig, the
Nichollses and others. I would like to know if the following
approach to implementing listeners could create potential problems:
(1) Add an oLeadListener property to my abstract listener class.
(2) In the Init, set oLeadListener = This and have an assign
method that propagates the reference to all of the successor
listeners in the chain.
(3) Any pre- Render and post-Render changes done by the lead
and/or the successor listeners are implemented on the lead listener.
(4) The lead listener's Render is the one that is called. Add an
lRender switch to the abstract listener class in case there is
ever a situation where a different (or more than one) listener's
Render needs to be called.
Seems to me that would be a simpler approach than trying to
make sure that everything is properly shared by propagating
downward through the successor chain.
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only