[AccessD] Interface Callback Class Questions.

Robert,

Oh, now you're getting greedy! ;-)

The report object can't sink section events. Likely, you'd have to invent a
section class that sinks section events. You'd need to make a collection of
Section objects for all the sections used in your report, and have them hook
the OnPrint or OnFormat events for their individual section.

The collection would be maintained in your Report object, so its
responsibilities would expand to hooking report events, setting up the
section collection, having them hook their section events, and possibly
servicing the section object requests.

-Ken

-----Original Message-----
From: Robert Gracie [mailto:Subscriptions at servicexp.com]
Sent: Thursday, January 29, 2004 8:17 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Interface Callback Class Questions.


Ken,
 Thanks A Million!!

 Yep the report did not have module....:-), and that solved the
problem...

 How in the world do I sink the OnPrint, or OnFormat events...

with
 mrRpt.Section(acDetail).OnPrint = pcsEventStub

I think I have tried every possible stub, and it seems like it's just
ignored....

Thanks Again!!
Robert Gracie