What happened to the CommandButton_Click event?

[stonward]

Evening All,

Forgive me, but this question is related to my last question...

In Access 2002 I used a simple "buttonname_Click" command to activate a button on a form from another form.

When I try this in version 2007, i get a 'Method or data member not found' error: although intellisense adds all the right capital letters etc. It fails on Compile too; the code doesn't need to be run.

Did anyone else us this command previously, and is there an equivilent now?

Thankyou for your patience,


Stonward

[Seth Schrock]

So your sub looks like the following?

Private Sub ButtonName_Click()
 
End Sub

And when you debug the code, it selects the first line?

Try going into your button's event list in the properties window and create the event through that instead of manually typing in the code.

[zmbd]

I find that all too often, I'll cut and paste a button code (usually the "close/exit" button) and it fails with that error; Because, you have to establish the "click" event first thru the properties dialog box. This does two things, it adds the "sub()" to the VBA editor that we're used to working with and it adds a pointer to the event within the collection.

[NeoPa]

My first bit of advice is to avoid doing that. Never call event procedures directly from code. A maintainer is likely to get caught out.

That said, can you show us the exact code you're trying. Without it, and without your question explaining all the details fully, we are left guessing at whether or not the reference is qualified or otherwise; whether the declaration is Public or Private (If the latter then it would never have worked of course).

[stonward]

The button on the 'main' form, cmdReset has a click event attached to it and works correctly. Looking back at what I've done before, it would seem I've called 'that' (a) buttons click event from another button on the same form, where simply entering cmdReset_Click works. I thought if I qualified everything I'd be able to do the same from another form, but doesn't look like its possible.

Interesting point about calling procedures from code NeoPa - it's the sort of thing I'm always trying! I've another question now, so hopefully I'll speak to you all again soon.

Many thanks for your help; it can be a lonely place working on these projects and having someone (other than my dog) to tell is a great help!

stonward

[TheSmileyCoder]

You can call a click event from another form BUT you need to first modify the default code

Private Sub MyButtonName_Click()
 
End sub

to change the private to public

Public Sub MyButtonName_Click()
 
End sub

This is not enough though, you now need to fully qualify the forms like so:

Call Forms!Frm_Main!MyButtonName_Click

[stonward]

Thanks TheSmileyCoder. I tried making the button event public, now going to check I've done that AND fully qualified all names.

Get back to you.

Thanks again,

Stonward

[stonward]

TheSmileyCoder: spot on - that did it...make button public, make sure everything is fully named/called in the originating code. Now my listbox updates automatically!

Super Thanks,

Stonward

[TheSmileyCoder]

Thats good to hear. Best of luck with your project.

[NeoPa]

I feel I need to repeat that fully specified external references are not a good idea when called from within the associated form's module. If a Me reference will work, then it really should be used in place of an external reference.