Fabio,
While not definitive, I believe this to be by design. If you're bound to an object, all code associated with that object, both direct and bound, should occur within the context of the bound object.

Why would you want bound code to execute in its own context and not in its "parent" context?

>Hi,
>
>On VFP a object is binded to a datasession;
>when you call a object procedure,
>VFP set the current datasession to the binded datasession.
>
>Problem: BINDEVENT not respect this rule.
>
>When VFP call a delegate procedure, datasession not change.
>
>1. I haven't found documentation for this behaviour
>
>2. Is this behaviour by design ?