VB/Menus

[Emmett]

Hi,

I have a number of button-driven functions/subs that I'd like to
migrate to menu items. I have one problem however.

In a button-driven sub I would refer to a field in the current form as,
for example, 'Me.Name' or 'Me.Tel'. However this doesn't work when the
code is used in a menu. I've also tried Me!Name.

I'd appreciate to a any pointers as to how I refer to fields in the
current form in a menu.

Thanks

Emmett

[PC Datasheet]

Forms!MyForm!MyField

Note that the form must be open.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdatasheet.com
www.pcdatasheet.com
<Em****@Silico-Research.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...

Hi,

I have a number of button-driven functions/subs that I'd like to
migrate to menu items. I have one problem however.

In a button-driven sub I would refer to a field in the current form as,
for example, 'Me.Name' or 'Me.Tel'. However this doesn't work when the
code is used in a menu. I've also tried Me!Name.

I'd appreciate to a any pointers as to how I refer to fields in the
current form in a menu.

Thanks

Emmett

[Emmett Power]

That's worked great. Thanks for your help.

Regards

Emmett

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Albert D. Kallal]

99% of the time the code is in the form, so you don't have to change
anything.

The only change you need to your button code is to make it a public
Function.

So, if you have a button on the current from to print the current record,
the code would look like:
me.Refresh ' force a disk write

docmd.OpenReport "invoice",acViewPreview,,"id = " & me!id

To move the above code to a button on a custom menu, we would change the
button code to:

PrintInvoice

And, then cut and past out the code right below to:

Public Function PrintInvoice
me.Refresh ' force a disk write

docmd.OpenReport "invoice",acViewPreview,,"id = " & me!id
end function.
Then, in the menu's on-action, you simply go:

=PrintInvoice()

All of the code for the button and form SHOULD and can remain in the current
form. There is NO reason to start re-writing the actual code, and changing
references like me. to forms!YourFormname. This is simply not required at
all.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal