>I'll extend that here to say that there are situations where you should use RaiseEvent() to make an event fire, but that's something different entirely.

There may be things I don't know about VFP's execution engine. It's the only reason I can think to not put code in an event and call it explicitly.

In Visual FreePro, Jr. I added a flag to indicate if the call into the event comes from an event firing, or an explicit function call, and the two work slightly differently internally, but identically from the developer's point of view.