[RESOLVED] Fire event in other form

[mutley]

Hi

How can I to fill other forms and to fire some event (click eg) in other form

Tia

[techgnome]

Same app? Different app? We'd need some details... it depends on the situation. My first reaction on reading the title is - you don't. You put what you need to call into a friend or public method and call that from the places where you need to. But then I read the post... so now the answer changes depending on what you're doing.

-tg

[mutley]

Same app? Different app? We'd need some details... it depends on the situation. My first reaction on reading the title is - you don't. You put what you need to call into a friend or public method and call that from the places where you need to. But then I read the post... so now the answer changes depending on what you're doing.

-tg

Hi thank you, is same application
I have a form A , have a grid with data , when the user change row I must to fill other form (same application ) Form B and validate data inserted by user in grid and to fire events Clicks some buttons

[techgnome]

Then do it like I mentioned... move the code you wish to execute to a firend sub and have the other form and the click event call it.

-tg

[stum]

Form1.Command1.Value = True

is what you're looking for.

if the control does not have a .value property, you can set the sub to public and call it from anywhere.

Public sub Command1_Click()
    Msgbox "i'm a button"
End Sub

Private sub Form_Load()
    Command1_Click
End Sub

[mutley]

Then do it like I mentioned... move the code you wish to execute to a firend sub and have the other form and the click event call it.

-tg

Sorry, but I did not understand

I have a Form A and Form B

In Form A I put a call sub (procedure) inside Form B

In Form B in Event (s) I build a call to Sub ?

[techgnome]

In form B:

Private sub SomeObject_Click)
  MyClickHandler() 'That is all...
End Sub

public Sub MyClickHandler()
' do the stuff you would have put in the click event above
End Sub

From Form A:

FormB.MyClickHandler() 'Simple as that

-tg

[techgnome]

Form1.Command1.Value = True

is what you're looking for.

if the control does not have a .value property, you can set the sub to public and call it from anywhere.

Public sub Command1_Click()
    Msgbox "i'm a button"
End Sub

Private sub Form_Load()
    Command1_Click
End Sub

While that's OK for some controls and events, personally I think it's a bad habit to get into. There can be unintended consequences. Especially the moment you decide that click event needs to also do something else, forgetting it's called from other locations where you DON'T want that second action to take place... Been there done that, got a collection of t-shirts. That's why the moment I find that event code needs to be called by a process outside the event, I move it to it's own dedicated sub and refactor as needed.

-tg

[stum]

I long ago stopped asking one-question-users the Why and focus more on the How, knowing that most of them likely will only come back to see a solution.
regarding this specific topic, in my personal opinion, placing a shared function on a module or a class would be a far more superior approach than calling it directly from the form.
may it be noted that in general, i'm against public code-snippets wondering on forms, from the get-go.

[mutley]

While that's OK for some controls and events, personally I think it's a bad habit to get into. There can be unintended consequences. Especially the moment you decide that click event needs to also do something else, forgetting it's called from other locations where you DON'T want that second action to take place... Been there done that, got a collection of t-shirts. That's why the moment I find that event code needs to be called by a process outside the event, I move it to it's own dedicated sub and refactor as needed.



-tg

Thank you , I believe worked

[LaVolpe]

Also be aware that calling events in other forms can load the form if it was previously unloaded. This can result in your app staying loaded when your user closes the app because that now-loaded form was never unloaded.