>
>Also, now with VFPCOM, oyu can create a VFP object and bind it's events to the word object. Word only exposes 2 events, but lucky for you, one of them is close. So you can now create a class that fires your code when the user quits...

I've been trying VFPCOM BindEvents with Word and it works. I can sink the DocumentChange and Quit events from Word Application. Also, a Document Object exports 3 events, Close, New, and Open. I got the Close event to sink, but couldn't figure out the other 2 (since you can BindEvents to a document object instance only, they don't make sense by themselves). I also tried sinking both the application events and a document's events, and it looks like the application events took precedence, ie: the Application.DocumentChange event fired but not the Document.Close. And lastly, although I can release and recreate objects and re-BindEvents with no problem, calling UnBindEvents consistently causes a catastrophic failure. I tried on both Win 95 and NT, both with SP3 but not IE5, and UnBindEvents crashes every time. Probably not the end of the world since VFPCOM seems to handle things when objects are released, but could cause problems if someone wants to unbind the events without releasing the object.


Thanks

Rod Poujade
Montreal, Canada