>Why should an event have any return value? That's what methods are for. If you want to run code that returns a value to you, write a method.

In the strict sense, you are correct. However, there are occasions (actually it's a design pattern - forgot the name) where binding custom methods utilizing return values provides powerfull solutions.

>You should never write code like your example. You should always use the "2" flag of BindEvent() and then use RaiseEvent() to actually call the event.

I disagree. Circumstances very on how BindEvents is used. The code I provided was only repo code that shows a behavior change fron VFP8 - VFP9.