> > Okay, just thought of this, but maybe similar to using an

> > 'object factory' to create objects, a 'bindevents factory'

> > can handle bindevents. The object factory (if I'm using the

> > term correctly) maintains a cursor of currently active

> > objects. Similarly, the bindevents factory can maintain a

> > cursor all active bindevents, and that way Joe can have

> > diagnostics showing all current objects and active bindevents

> > (viewable in a separate diags screen, of course). Be a good

> > reminder they are active in the system.

> >

> You off-course can provide in a tool thet uses the Sys(1270)

> and the AEVENTS(laBind, oObject) to provide Joe in a method

> of 'reading' which methods are delegated to others.

Hi Sietse,

True, but by using a 'control point' other information can be collected

as well, such as who issued the bindevents, when, and perhaps even why.

Bill

> Sietse

>