Re: How to kill a form
- From: Jack Jackson <jacknospam@xxxxxxxxxxxxxxx>
- Date: Wed, 18 Jul 2007 17:25:59 -0700
That can't be it.
Form references are different from other references. When a form is
released, all of the references to it are set to NULL and the form is
released.
On Wed, 18 Jul 2007 14:11:12 -0700, "Paul Pedersen" <nospam@xxxxxxx>
wrote:
Funny you should ask. I just ran into that today. It turned out (I think).
that there was a reference I didn't think of, which resulted from something
like this (in a process external to the form)
result = CloseForm(oFormRef)
PROCEDURE CloseForm
LPARAMETERS oForm
oForm.release
The remaining reference is in the calling proc (oFormRef).
This doesn't apply directly to your situation, since like I said it's
external to the form. No thisform.release anywhere. But check again for
references you might have missed. A forms collection perhaps?
Also, a reference to any of the objects on a form will prevent the form from
closing. Check for those too.
"Ook" <zootal@xxxxxxxxx> wrote in message
news:1184792458.127647.11260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a form with nested page frames, tons of code, etc. When I
thisform.release, nothing happens. I have verified that there are no
public variables hanging around, all objects added to the form are
removed, all open tables are closed. AFAICT, I have properly cleaned
up everything that should need to be cleaned. Display Memory/Status
does not show anything that should stop the form from closing. What
else would stop a form from closing?
One thing I wish VFP had was a KillFormNowNoMatterWhatDammIt!()
function :)
- References:
- How to kill a form
- From: Ook
- Re: How to kill a form
- From: Paul Pedersen
- How to kill a form
- Prev by Date: Re: List Box
- Next by Date: Re: How to kill a form
- Previous by thread: Re: How to kill a form
- Next by thread: Re: How to kill a form
- Index(es):
Relevant Pages
|