>>My forms, which used to release just fine in VFP6 no longer do so. I can't tell where it's happening at this stage. It's as if there's a new unreleased object bound to the form that I don't know about (but my base class code is unchanged).
>>I you click on the forms close box the close button becomes disabled, whereas in VFP6 the release/queryunload etc would fire and shutdown the form.
>>Also if I programmatically release the form, that fails too, with out error. If I then shutdown the app I get a C000..05 error on doing a "clear all".
>>
>>Sure, I have lots of code in my base classes for queryunload, release, destroy etc but no idea where to look yet.
>>
>>Anybody found anything similar?
>
>My guess is a dangling object reference as you have said. Best best is to fire up the debugger in both methods and poke around in the LOCALS window for objects that aren't being released. Release them explicitly in code if you have to.
Hmmm... that's the problem, I can't find any. And the absolutely identical code works in VFP6. Maybe, VFP7 is more thorough in this regard - I normally clean up objects (eg arrays of objects) in the destroy event. Perhaps that is too late now. Anyway I'll start hacking out components of my base class system. :-(
I bet I find something very interesting.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only