Destroying Forms.

(A) and (B) are two forms.

I have been using createnew to create a form (B) just before the call to its (B) Show method.  When the form  (B) is closed I then call form(B).release method upon returning to the calling form (A).

I find, by using the 'UBEAUT' new IDE enhancement in DELPHI 3, that the db components (table, datasource,query) have not been freed (as they report as a pointer - not NIL).  This of course means that the form (B) cannot then be freed.

So in the form (B) I have included calls to the various db component's Destroy methods.  I had hoped that this would allow the form (B) to *DIE*.  No such luck.

Next time I need to open this form (B) I check if it is NIL and  if so recreate it.  But it is not NIL so I attempt to access a component (such as a label for changing the forms title or what ever) and BANG the label has a NIL pointer and therefor causes a ACCESS VIOLATION and messes up the application.

Of course one could just leave the form 'ALIVE' until the next time it is needed but this application has some 30 forms and uses  25%-40% of system resources.  I would like to know if it is normal for responsible PC programmers to want to uses a few resource at any one time as possible by  destorying invisible forms or have I spend too much time over the years programming on machines with < 1meg or memory
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Some source please. I think so you must use :  B.Free;
this is from Delphi help, so i think that you play more with source.

"..The CreateNew method creates a new instance of the current form type without reading any state information from resource files or .DFM files. The form is blank, with no controls and all properties at their default. It can be used in place of Create to bypass loading of the associated form file..."
I think so when You call release the form was freed but valiable not setted to nil. try :
  B := nil;
Amazon Web Services

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

Why are you sure that they aren't freed? Pointers usually aren't set to NIL when memory is freed, so this may be your problem.
You are calling the Show-methode so the form is modeless, right?
You can't call free, release etc. because you don't know when the form is closed.
You must write this statement in B's FormClose-event:

Action := caFree;

This will free the form from meory and release all of B's controls/components.


ZonnaldAuthor Commented:

The form is modal an I have tried caFree.

With regard to AvonWyss' comment - if it isn't NIL how does one know whether or not it need to be recreated.

Anyway I think that maybe **Win95** may actually be at fault (but don't tell BILL)

I know it is not free as I check using the WATCHES and various other neat debugging tools

Thanks again
I think you've misunderstood Delphi objects a bit, therefore I try submitting this as an answer.

  Form1, Form2 : TForm1;

Form1 := nil;
Form1 := TForm1.Create;  
Form2 := Form1;          

This probably illustrates the problem...

The compiler cannot know how many variables you have pointing to the actual TForm1 instance unless full garbage-collection is implemented. Delphi does not implement garbage-collection for objects, as that would slow everything down quite a bit.

You need to explicitly set Form1 := nil after you've freed it.


procedure TForm1.SomeEvent...
  Form1 := nil;

This is perfectly legal, as the variable Form1 is simply a pointer to the TForm1 instance. An instance doesn't need to have anything pointing to it, therefore you can e.g. do this

with TForm1.Create(Self) do begin

The fact that you get an access violation when accessing properties/fields of the form indicates that the form is actually freed, and that Form1 points to unallocated memory.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ZonnaldAuthor Commented:
Thanks I'll try this.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.