Keith Furino reported this to us via the feedback mechanism and I reproduced it and submitted it on his behalf. I'm not yet sure if it is an intentional change or a bug, but it looks like a bug to me.

>There is a MAJOR bug with the just released VFP9 with respect to BINDEVENTS.
>
>The return value is always that of the event source and never that of the delegate no matter what the flag setting.
>
>Steps to reproduce:
>
>

>*-- Class:        cntevent (c:\program files\microsoft visual foxpro 9\class1.vcx)
>*-- ParentClass:  container
>*-- BaseClass:    container
>*-- Time Stamp:   12/22/04 08:50:04 PM
>
>DEFINE CLASS cntevent AS container
>       Name = "cntevent"
>
>       PROCEDURE dothisthing
>      	 LPARAMETERS tcThing
>       ENDPROC
>ENDDEFINE
>
>*-- Class:        cnthandler (c:\program files\microsoft visual foxpro 9\class1.vcx)
>*-- ParentClass:  container
>*-- BaseClass:    container
>*-- Time Stamp:   12/22/04 08:51:12 PM
>
>DEFINE CLASS cnthandler AS container
>       PROCEDURE dothisthing
>	 LPARAMETERS tcThing
>	 RETURN .F.
>       ENDPROC
>ENDDEFINE
>
>oevent = NEWOBJECT([cntevent],[c:\program files\microsoft visual foxpro 9\class1.vcx])
>ohandler = NEWOBJECT([cnthandler],[c:\program files\microsoft visual foxpro 9\class1.vcx])
>BINDEVENT(oevent,[dothisthing],ohandler,[dothisthing],1)
>
>?oevent.dothisthing()
>
>Always returns .T. no matter how the flag is set.
>
>

>
>This is a GIANT show stopper.
>
>We have used BINDEVENTS extensively in a new innovative framework using VFP8. We will not be upgrading (nor will we upgrade ours clients) to VFP9 until this gets fixed.