>> Richard is right, but he is also wrong. Harking back to the original definitions of OOP (as in SmallTalk), defining a property and a handler for it constitutes raising and event and handling that meets all of the OOP definitions of event-raising and handling. The fact that VFP cannot raise specific kinds of events is at most ho-hum.

The original definitions of OOP and the fact that you consider my point ho-hum are completely irrelevant. The challenge was to post something that can be done in VB which cannot be done in VFP, which I have successfully done.

>>This business of "my event raising is better than your event raising" is a useless debate.

The only person engaging in any kind of debate regarding one thing being better than another is you. I simply responded to the challenge with something that Fox cannot do. This kind of mentality is something that really hurts the FoxPro community. There's such an underlying paranoia in many Fox developers heads, apparently yourself included, that they think everything is a debate. They constantly feel the need to justify the use of their tool and get so caught up in "Fox Can Do It" that they don't always look at things objectively or look at things from the perspective of choosing the right tool for the job. VB can raise COM events and VFP can't. It's simple. There's no debate. My basic opinion is so what. I didn't make any claims about VB being better than VFP or anything that even resembles that remotely. I do database work and in most cases Fox is the best tool for the job and I'll continue to use it as long as it is.

Dick