>>I'm trying to adapt a previously-constructed form to use a custom object for some of its functionality. It's been like juggling chainsaws under fire - you've got a 100% chance of injury. Anyway, if any of the custom object's methods get called, the form lodges in memory and won't destroy.
>
>Do you add this object to the form as an object, or store it in a property? Make sure to .NULL. it if its in a property in your Destroy()
I was doing neither. In the form designer, I had simply added it as another object. That was probably the mistake. Heck, I don't even normally do that, but it worked fine in a prototype.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
