Public procedures in a Form are not visable to other Modules ?

[Harry J. Smith]

In my program VPCalc, Public procedures in a Form are not visible to
other Modules.
Is this how it should be?

-Harry http://home.netcom.com/~hjsmith

[J French]

On Wed, 07 Jan 2004 22:44:16 GMT, "Harry J. Smith"
<hj*****@ix.netcom.com> wrote:

In my program VPCalc, Public procedures in a Form are not visible to
other Modules.
Is this how it should be?

Form1.MyProc

[Dikkie Dik]

J French wrote:

On Wed, 07 Jan 2004 22:44:16 GMT, "Harry J. Smith"
<hj*****@ix.netcom.com> wrote:

In my program VPCalc, Public procedures in a Form are not visible to
other Modules.
Is this how it should be?

Form1.MyProc

Well, yes and no.

They should be public and they probably are: they are public methods of
any instance of the form. So if you have defined a variable as the the
type of your form (supposing is is called "Form1" here):

dim frm as Form1 ' every form definition has its own type
set frm=new Form1 ' create a new instance. You could also get it out
' of the Forms collection
frm.VPcalc ' When you type the dot, VPcalc should be in the
' autocomplete list, as it is public.

Best regards,
Dikkie Dik

[Harry J. Smith]

"Dikkie Dik" <Ab***@SpamBusters.com> wrote in message
news:3f***********************@dreader-2.news.scarlet-internet.nl...

J French wrote:

On Wed, 07 Jan 2004 22:44:16 GMT, "Harry J. Smith"
<hj*****@ix.netcom.com> wrote:

In my program VPCalc, Public procedures in a Form are not visible to
other Modules.
Is this how it should be?

Form1.MyProc

Well, yes and no.

They should be public and they probably are: they are public methods

of any instance of the form. So if you have defined a variable as the the
type of your form (supposing is is called "Form1" here):

dim frm as Form1 ' every form definition has its own type
set frm=new Form1 ' create a new instance. You could also get it out
' of the Forms collection
frm.VPcalc ' When you type the dot, VPcalc should be in the
' autocomplete list, as it is public.

Best regards,
Dikkie Dik

Thanks, this works great.

First I found that after the new instance of the form, you can ignore
the frm variable:

dim frm as Form1
set frm=new Form1 'Bring up Form1
Set frm = Nothing 'No longer need frm
Form1.VPCalc 'Call the Sub VPCalc

Then I removed the first three lines and the form came up anyway:

Form1.VPCalc 'Call the Sub VPCalc

I tried doing the first two lines by themselves and the form did not
come up. They appear to do nothing but set frm which is not needed.

I will just do the one-liner and be happy I have a solution.

-Harry

[Steve Gerrard]

"Harry J. Smith" <hj*****@ix.netcom.com> wrote in message
news:Wl**************@newsread1.news.pas.earthlink .net...

First I found that after the new instance of the form, you can ignore
the frm variable:

dim frm as Form1
set frm=new Form1 'Bring up Form1
Set frm = Nothing 'No longer need frm
Form1.VPCalc 'Call the Sub VPCalc

Then I removed the first three lines and the form came up anyway:

Form1.VPCalc 'Call the Sub VPCalc

I tried doing the first two lines by themselves and the form did not
come up. They appear to do nothing but set frm which is not needed.

I will just do the one-liner and be happy I have a solution.

-Harry

When you use Form1.VPCalc, you are using the "implied" instance variable
in VB. This works fine in applications where forms are not frequently
loaded and unloaded.

The other approach is to declare and manage your own instance variables,
as was illustrated. The complete sequence would be:
Dim frm as Form1
Set frm = New Form1
frm.VPCalc
frm.Show

This is mainly an advantage when you need to keep track of more than
one form instance, or want to run VPCalc before showing the form, or
need to manage forms in other ways.

[Harry J. Smith]

"Steve Gerrard" <no*************@comcast.net> wrote in message
news:Z6********************@comcast.com...

"Harry J. Smith" <hj*****@ix.netcom.com> wrote in message
news:Wl**************@newsread1.news.pas.earthlink .net...

First I found that after the new instance of the form, you can ignore the frm variable:

dim frm as Form1
set frm=new Form1 'Bring up Form1
Set frm = Nothing 'No longer need frm
Form1.VPCalc 'Call the Sub VPCalc

Then I removed the first three lines and the form came up anyway:

Form1.VPCalc 'Call the Sub VPCalc

I tried doing the first two lines by themselves and the form did not
come up. They appear to do nothing but set frm which is not needed.

I will just do the one-liner and be happy I have a solution.

-Harry
When you use Form1.VPCalc, you are using the "implied" instance

variable in VB. This works fine in applications where forms are not frequently
loaded and unloaded.

The other approach is to declare and manage your own instance variables, as was illustrated. The complete sequence would be:
Dim frm as Form1
Set frm = New Form1
frm.VPCalc
frm.Show

This is mainly an advantage when you need to keep track of more than
one form instance, or want to run VPCalc before showing the form, or
need to manage forms in other ways.

Right, I have seven forms in my application. Only one needs to have more
than one copy up at the same time. I now use the simple method for all
of the forms but this special one. If I use the simple method for this
one, when you bring up a second copy the first copy goes away.

-Harry

[Steve Gerrard]

"Harry J. Smith" <hj*****@ix.netcom.com> wrote in message
news:I9***************@newsread1.news.pas.earthlin k.net...

Right, I have seven forms in my application. Only one needs to have more than one copy up at the same time. I now use the simple method for all
of the forms but this special one.
That seems very sensible.
If I use the simple method for this
one, when you bring up a second copy the first copy goes away.

That seems odd. Maybe they are just on top of each other? You should in
principle be able to use Form1 (the implied instance) and frm (the
declared instance) and have two, although most programmers would at this
point just declare two (say frmA and frmB) and not use Form1 at all.

[Harry J. Smith]

"Steve Gerrard" <no*************@comcast.net> wrote in message
news:Rv********************@comcast.com...

"Harry J. Smith" <hj*****@ix.netcom.com> wrote in message
news:I9***************@newsread1.news.pas.earthlin k.net...

Right, I have seven forms in my application. Only one needs to have more

than one copy up at the same time. I now use the simple method for all of the forms but this special one.

That seems very sensible.

If I use the simple method for this
one, when you bring up a second copy the first copy goes away.

That seems odd. Maybe they are just on top of each other? You should

in principle be able to use Form1 (the implied instance) and frm (the
declared instance) and have two, although most programmers would at this point just declare two (say frmA and frmB) and not use Form1 at all.

You’re probably not THAT interested, but I put the compiled version of
the program and all of the source code on my web site. They can be
downloaded from:

http://www.geocities.com/hjsmith_geo...ad.html#VPCalc

-Harry