Hi there,

I am having trouble referencing form objects in my custom-defined sub routine.


- In the calling statement, I pass the form as 'Me'; defining it as 'thisForm
As Form' in the custom sub's argument list. This is recognised in my
subroutine and is not a problem.

- In the calling statement, I also pass a reference to a button control on
this form as a subsequent argument. In this instance, I pass the control as
'Me!btnOpenReport'; and define it as 'strButtonName As String' in the custom
sub's argument list.

- When I then try to manipulate Me!btnOpenReport's properties from within my
custom subroutine, eg. via 'thisForm!strButtonName.enabled = False', I
receive the following error..

Run-time error '2465':

Microsoft Office Access can't find the field 'strButtonName' referred to in
your expression.

I expect I should not pass the button reference as a string but cannot figure
out the correct syntax. Can anyone help?

--
Message posted via http://www.accessmonster.com

Declare the button as a control. Something like this:

sub Example (Thisform as form, Button as control)
Button.enabled=false
end sub

Call the sub like this:
Call Example (Me, NameOfTheButton)

--
Gerwin Berentschot
(E-Mail Removed).(nospam)
Mr. Access - Access development and training



"every1luvsVB via AccessMonster.com" wrote:

> Hi there,
>
> I am having trouble referencing form objects in my custom-defined sub routine.
>
>
> - In the calling statement, I pass the form as 'Me'; defining it as 'thisForm
> As Form' in the custom sub's argument list. This is recognised in my
> subroutine and is not a problem.
>
> - In the calling statement, I also pass a reference to a button control on
> this form as a subsequent argument. In this instance, I pass the control as
> 'Me!btnOpenReport'; and define it as 'strButtonName As String' in the custom
> sub's argument list.
>
> - When I then try to manipulate Me!btnOpenReport's properties from within my
> custom subroutine, eg. via 'thisForm!strButtonName.enabled = False', I
> receive the following error..
>
> Run-time error '2465':
>
> Microsoft Office Access can't find the field 'strButtonName' referred to in
> your expression.
>
> I expect I should not pass the button reference as a string but cannot figure
> out the correct syntax. Can anyone help?
>
> --
> Message posted via http://www.accessmonster.com
>
>

"every1luvsVB via AccessMonster.com" <u18005@uwe> wrote in message
news:6ba6991e03231@uwe
> Hi there,
>
> I am having trouble referencing form objects in my custom-defined sub
> routine.
>
>
> - In the calling statement, I pass the form as 'Me'; defining it as
> 'thisForm As Form' in the custom sub's argument list. This is
> recognised in my subroutine and is not a problem.
>
> - In the calling statement, I also pass a reference to a button
> control on this form as a subsequent argument. In this instance, I
> pass the control as 'Me!btnOpenReport'; and define it as
> 'strButtonName As String' in the custom sub's argument list.
>
> - When I then try to manipulate Me!btnOpenReport's properties from
> within my custom subroutine, eg. via 'thisForm!strButtonName.enabled
> = False', I receive the following error..
>
> Run-time error '2465':
>
> Microsoft Office Access can't find the field 'strButtonName' referred
> to in your expression.
>
> I expect I should not pass the button reference as a string but
> cannot figure out the correct syntax. Can anyone help?

You're right. You shouldn't be defining the argument as a string.
Instead, define it as one of the following

Access.CommandButton
Access.Control
Object

(listed in descending order of specificity). I would use the first one,
by preference, as that will give you the intellisense dropdown for the
properties and methods that apply specifically to the CommandButton
control.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

every1luvsVB via AccessMonster.com wrote:
>- In the calling statement, I pass the form as 'Me'; defining it as 'thisForm
>As Form' in the custom sub's argument list. This is recognised in my
>subroutine and is not a problem.
>
>- In the calling statement, I also pass a reference to a button control on
>this form as a subsequent argument. In this instance, I pass the control as
>'Me!btnOpenReport'; and define it as 'strButtonName As String' in the custom
>sub's argument list.
>
>- When I then try to manipulate Me!btnOpenReport's properties from within my
>custom subroutine, eg. via 'thisForm!strButtonName.enabled = False', I
>receive the following error..
>
>Run-time error '2465':
>
>Microsoft Office Access can't find the field 'strButtonName' referred to in
>your expression.
>
>I expect I should not pass the button reference as a string but cannot figure
>out the correct syntax. Can anyone help?


If you call the procedure with a control reference AND the
procedure is declared as a value variable, then the
control's Value is passed as the argument. If you intended
to pass the name of the control, then you need to explicitly
use the control's Name property.

proc Me, Me!btnOpenReport.Name

but that passes the identical string as:

proc Me, "btnOpenReport"

In either of those cases, the procedure would use the
arguments this way:

thisForm(strButtonName).Enabled = False

With that explanation of your problem out of the way, I
suggest that if the form object is not used for other
things, it is usually better to declare the procedure as:

Sub myproc(ctl As Control)

and use this:

ctl.Enabled = False

--
Marsh
MVP [MS Access]

Guys,

Thanks heaps for the advice. The Control declaration works. And Marshall;
very good point; I do not need to pass the form reference at all to achieve
what I need to achieve.

Thanks for all your help!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...oding/200701/1

Hi All,

I am trying to achieve a similar thing here, passing a reference to a
control to a subroutine. Following the logic in code of:

call subMySub ("ThisControl")

or

call subMySub (ThisControl.Name)

Private Sub subMySub (ctrl as Control)

ctrl.enabled = false

End Sub

I get a type mismatch when calling the sub. Have I missed something?


Thanks

swas


"Marshall Barton" wrote:

> every1luvsVB via AccessMonster.com wrote:
> >- In the calling statement, I pass the form as 'Me'; defining it as 'thisForm
> >As Form' in the custom sub's argument list. This is recognised in my
> >subroutine and is not a problem.
> >
> >- In the calling statement, I also pass a reference to a button control on
> >this form as a subsequent argument. In this instance, I pass the control as
> >'Me!btnOpenReport'; and define it as 'strButtonName As String' in the custom
> >sub's argument list.
> >
> >- When I then try to manipulate Me!btnOpenReport's properties from within my
> >custom subroutine, eg. via 'thisForm!strButtonName.enabled = False', I
> >receive the following error..
> >
> >Run-time error '2465':
> >
> >Microsoft Office Access can't find the field 'strButtonName' referred to in
> >your expression.
> >
> >I expect I should not pass the button reference as a string but cannot figure
> >out the correct syntax. Can anyone help?
>
>
> If you call the procedure with a control reference AND the
> procedure is declared as a value variable, then the
> control's Value is passed as the argument. If you intended
> to pass the name of the control, then you need to explicitly
> use the control's Name property.
>
> proc Me, Me!btnOpenReport.Name
>
> but that passes the identical string as:
>
> proc Me, "btnOpenReport"
>
> In either of those cases, the procedure would use the
> arguments this way:
>
> thisForm(strButtonName).Enabled = False
>
> With that explanation of your problem out of the way, I
> suggest that if the form object is not used for other
> things, it is usually better to declare the procedure as:
>
> Sub myproc(ctl As Control)
>
> and use this:
>
> ctl.Enabled = False
>
> --
> Marsh
> MVP [MS Access]
>

In news:C2779CEF-CB3C-4552-B9F3-(E-Mail Removed),
swas <(E-Mail Removed)> wrote:
> Hi All,
>
> I am trying to achieve a similar thing here, passing a reference to a
> control to a subroutine. Following the logic in code of:
>
> call subMySub ("ThisControl")
>
> or
>
> call subMySub (ThisControl.Name)
>
> Private Sub subMySub (ctrl as Control)
>
> ctrl.enabled = false
>
> End Sub
>
> I get a type mismatch when calling the sub. Have I missed something?

Either:

Call subMySub("ThisControl")

...

Private Sub subMySub(ControlName As String)

Me.Controls(ControlName).Enabled = False

End Sub

Or:

Call subMySub(ThisControl)

...

Private Sub subMySub(ctrl as Control)

ctrl.Enabled = False

End Sub

In other words, either pass the name of the control and use that name
as a string index into the Controls collection, or pass an object
reference to the control itself. Don't mic the two.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Thanks Dirk.

I should have known better.


swas

"Dirk Goldgar" wrote:

> In news:C2779CEF-CB3C-4552-B9F3-(E-Mail Removed),
> swas <(E-Mail Removed)> wrote:
> > Hi All,
> >
> > I am trying to achieve a similar thing here, passing a reference to a
> > control to a subroutine. Following the logic in code of:
> >
> > call subMySub ("ThisControl")
> >
> > or
> >
> > call subMySub (ThisControl.Name)
> >
> > Private Sub subMySub (ctrl as Control)
> >
> > ctrl.enabled = false
> >
> > End Sub
> >
> > I get a type mismatch when calling the sub. Have I missed something?
>
> Either:
>
> Call subMySub("ThisControl")
>
> ...
>
> Private Sub subMySub(ControlName As String)
>
> Me.Controls(ControlName).Enabled = False
>
> End Sub
>
> Or:
>
> Call subMySub(ThisControl)
>
> ...
>
> Private Sub subMySub(ctrl as Control)
>
> ctrl.Enabled = False
>
> End Sub
>
> In other words, either pass the name of the control and use that name
> as a string index into the Controls collection, or pass an object
> reference to the control itself. Don't mic the two.
>
> --
> Dirk Goldgar, MS Access MVP
> www.datagnostics.com
>
> (please reply to the newsgroup)
>
>
>

How can the current control on a form be passed to a subroutine? For example,
in the form.dirty event:

call subMySub(<Selected form control>)

Sorry but still getting over this one... I understand directly passing a
single control as explained below though.

swas

"Dirk Goldgar" wrote:

> In news:C2779CEF-CB3C-4552-B9F3-(E-Mail Removed),
> swas <(E-Mail Removed)> wrote:
> > Hi All,
> >
> > I am trying to achieve a similar thing here, passing a reference to a
> > control to a subroutine. Following the logic in code of:
> >
> > call subMySub ("ThisControl")
> >
> > or
> >
> > call subMySub (ThisControl.Name)
> >
> > Private Sub subMySub (ctrl as Control)
> >
> > ctrl.enabled = false
> >
> > End Sub
> >
> > I get a type mismatch when calling the sub. Have I missed something?
>
> Either:
>
> Call subMySub("ThisControl")
>
> ...
>
> Private Sub subMySub(ControlName As String)
>
> Me.Controls(ControlName).Enabled = False
>
> End Sub
>
> Or:
>
> Call subMySub(ThisControl)
>
> ...
>
> Private Sub subMySub(ctrl as Control)
>
> ctrl.Enabled = False
>
> End Sub
>
> In other words, either pass the name of the control and use that name
> as a string index into the Controls collection, or pass an object
> reference to the control itself. Don't mic the two.
>
> --
> Dirk Goldgar, MS Access MVP
> www.datagnostics.com
>
> (please reply to the newsgroup)
>
>
>

hi,

swas wrote:
> How can the current control on a form be passed to a subroutine? For example,
> in the form.dirty event:
You may use Screen.ActiveControl, but i assume you mean somthing like that:

Private Sub cmdButton_Click()

subMySub cmdButton

End Sub

In the case of referencing the calling control, you have to hard code it.

When you need it very often, you may take a look at mztools.com. This
VBA plugin has a some template functions.


mfG
--> stefan <--