Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Destroying Forms.

Posted on 1997-08-10
Medium Priority
Last Modified: 2010-04-04
(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
Question by:Zonnald
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Expert Comment

ID: 1341065
Some source please. I think so you must use :  B.Free;

Expert Comment

ID: 1341066
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..."

Expert Comment

ID: 1341067
I think so when You call release the form was freed but valiable not setted to nil. try :
  B := nil;
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

LVL 14

Expert Comment

ID: 1341068
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.

Expert Comment

ID: 1341069
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.



Author Comment

ID: 1341070

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

Accepted Solution

sperling earned 100 total points
ID: 1341071
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.



Author Comment

ID: 1341072
Thanks I'll try this.


Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to create forms/units independent of other forms/units object names in a delphi project. Have you ever created a form for user input in a Delphi project and then had the need to have that same form in a other Delphi proj…
Hello everybody This Article will show you how to validate number with TEdit control, What's the TEdit control? TEdit is a standard Windows edit control on a form, it allows to user to write, read and copy/paste single line of text. Usua…
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
Suggested Courses

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question