That's really odd. I tried adding the comment, and BindEvents worked. I can bind to other event methods like QueryUnload without any code in those methods, I wonder why it only works for the destroy method when code is included in that method? Does FoxPro internally look at the object code, and decide not to issue certain events based on code existance, or does the BindEvents() call fail implicitly if you try to bind to a destroy method with no code?

At any rate, thanks for the tip

Brian Vander Plaats