Moving ALL of Form's procs into Module Save Mem?

I am interested in making a program that can create tons of instances of a particular form. I do this like so:

Dim MyFormInstances() as Form1

Redim MyFormInstances(10)
Set MyFormInstances(0) = New Form1

In Form1 i have TONS of procedure calls: some my own, some "events" that i am handling. I was wondering though, if i am creating several nstances of the same form ("Form1" in this case) would each of these procedures that were inside the form1 be duplicated into each of these instances?  If so wouldnt this mean each instance would continue to use more and more memory?

If so then would it be wiser to rewrite and move ALL of my procedures (and functions) that exist in the Form1 into a Module and pass to the module's proc's/func's the Form who is requesting the information..Like this:

----
FORM1 CODE:

Public MyValue as integer

private sub FORM1_CLICK()
  'Me is VB's term for the current form -- in this case, the instance
  Call Module_FORM1_CLICK(Me)
end sub

------
MODULE CODE:

public sub Module_FORM1_CLICK(Form as Form1)
  Form.MyValue = 1
end sub

----

I would do this with EVERY procedure that existed inside FORM1. I know this wouldn't eliminate the possibilty of using more and more memory but at least (as it appears) it will reduce it significantly.  PLEASE LET ME KNOW IF THIS IS CORRECT or if Windows handles this.  Please explain in detail please.  
ljaquesAsked:
Who is Participating?
 
caraf_gCommented:
I wouldn't recommend doing what you're thinking of doing - it goes against all proper "object - oriented" design.

Just imagine the sort of trouble you're getting yourself into: you will no longer be able to access any of your form's Private variables, procedures and properties, for starters.

Even if you wanted to access your form's Public vars etc, you will have to modify each and every procedure so that you pass in an extra parameter as an object variable so that you can pass in Me when you call it from your form.

Finally, for dealing with Object type variables you are probably better off using a Collection rather than an array.

0
 
mcixCommented:
There is a certain amount of over-head associated with each instance of a form.  Memory consumption on multiple instances of a form is more dependent on the number of controls on the form rather than the underlying code.  The Code is loaded into memory as it is executed.  If you have a lot of form level variables, it could become more intensive with each new instance.

Instead of using your own array (MyFormInstances())

Try declaring a new instance like this:

Dim moForm1 As Form1
   
Set moForm1 = Forms.Add("Form1")
moForm1.Visible = True

You can then refer to the VB forms collection:

MsgBox Forms.Count
MsgBox Forms(0).Caption




0
 
ljaquesAuthor Commented:
So, by using the Collections object i can save MASSIVE amounts of memory or is it just a good way of keeping things organized?!?
0
 
caraf_gCommented:
You won't be able to save massive amounts of memory and your solution causes more problems than it will solve.

Using a collection is just a good way of keeping things organised.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.